Skip to content
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

Closed
silverwind opened this issue Mar 10, 2017 · 4 comments
Closed

Command line option for the custom directory path #1208

silverwind opened this issue Mar 10, 2017 · 4 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@silverwind
Copy link
Member

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).

@tboerger
Copy link
Member

Just define the GITEA_CUSTOM environment variable to set this path. We won't break this behavior for minor releases.

@tboerger tboerger added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Mar 10, 2017
@silverwind
Copy link
Member Author

Thanks, I wasn't aware of that variable. Probably a good idea to add supported environment variables to --help to raise awareness.

@pgaskin
Copy link
Contributor

pgaskin commented Mar 10, 2017

I am currently working on documenting these lesser known features of gitea.

@gsantner
Copy link

I would too suggest to add it at least to the --help help, as this is the command most likely used first to find out which argument needs to be set, after trying --config= and seeing it does not work 😄

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

4 participants