Redwood: Deployment Targets tracking issue

[peterp]

We want to deploy to all the things. Write once, learn once, run everywhere.

Serverless Function Providers

• [x] Netlify Status: working
• [x] Vercel: Status working
• [x] AWS Lambda: Status working, need to document steps and figure out how to make it seamless
• [ ] Azure functions Serverless
• [ ] Google Cloud Functions

Others

• [ ] Self hosted: Status working, but need to remove the "watch" code from the "dev-server" and come up with a way to restart a long running node_process.

[hemildesai]

Hey @peterp, I'm interested in deployments and have some experience with infrastructure and cloud providers. So I'd love to get involved and contribute towards adding multiple deployments to redwood. Let me know if there are any such opportunities.

[peterp]

@hemildesai Amazing, let's chat! Could you ping me on Discord?

[thedavidprice]

@hemildesai @bcoe @kimadeline @peterp

Hi all! I'm continuing the conversation we started yesterday (minus Peter) about the current work implementing...

1. the Serverless Framework as well as
2. the Redwood Container POC...

...can be leveraged to plan deployment support on Azure (Kim-Adeline) and Google Cloud (Ben Coe).

What's the best way to move this discussion forward if not here in an Issue? I'd be happy to help set up a time to discuss live if preferred.

--

So excited about this it gets the DoubleRocket™ sign off 🚀🚀

[kimadeline]

I'm good with anything: here, GH issue, Discord, Slack, forum, Linkedin DMs...

Side note: I've been tinkering Azure Static Web Apps, which would not only host the API side (via Azure Functions), but also the front-end. I don't think function-only deployment would be too far off though.

[thedavidprice]

Update: Peter and I connected about this yesterday. Near-term priority for him is TypeScript and then he'll get back to the containerization work. Once he's "ready to demo/discuss" containers, that will be the trigger for me to schedule a real-time meeting for us.

Sound good?

[bcoe]

👋 hello, acknowledging that I've seen this thread.

Since my initial spike on this work, I've been using firebase hosting. It seems like it would be ideal for running redwood on Google Cloud:

1. you deploy the react app to a CDN.
2. you deploy containers to Cloud Run (which is a platform for running arbitrary Docker containers).

[peterp]

@bcoe Cool - I have a proof of concept that puts RW's API in a container for AWS Fargate. We're not far off at all.

[andrew-hwahin]

Looking forward to deploying to Azure functions Serverless 😁

[viperfx]

Hey all - just wanted to add my 2cents and experience with self hosting.

I had trouble using the netlify auth provider under a self hosted setup. I am using the api-server under pm2.

Ive started a thread on the forums here - https://community.redwoodjs.com/t/redwood-api-server-context-creation-failed/1493

Is this a known issue or is there something going wrong unexpectedly? I did notice that netlify auth is handled differently in production.

Let me know if you need more info.