3ghan
WWasp-lang
•Created by 3ghan on 6/13/2024 in #🙋questions
Proper way to stop process
thanks! ya, Mac OS 13, iterm, wasp 0.13.2, it it killed the process, but released the console before it had maybe? but then previously I had several spun up that had been running in the background that I had to manually kill. No big deal, just didn't see any documentation about preferred stopping method so was wondering if I was stopping wasp wrong
8 replies
WWasp-lang
•Created by 3ghan on 6/13/2024 in #🙋questions
Proper way to stop process
ok kapa, that's what I've been doing
8 replies
WWasp-lang
•Created by 3ghan on 5/13/2024 in #🙋questions
Hello! thanks! I'm debugging a deployment with an additional Dockerfile
anybody reading this, looks like a -no- from wasp re/multiple containers(?) and no docker-compose from fly.io, closest solution seems to be https://fly.io/docs/apps/processes/
but looks unlikely to be worth the extra work vs. just hosting separate entities
11 replies
WWasp-lang
•Created by 3ghan on 5/13/2024 in #🙋questions
Hello! thanks! I'm debugging a deployment with an additional Dockerfile
here's the output from wasp dockerfile, can you see any issues @kapa.ai :
FROM node AS base
RUN apk --no-cache -U upgrade
FROM base AS server-builder
RUN apk add --no-cache python3 build-base libtool autoconf automake
WORKDIR /app
COPY src ./src
COPY package.json .
COPY package-lock.json .
COPY server .wasp/build/server
COPY sdk .wasp/out/sdk
Install npm packages, resulting in node_modules/.
RUN npm install && cd .wasp/build/server && npm install
COPY db/schema.prisma .wasp/build/db/
RUN cd .wasp/build/server && npx prisma generate --schema='../db/schema.prisma'
Building the server should come after Prisma generation.
RUN cd .wasp/build/server && npm run bundle
RUN apk add --no-cache python3
ENV NODE_ENV production
WORKDIR /app
COPY --from=server-builder /app/node_modules ./node_modules
COPY --from=server-builder /app/.wasp/out/sdk .wasp/out/sdk
COPY --from=server-builder /app/.wasp/build/server/node_modules .wasp/build/server/node_modules
COPY --from=server-builder /app/.wasp/build/server/bundle .wasp/build/server/bundle
COPY --from=server-builder /app/.wasp/build/server/package*.json .wasp/build/server/
COPY --from=server-builder /app/.wasp/build/server/scripts .wasp/build/server/scripts
COPY db/ .wasp/build/db/
EXPOSE ${PORT}
WORKDIR /app/.wasp/build/server
ENTRYPOINT ["npm", "run", "start-production"]
FROM node:20-alpine
USER root
RUN echo 'Flowise Dockerfile script has started...'
RUN apk add --no-cache git \
python3 py3-pip make g++ \
cmake build-base cairo-dev pango-dev \
chromium
ENV PUPPETEER_SKIP_DOWNLOAD=true
ENV PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium-browser
RUN npm install -g flowise
WORKDIR /data
ENTRYPOINT ["/bin/sh", "-c", "\
if [ -z "$PORT" ]; then \
echo 'Error: PORT environment variable is not set.' >&2; \
exit 1; \
else \
echo 'Starting Flowise on port ' $PORT; \
flowise; \
fi \
"]
11 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
@martinsos thanks! I'm trying to get google auth to work w/opensaas and fly.io. I'm having trouble with the previous instructions link you provided, the wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=https://alteraug.com command fails with :
wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=https://alteraug.com
$ flyctl version
flyctl v0.2.33 darwin/arm64 Commit: 201c782c0d8d21c4a16ba1bcc1e28ea7e35e095a-dirty BuildDate: 2024-04-15T15:24:16Z
$ flyctl auth whoami
[email protected]
🚀 Running server command: flyctl secrets set WASP_WEB_CLIENT_URL=https://alteraug.com
$ cd
$ flyctl secrets set WASP_WEB_CLIENT_URL=https://alteraug.com
Error: the config for your app is missing an app name, add an app field to the fly.toml file or specify with the -a flag
❌ --- [Error] Deploy command failed: ---------------------------------------------
Deploy command failed with exit code: 1
::::
clearly flyctl is looking for fly.toml and wasp is generating fly-server.toml and fly-client.toml .
so, has anyone tested these scripts successfully?
Has someone tested opensaas to fly w/google auth? I'm working pretty boilerplate so it's weird for a setter to not work
I've tried updating everything, but perhaps I need to do a fresh install in latest version? my base is only about a week old.
is there more error logging somewhere? is there an easy way to see the env vars on a fly machine? Thanks!
is there more error logging somewhere? is there an easy way to see the env vars on a fly machine? Thanks!
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
@kapa.ai ok but I'm trying to execute a wasp command that uses flyctl, the command i'm trying to use is: wasp deploy fly cmd --context server secrets set WASP_WEB_CLIENT_URL=https://mycoolapp.com
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
@kapa.ai I'm using opensaas and there are two fly.toml files, fly-server.toml and fly-client.toml but no fly.toml, both of the files I have already had app names. why then the error?
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
@kapa.ai provide location file and example code to solve:
Error: the config for your app is missing an app name, add an app field to the fly.toml file or specify with the -a flag
❌ --- [Error] Deploy command failed: ---------------------------------------------
Deploy command failed with exit code: 1
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
mids
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
@kapa.ai but not setting it by default means it by default doesn't work out of the box for remote production deployment to all in one services like fly.io, as it's known that the user controls the client and server locations there is no security concern, so what is the concern with setting it by default?
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
@kapa.ai is there a good reason not to default WASP_WEB_CLIENT_URL to the known server url in production deployment if the user can manually set it if they need to use a different url?
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
@kapa.ai why is WASP_WEB_CLIENT_URL not set in production deployment when REACT_APP_API_URL is? what is the benefit of this approach?
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
hey @kapa.ai I see in my deployment logs that REACT_APP_API_URL gets set to my deployment url successfully, do I additionally need to add WASP_WEB_CLIENT_URL env var to my server env ? if so, why is this preferred?
39 replies
WWasp-lang
•Created by 3ghan on 4/12/2024 in #🙋questions
google auth on fly.io with opensaas/wasp
haha figured, thanks for confirming
39 replies
WWasp-lang
•Created by Vinny (@Wasp) on 4/2/2024 in #🙋questions
ui
thanks I'm going to try that out hadn't see it
9 replies
WWasp-lang
•Created by 3ghan on 4/3/2024 in #🙋questions
default password
ha ya, clever. so, in practical dev process, some, as myself, will spin up several versions to test features atomically. wasp handles this very poorly? not sure where the issue arises but where I've gotten to so far is:
docker volume ls | grep wasp-dev-db
shows many volumes, if you manually kill a db, (prisma?) cache does not update, so you env updates to new db url but all wasp db commands will fail with:
'database "OpenSaaS-ff8c20a255" does not exist'
I went with wasp uninstall reinstall, I'll document and file the issue on the repo once I've narrowed it down a bit.
But you guys might wanna be aware of it as it's a full stop for some devs because that cache is hidden (somewhere in prisma land I'd guess), and so requires full debug (no search and fix)
18 replies
WWasp-lang
•Created by 3ghan on 4/3/2024 in #🙋questions
default password
on the topic of Auth and DB seed, I think the docs would benifit from a short prisma sentance around " 2. Run the development database (and leave it running):
wasp db start"
Even just changing this to 'build the development database from main.wasp config" would make it more clear that prisma isn't going to rebulid that database shape, right? once you hit that db start your auth method is locked in right? RTFM gets complicated with large stacks 🙂
18 replies
WWasp-lang
•Created by 3ghan on 4/3/2024 in #🙋questions
default password
ahahaha right. THANKS! nice to be free of next for a minute
18 replies
WWasp-lang
•Created by 3ghan on 4/3/2024 in #🙋questions
default password
Hey thanks! sorry yes opensaas, I just needed to dig into the db studio/prisma config. Fantastic project, great work loving it. for indi devs in the ai space it's huge to be able to spin up Next with auth and tools fast.
18 replies
WWasp-lang
•Created by 3ghan on 4/3/2024 in #🙋questions
default password
If anybody else comes across this issue, pretty sure it's the data shaping, so I would recommend choosing your auth method before building your database out.
18 replies