How to change the name of my app while keeping all data in the app?

,
1

Hi, i got a letter where, long story short, they say the name of my app is copyright. So now i deleted the domain from my app and i am left with the initial fly.dev domain. In that domain is still the copyright name so i want to get rid of that, now i know that i can’t change the name just like that.

what is the best way to maybe setup a new app and transfer all data etc to that new app with the new name, without loosing al functionalities and all.

I hope there is a solution to this because I do not want to loose that data.

2

Hi,

The simplest way to do this would be:

  1. create a new app with fly app create new-name
  2. Update your fly.toml so app="new-name"
  3. fly deploy, this will deploy the same code under the new app’s name.

Note that this will not automatically migrate any data or secrets your app may have. You need to move those over somehow, manually.

For secrets, you can just fly secrets set them on the new app.
For data, I can’t provide concrete advice since I don’t know where/how you store your data. It could be as simple as : it uses a database that’s in another app, in that case you should only need to configure the new app to connect to the same database. Or it could be about moving files from one app to the other. This part is really up to you :slight_smile:

Hope this helps!

3

It sounds like you own an app, but do not know how it works. That’s unusual on a platform built for engineers. Are you vibe-coding, or perhaps you’ve purchased a small SaaS? I ask because it is, obviously, a risk to be running technology while not knowing how to maintain it (or, in this case, how to re-platform it).

4

Thanks for the reply, don’t worry about the risks that part is fine. However the only thing i am insecure of is how to safely transfer the data. Especially in a simple way or by reusing a volume for example.

I hop any of you can give tips on what is a proper way.

5

Hi, you can create a snapshot of a volume for app A, and then restore the snapshot on app B, this gives you a copy for the volume on app B, it might be a way to move data you have in volumes.

fly volumes snapshots create -a app_a vol_origin

wait for the snapshot to show as created in fly vol snapshots list vol_origin. Then:

fly volumes create volume_name --snapshot-id vs_the_snapshot --region X --size Y -a app_b

Hope it helps!

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.