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.
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
For development docker would be exceptional for laptops and dev purposes to separate the main computer files and dev files including networks.
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.
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:
- Discourse
- 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 ![]()