You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The scripts that are run on install (aka deploy) are stored in: dbicdh/_common/deploy/VERSION
If there are no scripts in there, then you wouldn't get an admin user or apikey.
Part of this is due to changing how --install worked. It always used to install version 1, and then you would have to upgrade to get to the current version. The change in the user database (adding password_salt) broke that, since the code tried to install a column that doesn't exist in earlier versions of the schema. Now, the install files would need to be copied into every VERSIONS's deploy folder, or, install an earlier version and run an upgrade.
I blew away my database with --install --ok, but it didn't recreate admin.
The text was updated successfully, but these errors were encountered: