.env parameter change not recognized by front end #2323

New Issue

OVERLORD · 2026-02-05T03:40:07+03:00

OVERLORD commented

2026-02-05 03:40:07 +03:00

Originally created by @whentotrade on GitHub (Jul 16, 2021).

Changing .env parameter, but not recognized on front end when visiting site via a browser

I changed from oauth 2 provider via setting in the env file:
New entry
AUTH_METHOD=standard

Old entry (removed)
AUTH_METHOD=saml2

However, the login page still links to my IDP provider.

I observe similar behaviour if changing env parameters which are not picked up when visiting the front end via the browser.

Question:
What is required in order to bookstack app recognize .env parameter changes?

Originally created by @whentotrade on GitHub (Jul 16, 2021). Changing .env parameter, but not recognized on front end when visiting site via a browser I changed from oauth 2 provider via setting in the env file: New entry AUTH_METHOD=standard Old entry (removed) AUTH_METHOD=saml2 However, the login page still links to my IDP provider. I observe similar behaviour if changing env parameters which are not picked up when visiting the front end via the browser. Question: What is required in order to bookstack app recognize .env parameter changes?

OVERLORD closed this issue

2026-02-05 03:40:11 +03:00

OVERLORD commented

2026-02-05 03:40:20 +03:00

@whentotrade commented on GitHub (Jul 16, 2021):

I found the solution:

I needed to run the following command to in order for the app to pick up latest .env settings and changes:

artisan config:cache

response:

Configuration cache cleared!
Configuration cached successfully!

@whentotrade commented on GitHub (Jul 16, 2021): I found the solution: I needed to run the following command to in order for the app to pick up latest .env settings and changes: `artisan config:cache` response: ``` Configuration cache cleared! Configuration cached successfully! ```

OVERLORD commented

2026-02-05 03:40:26 +03:00

@ssddanbrown commented on GitHub (Jul 17, 2021):

Hi @whentotrade,
Note that since you've cached your config you'd need to run that on any config change or app version update.
You can also run artisan config:clear to simply clear this cached config.

@ssddanbrown commented on GitHub (Jul 17, 2021): Hi @whentotrade, Note that since you've cached your config you'd need to run that on any config change or app version update. You can also run `artisan config:clear` to simply clear this cached config.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#2323