-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App doesnt connect to the database #51
Comments
Interesting. Did you make any changes to the docker-compose.yml file? I've just tagged a new release with updated install instructions. Want to give that a shot and see if it works better? |
Had a look at your new instructions. I tried a fresh installation now and it seems to work, but the login page layout is not adapting well. Also I tried to register a new user and for this
|
Ok i fixed the error with the register, it was a permission problem. The website however is unusable due to how big the images are showing for me (every image is scaling to "fullscreen"). |
Curious what the permissions problem was? Was it something unique to your set up? Or is it something that should be documented? As far as the images looking "huge" - have you updated the APP_URL: "http://localhost:8000"
ASSET_URL: "http://localhost:8000" I suspect that's the issue. |
The permission issue I'm trying to figure out, because it happen again after I did some changes and redeployed, which is strange. Regarding the images, I'm not sure how would string affect the images, but I've tried it as you suggested both in the env and the compose file and nothing changed. If it helps, when I zoom in/out within the browser the text and field do resize, but the images do not. |
Ok this is strange, but I commented out the ASSET_URL line in the compose file and it looks nice now. |
So my .env file is a copy paste of yours, I just changed the port because that one was already in use for me. I started to do some test uncommenting each line and narrowed it down to the SESSION_DRIVER and REDIS_HOST which can't be commented. This compose works for me:
|
I don't think you can reliably have both a .env AND set environments in your compose file. Not even sure which environments Docker would prioritize. My recommendation is to choose one or the other. To avoid this in future, I'll probably do something like this - so conflicts wont / cant occur: app:
image: investbrainapp/investbrain:latest
container_name: investbrain-app
restart: unless-stopped
tty: true
ports:
- "${APP_PORT:-8000}:80"
environment:
APP_KEY: ${APP_KEY:-""} # Generate a key using `openssl rand -base64 32`
APP_URL: ${APP_URL:-http://localhost:8000}
ASSET_URL: ${ASSET_URL:-http://localhost:8000}
DB_CONNECTION: ${DB_CONNECTION:-mysql}
DB_HOST: ${DB_HOST:-investbrain-mysql}
DB_PORT: ${DB_PORT:-3306}
DB_DATABASE: ${DB_DATABASE:-investbrain}
DB_USERNAME: ${DB_USERNAME:-investbrain}
DB_PASSWORD: ${DB_PASSWORD:-investbrain}
SESSION_DRIVER: ${SESSION_DRIVER:-redis}
QUEUE_CONNECTION: ${QUEUE_CONNECTION:-redis}
CACHE_STORE: ${CACHE_STORE:-redis}
REDIS_HOST: ${REDIS_HOST:-investbrain-redis}
volumes:
- ./storage:/var/www/app/storage:delegated
depends_on:
- mysql
- redis
networks:
- investbrain-network Would be curious if this works in your compose file? |
Now I get this
|
Do you see a ./storage directory in the same directory as your docker-compose.yml file? You're not the only one seeing the laravel.log permission error. I also saw them when I was re-working the container. What user are you running docker with? Can you do a |
I usually use Komodo to manage my stacks. But I tried just not directly via SSH with root user and am getting the same error. |
Oh and yes there is a "storage" folder in the same place as the yml. |
I tried starting from scratch with Now I get a symphony error:
|
Appreciate your patience in troubleshooting this with me. All of these error messages are pointing to permission issues. I just tagged a new release that should address these issues. It's still building, but should be on ghcr and dockerhub shortly! Pretty confident that should solve all these issues once and for all! 👍 |
I've follow the instructions but it seems that while the data base is ready, the app can't reach it.
The text was updated successfully, but these errors were encountered: