Cloudron Forum

@harryz A way to migrate the data is:

Create a backup of the app Install a new app instance with Cloudron user management Import the backup into new instance . https://docs.cloudron.io/backups/#import-app-backup

Please double, no triple check the user management setup after import. The reason we don't have an easy way to change the SSO is because each app acts very differently when moving auth providers. Especially creation of default accounts, admin accounts, registration etc is all very app specific.

@joseph Thanks for this! I was trying to wrap it up last night so I decided to just reset all the users passwords to a known password, and then send them a password reset link to change it to their old password on their own. I will definitely keep the group approach in mind next time I'm migrating to Cloudron - but my next server likely won't migrate until XMPP gets some love 😉 ( https://forum.cloudron.io/topic/10465/xmpp-server-prosody/26?_=1723504540984 )

@nebulon

Okay, thank you very much.

I think it could be good also keep some options for non-developers that allow users to import and export mailboxes, avoiding REST APIs that require deep knowledge of development. This aligns with part of Cloudron's payoff: 'Self-hosting has never been simpler.'

Thank you very much!

You can run the CLI tool on Cloudron like https://docs.cloudron.io/apps/mattermost/#command-line-tool . Instead of the import command at https://docs.cloudron.io/apps/mattermost/#migration , use the export command.

To get a file off Cloudron, easiest way is to export to a path under /app/data and then use the File manager to download it.

I am also curious why you are not able to update mattermost on Cloudron. It's all automatic.

@ekevu123 good idea!

This was sorted out in support.

This is fixed in master as well now.

Fixed for next release with https://git.cloudron.io/cloudron/box/-/commit/93d4271bce299c1d3aba9036f8d15805adaa1f2e

@roofboard There's an example of how to use a bearer token here: https://forum.cloudron.io/post/65043

Looks like this in N8N for single use:
05b953ab-3962-44e9-815d-69d7fa842c10-image.png

To reuse it in all nodes, this should work:
https://community.n8n.io/t/how-to-authorize-using-bearer-token/25674

@p44 This is a bug in the current release, which is already fixed. To workaround, put the backup somewhere in the filesystem and import using the Filesystem provider.

@jayonrails We just started on it, so will take a month probably atleast.

Thanks @d19dotca and @girish

Would love to see streamlined options for Local "desktop/workstation" backups and restore process for apps and Cloudron.

I believe there is a large segment of non tech savvy users who want to use something like Cloudron (for instance those interested in de googling/ taking control of their data) who currently will not because backing up using buckets adds significant cost and overhead. The cost of a Cloudron license, server rental and bucket adds up quickly and for many having a manually saved backup is enough. It makes it easier to justify purchasing a Cloudron license.

@girish said in How to upload/import app backup in Cloudron:

Can you make a feature request and link to this post?

Filed it here: https://forum.cloudron.io/topic/8359/ability-to-import-backups-from-computer-disk-rather-than-needing-to-scp-files/1

We'll set up an fresh instance. This is quite simpler.
thanks for help!!!

@jdaviescoates Thank you too. This was the solution I needed.

@mdreira It should clean them up.

For a start, the next version will require the user to add an encryption password if the backup config indicates that the backup is encrypted.

@girish Thanks!

One other note, the .sql file originally failed to upload due to the dump having the following line:

Create SCHEMA public;

I commented that out and the import ran fine. I'm guessing there is a command to dump the Postgres DB without a create statement but someone smarter than me probably knows it. I haven't used Postgres a day in my life until yesterday so I'm still getting to know it. I have only used MySQL, Maria and MS SQL and all of those have an option to dump without the create statement, but I figured it was just easier to comment that line out of the SQL file instead of looking up the command and doing a new dump.