Advice needed for changing name of fly app.
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.
3 Replies
Hi @Sven. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Wasp’s docs and issues don’t describe a “rename Fly app” flow or a turnkey “migrate everything to a new Fly app” procedure, so I can’t give you a precise, supported step‑by‑step for moving data between two Fly apps. The general pattern, however, is:
1. Create a new Fly app with the new name via Wasp
Use the Wasp CLI to set up a fresh Fly deployment (with a different app basename) and let Wasp create the new
2. Configure env vars / secrets on the new server app
Make sure all server‑side secrets are set on the new
This is the critical bit, and it is not documented in Wasp’s docs or the linked issues. They only cover creating/using a Fly Postgres DB and setting
Because of that, I can’t give you a Wasp‑specific, officially documented procedure for exporting from the old
- If you’ll use a custom domain for the new app, you can follow the same steps as in the existing “Using a Custom Domain” section—create certs on the new client app and set
- If you’re deploying the client separately (e.g., Netlify), make sure any
After you’ve confirmed the new name and deployment work, you can safely remove the old Fly apps. Wasp’s docs mention destroying apps if setup fails and Fly doesn’t allow reusing names, but they don’t walk through a full “rename/migrate” scenario. [Manual Fly setup; unique-name issue] Because the Wasp docs don’t cover DB data transfer between Fly apps, I can’t guarantee a no‑data‑loss migration path purely from the provided material. For the data‑migration step specifically, you’ll need to rely on Fly/Postgres documentation or support. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Sven, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
Use the Wasp CLI to set up a fresh Fly deployment (with a different app basename) and let Wasp create the new
*-server, *-client, and *-db apps plus the fly-server.toml / fly-client.toml files for that new name. [Deploying with CLI; setup]2. Configure env vars / secrets on the new server app
Make sure all server‑side secrets are set on the new
*-server app (JWT secret, social auth secrets, etc.) the same way you did for the original app. Wasp’s docs show using --server-secret when launching, or Fly secrets directly for manual deploys. [launch; manual Fly setup]
3. Migrate database data from old DB app to new DB appThis is the critical bit, and it is not documented in Wasp’s docs or the linked issues. They only cover creating/using a Fly Postgres DB and setting
DATABASE_URL, not copying data between DBs. [Manual Fly setup]Because of that, I can’t give you a Wasp‑specific, officially documented procedure for exporting from the old
*-db and importing into the new one. You would need to follow Fly/Postgres–level instructions for dump/restore or similar, which are outside the scope of the Wasp docs we have.
4. Point your client and custom domain (if any) at the new app- If you’ll use a custom domain for the new app, you can follow the same steps as in the existing “Using a Custom Domain” section—create certs on the new client app and set
WASP_WEB_CLIENT_URL on the new server app. [Custom domain]- If you’re deploying the client separately (e.g., Netlify), make sure any
WASP_SERVER_URL / WASP_WEB_CLIENT_URL secrets or build‑time env vars reference the new Fly server domain (or your new custom domain). [Manual Fly deploy; manual setup envs]
5. Retire the old Fly apps once you’ve verified everythingAfter you’ve confirmed the new name and deployment work, you can safely remove the old Fly apps. Wasp’s docs mention destroying apps if setup fails and Fly doesn’t allow reusing names, but they don’t walk through a full “rename/migrate” scenario. [Manual Fly setup; unique-name issue] Because the Wasp docs don’t cover DB data transfer between Fly apps, I can’t guarantee a no‑data‑loss migration path purely from the provided material. For the data‑migration step specifically, you’ll need to rely on Fly/Postgres documentation or support. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Sven, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
ANyone that can help?
Have you tried doing what the bot suggested? It's a pretty solid advice, you'll need to figure out how to migrate the Postgres database (but there should be enough materials on how to migrate Postgres DB from one Fly DB to another)