We have to clone the github repository to launch MediaCMS with Docker!

[miltuss]

The problem is in the title. Docker allows you to launch applications in isolation from the system without having to download the application installation files to the file system. Whereas the installation of MediaCMS requires cloning the git repository so that the command command: "./deploy/docker/prestart.sh" from the docker compose file can be executed!

I would like to install Media CMS with Docker compose without having to clone the git repository. How to do it?

[mjbergman92]

I'm having the same predicament while attempting to use with Portainer.

What I am going to do, but doesnt solve the issue, is install on docker, run mediacms, then reverse engineer a docker compose without the install script if possible, and then use that docker compose file in portainer with modifications for the volumes and my networks.

UPDATE:

For me, cloning the repository is not an issue. Once the repository is cloned, I just had to adjust the volume binding paths to the clone repo directory, which isn't unusual. At one point, that was not working for some reason, but I am now unable to reproduce that issue.

Given MediaCMS is focused on a micro-service-based structure, the project is made to be able to configure each service individually. I don't think it would be beyond reason to build an image for each of the ~5 containers and have a "pre-built" docker compose, keeping the microservice architecture without the requirement in the docker compose for the execution of the bash scripts.