Workflow for Theme Development, Permissions Issues?

[david-cako]

Hi!

I understand that this is a newer deployment pipeline for Ghost, but I happened to be building a local development workflow and discovered that this is where things are headed.

When I spin up the docker compose stack it works.

Now I copied my theme into the volume where it belongs. Upon restarting ghost, it tries to chown all of the theme files and doesn't start. Next, I tried chowning all of the theme files from the shell in my host environment to 1000:1000 (which does seem to be correct for the ghost container's user). That did not work either.

The only thing that worked is chmoding the theme to 777 from the host shell. Ghost starts fine, and the theme is accessible from the admin panel. Certainly this isn't the only solution though, right? Ghost CLI will not run a theme with these permissions. I want to develop on the exact same folder and permissions as I would deploy in production.

Bottom line, if I have a json export of my blog and a folder with my theme, what is the recommended workflow for local development?

Thanks folks. I've been using Ghost for almost 10 years.

[david-cako]

docker compose cp THEME_DIRECTORY ghost:/var/lib/ghost/content/themes/ works until I do anything in git. Permissions errors for the .git directory when starting the container. For now I just work on my theme outside of the mount and re-run a script to copy the theme and re-up the ghost and caddy services.

[david-cako]

Likewise for images, I wrote this script which does work:

mkdir -p images
rsync -azP MY_SITE:/ghost/content/images/ images

cd ghost-docker
docker compose cp ../images ghost:/var/lib/ghost/content/

Before that, I tried making an outer compose.yml that inherits the ghost service and adds a bind mount. Every time the blog started, it would spit out every single image saying it could not find every image (although it somehow listed every image, and they were all clearly visible when running a shell in the container as the node user):

ghost-1  | find: /var/lib/ghost/content/images/2026: No such file or directory
ghost-1  | find: /var/lib/ghost/content/images/2019: No such file or directory
ghost-1  | find: /var/lib/ghost/content/images/2021: No such file or directory
... (same output for every single directory and file)

Finally, I tried putting that bind mount directly into the compose.yml from this repo. Same thing.

🤷

[david-cako]

Perhaps also of interest for others: I have used VS Code Dev Containers in the past, but I don't really want to bake it into this particular workflow. I wonder if that would work, in this case, to keep permissions as they belong from within the container (while editing files and using git).