3 ms·
I also really dig the approach of Backstage but found maintaining the installation a real pita. They even give you a tool that tells you which lines have to be
by mdlnr 4y ago
I also really dig the approach of Backstage but found maintaining the installation a real pita. They even give you a tool that tells you which lines have to be manually updated in your installation when updating (https://backstage.github.io/upgrade-helper/ https://backstage.github.io/upgrade-helper/).
- grinnick 4y agoThis is exactly why we created https://roadie.io https://roadie.io I'm the founder.
- kenrose 4y agoAgreed. We've seen this with our customers at OpsLevel who lean away from Backstage. Installing (and updating) Backstage is painful. One of our team members who previously ran a Backstage instance at $OldJob wrote about that pain: https://www.opslevel.com/blog/hands-on-backstage-learnings https://www.opslevel.com/blog/hands-on-backstage-learnings
- prmoustache 4y agoThe problem isn't really installing backstage but integrating all the stuff around it. It is not a turnkey solution per se and what they call plugins aren't plugins in the traditionnal sense where you would just download a package and put it in a directory. It requires editing the actual react code to set most of them. So maintaining backstage involve maintaining a set of patches and a pipeline to build a docker image.