- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello. I did not know of frappe docker before, interesting to see others than me use extension fields for these things.
I'd recommend you try out ECS Compose-X which will do just exactly what you are trying to do.
In ECS Compose-X, instead of using that configurator, you simply define the depends_on
with the service names.
The services of your docker-compose file that you want to see grouped together in the same task definition, as opposed to being their own services, you using the deploy.labels as described here. As for the success condition is ECS, you simply then use this label to define the desired outcome. Typically I use that for all my sidecars that would have to do something such as render environment configuration, test connectivity and so on, before the main application.
Compose-X will also automatically understand which containers are Essential
and which ones are not (your sidecar doing the init, does not need to run forever typically).
I see that you also use RDS: you can use x-rds to lookup (via tags) your DB cluster/instance and allows you to define environment variables to your service obtained via API based discovery.
Note that there are a few other side projects to help with typically these things, such as files-composer which I now use all of the time to configure my NGINX and what not.
Checkout the labs for real-life examples.
Hope this helps, feel free to reach out if you wanted more details about ECS Compose-X.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa