-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command line option for the custom directory path #1208
Comments
Just define the GITEA_CUSTOM environment variable to set this path. We won't break this behavior for minor releases. |
Thanks, I wasn't aware of that variable. Probably a good idea to add supported environment variables to |
I am currently working on documenting these lesser known features of gitea. |
I would too suggest to add it at least to the |
To keep the gitea directory pristine, I currently symlink the
custom
directory to a directory outside which contains my config and various overrides.I think it would be useful if one could specify the path to the custom directory, for example through a
-c <custom-dir>
switch (which would enable me to skip the symlink step).The text was updated successfully, but these errors were encountered: