Wasp•15mo ago

Update / maintain production deployment

Lets say i deploy to fly my V1 of my app. How would i then maintain it and for example update it without having users loose data.

Let say i add a new page and some new actions locally. How can i push these to fly?

kapa.ai•10/19/24, 2:47 PM

Hi @Sven. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

kapa.ai•10/19/24, 2:48 PM

----------------------
To update your deployed app on Fly with the latest changes, you can use the

wasp deploy

wasp deploy

command. Here's how you can do it:

wasp deploy fly deploy

wasp deploy fly deploy

This command pushes your client and server live. Run this command whenever you want to update your deployed app with the latest changes [^1^].

If you are deploying manually, for example on Railway, you would need to run

wasp build

wasp build

to rebuild your app and then

railway up

railway up

in the

.wasp/build

.wasp/build

directory (server). Repeat all the steps in the

.wasp/build/web-app

.wasp/build/web-app

directory (client) [^3^].

When it comes to data migrations, it's important to have a good migration workflow and documentation for production. This is especially crucial when you're updating your app to ensure users don't lose data [^9^].

If you need to modify the server code a bit to execute some code after login / after signup, you can modify the

.wasp/out

.wasp/out

files. However, when deploying to Fly, Wasp builds a fresh build in

.wasp/build

.wasp/build

so those manual changes won't be deployed. One way to solve this is to have a "patched" version of the file you need to modify, somewhere in the project root. Then you provide your own custom

Dockerfile

Dockerfile

(which can be just the copy-paste version of the

Dockerfile

Dockerfile

.wasp/build

.wasp/build

folder). In that

Dockerfile

Dockerfile

include a line with something like

cp ./my-patched-file.js server/something/somewhere.js

cp ./my-patched-file.js server/something/somewhere.js

[^2^].

[^1^]: (source: https://wasp-lang.dev/docs/advanced/deployment/cli#deploy)
[^2^]: (source: 🙋questionsIssue with deploying my wasp app to fly.io)
[^3^]: (source: https://wasp-lang.dev/docs/advanced/deployment/manually#updates--redeploying)
[^9^]: (source: https://github.com/wasp-lang/wasp/issues/330)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•10/19/24, 2:48 PM

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?

SvenOP•10/19/24, 2:49 PM

Huh?

sachdva•10/19/24, 8:02 PM

A migration doesn't break your production database
Use wasp deploy fly deploy to deploy to prod

SvenOP•10/19/24, 8:47 PM

Ahh so then it updates all stuff

SvenOP•10/19/24, 8:47 PM

And lets say i add an env var i use -server-secret?

SvenOP•10/19/24, 8:47 PM

Or secret set

Ssachdva A migration doesn't break your production database Use wasp deploy fly deploy t...

SvenOP•10/19/24, 8:47 PM

Thanks to

SSven And lets say i add an env var i use -server-secret?

sachdva•10/19/24, 9:32 PM

It's in the wasp deploy docs but yeah something like that

Ssachdva A migration doesn't break your production database Use wasp deploy fly deploy t...

wardbox•10/19/24, 9:37 PM

This is not in all cases, it depends what you’re changing. Some migrations can require manual intervention

Wwardbox This is not in all cases, it depends what you’re changing. Some migrations can r...

SvenOP•10/19/24, 9:37 PM

Hmm why is that?

wardbox•10/19/24, 9:38 PM

Let’s say you have a field that’s a string in prod, if you’re changing it to a Date field you’re going to run into issues

wardbox•10/19/24, 9:39 PM

If you do migrate dev locally and it runs into issues like that, the same thing will happen in prod. You can ssh to the db and fix it in that case though

MEE6•10/19/24, 9:39 PM

Wohooo @wardbox, you just became a Waspeteer level 9!

wardbox•10/19/24, 9:45 PM

Usually when I need to change a field like that i add a brand new field with a slightly different name, leave the old one and make it optional if it isn’t already, and update references to the field to use the new one with the new type. Then once all references to the old field are eventually not in use you can just remove the old field from the schema

wardbox•10/19/24, 9:45 PM

But if you aren’t changing types or adding unique constraints, most of the time the migration is fine

SvenOP•10/19/24, 10:14 PM

Yeah thanks clear

Wwardbox This is not in all cases, it depends what you’re changing. Some migrations can r...

sachdva•10/20/24, 7:01 AM

Sure - I agree, any migration that requires manual intervention on your local development side as well.
So when wasp db-migrate dev requires manual intervention then manual intervention in prod -- if you or anyone from wasp could make a slight guide or tell me some tips about how to do this this would be great.

This is the only part which I'm queasy about. The SQL migrations when new fields are added - do you have any helpful tips/links about that?

MEE6•10/20/24, 7:01 AM

Wohooo @Adam, you just became a Waspeteer level 4!

Ssachdva Sure - I agree, any migration that requires manual intervention on your local de...

wardbox•10/20/24, 8:02 AM

https://www.prisma.io/dataguide/types/relational/migration-strategies

not wasp specific, but this outlines strategies for handling migrations

Prisma's Data Guide

Migrating database schema changes | Prisma's Data Guide

Learn about the advantages and disadvantages of various techniques for deploying schema changes to your database.

sachdva•10/20/24, 8:26 AM

Awesome thanks!

Wwardbox https://www.prisma.io/dataguide/types/relational/migration-strategies not wasp ...

SvenOP•10/20/24, 6:55 PM

But ward,

Lets say I changed somethings on the frontend. And added some actions. How would i makensure these changes get to production? After i already deployed the first version?

wardbox•10/20/24, 7:13 PM

You just do a new deploy

Wwardbox You just do a new deploy

SvenOP•10/20/24, 7:50 PM

any tips on connecting to prod. database with ext tools?

SvenOP•10/20/24, 7:50 PM

to view tables

wardbox•10/20/24, 7:53 PM

@kapa.ai how do you connect over wireguard to fly.io Postgres database with wasp db studio

kapa.ai•10/20/24, 7:53 PM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•10/20/24, 7:53 PM

----------------------
To connect to your Fly production database, you can open up a tunnel with the following command:

fly proxy 5432 -a <db-name>

fly proxy 5432 -a <db-name>

After setting up the tunnel, you can execute

wasp db studio

wasp db studio

to interact with your database using Prisma Studio [^1^].

However, please note that you should be careful when interacting with your production database. It's recommended to remove the

DATABASE_URL

DATABASE_URL

with the production database URL from

.env.server

.env.server

after you're done, to avoid accidentally making unwanted changes to the production database [^1^].

For more detailed steps on how to seed a production database, you can refer to this Github issue (https://github.com/wasp-lang/wasp/issues/1464) [^5^].

[^1^]: (source: 🙋questionsHow to interact with database in prisma studio after deployment?)
[^5^]: (source: https://github.com/wasp-lang/wasp/issues/1464)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•10/20/24, 7:53 PM

Sorry @wardbox, 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?

Kkapa.ai ---------------------- To connect to your Fly production database, you can open ...

SvenOP•10/20/24, 8:37 PM

@kapa.ai how i ran the fly proxy 5432 -a <db-name>
, how can i now show the prisma studio in browser?

kapa.ai•10/20/24, 8:37 PM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•10/20/24, 8:37 PM

----------------------
After you've set up the tunnel with

fly proxy 5432 -a <db-name>

fly proxy 5432 -a <db-name>

, you can run Prisma Studio with the following command:

wasp db studio

wasp db studio

This command will start Prisma Studio and automatically open it in your default web browser [^1^].

Please ensure that you've set the correct

DATABASE_URL

DATABASE_URL

in your

.env.server

.env.server

file. If Prisma Studio fails to connect, it might be due to an incorrect

DATABASE_URL

DATABASE_URL

(wrong password or database name), or something else might already be running on port 5432 [^5^].

[^1^]: (source: 🙋questionsHow to interact with database in prisma studio after deployment?)
[^5^]: (source: https://github.com/wasp-lang/wasp/issues/1464)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•10/20/24, 8:37 PM

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?

Wwardbox @kapa.ai how do you connect over wireguard to fly.io Postgres database with wasp...

SvenOP•10/20/24, 9:17 PM

ah cool clear. now i also have my own server. What I want it for it to fill the production database table "datatable" with data everyday (python). I already have it working with a different postgres db. but how would i connect to it using my production DB?

SvenOP•10/20/24, 9:18 PM

psycopg2 is what i use.

wardbox•10/20/24, 9:19 PM

Not sure, I haven’t used python with wasp

Wwardbox Not sure, I haven’t used python with wasp

SvenOP•10/20/24, 9:19 PM

ahh but like how could i connect from an external server?
what credentials do i use?

SvenOP•10/20/24, 9:20 PM

@kapa.ai I have an app running on a server, how can iconnect to my production database (fly) through this python app? I want the app to inset data into a table everyday/

kapa.ai•10/20/24, 9:20 PM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•10/20/24, 9:21 PM

----------------------
To connect to your production database from a Python app, you'll need to use a PostgreSQL client for Python, such as

psycopg2

psycopg2

sqlalchemy

sqlalchemy

. You'll also need the connection details for your database, which include the host, port, database name, username, and password.

Here's a basic example of how you might establish a connection using

psycopg2

psycopg2

import psycopg2

# Replace these with your actual values
host = "localhost"
port = "5432"
dbname = "<db_name>"
user = "postgres"
password = "<password>"

# Establish a connection
conn = psycopg2.connect(
    host=host,
    port=port,
    dbname=dbname,
    user=user,
    password=password
)

# Create a cursor object
cur = conn.cursor()

# Execute a query
cur.execute("SELECT * FROM your_table")

# Fetch all rows from the last executed statement
rows = cur.fetchall()

# Close the connection
conn.close()

import psycopg2

# Replace these with your actual values
host = "localhost"
port = "5432"
dbname = "<db_name>"
user = "postgres"
password = "<password>"

# Establish a connection
conn = psycopg2.connect(
    host=host,
    port=port,
    dbname=dbname,
    user=user,
    password=password
)

# Create a cursor object
cur = conn.cursor()

# Execute a query
cur.execute("SELECT * FROM your_table")

# Fetch all rows from the last executed statement
rows = cur.fetchall()

# Close the connection
conn.close()

To get the connection details, you can use the

fly postgres connect -a <db-name>

fly postgres connect -a <db-name>

command to get the DB name [^5^]. For the DB password, you can use the

fly ssh console -a <db-name>

fly ssh console -a <db-name>

command and then

echo $OPERATOR_PASSWORD

echo $OPERATOR_PASSWORD

[^5^].

Please note that this is a basic example and doesn't include error handling or other best practices for working with databases in Python. You'll also need to install the

psycopg2

psycopg2

package, which you can do with

pip install psycopg2

pip install psycopg2

.

For inserting data into a table every day, you might want to look into using a task scheduler like cron on Unix-based systems, or Task Scheduler on Windows.

[^5^]: (source: https://github.com/wasp-lang/wasp/issues/1464)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•10/20/24, 9:21 PM

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?

kapa.ai•10/20/24, 9:21 PM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•10/20/24, 9:21 PM

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?

SvenOP•10/20/24, 9:22 PM

but this is for localhost, how can i conect from a app running on a server? @kapa.ai

kapa.ai•10/20/24, 9:22 PM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•10/20/24, 9:22 PM

----------------------
To connect to your Fly production database from a Python app running on a server, you'll need to replace the

localhost

localhost

in the connection string with the actual host of your Fly database.

The host is typically a URL or IP address that points to the location of your database on the internet. You can find this information in the settings or configuration of your Fly database.

Here's how you might modify the previous Python code:

import psycopg2

# Replace these with your actual values
host = "<your-fly-db-host>"
port = "5432"
dbname = "<db_name>"
user = "postgres"
password = "<password>"

# Establish a connection
conn = psycopg2.connect(
    host=host,
    port=port,
    dbname=dbname,
    user=user,
    password=password
)

# Create a cursor object
cur = conn.cursor()

# Execute a query
cur.execute("SELECT * FROM your_table")

# Fetch all rows from the last executed statement
rows = cur.fetchall()

# Close the connection
conn.close()

import psycopg2

# Replace these with your actual values
host = "<your-fly-db-host>"
port = "5432"
dbname = "<db_name>"
user = "postgres"
password = "<password>"

# Establish a connection
conn = psycopg2.connect(
    host=host,
    port=port,
    dbname=dbname,
    user=user,
    password=password
)

# Create a cursor object
cur = conn.cursor()

# Execute a query
cur.execute("SELECT * FROM your_table")

# Fetch all rows from the last executed statement
rows = cur.fetchall()

# Close the connection
conn.close()

Remember to replace

<your-fly-db-host>

<your-fly-db-host>

<db_name>

<db_name>

, and

<password>

<password>

with your actual database host, database name, and password respectively.

Please note that exposing your database to the public internet can have security implications. It's recommended to secure your database connection, for example by using SSL/TLS encryption or by setting up a VPN or SSH tunnel. You might also want to restrict access to your database to specific IP addresses or ranges.

For more information on how to connect to your Fly database, you can refer to the Fly documentation (https://fly.io/docs/) or the Fly CLI command reference (https://fly.io/docs/flyctl/).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•10/20/24, 9:22 PM

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?

SvenOP•10/20/24, 9:31 PM

any wasp team that could help, i would like to connect to my fly.io database from a python app running on a server.

SvenOP•10/20/24, 9:31 PM

which does some actoins everyday and inserts data in a table. Is there any way of connecting to my production fly postgres (from a server)?

Any tips? Maybe should i deploy my database somewhere else? And how would I make my app connect to that one then? Just secret set “DATABASE_URL” to my other host? And will this then automaticallly create the tables?

import psycopg2 # Replace these with your actual values host = "localhost" port = "5432" dbname = "<db_name>" user = "postgres" password = "<password>" # Establish a connection conn = psycopg2.connect( host=host, port=port, dbname=dbname, user=user, password=password ) # Create a cursor object cur = conn.cursor() # Execute a query cur.execute("SELECT * FROM your_table") # Fetch all rows from the last executed statement rows = cur.fetchall() # Close the connection conn.close()

import psycopg2 # Replace these with your actual values host = "<your-fly-db-host>" port = "5432" dbname = "<db_name>" user = "postgres" password = "<password>" # Establish a connection conn = psycopg2.connect( host=host, port=port, dbname=dbname, user=user, password=password ) # Create a cursor object cur = conn.cursor() # Execute a query cur.execute("SELECT * FROM your_table") # Fetch all rows from the last executed statement rows = cur.fetchall() # Close the connection conn.close()

Update / maintain production deployment

Similar Threads

Similar Threads

Similar Threads