search

S1SYPHOS / Docker-Kirby-Starter-Kit

Getting started with Docker Compose & Kirby v3 in no-time
MIT License
20 stars 3 forks source link

panel not working #1

Open KHBerlin opened 4 years ago

KHBerlin commented 4 years ago

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.

S1SYPHOS commented 4 years ago

I'll have a look when there's time.

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 :fox_face:

Gong-Bao-Chicken commented 3 years ago

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:

1) Find your local UserID, on Linux: echo $UID, in my case it was 1000 2) 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.