• Git & Deploy functionality (for docker-compose + mounted volumes)
• Backups (docker-compose + mounted volumes)

I think the UX could use some work. Deploying a public service right now feels daunting, even as a long-time Docker user. Perhaps this is just a documentation issue. Deploying a php-based website with Ploi is super intuitive; however, if I want to host that same code in a Docker container in Ploi, I've really never figured out how to make it work - everythings feels a bit opaque, especially the relationship between "Sites" and "Applications" as well as how to handle deployments.

• INTERFACE/UX: setup a container like a "site" with or without git
  • with git, so you can get docker-compose.yaml and config/data from git
  • without, like it is now, manual setup
  • ??? auto compose down/up on git "deployment"
• BACKUPS: ability to setup backups for each container folder
• STATS: use docker stats to see memory usage etc per container
• maybe: rename "applications" as in "Create application" to containers

i wish it come with one click install software, such as easypanel did, that would be beeeeest for new user,

Merged Docker - Compose - Read-Only - Sync with server - history and share. into this item \n\n Created by: bkeeper \n\n 1-It would be very useful if we could mark a config as read only to prevent accidental mmodifications.

2-It would also be great if we could sync with the server. Add an app for every ploi subfolder and sync docker compose contents.

3-Backup compose history.

4-Share apps (compose files). Similar to the laravel commands share option.

Have the container status (stopped/started) based on docker status, so ploi only needs to "save" the container id maybe? and get the information based on that.

Also, have all containers shown in ploi, even those created outside of ploi so you could start/stop, see stats and logs.

Ploi currently runs all docker applications as root. This can be a security issue once an application manages to break out of it's container (e.g through a mounted volume).

To limit damage, the application should be scoped in their privileges (comparable as user-separation for php / nodejs applications). Therefore it could use the rootless mode or container isolation.

• Rootless mode
• Container isolation

(NOTE: I'm not using ploi for docker atm, so please correct me if this already has changed. Looking forward to use it again, once it get's more features)