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
Yeah let's instead install a massive bloated shit project that the original developers left years ago and the maintainers don't know heads from tails of the codebase because it's too massive to maintain, with enough dependencies to make even a small child think he's independent by comparison.
All so that we can, uh, synchronize a markdown text file across 3 computers.
These projects exist so that we don't all have to re-invent the wheel every single time we need something simple. They have a purpose, even if they're not pushing the envelope. I've developed a bunch of software to do extremely simple things for myself because all the existing options are massive and bloated and do a million more things than I need.
I'm sure your projects look impressive on your resumé, though.
So much this. I recently had OneDev recommended to me as a forgejo alternative. I was told that it was "very lightweight." Intrigued I tried it out. It fuckin' runs java and is resource heavy as fuck. Just sitting idle it consumes almost 13% of VPS RAM: http://i.xno.dev/u/SGXxO2.png
You still have 63% RAM available in that screenshot, there are zero problems with Java using 13% RAM. It's the same as the tired old trope of "ChRoMe Is EaTiNg My MeMoRy". Unused memory is wasted memory if it can be used for caching instead, so unless you're running out of available memory, there is no problem.
Also, the JVM has a lot of options for configuring its various caches as well as when it allocates or releases memory. Maybe take a look at that first.
Edit: Apparently people don't want to hear this but don't have any actual arguments to reply with. Sorry to ruin your "JaVa BaD" party.
Sad that you're downvoted for being right.
Java apps can be memory hogs, but anything else can be too. The jvm is exceptionally performant for persistently running apps.