adriensβ About
π«΅ Have you already been challenged with the following questions :
π€ Hey... What's your stack ?
π€ Is our version of
${product}still supported βπ± Since how many years are we out of support on
${product}βοΈ
βοΈ If yes... this post is for you.
As we were asking ourselves these questions, we decided to industrialize this:
- ποΈ At scale
- π§° With code and tools
- βΎοΈ As part of our
DEVOPSculture - π
data-driven(APIs, databases, quality & analysis tools...) - π§βπ€βπ§ With collaborative tools
πΏ Demo (< 30')
π Resources
π€ Further with eol
π‘ Feature request > Better markdown reports (applies to rst)
#135
β About
Currently, when asking for multiple products output in markdown eol makes a "brutal" append by looping eol on each product... and it can become tricky to find each product section while browsing the output.
The purpose of this issue to enhance that for a better UX on markdown exports.
π‘ Idea
Instead of having to manually edit the list of products eols, would it be possible to insert md sections ?
This would give the following meta code :
## `product_1`
Output from `eol product_1 --format md`
## `product_2
Output from `eol product_2 --format md`
π° Benefits
Stack examples
π Python
eol python django psql --format md > stack_pyton.md`
β
eol java maven spring-boot psql --format md > stack_java.md
