Still container-dependent?
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
I'm running it bare metal on my NAS.
No problems, plus I don't have to do extra container stuff.
"not running in a container" is not "running on bare metal". It's just running outside a container.
I guess that's true.
I'm running it outside of a container and outside a VM... as there's no abstraction layer on top of the underlying OS. Which I guess is inside the bare metal.
So, Yep.
"Bare metal" has traditionally meant without any os either. Your code executes directly on hardware and has direct control over everything. Like a micro controller.
Code in a container executes on the hardware in exactly my the same way as code not running in a container - with the os as an intermediary.