Skip to content
Snippets Groups Projects
Commit 235df450 authored by Richard Fernando Heise Ferreira's avatar Richard Fernando Heise Ferreira
Browse files

Merge branch 'rfhf19-main-patch-20449' into 'main'

Update README.md

See merge request mecred/setup-guide!3
parents 30d4859f 275f1e08
No related branches found
No related tags found
1 merge request!3Update README.md
......@@ -399,12 +399,18 @@ The button to download a collection was not working. This is due, most likely, t
- First, copy all the public dir from the old production VM to the new backend public dir.
- Now, make sure the new backend is up and running via docker.
- Ajust the .env file to replicate de env_vars.txt from the old backend.
- Adjust the .env file to replicate de env_vars.txt from the old backend.
- Make the migrations necessary in the database, but remember that those columns will **not have** data, so one needs to manually add data.
- Create a transaction with BEGIN; and finish it with COMMIT;
- Make sure the database is snapshoted/dumped so we don't lose user data. Also, stop the frontend so no new data will be inserted during this operation.
- Make every user have a *streak* of 0
- Make every user have a *high_streak* of 0
(```SQL
update "users" set streak = 0, high_streak = 0;
```)
- Make every user have a *last_action_at* of the current_date, **wihtout timestamps, just the year-month-day**
(```SQL
update "users" set last_action_at = current_timestamp;
```)
- Run the new backend and do some testing. Try to get statistics and make a search. If the searchs breake, remember to reindex everything via rails console.
- Point the frontend to the new API and all should be good
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment