-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add --db-image
argument to wasp deploy railway
#3184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
00b0ad6
717acb5
7a84c2a
f5c05cf
45862be
c276d57
dee1cbc
984c58a
0d82d87
3c76921
7798922
8c9c0dd
4217d57
97ad6e9
5f66ed4
91b92db
3d67589
12a0177
09b1f8e
7d91499
143d365
f23dfab
aeca0f1
c130a77
f38591d
c682352
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,6 +5,7 @@ | |
### 🎉 New Features | ||
|
||
- You can now specify which PostgreSQL image to use in `wasp start db` with the `--db-image` argument. ([#3182](https://github.com/wasp-lang/wasp/pull/3182)) | ||
- You can now specify which PostgreSQL image to use in `wasp deploy railway` with the `--db-image` argument. ([#3184](https://github.com/wasp-lang/wasp/pull/3184)) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Again, I'd list this as a feature :) Btw, please bump the version in waspc.cabal to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I will wait until we decided on the postmortem There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we decided we want to bump right away, does this make this comment actionable now? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I did it on here since I don't want to mix concerns in the same PR, we can merge that one first |
||
|
||
### 🐞 Bug fixes | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
import CodeBlock from '@theme/CodeBlock' | ||
|
||
#### Using a custom PostgreSQL database | ||
|
||
By default, Wasp uses the standard PostgreSQL image provided by Railway when creating a new database for your app. However, if your application requires specific PostgreSQL extensions (e.g., PostGIS), you can specify a Docker image with a custom PostgreSQL installation, with the `--db-image <docker-image>` flag. | ||
|
||
:::tip | ||
You only need to specify the Docker image once, when first creating the app. | ||
::: | ||
|
||
<CodeBlock language="shell">{ | ||
`# Use PostGIS: | ||
wasp deploy railway ${props.command} my-wasp-app --db-image postgis/postgis | ||
` | ||
}</CodeBlock> | ||
|
||
<CodeBlock language="shell">{ | ||
`# Use pgvector: | ||
wasp deploy railway ${props.command} my-wasp-app --db-image pgvector/pgvector:pg16 | ||
` | ||
}</CodeBlock> | ||
|
||
The service name will always be `Postgres`, regardless of the image used. |
Uh oh!
There was an error while loading. Please reload this page.