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

Admin user is not created when LOG_LEVEL isn't provided #55

Closed
dallashuggins opened this issue Nov 5, 2021 · 2 comments
Closed

Admin user is not created when LOG_LEVEL isn't provided #55

dallashuggins opened this issue Nov 5, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@dallashuggins
Copy link
Contributor

Overview

When LOG_LEVEL is not set, the admin user will not be created when the npm run bootstrap script is run. Therefore, it says it's successful in bootstrapping, but when you go to login with your username and password, it doesn't work.

To reproduce

Steps to reproduce the behavior:
This should be for a new project without a user.

  1. Comment out LOG_LEVEL
  2. Go to apps/cms
  3. Run npm run bootstrap
  4. Check CMS database table directus_users; there's no user. It also will specify in the logs it created the user if it worked.

Expected behavior

When LOG_LEVEL is warn, the admin user is created as expected and you can login.

Additional context

When you console log console.log({ userCount }) in the bootstrap file, it returns:

{
  usersCount: '17:00:32 ✨ Loaded extensions: price-conversion, pack-price\n0\n'
}
@dallashuggins dallashuggins added the bug Something isn't working label Nov 5, 2021
@IanPirro
Copy link
Contributor

@dallashuggins did #56 resolve this issue?

@dallashuggins
Copy link
Contributor Author

@IanPirro It did - forgot I opened this. Closing since fixed. 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants