โ 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
Top comments (3)
Discussion on
endoflife.date