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
We have setup an instance following the steps mentioned and are able to play with demo data.
Further we went ahead and added our own data like new programs, facilities, users, etc. But this data is getting wiped across reboots and restarts. We tried production mode option, but still the data is getting wiped - actually with production mode we are not able to login. Is there any step we are missing - or particular sequence of steps to keep the newly added data from getting wiped?
Any help or pointers would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered:
prasadbmore
changed the title
Retain db across server reboots
Retain db across restart or server reboots
May 29, 2024
To fix this you need to set ./deploy_to_env.sh and settings.env(export spring_profiles_active=production).
Step 1 in deploy.sh file.
set export KEEP_OR_WIPE="keep"
export PROFILES='production' # strip any leading commas
export spring_profiles_active=$PROFILES
echo "Profiles to use: $spring_profiles_active"
start it up
docker-compose up --build --force-recreate -d
Step 2. In docker-compose.yml set pg_data as external volume.
Example:
We have setup an instance following the steps mentioned and are able to play with demo data.
Further we went ahead and added our own data like new programs, facilities, users, etc. But this data is getting wiped across reboots and restarts. We tried production mode option, but still the data is getting wiped - actually with production mode we are not able to login. Is there any step we are missing - or particular sequence of steps to keep the newly added data from getting wiped?
Any help or pointers would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered: