Context:

I am running about 20 of the Cloudron LAMP app instances.

I have been updating them via WINSCP/FileZilla. I'm switching to doing a git pull (since all of the content is managed in a git repo).

Currently I have to:

su www-data -c "git pull"

Otherwise I get:

root@16405153-e269-41e3-ab8d-095606d5b07e:/app/data/public/KNEL/FetchApply# git pull
fatal: detected dubious ownership in repository at '/app/data/public/KNEL/FetchApply'
To add an exception for this directory, call:

    git config --global --add safe.directory /app/data/public/KNEL/FetchApply
root@16405153-e269-41e3-ab8d-095606d5b07e:/app/data/public/KNEL/FetchApply# git config --global --add safe.directory /app/data/public/KNEL/FetchApply
error: could not lock config file /root/.gitconfig: Read-only file system

I want to make an alias for the su -... command.

Editing .bashrc says read only filesystem.

Question 1: Should we have the ability to customize the root shell on cloudron? Does this compromise the integrity of the system? What are the downsides? What are the rollback / recovery mechanisms?

Question 2: Should we have the ability to change shells? (I am a huge zsh user, cloudron is the only system in my fleet not using zsh).

Question 3: How should different kinds of customizations be handled? For example, aliases/ps(x)/themes etc? Should it only be a single custom file where you can put "whatever you want"? Should it be a set of files?

Question 4: Can the files be able to be pulled from version control?