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
Official SQLite support? #71
Comments
Hello I know there are others using SQLite just not sure if they are using Docker. Can you try |
Touching & migrating works without an error. Sadly, the page still returns 500 errors.
|
Alright so from that it doesn't seem to be a database issue, is there anything in the PHP or Laravel logs? |
Are they redirect to the container stdout? If so, then no. |
log location: /app/storage/logs/laravel.log |
Sorry, that it took a while to respond😅 So, I've changed my setup a bit. It is now in a private network utilizing homeall/caddy-reverse-proxy-cloudflare. docker-compose.yaml
.env
My setup steps were:
For |
Thanks for the logs. Seeing as though you have run Perhaps running These are the commands that come up as solutions for "No application encryption key has been specified" in production |
Changing the container to |
Hi,
I'd like to run my idlers with a sqlite database, since for my usecase there is a very limited amount of data and another database container seems excessive. Is there a way to do this?
My current approach (using docker-compose) looks like this:
This however throws only 500-errors, even after
... artisan migrate:fresh ...
and does not print anything to stdout, so I am not sure what exactly fails.The text was updated successfully, but these errors were encountered: