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
Great dockerfiles! I made a fresh install with current kirby. the pages works, but panel/ doesn't. There are several 404s, for assets as well.
I am also confused about .htaccess, which is not read by nginx. So I wonder how it can work at all? I also realized that the paths to kirby/ are not blocked. It's possible to read the composer.json for example.
I followed the instructions with plainkit.
The text was updated successfully, but these errors were encountered:
As this is a development setup, it's not meant to be used with Docker in production. Thus, no rules to protect sensitive directories / files! The .htaccess is there for folks replacing NGINX with Apache 🦊
I was facing the same issue. In my case in addition to the panel, thumbnails and its media folder could not be generated because of missing write permissions. In order to solve the issue two steps were necessary:
Find your local UserID, on Linux: echo $UID, in my case it was 1000
Edit user property of fpm.conf
[global]
daemonize = no
[www]
listen = /sock/docker.sock
user = 1000 #Local UserID
group = www-data
listen.owner = www-data
listen.group = www-data
listen.mode = 0660
I am not sure, if there is a better way to solve this. But if you find one, let me know.
Great dockerfiles! I made a fresh install with current kirby. the pages works, but panel/ doesn't. There are several 404s, for assets as well.
I am also confused about .htaccess, which is not read by nginx. So I wonder how it can work at all? I also realized that the paths to kirby/ are not blocked. It's possible to read the composer.json for example.
I followed the instructions with plainkit.
The text was updated successfully, but these errors were encountered: