You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m currently working on deploying FreeScout on AWS ECS using Docker Compose. While I’ve made some progress, I’ve run into challenges specific to ECS compatibility. For example, volume mounts like:
- ./db:/var/lib/mysql
don’t work with ECS, as it doesn’t support host-based volume mounts in this way.
Could you provide guidance or suggestions on how to adapt FreeScout to work on ECS? Alternatively, are there any plans to support ECS officially in the future? I’m eager to make FreeScout functional on ECS and would be happy to share any insights from my implementation efforts.
The text was updated successfully, but these errors were encountered:
Run MySQL in its own container and then map the volume in the way that suits you best.
If you're looking to run multiple containers for availability, then you may need to look at using EFS and map the volume that way.
There's also RDS but that will of course raise the price somewhat, but will mean that you don't need to manage the MySQL container and you can then focus on PHP + webserver.
Description:
Hi FreeScout team,
I’m currently working on deploying FreeScout on AWS ECS using Docker Compose. While I’ve made some progress, I’ve run into challenges specific to ECS compatibility. For example, volume mounts like:
- ./db:/var/lib/mysql
don’t work with ECS, as it doesn’t support host-based volume mounts in this way.
Could you provide guidance or suggestions on how to adapt FreeScout to work on ECS? Alternatively, are there any plans to support ECS officially in the future? I’m eager to make FreeScout functional on ECS and would be happy to share any insights from my implementation efforts.
The text was updated successfully, but these errors were encountered: