19 Commits

Author SHA1 Message Date
Moriz Wahl
0d1da0d83d
Update backend/src/db/migrate/store.js
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
2022-08-30 10:14:39 +02:00
Moriz Wahl
3e6cabaa1c
Update backend/src/db/migrate/store.js
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
2022-08-30 10:13:56 +02:00
Wolfgang Huß
f2aba3e12e Put exclamation mark behind console log text of successfully created default admin user for consistency 2022-08-25 18:03:21 +02:00
Moriz Wahl
d948067f44 add category name again to seed and init to avoid conflicts with graphql model 2022-08-22 20:47:37 +02:00
Moriz Wahl
6425e5d172 seed categories on db:migrate init 2022-08-22 19:44:20 +02:00
Wolfgang Huß
49e4111def Fix to set 'sendNotificationEmails' on admin of db init
- 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`.
2021-09-29 10:32:51 +02:00
Moriz Wahl
75485fe237 linting 2020-12-21 10:07:43 +01:00
Moriz Wahl
3f02ade329 createdAt converted toString in Email 2020-12-21 09:52:45 +01:00
Moriz Wahl
cee3317918 default user can login 2020-12-18 09:40:04 +01:00
Moriz Wahl
4fd136c625 Default user is created but cannot login sofar 2020-12-17 19:56:41 +01:00
roschaefer
276ea79e8f Update prettier to v2 2020-03-24 21:11:11 +01:00
Moriz Wahl
7d29400ef9 tag fulltext index added to store 2020-03-19 15:44:30 +01:00
roschaefer
e343701057 Reverted a couple changes by @mattwr18
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)
2020-01-23 17:38:31 +01:00
mattwr18
28dae1f854 Update docs, follow @roschaefer suggestions
- 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
2020-01-23 15:44:34 +01:00
mattwr18
561889c530 Add migration to merge duplicate Locations
- 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.
2020-01-22 13:19:38 +01:00
roschaefer
a86b26a756 Various fixes for data migrations
* Add unique index for `Migration`s
* Fix proper use of `next` callback. First argument is potential error.
* Update migration template
2020-01-20 17:25:36 +01:00
roschaefer
98a4521ecc Add back missing search constraint 2020-01-20 11:28:36 +01:00
roschaefer
b063847849 refactor: Make db:setup init stage of migrate 2020-01-20 11:00:52 +01:00
roschaefer
daf2c40cae Implement Neo4J store for migrate 2020-01-20 10:59:15 +01:00