Sounds good figured I would ask. Perhaps it might make a good video, basically what kind of of things should a non native programmer think about prior to launching a site live. Just from your perspective.

@John Webber Thanks John and @Corbin Brown I am most likely purchasing boost, and great advice John. That is my current workflow I guess I was just concerned about security holes etc. But I like Corbin's approach. Thanks everyone

Fair I was wondering about that at first. Definitely following. Thanks for all you do for us.

Very nice. I just got a evotec 128bg ram to run openclaw locally. With some self hosted models

interesting i have not been nerfed like that. I do rotate models a tad. I will have to keep an eye. Do you think location matters? like Country etc?

This is a good read about it: https://medium.com/write-a-catalyst/the-future-of-coding-i-tested-google-gemini-3-and-its-antigravity-ide-and-heres-what-blew-my-mind-33a70011259c

Here is a example of a deploy agent workflows: # /deploy Workflow This workflow creates a new version release and deploys to the live Firebase site. ## Steps // turbo-all 1. Stage all changes: ```powershell git add . ``` 2. Check git status to see what will be committed: ```powershell git status ``` 3. **ASK USER for commit message** or use the CHANGELOG entry for the version 4. Create release (bumps version, updates CHANGELOG, creates git tag): ```powershell npm run release ``` 5. Push to GitHub with tags: ```powershell git push --follow-tags ``` 6. Build the production bundle: ```powershell npm run build ``` 7. Deploy to Firebase Hosting: ```powershell firebase deploy --only hosting ``` ## Notes - This deploys to the LIVE site - use with caution - For save-only (no deploy), use `/save` instead - Always review the `git status` output before confirming