Workflow for Theme Development, Permissions Issues?

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?

Thank you for this fun, self-hosted tool. I've been using Ghost for over 10 years.

Start with the docker-compose stack and the host-mounted theme workflow described in the issue, focusing on container ownership and permissions. Reproduce the setup with a JSON export and theme folder, then document the recommended local-development workflow, including permissions that work without chmod 777 and remain compatible with Ghost CLI.