Custom path doesn't follow config argument #877

Closed
opened 2025-11-02 03:40:04 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @camlafit on GitHub (Jul 11, 2017).

On master (and at least 1.1) if we start with a specific config file, custom path doesn't follow this change.

su -l git -s /bin/bash -c "/var/opt/gitea/gitea web --config /var/opt/gitea/project/custom/conf/app.ini"
Custom path is /var/opt/gitea/custom should be more logical to get var/opt/gitea/project/custom/

Maybe should be better to set custom path as arg and not only config file

Originally created by @camlafit on GitHub (Jul 11, 2017). On master (and at least 1.1) if we start with a specific config file, custom path doesn't follow this change. `su -l git -s /bin/bash -c "/var/opt/gitea/gitea web --config /var/opt/gitea/project/custom/conf/app.ini" ` Custom path is `/var/opt/gitea/custom` should be more logical to get `var/opt/gitea/project/custom/` Maybe should be better to set custom path as arg and not only config file
GiteaMirror added the type/proposal label 2025-11-02 03:40:04 -06:00
Author
Owner

@camlafit commented on GitHub (Jul 11, 2017):

To complete we can workaround with an export GITEA_CUSTOM=/var/opt/gitea/project/custom

Maybe should be better to provide an 'custom_path' argument and follow specification in this directory if we want use a specific app.ini , theme, ...

@camlafit commented on GitHub (Jul 11, 2017): To complete we can workaround with an `export GITEA_CUSTOM=/var/opt/gitea/project/custom` Maybe should be better to provide an 'custom_path' argument and follow specification in this directory if we want use a specific app.ini , theme, ...
Author
Owner

@lunny commented on GitHub (Jul 13, 2017):

When you specify a config file on command line, the GITEA_CUSTOM will not be used for config file path.

@lunny commented on GitHub (Jul 13, 2017): When you specify a config file on command line, the `GITEA_CUSTOM` will not be used for config file path.
Author
Owner

@camlafit commented on GitHub (Jul 13, 2017):

I don't understand.

Without GITEA_CUSTOM, ( su -l git -s /bin/bash -c "/var/opt/gitea/gitea web --config /var/opt/gitea/project/custom/conf/app.ini" ) I get :

[T] Custom path: /var/opt/gitea/custom
[T] Log path: /var/opt/gitea/project/log

With su -l git -s /bin/bash -c "export GITEA_CUSTOM=/var/opt/gitea/project/custom/ ; /var/opt/gitea/gitea web --config /var/opt/gitea/project/custom/conf/app.ini"

[T] Custom path: /var/opt/gitea/project/custom/
[T] Log path: /var/opt/gitea/project/log

To set a specific custom path (to personalize theme for example) to only project looks be required to set GITEA_CUSTOM and config arg.

Should be useful to have a relative path if --config is set or provide/replace a new argument to set --custom_path.

@camlafit commented on GitHub (Jul 13, 2017): I don't understand. Without GITEA_CUSTOM, ( `su -l git -s /bin/bash -c "/var/opt/gitea/gitea web --config /var/opt/gitea/project/custom/conf/app.ini" ` ) I get : > [T] Custom path: /var/opt/gitea/custom > [T] Log path: /var/opt/gitea/project/log With `su -l git -s /bin/bash -c "export GITEA_CUSTOM=/var/opt/gitea/project/custom/ ; /var/opt/gitea/gitea web --config /var/opt/gitea/project/custom/conf/app.ini" ` > [T] Custom path: /var/opt/gitea/project/custom/ > [T] Log path: /var/opt/gitea/project/log To set a specific custom path (to personalize theme for example) to only `project` looks be required to set GITEA_CUSTOM and config arg. Should be useful to have a relative path if `--config` is set or provide/replace a new argument to set `--custom_path`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#877