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
Following an upgrade, I no longer have my data.
So I start to check my files and they are there but not read by Sémaphore.
Semaphore actually created a new folder "0.0.0.0" in home without reading the /config which I know is read because it contains the oidc data.
With the environment variable "SEMAPHORE_DB_HOST" I managed to correct my problem.
So I think we should correct the problem first and rename the default value 0.0.0.0 with a new, more relevant name for a quick installation.
Impact
Database
Installation method
Docker
Database
BoltDB
Browser
Chrome
Semaphore Version
v2.9.100-beta
Ansible Version
No response
Logs & errors
No response
Manual installation - system information
No response
Configuration
Config.json and env variables
Additional information
No response
The text was updated successfully, but these errors were encountered:
@fiftin I still have the problems and now I have the problems, if I set it by the configuration file (bolt/host) or the environment variable (SEMAPHORE_DB_HOST: /home/semaphore/boltdb/database.boltdb) now the value always remains at "/var/lib/semaphore/database.boltdb"
Issue
Following an upgrade, I no longer have my data.
So I start to check my files and they are there but not read by Sémaphore.
Semaphore actually created a new folder "0.0.0.0" in home without reading the /config which I know is read because it contains the oidc data.
With the environment variable "SEMAPHORE_DB_HOST" I managed to correct my problem.
So I think we should correct the problem first and rename the default value 0.0.0.0 with a new, more relevant name for a quick installation.
Impact
Database
Installation method
Docker
Database
BoltDB
Browser
Chrome
Semaphore Version
v2.9.100-beta
Ansible Version
No response
Logs & errors
No response
Manual installation - system information
No response
Configuration
Config.json and env variables
Additional information
No response
The text was updated successfully, but these errors were encountered: