Run database migrations in job to allow scaling #17
No reviewers
Labels
No labels
Security
TeX
board
done
board
ready
board
todo
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
source::aleksolotl
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-k8s!17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "add-migrations-job"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
added 1 commit
24ec8ec5- Add job for migrationsCompare with previous version
Waiting for AlekSIS/official/AlekSIS-Core!551
assigned to @nik
added 1 commit
074d79de- Fix run_modeCompare with previous version
added 5 commits
master25af2294- Merge branch 'master' into add-migrations-jobCompare with previous version
(For consistency with naming in
docker-startup)This is wrong. It shadows
docker-startup, and thepreparerun mode will never run. In doing so, it misses out on parts, e.g. oncreateinitialrevisions.Please check when the superuser is created. If it is created in a migration (or post-migrate hook), this is correct, but in that case, please strip this environment from all other contianers as they do not need it anymore in that case. If it is reated outside migrations, remove this environment from the job ocntianer instead.
The full
preparemode also generates static files, so you need to mount all volumes.How is this job linked to the deployment? How do you ensure it is run whenever a new image version is pulled, or whatever might cause the database to get outdated? In other words: When is this job run, and how is that defined?
The necessary changes to disable preparation in all othe rcontainers are missing.
resolved all threads
changed this line in version 5 of the diff
changed this line in version 5 of the diff
added 1 commit
Compare with previous version
fixed
resolved all threads
added 1 commit
ce563a24- Mount all volumes in jobCompare with previous version
added 1 commit
d43c743d- Add gitignoreCompare with previous version
added 2 commits
a740f411- 1 commit from branchmaster6ef5d697- Merge branch 'master' into add-migrations-jobCompare with previous version
added 1 commit
189dc2ba- Fix indentationCompare with previous version
changed this line in version 10 of the diff
added 1 commit
1d358572- Fix indentationCompare with previous version
added 1 commit
b3be882b- Fix valuesCompare with previous version
added 1 commit
5c48f686- Run after upgradeCompare with previous version
added 1 commit
27bfe0a0- Fix indentation of volumesCompare with previous version
added 2 commits
519846f3- 1 commit from branchmasterb35adfad- Merge branch 'master' into add-migrations-jobCompare with previous version
added 1 commit
daaf7251- Remove apps path from gitignoreCompare with previous version
mentioned in commit
d58e38b069