* clean migrate scripts
- refactor migrate:init
- separate admin seed
- separate categories seed
- rework backend README regarding the database
- remove `db:clean` command as its a duplicate of `db:reset`
- remove `__migrate` helper alias
* renamed clean.ts to reset.ts
* set indices & constrains in init function
* fix comment
* disable migrations touching indices
* remove obsolete comment
* always run init on kubernetes
* reset db with or without migrations
* lint fixes
* Refine 'README.md'
* Refine more 'README.md'
* fix lint
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
- Set other missing properties on admin of db init.
- Additionally set default donations `progress` value to `7000` to have a better looking design on the news feed for devs and testers.
- Fix test in `pages/admin/donations.spec.js`.
We have to figure out if `mergeRels: true` is actually avoiding
duplicate relationships 🤔.
Before:
(l1)-[:IS_IN]->(l2)
(l1)-[:IS_IN]->(l3)
After:
(l1)-[:IS_IN]->(new)
(l1)-[:IS_IN]->(new)
- create command should be run with --date-format to be more human
readable, and --template-file to use our template instead of migrate's
default
- rename migrations
- rename createdAt to migratedAt to remove ambiguity
- do not merge relationships for Location nodes as we don't want to
create duplicate relationships
- use singular locationId as it's iterating one at a time
- having duplicate Location nodes in the production database blocks us
from adding a unique constraint, so that Locations are not created
which have the same id.
