You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: waspc/ChangeLog.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,10 @@ app todoApp {
17
17
}
18
18
```
19
19
20
+
### 🐞 Bug fixes / 🔧 small improvements
21
+
- Changed the minimum number of machines that a server app is using when deployed to Fly.io from 0 to 1. This prevents the server app from shutting down when there are no requests to it. There might be some other work that the server is doing e.g. running periodic Jobs or sending e-mails, so we want to make sure that the server is always running.
Copy file name to clipboardExpand all lines: web/docs/advanced/deployment/cli.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,19 +47,23 @@ wasp deploy fly create-db mia
47
47
wasp deploy fly deploy
48
48
```
49
49
50
-
The commands above use the app basename `my-wasp-app` and deploy it to the _Miami, Florida (US) region_ (called `mia`).
50
+
The commands above use the app basename `my-wasp-app` and deploy it to the _Miami, Florida (US) region_ (called `mia`). Read more about Fly.io regions [here](#flyio-regions).
51
+
52
+
:::caution Unique Name
53
+
Your app name must be unique across all of Fly or deployment will fail.
54
+
:::
51
55
52
56
The basename is used to create all three app tiers, resulting in three separate apps in your Fly dashboard:
53
57
54
58
-`my-wasp-app-client`
55
59
-`my-wasp-app-server`
56
60
-`my-wasp-app-db`
57
61
58
-
:::caution Unique Name
59
-
Your app name must be unique across all of Fly or deployment will fail.
60
-
:::
62
+
You'll notice that Wasp creates two new files in your project root directory:
63
+
-`fly-server.toml`
64
+
-`fly-client.toml`
61
65
62
-
Read more about Fly.io regions [here](#flyio-regions).
66
+
You should include these files in your version control so that you can deploy your app with a single command in the future.
63
67
64
68
### Using a Custom Domain For Your App
65
69
@@ -159,6 +163,8 @@ It accepts the following arguments:
159
163
After running `setup`, Wasp creates two new files in your project root directory: `fly-server.toml` and `fly-client.toml`.
160
164
You should include these files in your version control.
161
165
166
+
You **can edit the `fly-server.toml` and `fly-client.toml` files** to further configure your Fly deployments. Wasp will use the TOML files when you run `deploy`.
167
+
162
168
If you want to maintain multiple apps, you can add the `--fly-toml-dir <abs-path>` option to point to different directories, like "dev" or "staging".
0 commit comments