Add flightcontrol deploy command

[beerose]

This PR adds rw setup deploy flightcontrol and rw deploy flightcontrol commands.

Link to the docs PR: #4788

---

Had some problems with testing the rw deploy command. I have a minimal redwood project, and running yarn dev deploy flightcontrol web --cwd <path to my project> was resulting in Could not find a "redwood.toml" file, are you sure you're in a Redwood project? error. The file was there and it looked like the command was run in the correct directory. Any pointers would be appreciated 🙏

[netlify]

✅ Deploy Preview for redwoodjs-docs canceled.

🔨 Explore the source changes: bcd2a71

🔍 Inspect the deploy log: https://app.netlify.com/sites/redwoodjs-docs/deploys/62357d761e9e28000958bf99

[cannikin]

Hello! Welcome and thanks for the PR! We've been big fans of @flybayer since we both started our frameworks around the same time. We're rooting for him and the team with Flightcontrol!

That command you pasted, yarn dev deploy flightcontrol web should really be yarn rw deploy flightcontrol web (rw instead of dev). Maybe that's the issue?

Whoops! Turns out yarn dev is a real command that I didn't even know existed! 😬 Ignore me, see @thedavidprice's comment below!

[thedavidprice]

@jtoar FYI re:

yarn dev deploy flightcontrol web --cwd

^^ I've noticed this isn't working for me locally as well. My guess is that it has something to do with recent move to Yarn 3

[thedavidprice]

@beerose This is amazing! Excited to help you get this into Redwood.

Local Dev
Gah, I think we busted that --cwd command during our recent migration to Yarn 3. (Also, I'm assuming you have a local test project and are setting --cwd at that project outside the Framework codebase, correct?)

What you can use instead is the rwfw project:sync command, which you run from the local test project. Here's the doc explaining what that is and how it works:

• https://github.com/redwoodjs/redwood/blob/main/CONTRIBUTING.md#testing-the-framework-in-your-project

Also, here are the two main Contributing docs for ongoing reference:

• https://redwoodjs.com/docs/contributing-overview
• https://redwoodjs.com/docs/contributing-overview

Deploy Target CI Repo
I've followed up with you directly about next steps to first set this up over here: https://github.com/redwoodjs/deploy-target-ci

That's the best way I can understand how everything works in order to review this PR and make sure all the pieces are connected!

[thedavidprice]

I updated this because it was broken as is. Assuming you'll be port forwarding. Otherwise, I recommend updating in redwood.toml or just hardcoding here.

[thedavidprice]

Because the apiUrl was changed to use an env var, we need to make sure there's a value for local dev

[thedavidprice]

FYI updated these commands

[thedavidprice]

This one as well

[thedavidprice]

@beerose @flybayer Thanks again for getting this going! I've fixed some issues and made some config and command changed -- do review my changes, please, to confirm they'll all work with Flighcontrol.

So we can move forward, I'm going to merge this and use the corresponding published canary version over here: https://github.com/redwoodjs/deploy-target-ci

Things aren't quite working, so we'll keep at it!