Prisma Studio Deployed App (Fly)

1. Open a tunnel to your Fly.io database using the command:

fly proxy 5432 -a <db-name>

fly proxy 5432 -a <db-name>

1. After opening the tunnel, run the following command in your Wasp project directory:

wasp db studio

wasp db studio

.env.server

.env.server

1. Make sure you've run

   wasp db migrate-dev

   wasp db migrate-dev

   before attempting to use Prisma Studio. This command is crucial for setting up your database schema Discord support thread (🙋questions(Resolved) Prisma Error on Mac).
2. If you've made any recent changes to your project, try running

   wasp clean

   wasp clean

   and then

   wasp start

   wasp start

   again. This has helped resolve Prisma-related issues for some users Discord support thread (🙋questions(Resolved) Prisma Error on Mac).
3. Check that your Prisma schema file (usually located at .wasp/out/db/schema.prisma.wasp/out/db/schema.prisma) is correctly configured and that the

   DATABASE_URL

   DATABASE_URL

   in your

   .env.server

   .env.server

   file is set to the correct value for your Fly.io database.
4. Ensure that the tunnel to your Fly.io database is still open and functioning correctly.

1. First, try cleaning your Wasp project and reinstalling dependencies:

   wasp clean
   wasp start

   wasp clean
   wasp start

node_modules

node_modules

1. If the above doesn't work, you can try manually installing the missing package:

   cd .wasp/out/server
   npm install rollup-plugin-esbuild

   cd .wasp/out/server
   npm install rollup-plugin-esbuild

wasp start

wasp start

1. If you're still encountering issues, it might be worth checking if there's a

   package.json

   package.json

   file in a parent directory of your project. Sometimes, this can interfere with Wasp's package management GitHub Issue (https://github.com/wasp-lang/wasp/issues/787).
2. Make sure you're using the latest version of Wasp. You can check your version with

   wasp version

   wasp version

   and upgrade if necessary Discord support thread (🙋questionsIssue with deploying my wasp app to fly.io).

1. Cannot find package 'rollup-plugin-esbuild'Cannot find package 'rollup-plugin-esbuild': This means that the Node.js runtime is unable to locate the rollup-plugin-esbuildrollup-plugin-esbuild package, which is required by your project's build process.
2. Error [ERR_MODULE_NOT_FOUND]Error [ERR_MODULE_NOT_FOUND]: This is a standard Node.js error code indicating that a module (in this case, a package) could not be found in the project's dependencies.
3. The error is occurring in the file /home/rootall/apps/minisaas-boilerplate/app/.wasp/out/server/rollup.config.js/home/rootall/apps/minisaas-boilerplate/app/.wasp/out/server/rollup.config.js: This suggests that the missing package is required for the server-side build configuration of your Wasp project.

• Incomplete or failed package installations
• Conflicts with package versions
• Issues with the Node.js environment

wasp clean

wasp clean

wasp start

wasp start

1. First, make sure you're in your Wasp project directory.
2. Run the following command to set up the server app on Fly.io:

   wasp deploy fly setup <app-name> <region>

   wasp deploy fly setup <app-name> <region>

<app-name>

<app-name>

   wasp deploy fly setup my-wasp-app mia

   wasp deploy fly setup my-wasp-app mia

1. After running the setup, you'll need to create a database for your app:

   wasp deploy fly create-db <region>

   wasp deploy fly create-db <region>

1. Finally, deploy your server:

   wasp deploy fly deploy

   wasp deploy fly deploy

deploy

deploy

wasp deploy fly deploy --server-secret MY_VAR=value

wasp deploy fly deploy --server-secret MY_VAR=value

1. Check your Google Analytics configuration:
   Make sure you have properly set up the Google Analytics configuration in your Wasp file. It should look something like this:

   app MyApp {
     // ...
     client: {
       // ...
       setupGoogleAnalytics: {
         measurementId: "G-XXXXXXXXXX"
       }
     }
   }

   app MyApp {
     // ...
     client: {
       // ...
       setupGoogleAnalytics: {
         measurementId: "G-XXXXXXXXXX"
       }
     }
   }

1. Verify environment variables:
   If you're using environment variables for the Google Analytics configuration, make sure they are properly set on Fly.io. You can set server-side environment variables using the Wasp CLI:

   wasp deploy fly deploy --server-secret GOOGLE_ANALYTICS_ID=your-measurement-id

   wasp deploy fly deploy --server-secret GOOGLE_ANALYTICS_ID=your-measurement-id

1. Check your `googleAnalyticsUtils.ts` file:Review the code in this file, particularly around line 4, to ensure that you're not trying to access an undefined value. Make sure all necessary imports and variables are properly defined.
2. Redeploy your app:After making any necessary changes, redeploy your app using:

   wasp deploy fly deploy

   wasp deploy fly deploy

1. Monitor the logs:
   After redeploying, monitor the Fly.io logs to see if the error persists or if new errors appear.

1. Google Analytics Configuration:
   Make sure your Wasp file (

   main.wasp

   main.wasp

   ) has the correct Google Analytics setup:

   app MyApp {
     // ...
     client: {
       // ...
       setupGoogleAnalytics: {
         measurementId: "G-XXXXXXXXXX"
       }
     }
   }

   app MyApp {
     // ...
     client: {
       // ...
       setupGoogleAnalytics: {
         measurementId: "G-XXXXXXXXXX"
       }
     }
   }

1. Environment Variables:
   Ensure that the Google Analytics measurement ID is properly set as an environment variable on Fly.io. You can set it using the Wasp CLI:

   wasp deploy fly deploy --client-secret REACT_APP_GA_MEASUREMENT_ID=your-measurement-id

   wasp deploy fly deploy --client-secret REACT_APP_GA_MEASUREMENT_ID=your-measurement-id

1. Check `googleAnalyticsUtils.ts`:If possible, review the content of `/app/src/analytics/providers/googleAnalyticsUtils.ts`, particularly around line 4. Make sure it's not trying to access an undefined value.
2. Temporary Disable Google Analytics:If the issue persists, you might want to temporarily disable Google Analytics in your Wasp file to isolate the problem:

   app MyApp {
     // ...
     client: {
       // ...
       // Comment out or remove the setupGoogleAnalytics section
       // setupGoogleAnalytics: {
       //   measurementId: "G-XXXXXXXXXX"
       // }
     }
   }

   app MyApp {
     // ...
     client: {
       // ...
       // Comment out or remove the setupGoogleAnalytics section
       // setupGoogleAnalytics: {
       //   measurementId: "G-XXXXXXXXXX"
       // }
     }
   }

1. Redeploy:
   After making changes, redeploy your app:

   wasp deploy fly deploy

   wasp deploy fly deploy

1. Check Logs:
   After redeploying, monitor the Fly.io logs to see if the error is resolved or if new errors appear.

node -r dotenv/config ./scripts/validate-env.mjs

server@0.0.0 validate-env

1. Set the Google OAuth environment variables:
   You need to set both the GOOGLE_CLIENT_IDGOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRETGOOGLE_CLIENT_SECRET as server secrets on Fly.io. Use the following Wasp CLI command:

   wasp deploy fly deploy --server-secret GOOGLE_CLIENT_ID=your-client-id --server-secret GOOGLE_CLIENT_SECRET=your-client-secret

   wasp deploy fly deploy --server-secret GOOGLE_CLIENT_ID=your-client-id --server-secret GOOGLE_CLIENT_SECRET=your-client-secret

1. Verify Google OAuth setup:
   Ensure that you've correctly set up Google OAuth in your Wasp file (

   main.wasp

   main.wasp

   ). It should look something like this:

   auth: {
     userEntity: User,
     methods: {
       google: {}
     },
     onAuthFailedRedirectTo: "/login"
   }

   auth: {
     userEntity: User,
     methods: {
       google: {}
     },
     onAuthFailedRedirectTo: "/login"
   }

1. Check Google OAuth app configuration:Make sure your Google OAuth app is correctly set up in the Google Cloud Console. Verify that the authorized redirect URIs include your Fly.io app URL, for example:`<https://your-app-name.fly.dev/auth/google/callback`>**Google OAuth App Setup** (<https://wasp-lang.dev/docs/auth/social-auth/google#3-creating-a-google-oauth-app>)
2. Redeploy your app:After setting the environment variables and verifying your configuration, redeploy your app:

   wasp deploy fly deploy

   wasp deploy fly deploy

1. Monitor the logs:
   After redeploying, check the Fly.io logs to see if the error is resolved.

wasp deploy fly deploy

wasp deploy fly deploy

1. First, you need to set the secrets using the wasp deploy fly cmdwasp deploy fly cmd command:

wasp deploy fly cmd secrets set GOOGLE_CLIENT_ID=253947131570-kirb3t9nnktfbj60mhqcgp4n9iu0tmak.apps.googleusercontent.com GOOGLE_CLIENT_SECRET=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 --context=server

wasp deploy fly cmd secrets set GOOGLE_CLIENT_ID=253947131570-kirb3t9nnktfbj60mhqcgp4n9iu0tmak.apps.googleusercontent.com GOOGLE_CLIENT_SECRET=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 --context=server

1. After setting the secrets, you can deploy your app:

wasp deploy fly deploy

wasp deploy fly deploy

1. Port Mismatch:Your server is listening on port 8080:```Server listening on port 8080```However, Fly.io is expecting it to listen on port 3000:```is your app listening on 0.0.0.0:3000?```
2. Address Binding:The server might be binding to `127.0.0.1` (localhost) instead of `0.0.0.0` (all available network interfaces).

1. Modify your server configuration:
   In your Wasp file (

   main.wasp

   main.wasp

   ), ensure that your server is configured to listen on the correct port and address. Add or modify the

   server

   server

   section:

   app MyApp {
     // ...
     server: {
       port: 3000,
       host: "0.0.0.0"
     }
   }

   app MyApp {
     // ...
     server: {
       port: 3000,
       host: "0.0.0.0"
     }
   }

1. Update your

   Dockerfile

   Dockerfile

   :
   If you have a custom

   Dockerfile

   Dockerfile

   for your server, make sure it's exposing the correct port:

   EXPOSE 3000

   EXPOSE 3000

1. Update Fly.io configuration:
   In your

   fly.toml

   fly.toml

   file, ensure that the internal_port is set to 3000:

   [[services]]
     internal_port = 3000
     # ...

   [[services]]
     internal_port = 3000
     # ...

1. Redeploy your app:
   After making these changes, redeploy your app using:

   wasp deploy fly deploy

   wasp deploy fly deploy

1. Monitor the logs:
   After redeploying, check the Fly.io logs to see if the server starts correctly and listens on the expected address and port.

1. Fly.io Configuration:Your `fly.toml` file is correctly set to use port 3000, which is the expected configuration for Fly.io.
2. Server Behavior:Despite this, your server is listening on port 8080. This suggests that the server configuration is overriding the Fly.io settings.

1. Check your Wasp file:
   In your

   main.wasp

   main.wasp

   file, look for or add a server configuration section:

   app MyApp {
     // ...
     server: {
       port: 3000,
       host: "0.0.0.0"
     }
   }

   app MyApp {
     // ...
     server: {
       port: 3000,
       host: "0.0.0.0"
     }
   }

1. Check environment variables:
   Ensure there are no environment variables overriding the port setting. You can check and set environment variables in Fly.io using:

   wasp deploy fly cmd secrets list

   wasp deploy fly cmd secrets list

PORT

PORT

   wasp deploy fly cmd secrets unset PORT

   wasp deploy fly cmd secrets unset PORT

1. Rebuild and redeploy:
   After making these changes, rebuild your Wasp app and redeploy to Fly.io:

   wasp build
   wasp deploy fly deploy

   wasp build
   wasp deploy fly deploy

1. Monitor the logs:
   After redeploying, check the Fly.io logs to ensure your server starts on the correct port:

   wasp deploy fly cmd logs

   wasp deploy fly cmd logs