Migration instructions for Dockerfile (#1808)

This commit is contained in:
Mihovil Ilakovac 2024-02-23 17:28:14 +01:00 committed by GitHub
parent f3428c7412
commit 5634481dff
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -361,6 +361,16 @@ module.exports = {
</TabItem>
</Tabs>
### Default Server Dockerfile Changed
:::note
If you didn't customize your Dockerfile or had a custom build process for the Wasp server, you can skip this section.
:::
Between Wasp 0.11.X and 0.12.X, the Dockerfile that Wasp generates for you for deploying the server has changed. If you defined a custom Dockerfile in your project root dir or in any other way relied on its contents, you'll need to update it to incorporate the changes that Wasp 0.12.X made.
We suggest that you temporarily move your custom Dockerfile to a different location, then run `wasp start` to generate the new Dockerfile.
Check out the `.wasp/out/Dockerfile` to see the new Dockerfile and what changes you need to make. You'll probably need to copy some of the changes from the new Dockerfile to your custom one to make your app work with Wasp 0.12.X.
### Migrating to the New Auth
As shown in [the previous section](#new-auth), Wasp significantly changed how authentication works in version 0.12.0.
This section leads you through migrating your app from Wasp 0.11.X to Wasp 0.12.X.