Updating existing installations
When you make a new release for WASP or OpenSaaS is there a way for existing installations to merge new changes to live installations without breakage? If there is no system for doing this then existing installations will be stuck with older bugs and miss out on new features
2 Replies
Hi @cassofthenight. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Yes, there are ways to update your existing Wasp installations and projects to incorporate new changes and features. Here's how you can do it:
1. Update Wasp CLI: The Wasp CLI (Command Line Interface) is a binary that you install on your machine. To update it, you need to install the new version on your development machine. This is done by running the installer script again with
curl -sSL <https://get.wasp-lang.dev/installer.sh> | sh. If you already have Wasp installed, it will tell you to run it a bit differently to overwrite those files[^1^][^5^].
2. Update Your Project: Once you've updated the Wasp CLI, you'll need to update the codebase of your app to work with the newer version of Wasp. For significant breaking changes, the Wasp team provides detailed instructions and even scripts that do part of the job for you[^1^].
3. Deploy Your Updated App: After making updates to your app, you can deploy the changes using the wasp deploy command[^2^]. If you're deploying manually, you'll need to run wasp build to rebuild your app, then run railway up in the .wasp/build directory for the server, and repeat all the steps in the .wasp/build/web-app directory for the client[^3^].
Please note that the process of updating Wasp is being improved to make it easier and more intuitive[^5^]. In the future, there might be a wasp update or wasp upgrade command that simplifies the process[^4^][^6^].
^1^]: [Discord Support Thread (https://discord.com/channels/686873244791210014/1210312601158946826)
^2^]: [Wasp CLI Deploy Documentation (https://wasp-lang.dev/docs/advanced/deployment/cli#deploy)
^3^]: [Wasp Manual Deployment Documentation (https://wasp-lang.dev/docs/advanced/deployment/manually#updates--redeploying)
^4^]: [Github Issue 111 (https://github.com/wasp-lang/wasp/issues/111)
^5^]: [Github Issue 616 (https://github.com/wasp-lang/wasp/issues/616)
^6^]: [Github Issue 616 Comments Part 1 (https://github.com/wasp-lang/wasp/issues/616)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @cassofthenight, 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?Wasp is versioned, same like let's say Node -> so you can upgrade your project to new version of Wasp. With each breaking cahgne we also produce migration instrutions to help with migrating. So yeah, definitiely!
For OpenSaas we don't expect you to upgrade because it is a template, boilerplate -> we expect you modified it to your needs so there is no direct way to upgrade it. It is a starting point. But, since OpenSaas is not so complex, manually porting some of the updates if you really want them shouldn't be too hard!