I’ve read threads like this and others, and it seems like to date, there’s no easy way to pop a Discourse image into something like ECS, or GKE or whatever container orchestration you like and have it work easily… I use Terraform to manage an Elasticache cluster, an RDS instance, and an ECS cluster. I just want to be able to say, “Here’s my Discourse image, and here are the environment variables to connect to Postgres, Redis, SMTP, etc.” Does anything like this exist in 2020? It seems like in all the conversations around this topic previously, no satisfying resolution was reached, and we’re still stuck with Discourse’s custom scripts that defy container conventions and break compatibility with the idiomatic way people use containers…

I replied a similar question two days ago [imagem] Looking for Production Discourse Instructions Self-hosting Yes and that is the way to go. They bought bad crystal balls to predict the future. Told em to buy better ones for the next project joy Being serious, like you asked it’s easy to save the resulting image in a container registry and deploy it afterwards using the tool you like the most. And since you can run said container using some bash scripts, puppet, chef, ansible, terraform, backed into the AMI, user-data script, docker swarm, docker compose, kubernetes, capistrano, AWS ECS or many o…

[imagem] lktmxjv: Here’s my Discourse image, and here are the environment variables to connect to Postgres, Redis, SMTP, etc. This is an incorrect assumption. All of those are elements of Discourse, and need to be controlled by Discourse within its container to guarantee successful setup. If you get into complex multiple container scenarios, that’s only necessary for large customers with lots of $, and I’d refer you to our enterprise hosting service..

[imagem] codinghorror: All of those are elements of Discourse, and need to be controlled by Discourse within its container to guarantee successful setup. Why’s that require this weird bootstrap script that launches containers and acts as an orchestrator though? Why can’t the Discourse image accept env variables and in its entrypoint reach out to all those resources and create the tables it needs, etc.? Other services / web apps that rely on external persistence tiers have been successfully containerized in this way. You just pop them into an ECS or EKS or whatever, tell them where to find the database, etc., and it all works great. Is this possible with Discourse? [imagem] codinghorror: If you get into complex multiple container scenarios, that’s only necessary for large customers with lots of $, and I’d refer you to our enterprise hosting service… It’s because we’re the opposite—a non-profit org without tons of budget—that we want to keep things as cheap as possible by throwing all our enterprise apps onto a single AWS ECS host. But that requires that the individual apps are neatly containerized and can be defined as ECS task definitions, i.e., self-contained Docker images.

Well, sort of – given that Discourse easily fits into a $5/month VPS as a straightforward single Docker install image, I’m not sure squeezing a few pennies out of that number – with a massive increase in install difficulty and ongoing maintenance complexity – is really worth the hassle? Keep it simple!

As the above link describes, you can build containers and launch them with kubernetes. I’ve done GKE deployments for some clients who insisted on it because they were tied to the platform. If your goal is saving money then a $5 to $10/month is the way to go.

[imagem] lktmxjv: Why can’t the Discourse image accept env variables and in its entrypoint reach out to all those resources and create the tables it needs, etc.? Other services / web apps that rely on external persistence tiers have been successfully containerized in this way. You just pop them into an ECS or EKS or whatever, tell them where to find the database, etc., and it all works great. Is this possible with Discourse? Our tools are optimized for the far and away most common user: small groups without specialized IT to manage container orchestration. The necessary parts are available though if y’all need to go Full Cloud. The source repository to look at is: https://github.com/discourse/discourse_docker The samples/web_only.yml file therein shows how to use external resources. The launcher script is also capable of building a custom docker image with the bootstrap subcommand.

Alguém conseguiu rodar o Discourse com sucesso no AWS ECS ou similar?

Dev

Falco (Falco) 15 Fevereiro , 2020 18:17 2

Respondi a uma pergunta semelhante há dois dias

Tópico		Respostas	Vistas
Clarifications Regarding Deploying Discourse Docker Image on AWS ECS Self-hosting	1	1111	13 Novembro , 2020
Document for installing on AWS ECS Self-hosting	14	14691	3 Dezembro , 2020
Running Discourse docker image in the environment on Amazon EC2 Container Service Self-hosting hosting	6	3384	3 Julho , 2017
Has anyone experience with AWS EC2 Container Service? Self-hosting hosting	13	2148	3 Novembro , 2017
Discourse in an AWS context Product Support	1	769	24 Abril , 2018

Alguém conseguiu rodar o Discourse com sucesso no AWS ECS ou similar?

Related topics