Replies: 8 comments
-
Hi- thanks for the feedback. Our Getting Started guide might need a little attention. If you can give some details on where you saw differences in the docs against current Quay we can take a look. This part of the Quay configuration is very specific to the database that you're using. Are you on Postgres or MySQL? You can find some more extensive documentation here- https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html/configure_red_hat_quay/config-fields-intro#database-connection-arguments |
Beta Was this translation helpful? Give feedback.
-
@BillDett -Scott |
Beta Was this translation helpful? Give feedback.
-
Back at it again ..... and now .... I'm losing my mind. Please help .... |
Beta Was this translation helpful? Give feedback.
-
Hi Scott- yeah this can be confusing. We don't ship with any users predefined. Click 'Create Account' from the login page and create a new user. If you want to make any superusers, create a regular accounts and then add the usernames as a list into the SUPER_USERS stanza of your config.yaml.
|
Beta Was this translation helpful? Give feedback.
-
Bill, Thanks, |
Beta Was this translation helpful? Give feedback.
-
NVM That’s what get for trying to tweak the config on the first run. FEATURE_USER_CREATION: false Needs to be true for the “Create User” link to show up. |
Beta Was this translation helpful? Give feedback.
-
Thanks for confirming Scott- that would have been my next place to check. |
Beta Was this translation helpful? Give feedback.
-
The connection args are changed to use underscore. the accepted keys can be found here: https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWORDS |
Beta Was this translation helpful? Give feedback.
-
As a first-time user of quay, I started with the "Getting Started" in the docs.
There were some minor differences in the existing docs from the current interface, but nothing I couldn't resolve easily. However, when I started the container, it would die with:
It seems something has changed in the DB configuration???
In order to get the container to start, I had to make the following changes to the config:
Original:
Working:
Each of the items removed from that section caused the same "invalid dsn:" error.
Beta Was this translation helpful? Give feedback.
All reactions