Replies: 2 comments 9 replies
-
|
Inside the docker-compose.yml replace the 127.0.0.1:80:80 to 80:80 and then redeploy |
Beta Was this translation helpful? Give feedback.
-
|
Set to 'dev', setting to 'development' wouldn't give an error, but the container would exit after starting. here is the here are the logs, I waited until CPU activity dropped completely after attempting to connect. Now, instead of the "WOOPS!!" message I am getting the error "The application environment is not set correctly" displayed on the blank screen. |
Beta Was this translation helpful? Give feedback.
-
|
I tried to do the docker-compose up here and it works. Even when I set the CI_ENVIRONMENT to development I can access the page. What version of docker are you using? Perhaps check if you have a recent one. |
Beta Was this translation helpful? Give feedback.
-
|
Also what logs do you see when you set the value to development? |
Beta Was this translation helpful? Give feedback.
-
|
Can you perhaps remove any created docker volumes before restarting the stack? In this case |
Beta Was this translation helpful? Give feedback.
-
|
Docker version: Volumes removed, static host directories made for the logs and uploads volumes., and changed CI_ENVIRONMENT TO developement.... uh.. thats an issue.. Apparently I've either jumped realities or I've been spelling "develop" wrong for 40 years somehow, probably hadn't been noticing because of autocorrect fixing things so often. lol Any-hooo, I do have it up and running now, both with the 'development' and 'production' environment tags. the only substantive change I made was the static host directories, and wrapping them in quotation marks. Everything appears to be functional running on my clean lab server at work. I'll be trying this later at home. Thanks for the help. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I'll check that out later this morning.
…On Tue., Feb. 4, 2025, 05:15 jekkos ***@***.***> wrote:
Can you perhaps remove any created docker volumes before restarting the
stack? In this case docker volume rm opensourcepos_mysql check first how
the volume is named if this does not work docker volume ls´
—
Reply to this email directly, view it on GitHub
<#4168 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AX2LVYE5CABMTY6DAUFGVP32OCOOZAVCNFSM6AAAAABWK5HDQGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBVGM4TOMA>
.
You are receiving this because you authored the thread.Message ID:
<opensourcepos/opensourcepos/repo-discussions/4168/comments/12053970@
github.com>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I feel like I am probably missing something simple..
Followed the "Local Install Using Docker" instructions, seems pretty simple to me...
Everything appears to work, I get no errors when checking with
docker-compose build, or when Idocker-compose up -d, but when I go to localhost:80 am just met with a blank page, no errors, just a blank white page.Of all the things I have done with docker, this appears be quick and easy to get it up and just see whats what. What am I missing..? Is nginx not part of the image and I need to do it separately?
I saw the docker-compose.nginx.yml and tried starting it up using that instead, however I get errors about the env setting, like it can't see the .env file, so I was thinking it was just a testing file..
systems I have tried it on:
laptop: Lenovo P15 Gen2 with NixOS 24.11
server: 2x Xeon e5-2690 v2: proxmox:
Ubuntu server 22.04
Arch 25.01 (set up as a server os)
It is the exact same where ever I run it. just tell me what dumb thing I'm not doing and where I missed it....
Beta Was this translation helpful? Give feedback.
All reactions