G35x Comments - Answer Overflow

G35x

•Created by AC on 12/24/2024 in #🙋questions

Really struggling with deploy

Adding my 2 cents here.. I really prefer using GCP for my projects. Not the cheapest/easiest but it has advantages & it’s what I’m used to. Would love to see more love for GCP users. There is some documentation that TomD created for this, I can tell he’s experienced and am super appreciative of his contribution. Speaking candidly, experienced people sometimes aren’t the BEST teachers. One common pitfall, they can assume the audience has implicit information / contextual understandings which they might not. In other words, and with all due respect, there are some under documented steps, and some info missing. It could use a facelift! Was thinking to create a more detailed guide on deploying a wasp project from scratch using 100% google infrastructure but don’t want to step on any toes or take away from Tom’s contribution. Also not sure how in-demand support is for this ecosystem and it would take a few hours to put together.

38 replies

WWasp

•Created by AC on 12/24/2024 in #🙋questions

Really struggling with deploy

Nice!! Congrats on the successful deployment

38 replies

WWasp

•Created by AC on 12/24/2024 in #🙋questions

Really struggling with deploy

No problem! Looking forward to seeing what works to fix this. One more tip that helped me, if you aren’t already doing so, try to make as detailed as possible notes documenting all of your configurations, commands, strings etc used in your notes app while troubleshooting. The first week I was trying to deploy I was relying on my memory. I made way faster progress once I saved my “intellectual property” so I could wipe my environment, try new setups, and systematically test / compare which steps work, why, and how

38 replies

WWasp

•Created by AC on 12/24/2024 in #🙋questions

Really struggling with deploy

What I’m thinking might have happened is while you were testing different environment configurations to diagnose earlier sequential issues in your build / deploy stages, you could have done something to change your config.json and that’s why this new issue is occurring in the final stage

38 replies

WWasp

•Created by AC on 12/24/2024 in #🙋questions

Really struggling with deploy

Going back to the attempt prior to using sudo, Have you tried to verify the contents of your ~/.docker/config.json are correctly configured? Seeing that you’re running into more environment issues using Sudo makes me think an easier path would be to make the “docker-compose up —build” command work without requiring Sudo. A quick google search of the error code you got took me to a few different stack overflow threads. I didn’t see anything about using Sudo to resolve the “executable file not found at $PATH” I did see a lot of people mentioning steps to fix the configuration at ~/.docker/config.json specifically: “Check your ~/.docker/config.json and replace "credsStore" by "credStore" And “My config stopped working after I've installed Docker Desktop which apparently added "credsStore": "desktop" to my ~/.docker/config.json. Removing "credsStore": "desktop" fixed the issue as mentioned by various comments above”

38 replies

WWasp

•Created by AC on 12/24/2024 in #🙋questions

Really struggling with deploy

Hey @AC, I work from a mac M1 pro and had a bunch of unexpected issues deploying. My stack is - firebase front end - Google cloud run server - Google postrgresql DB Took me two weeks to successfully deploy. I nearly gave up. Hang in there. regarding the error: LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 50) I'm not certain this will be a non-issue for heroku, but this was a total non-issue for me at any point in my build or deploy. I get that warning every time I docker build and it hasn't caused any issues. You're definitely headed in the right direction using: docker buildx build --platform linux/amd64 -t <app-name> . docker tag <app-name> registry.heroku.com/<app-name>/web docker push registry.heroku.com/<app-name>/web Do you get any other errors during the docker build stage? Are you able to share the complete sequence of commands you're using & what directory you're in when running those commands during the build & push?

38 replies

WWasp

•Created by Kynetix on 10/18/2024 in #🙋questions

PayloadTooLargeError

Just wanted to let you guys know this fixed an issue for me & wanted to thank you both! you too kapa 😉 1) created a serverSetup.ts import express from 'express'; import bodyParser from 'body-parser'; export const serverSetup = () => { const app = express(); app.use(express.json({ limit: '50mb' })); app.use(express.urlencoded({ limit: '50mb', extended: true })); } export const serverMiddlewareFn = (middlewareConfig: any) => { middlewareConfig.set('express.json', bodyParser.json({ limit: '50mb' })); return middlewareConfig; } 2) added to my main.wasp: server: { middlewareConfigFn: import { serverMiddlewareFn } from "@src/server/serverSetup.js" }, and no more PayloadTooLargeError

28 replies

WWasp