sion0921 Posts - Answer Overflow

sion0921

•Created by sion0921 on 12/5/2024 in #🙋questions

Fly.io Multi-Region Wasp setup with database Replicas

I'm planning to run a multi-region service. My service, spellfast.ai, should be fast globally, so I'm scaling to multiple regions. The best way to do this in my case is by using database replicas, which are clones of the primary region's database. The benefit is that you have one database, and the clones receive updates. The setup involves setting up different ports for reading from database replicas and catching write requests, proxying them from replicas to the database in the primary region. docs: https://fly.io/docs/postgres/advanced-guides/high-availability-and-global-replication/#connecting-to-read-replicas Is such a custom setup even possible with Wasp? Any suggestions on how to achieve this?

13 replies

WWasp

•Created by sion0921 on 11/27/2024 in #🙋questions

Custom Backend URL is not getting set for Client

REACT_APP_API_URL issue I'm unable to set a custom backend domain for my webpage. It's a Wasp issue that appears to ignore the REACT_APP_API_URL=https://api.spellfast.ai client-side variable. I've already added CERTs and DNS records for the custom BE URL. When I deploy, I use this command:

REACT_APP_API_URL=https://api.spellfast.ai REACT_APP_STRIPE_CUSTOMER_PORTAL=https://billing.stripe.com/xxxx REACT_APP_GOOGLE_ANALYTICS_ID=G-xxx REACT_APP_EXTENSION_ID=xxxx wasp deploy fly deploy

REACT_APP_API_URL=https://api.spellfast.ai REACT_APP_STRIPE_CUSTOMER_PORTAL=https://billing.stripe.com/xxxx REACT_APP_GOOGLE_ANALYTICS_ID=G-xxx REACT_APP_EXTENSION_ID=xxxx wasp deploy fly deploy

So even if I check api url, it's https://spellfast-server.fly.dev while I need https://api.spellfast.ai

import { config } from 'wasp/client'

console.log(config.apiUrl)

import { config } from 'wasp/client'

console.log(config.apiUrl)

Interestingly, during deployment, I inspected the logs. For some reason, the client is using the fly.io 'https://spellfast-server.fly.dev' domain instead of my custom one, during npm run build

  Server has been deployed! 
🚀  Deploying your client now... 
$ cd /home/regent116/SpellFast/spellfast/app/.wasp/build/web-app
🚀  Building web client for production... 
$ npm install
...

found 0 vulnerabilities
$ REACT_APP_API_URL=https://spellfast-server.fly.dev npm run build <-- // should be https://api.spellfast.ai

  Server has been deployed! 
🚀  Deploying your client now... 
$ cd /home/regent116/SpellFast/spellfast/app/.wasp/build/web-app
🚀  Building web client for production... 
$ npm install
...

found 0 vulnerabilities
$ REACT_APP_API_URL=https://spellfast-server.fly.dev npm run build <-- // should be https://api.spellfast.ai

Frustration is setting in as I try to configure my backend to work with my custom domain, but I can't pinpoint my mistake.

15 replies

WWasp

•Created by sion0921 on 9/18/2024 in #🙋questions

How to generate Authorization header JWT token for custom API endpoint?

I've created operation which generates JWT token which is sent to my chrome extension.

action generateExtensionToken {
  fn: import { generateExtensionToken } from "@src/auth/extensionAuth",
  entities: [User]
}
...
api improve {
  fn: import { improve } from "@src/api/improve",
  httpRoute: (POST, "/spellxy/improve"),
  auth: true
}

action generateExtensionToken {
  fn: import { generateExtensionToken } from "@src/auth/extensionAuth",
  entities: [User]
}
...
api improve {
  fn: import { improve } from "@src/api/improve",
  httpRoute: (POST, "/spellxy/improve"),
  auth: true
}

The main goal is to access context.user for my custom API endpoint to verify if the user has a paid plan. I've tried many combinations, using userId, username, and even config.auth.jwtSecret instead of my JWT_SECRET_KEY in env.server, but none of these work with auth:true for api endpoint in a Postman request that includes a generated bearer token.

import jwt from 'jsonwebtoken';
import { HttpError } from 'wasp/server';
import { config } from 'wasp/server';

export const generateExtensionToken = async (args, context) => {
  if (!context.user) {
    throw new HttpError(401, 'Not authorized');
  }

  const token = jwt.sign({ userId: context.user.id }, config.auth.jwtSecret, { expiresIn: '1y' });

  return { token };
};

import jwt from 'jsonwebtoken';
import { HttpError } from 'wasp/server';
import { config } from 'wasp/server';

export const generateExtensionToken = async (args, context) => {
  if (!context.user) {
    throw new HttpError(401, 'Not authorized');
  }

  const token = jwt.sign({ userId: context.user.id }, config.auth.jwtSecret, { expiresIn: '1y' });

  return { token };
};

What's the right format to sign a JWT token for it to work with a custom API endpoint to access context.user? EDIT: I used the client-side sessionId for a custom API endpoint; however, some questions still remain

97 replies

Gaming

Programming