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've been very interested to use BigCapital, but I'm finding the docker compose deployment process to be too complex.
Basically, you have to clone a 60MB repository with quite a few files, use an alternative docker compose -f ... command to use the production file specifically, and it's "hardcoded" into the repository.
For instance, I want the volumes to point to a specific folder instead of being Docker named volumes. If I modify the production compose file, it will be overriden the next time I git pull this project.
Also, updating the install requires both to pull the repository and then to update the containers.
Would it be possible to have a simplified docker-compose.yml file which contains everything needed without any other dependency, i.e. without needing to clone a repository. This is what most self-hosted projects do and it's a lot easier to maintain in the long run.
The text was updated successfully, but these errors were encountered:
Hi there!
I've been very interested to use BigCapital, but I'm finding the
docker compose
deployment process to be too complex.Basically, you have to clone a 60MB repository with quite a few files, use an alternative
docker compose -f ...
command to use the production file specifically, and it's "hardcoded" into the repository.For instance, I want the volumes to point to a specific folder instead of being Docker named volumes. If I modify the production compose file, it will be overriden the next time I
git pull
this project.Also, updating the install requires both to pull the repository and then to update the containers.
Would it be possible to have a simplified
docker-compose.yml
file which contains everything needed without any other dependency, i.e. without needing to clone a repository. This is what most self-hosted projects do and it's a lot easier to maintain in the long run.The text was updated successfully, but these errors were encountered: