# Why Docker?

**URL:** <https://meta.discourse.org/t/why-docker/298865>\
**Category:** Self-hosting\
**Created:** [March 11, 2024, 11:42am UTC](https://meta.discourse.org/t/why-docker/298865 "2024-03-11T11:42:36Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![NullUsername](https://avatars.discourse-cdn.com/v4/letter/n/a183cd/32.png) [@NullUsername](https://meta.discourse.org/u/NullUsername)\
**Post date:** [March 11, 2024, 2:59pm UTC](https://meta.discourse.org/t/why-docker/298865/4 "2024-03-11T14:59:50Z")

</div>

> [@pfaffman](#):
>
> Because when they started developing Discourse, it was the best thing around.
> 
> If tney were to do it today, I’d guess that the only thing they’d do differently might be to use docker-compose rather than their own custom `launcher` commmand that builds and launches docker images.

I support this. `docker-compose` would be 100% better as i just watch a crash course on docker and docker-compose. It seems that if Discourse used docker-compose i would have solved this issue without the need to create a post.

`docker-compose` does all the heavy lifting similar to what the launcher does but with docker-compose i could have easily configured the network and bridge.

> [@pfaffman](#):
>
> From everything I see, most everyone who manages software on more than, say, 5 servers, is using some kind of container to manage things.

I agree. I do use containers. just pure LxC containers. No added software required. It’s not as simple as that though. For example: One of my servers i have a bronze package which is basically for developers. Cheap and easy setup. The moment a payment is confirmed the main server gets a request to create either a lxc container or VM based on the selection of the user, obviously a domain name is required or a custom sub domain will be issued for the server(lxc/vm). It also asks the user to configure their own network which then cannot be accessed by the main network and vice verse. Its basically a small AWS

> [@pfaffman](#):
>
> Increasingly developers run stuff on their laptops in containers to see that versions of everything is kept consistent.

For development docker would be exceptional for laptops and dev purposes to separate the main computer files and dev files including networks.

> [@pfaffman](#):
>
> Even managing a Discourse/rails/ember development environment on a single laptop is something of a challenge.

I cannot agree nor disagree as i have not personally developed anything with Discourse/rails/ember. thats out of my scope and if the devs say its easier i am in no place to disagree with something i do not know.

> [@pfaffman](#):
>
> That’s true. If you want a forum that you can use without Docker, you should not use Discourse.

This is my problem, I done over enough research on all available forums software and used quite a few of them.

My options all boiled down to 2 forums:

1. Discourse
2. Flarum

I choose discourse as the best forum software in all aspects and due to my only experience with docker which was Nginx Reverse Proxy Manager.

I thought all i had to do was input some of my information in the .yml file and then do `docker-compose up -d`. I was wrong.

The issue i currently have can be sorted it’s just going to take some time figuring out.  
I refuse to use Flarum because i have used Discourse on many platforms and no offence to other good forum softwares out there but Discourse is the best available forum on the market.

Maybe an upgrade to docker-compose could help 😃

---

_[View the full topic](https://meta.discourse.org/t/why-docker/298865)._