submitted 7 months ago by flor0@sh.itjust.works to c/selfhosted@lemmy.world

26 comments fedilink hide all child comments

For years I've been running my Nextcloud on bare metal. Now I finally decided to switch it to docker. I looked into Nextcloud All-In-One and it seems easy to deploy but it lacks configuration options like multiple domain names and putting it behind a traefik reverse proxy is kind of a pain to set up.

You can check out my solution on GitHub. I decided on a docker compose setup with nginx, php-fpm and redis(redis is now replaced by KeyDB) in separate containers. Obviously it's for experts but it's a lot more configurable. than AIO. It's also just as easy to migrate to as with any bare metal setup and just as configurable.Yes it's still a pain to set up, but better than the bare metal version lol

What do you guys think about putting the different components (webserver, php, redis, etc.) in separate containers like this, as compared to all in one? Feedback is greatly appreciated!

you are viewing a single comment's thread
view the rest of the comments

[-] ilmagico@lemmy.world 3 points 7 months ago

Well, since we want to be technical ... Docker is not bare metal. Linux apps are not bare metal. Arduino is bare metal.

[-] atzanteol@sh.itjust.works 1 points 7 months ago

No. The phrase means that you're not running in a virtual machine.

[-] ilmagico@lemmy.world 3 points 7 months ago

That's only the meaning you're used to, and that's my point. It depends on the context. I can assure you that, in the context of microcontrollers, for example, "bare metal" means running without an OS.

[-] atzanteol@sh.itjust.works 1 points 7 months ago

Either way its pretty stupid to use it in reference to containers.

[-] ilmagico@lemmy.world 2 points 7 months ago

My point is, since its meaning depends on the context, I don't see the issue for it to mean, in the context of containers, "outside of a container". Just like in the case of VMs, or OS vs No OS, it means there's one fewer layer between the app and the hardware, whether that's a VM, Container runtime, or the OS.

I'm pretty sure everybody, including you, understood its meaning in this context, it didn't really cause any misunderstanding.

[-] atzanteol@sh.itjust.works 1 points 7 months ago

No, it's confusing. Because some people do use VMs. So it makes it far less clear about what a person's setup is.

An application running in a container runs exactly the same as a non-container application. It uses the same kernel. And it all runs directly on the CPU. There is no metal/non-metal distinction to make. People just say it because it "sounds cool". And there are a lot of people in this community who don't understand what containers are. So it further muddies the water

this post was submitted on 06 Apr 2024

66 points (100.0% liked)

Selfhosted

40219 readers

885 users here now

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!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz