Overwriting Application name on two different instances #1609

New Issue

OVERLORD · 2026-02-05T01:25:24+03:00

OVERLORD commented

2026-02-05 01:25:24 +03:00

Originally created by @nolexio on GitHub (Mar 26, 2020).

Yesterday I installed two instances of the Bookstack App.

Bookstack App is installed in folder: /opt/bookstack/app1/BookStack
Bookstack App is installed in folder: /opt/bookstack/app2/BookStack

Both instances have been configured to use different databases, different subdomains and have different URLs configured which were configured in .env respectively.

Now when I set the Application name from within the web settings, the app name is being changed on both instances. At least that is what is being shown within the browser.

when checking "settings" table in the databses i can see that the app name is different.

Originally created by @nolexio on GitHub (Mar 26, 2020). Yesterday I installed two instances of the Bookstack App. 1. Bookstack App is installed in folder: /opt/bookstack/app1/BookStack 1. Bookstack App is installed in folder: /opt/bookstack/app2/BookStack Both instances have been configured to use different databases, different subdomains and have different URLs configured which were configured in .env respectively. Now when I set the Application name from within the web settings, the app name is being changed on both instances. At least that is what is being shown within the browser. when checking "settings" table in the databses i can see that the app name is different.

OVERLORD closed this issue

2026-02-05 01:25:26 +03:00

OVERLORD commented

2026-02-05 01:25:32 +03:00

@ssddanbrown commented on GitHub (Mar 26, 2020):

Hi @nobdev,
Have you configured any cache settings at all?

Settings, such as app-name, go through a layer of back-end caching so if the two instance use the same system for caching (Memcached or Redis) you may get some interference.

@ssddanbrown commented on GitHub (Mar 26, 2020): Hi @nobdev, Have you configured any cache settings at all? Settings, such as app-name, go through a layer of back-end caching so if the two instance use the same system for caching (Memcached or Redis) you may get some interference.

OVERLORD commented

2026-02-05 01:25:33 +03:00

@nolexio commented on GitHub (Mar 26, 2020):

Hi @ssddanbrown!
That was smart. That solved my problem. Just switched one instace to redis and everything seems fine. I was too lazy to get into setting up two memcached instances.

Problem solved for me!

@nolexio commented on GitHub (Mar 26, 2020): Hi @ssddanbrown! That was smart. That solved my problem. Just switched one instace to redis and everything seems fine. I was too lazy to get into setting up two memcached instances. Problem solved for me!

OVERLORD commented

2026-02-05 01:25:35 +03:00

@ssddanbrown commented on GitHub (Mar 26, 2020):

Alternatively we do have support for different prefixes:

# Cache key prefix
# Can be used to prevent conflicts multiple BookStack instances use the same store.
CACHE_PREFIX=bookstack

Could use the same store with different key prefixes per system.

@ssddanbrown commented on GitHub (Mar 26, 2020): Alternatively we do have support for different prefixes: ```env # Cache key prefix # Can be used to prevent conflicts multiple BookStack instances use the same store. CACHE_PREFIX=bookstack ``` Could use the same store with different key prefixes per system.

OVERLORD commented

2026-02-05 01:25:37 +03:00

@nolexio commented on GitHub (Mar 26, 2020):

Problem was based on a misconfigured memcached setup.

@nolexio commented on GitHub (Mar 26, 2020): Problem was based on a misconfigured memcached setup.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#1609