Easiest way to migrate NocoDB (PostgreSQL) from Pikapods to Cloudron?
-
Hi,
Currently, I have a NocoDB instance hosted on Pikapods and I would like to migrate it to my Cloudron server.
Pikapods use PostgreSQL for NocoDB, which is the same DB as Cloudron. Based on their documentation, it is possible to have access to the database using this guide.
Does anyone already moved its NocoDB instance to Cloudron, and could share his process, or any guide/tutorial he followed? That would be greatly appreciated!
Also, I have a few automations already set up in Zapier using NocoDB webhooks, if I keep the same domain and same DB, will my automation still work after migrating?
I am not an expert and don't know much about PostgreSQL but the way I think I can do it (I may be totally wrong though) is that I can dump the SQL data from Pikapod in a single file (E.g. nocodb.sql), then rename it the same as Cloudron SQL (Let's say that after creating my instance of NocoDB in Cloudron, the SQL file that has been created is named "cloudron-nocodb.sql", then I can simply rename nocodb.sql to cloudron-nocodb.sql and replace it with the one on the server via ssh or file manager??), and then just update the PostgreSQL user and password in the ENV setting inside Cloudron.
Does my plan make sense? Thanks
-
Hi,
Currently, I have a NocoDB instance hosted on Pikapods and I would like to migrate it to my Cloudron server.
Pikapods use PostgreSQL for NocoDB, which is the same DB as Cloudron. Based on their documentation, it is possible to have access to the database using this guide.
Does anyone already moved its NocoDB instance to Cloudron, and could share his process, or any guide/tutorial he followed? That would be greatly appreciated!
Also, I have a few automations already set up in Zapier using NocoDB webhooks, if I keep the same domain and same DB, will my automation still work after migrating?
I am not an expert and don't know much about PostgreSQL but the way I think I can do it (I may be totally wrong though) is that I can dump the SQL data from Pikapod in a single file (E.g. nocodb.sql), then rename it the same as Cloudron SQL (Let's say that after creating my instance of NocoDB in Cloudron, the SQL file that has been created is named "cloudron-nocodb.sql", then I can simply rename nocodb.sql to cloudron-nocodb.sql and replace it with the one on the server via ssh or file manager??), and then just update the PostgreSQL user and password in the ENV setting inside Cloudron.
Does my plan make sense? Thanks
@igaudette said in Easiest way to migrate NocoDB (PostgreSQL) from Pikapods to Cloudron?:
Also, I have a few automations already set up in Zapier using NocoDB webhooks, if I keep the same domain and same DB, will my automation still work after migrating?
Yes, since the automation is based on domains and the database is migrated (and thus keeping existing any api tokens and configuration), it should all work.
Famous last words
-
Hi,
Currently, I have a NocoDB instance hosted on Pikapods and I would like to migrate it to my Cloudron server.
Pikapods use PostgreSQL for NocoDB, which is the same DB as Cloudron. Based on their documentation, it is possible to have access to the database using this guide.
Does anyone already moved its NocoDB instance to Cloudron, and could share his process, or any guide/tutorial he followed? That would be greatly appreciated!
Also, I have a few automations already set up in Zapier using NocoDB webhooks, if I keep the same domain and same DB, will my automation still work after migrating?
I am not an expert and don't know much about PostgreSQL but the way I think I can do it (I may be totally wrong though) is that I can dump the SQL data from Pikapod in a single file (E.g. nocodb.sql), then rename it the same as Cloudron SQL (Let's say that after creating my instance of NocoDB in Cloudron, the SQL file that has been created is named "cloudron-nocodb.sql", then I can simply rename nocodb.sql to cloudron-nocodb.sql and replace it with the one on the server via ssh or file manager??), and then just update the PostgreSQL user and password in the ENV setting inside Cloudron.
Does my plan make sense? Thanks
@igaudette I would go about the importing like this:
-
Install a fresh NocoDB on Cloudron. Make sure the version of NocoDB on Cloudron PikaPods matches!
-
Then, upload and import the db dump from PikaPods into Cloudron. See https://docs.cloudron.io/guides/import-postgresql/ on how to do this .
-
If you had set up some custom configuration from https://docs.nocodb.com/getting-started/installation/#environment-variables in pika pods, then you have to put those in Cloudron in
/app/data/envusing File manager .
Let us know how it goes!
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login