helm values aading, make user as admin in db in xrengine

helm get values dev > dev.yaml vi dev.yaml ( add the values ) helm upgrade dev xrengine/xrengine -f dev.yaml

1. we need to loginto https://n3xus.city as admin user
2. update db with our id as admin Go into the database and manually change a user's userRole to 'admin', then also add at least the scopes 'user:read' and 'user:write' so that they can add and remove other scopes from the page /admin/users Alternatively, look up what might be causing the 'unknown option' issue. I tried it just now and it didn't throw that error, so I'm pretty sure it's a problem specific to whatever setup this is running on 3.One, if you already have a user who's an admin, they can go to /admin/settings, then pick a sub-section; Github credentials, along with other OAuth provider credentials, are under Authentication. There's a section for each OAuth provider - copy paste the new credentials, then click the Save button.

References : Those values, along with many others, are stored in the database. Once they're inserted into the database, any change to them in the values.yaml file will not be reflected in the database. There's a couple ways to update the database. One, if you already have a user who's an admin, they can go to /admin/settings, then pick a sub-section; Github credentials, along with other OAuth provider credentials, are under Authentication. There's a section for each OAuth provider - copy paste the new credentials, then click the Save button. Two, manually go into the database manually and change the values. OAuth is in the authentication table, in the column oauth. Three, you can reinitialize the database. This is generally only a good idea if you're first setting up a deployment - once you have users, locations, etc. in there, you'd better have a good reason for wiping those away. You can run helm upgrade --reuse-values --set-string api.extraEnv.FORCE_DB_REFRESH=true xrengine/xrengine (this assumes you've already applied the updated values.yaml file to , otherwise you'll want to add -f <values.yaml> to that command). This will tell the API server to reinitialize the database, which will wipe everything and insert all of the values from values.yaml. After that, run helm upgrade --reuse-values --set-string api.extraEnv.FORCE_DB_REFRESH=false xrengine/xrengine - this will ensure that any new API pods will not also wipe the database.