GDay
commented
3 years ago Sorry to hear that!
[17] [INFO] Booting worker with pid: 17
/usr/local/lib/python3.9/site-packages/environ/environ.py:637: UserWarning: Error reading back/.env - if you're not configuring your environment separately, check this.
warnings.warn(That's nothing to worry about. That's a normal warning from one of the libraries. Everyone gets that. Also, it shows that that the worker booted, so that's all looking good. The worker deals with a few things that run in the background.
[Q] INFO Q Cluster hydrogen-high-low-sierra running.That too is totally fine. that's the cluster for the workers that seems to be operational. This cluster will rotate every 15 minutes or so.
Based on that, I am pretty sure that the worker and probably also the app itself are running fine. Both the worker and the main app are started by supervisor. Since the worker is running, I am assuming that the app works too.
The issue in this case is likely caddy/nginx. You can use nginx if you want, that should work if you reverse port 8000 of the web through nginx. For that, I think you will have to take it out of the global network or set Ports on the web service to 8000:8000. Though, I am not an expert on Docker.
I have previously used nginx for this app, see the files here if you need that: https://github.com/chiefonboarding/ChiefOnboarding/tree/3d4a7ff07e9dcfaaabdc82df5c7c398b3f85d2ab/nginx
By the way, you are using the docker-compose config from here, right: https://docs.chiefonboarding.com/deployment/ ?
And not the one that is in the repo? The one that is in the repo is the development compose file.
Let me preface this with I have no doubt it is something I am doing wrong, or simply misunderstanding but I am having an inordinate amount of trouble getting this to deploy to our local docker host and to be able to access it.
I have tried a modified config for what our usual deployments are as per our other apps, but without success on this I have gone to basically copy-pasting the supplied docker-compose.yml file into the system (changing only the base URL and allowed hosts config, I think it is these that may ultimately be contributing to my issue) but without success (we do not use caddy but another system for our reverse proxying (NGINX based) but simply exposed caddy on non-standard ports and tried this for good measure). I have tried straight HTTP as well as HTTPS and direct to what should be exposed port. I do get this error consistently
[17] [INFO] Booting worker with pid: 17 /usr/local/lib/python3.9/site-packages/environ/environ.py:637: UserWarning: Error reading back/.env - if you're not configuring your environment separately, check this. warnings.warn(
Yes the error simply cuts off
depending on the exact configuration (based upon the changing of the Base URL and Allowed Hosts variables) I will get a report in the log simular to this after a while but still no response
[Q] INFO Q Cluster hydrogen-high-low-sierra running.
Any help would be appreciated