Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .env.main
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@ ADMIN_PWD=admincare
GUEST_EMAIL=guest@guest.com
GUEST_PWD=guestguest

# Skip first-time setup wizard: create admin from ADMIN_EMAIL / ADMIN_PWD and mark wizard complete (demo / dev pipelines).
DEV_SKIP_WIZARD=true
# First-time setup wizard: keep false so fresh main installs use /wizard.
DEV_SKIP_WIZARD=false

# nlp server
SERVICE_NLP_ENABLED=true
Expand Down
2 changes: 1 addition & 1 deletion Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,4 @@ WORKDIR content-server
RUN echo $ENV
RUN make ENV=$ENV build-frontend

CMD ["sh", "-c", "make ENV=$ENV NODE_ENV=production init dev-backend"]
CMD ["sh", "-c", "make ENV=$ENV NODE_ENV=production init dev-backend-wizard"]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to make sure, it is only used in the first run until settings are set?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes the wizard only runs while app.setup.wizardCompleted is unset/false. After setup completes, that setting is stored in the DB and the app routes to login/normal use instead of /wizard.

I also tested it locally and it works as expected.

Loading