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

Keep database password from preseeded configuration file #4217

Closed
2 of 7 tasks
tarelda opened this issue Jun 11, 2018 · 8 comments
Closed
2 of 7 tasks

Keep database password from preseeded configuration file #4217

tarelda opened this issue Jun 11, 2018 · 8 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality

Comments

@tarelda
Copy link
Contributor

tarelda commented Jun 11, 2018

  • Gitea version (or commit ref): fa3ceb6
  • Git version: not relevant to the issue
  • Operating system: alpine:latest
  • Database (use [x]):
    • PostgreSQL
    • MySQL (MariaDB)
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist: Not relevant

Description

I created fat gitea docker container, which contains also all other required services. It is just the way that suits my deployment. Issue I bumped into is, that database password is automagically generated in entrypoint and correctly seeded into configuration file, but when using installer it just omits it.
My expected behaviour is that when I preseed password it has to be kept instead of zeroing it.
Can this be fixed or at least available with feature switch like --enable-preseeded-config ?

@bkcsoft
Copy link
Member

bkcsoft commented Jun 15, 2018

If you seed your config-file you should set [security] INSTALL_LOCK = true to skip the /install step. If that is done the password should not be reseeded.

@tarelda
Copy link
Contributor Author

tarelda commented Jun 15, 2018

This is not a solution, because it disables installer, which I explicitly want to avoid.
What is more, I can't come up with single reason, why installer doesn't keep password from config while reading all of the other settings.

@bkcsoft
Copy link
Member

bkcsoft commented Jun 17, 2018

Before the installation, Gitea does not read the config file. Why would it, since it might not exist?

@tarelda
Copy link
Contributor Author

tarelda commented Jun 17, 2018

@bkcsoft, it seems you are wrong
https://github.com/go-gitea/gitea/blob/master/routers/install.go

func LoadConfigs() {

if com.IsFile(CustomConf) {

@lunny lunny added the type/enhancement An improvement of existing functionality label Jun 19, 2018
@lunny lunny added this to the 1.6.0 milestone Jun 21, 2018
@techknowlogick techknowlogick modified the milestones: 1.6.0, 1.7.0 Aug 29, 2018
@techknowlogick techknowlogick modified the milestones: 1.7.0, 1.8.0 Dec 19, 2018
@stale
Copy link

stale bot commented Feb 17, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Feb 17, 2019
@techknowlogick techknowlogick modified the milestones: 1.8.0, 1.9.0 Feb 19, 2019
@stale stale bot removed issue/stale labels Feb 19, 2019
@stale
Copy link

stale bot commented Apr 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Apr 20, 2019
@stale
Copy link

stale bot commented May 4, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed May 4, 2019
@techknowlogick techknowlogick reopened this May 4, 2019
@stale stale bot removed the issue/stale label May 4, 2019
@techknowlogick techknowlogick added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label May 4, 2019
@techknowlogick techknowlogick modified the milestones: 1.9.0, 1.10.0 Jun 25, 2019
@lunny
Copy link
Member

lunny commented Sep 24, 2019

should be closed by #4284

@lunny lunny closed this as completed Sep 24, 2019
@lunny lunny removed this from the 1.10.0 milestone Sep 24, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

4 participants