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 believe that this could easily be fixed as right now the docker images "as-is" are unusable.
A simple rewriting done by nginx (as provided above) could be easily included in the docker images.
The text was updated successfully, but these errors were encountered:
Hi @darioackermann, thanks for opening this issue and sorry that you're running into issues with the Docker containers.
Can you confirm if you were running into the nginx error after cloning the repo and using the default Docker compose files? Or were you using a different method to spin up the containers?
Additionally, would you be open to creating a PR with your proposed changes?
For added context, the default docker-compose file and the corresponding dockerfiles are meant to serve as templates, that should be enough to run out of the box but will require some customization if you wish to tailor it to for specific use. In some of your suggestions, I see there are specific references to what looks like an ECR link for the client image (which should be hosted on Docker Hub) and a custom domain name, which may not be the best to include within the default file.
Preflight Checklist
Issue Details
(irrelevant for this issue)
Expected Behavior
Actual Behavior
/usr/share/
, although frontend files are in/var/www
,/api/
on the same host.To Reproduce
Currently applied workaround
Easy fix:
docker-compose.yml
ccf/Dockerfile
default.conf
I believe that this could easily be fixed as right now the docker images "as-is" are unusable.
A simple rewriting done by nginx (as provided above) could be easily included in the docker images.
The text was updated successfully, but these errors were encountered: