Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Automatically complete install/configuration #1

Closed
geerlingguy opened this issue May 7, 2014 · 4 comments
Closed

Automatically complete install/configuration #1

geerlingguy opened this issue May 7, 2014 · 4 comments
Labels

Comments

@geerlingguy
Copy link
Owner

See: gogs/gogs#145 (comment)

Change security -> INSTALL_LOCK to true in custom/conf/app.ini will omit install page step.

@geerlingguy
Copy link
Owner Author

Also, when running the latest version of Gogs, I get:

No custom 'conf/app.ini' found, please go to '/install'

@rosstimson
Copy link

I'd like to see this feature too. I'm trying to setup a private Gogs in which I'll disable user registration and use an admin account to add users. I'd like to use options such as Redis for cache/sessions and Oauth but such settings in custom/conf/app.ini will be overwritten when I go through the web based '/install' step and furthermore they are not available to set during the web based install.

The problem is, how can I setup the initial admin user if I set INSTALL_LOCK = true?

My current workflow would have to be:

  1. Ansible playbook starts Gogs (+ custom/conf/app.ini mounted as a volume) and linked MySQL containers.
  2. The app.ini gets overwritten during install and initial admin user creation.
  3. Another Ansible playbook stops Gogs container and starts another linking to the MySQL container that now has an admin user in the DB and mount my final custom/conf/app.ini.

I don't know if there is a better way to do this but I can't figure it out so far, the only other alternative seems to be working out the raw sql to add the admin user during the Ansible play and set the INSTALL_LOCK = true option. Two seperate provisioning runs with manual intervention in the middle and a container/service restart or raw SQL hackery both seem very wrong.

@stale
Copy link

stale bot commented Mar 6, 2020

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@stale stale bot added the stale label Mar 6, 2020
@stale
Copy link

stale bot commented Apr 5, 2020

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

@stale stale bot closed this as completed Apr 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants