Repository navigation
docs: Add guide for migrating a self-hosted database to Cloud - #853
Merged
Merged
Conversation
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Co-authored-by: Jamiu Okanlawon <50176100+developerjamiu@users.noreply.github.com>
Isakdl
requested changes
Sep 24, 2026
Isakdl
left a comment
Isakdl
left a comment
Contributor
There was a problem hiding this comment.
Very cool to get this in, I got some suggestions here and there.
This was referenced Sep 24, 2026
developerjamiu
added
the
documentation
developerjamiu
approved these changes
Sep 28, 2026
Contributor
|
@Isakdl all your threads are addressed; could you take another look? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes: serverpod/serverpod#5768
Closes: serverpod/serverpod#5769
Adds a guide for moving a self-hosted database (Serverpod and PostgreSQL in Docker, for example on a VPS) into a Cloud project. Nothing covers this today, and the obvious
pg_dumpandpg_restore --data-onlyroute fails on the tables Cloud writes itself.--data-onlyat the source, which orders tables by foreign key. A full dump restored with--data-onlyfails onserverpod_auth_core_profile.--exclude-table-datacovers the data Cloud writes on each deploy, each pattern keeping a trailing*so the table's ID sequence is left out too.emailSecretHashPepperand the JWT keys are copied before any user rows land, otherwise sign-in fails withinvalidCredentialsand the first refresh deletes the session.serverpod_auth_core_profileandserverpod_auth_core_profile_imagereference each other and the Cloud database user cannot disable triggers.Every step run against a Cloud project on the starter plan, with a Docker Compose source on PostgreSQL 16, at Serverpod 4.0.0 and Cloud CLI 1.0.0.