Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Okay, let's be angry at the company and frown a lot at what happened. Gurr, bad company, evil.
And now think of what you'd rather have - a working system, or a reason to be angry? If you have something that integrated with something else, lock it down at a specific version so you control the upgrade and know those versions work 100% of the time together. "Latest" is just asking for trouble - be it in a docker image, in dependencies or elsewhere. It's absolutely not a "best practice" if it isn't even a code smell or an outright bug. You could've had a slightly outdated version, which won't be "exploitable" - you wouldn't have enough time to exploit anything in that time, especially with smaller companies and obscure exploits.
Instead of putting out the fire, you could've been now looking into the upgrade, seeing on UAT or Test or whatever that forms aren't supported, chilling till they are supported or complaining that they aren't.
Upgrades breaking shit is like programming / devops 101, and a huge reason for technical debt in very old projects. Leaving all that to chance is just irressponsible.
the upgrade command is sent manually, it's not automated and it's not unattended. It would have made ZERO difference if i tagged 29 and then in test tagged 30. The upgrade would have not failed, it would have given ZERO warnings, I would have seen that everything worked as expected (because who tests the useless survey that is filled once a semester?) and I would have pushed the update to production.
Who tests the useless survey? Everyone with regression tests. Like dude, everything you talk about has been written "in blood" from years of hosting production systems. If the useless survey is needed, then write a test for it, or a testcase to manually try it. Don't just upgrade, see that the app is up and push to prod, that's not testing, that's asking for trouble.
I'm not arguing that my procedure is right (it is not), I'm arguing that nextcloud rushed the release in an incredibly unprofessional way.
When it's the last time that Canonical, in the hurry to release Ubuntu xx.yy broke snapd without?
When it's the last time that Apple, in the hurry to release iOS xx, made it totally incompatible with iMovie and had no timeline on when it would be fixed?
When it's the last time that Microsoft pushed a Windows update that disabled Microsoft office and left it unfixed for months?
Nextcloud decided to take care of the forms app. They decided to promote it as a selling point. They decided when to release the update. They decided to still push the update even if their own form app didn't get any new release in 4 months and isn't compatible.
They aren't contractually obligated to release a new, indistinguishable version (except some new bits that make it incompatible) every quarter.
Not ready? Delay one week. Still not ready? Delay an additional week. It came out that it needs a complete rewrite and it will take months? Write a note in the blog saying that feature is no more a selling point but now it is deprecated/unmaintained/unsupported and it will be automatically disabled without confirmation.
As someone said, a good app is only late until it ships, a bad app is bad until it's patched. Why being perpetually bad with updates that nobody is asking?