❔ 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