3 ms·
Luckily the current self-hosted version has not been much of a burden to support so far. But I do wonder if/how that might change with an alternate licensing m
by scubakid 3y ago
Luckily the current self-hosted version has not been much of a burden to support so far.
But I do wonder if/how that might change with an alternate licensing model.
In the examples you've heard about, do you recall where the most significant support costs oftened stem from?
- milesvp 3y agoI think it was dealing with the myriad different environments they could be deployed in. I’ve done a lot of sysadmin work, and I can tell you that a lot of companies just don’t have a repeatable environment. That said, my suspicion is these days, with a good container type solution, if you maintain that, and support just what’s inside that boundary, that can go a long way to mitigate calls. Of course, I love containers until they break, especially when they break because of some implied dependency changes.
- scubakid 3y agoAh, makes sense. This one is containerized and orchestrated with Docker Compose. At this point, I can barely imagine trying to create and maintain a cross-platform self-hostable product the old school way.