Already on BrewInTH? How to publish your changes
Your site is live on BrewInTH and you want to change it? Keep chatting with the same AI and ask it to deploy. The site stays up and your data stays put.
Your site is live on BrewInTH and people have started using it. Then one day you want to change some text, fix a bug, add a page or make it look nicer. The obvious question follows: do I have to start over?
No. Keep chatting with the AI in the same chat, say what you want changed, and ask it to deploy the new version to BrewInTH. This article covers everything you need: how to ask, what to do when the token has expired, switching computers or AI tools, and going back to an earlier version.
In short
✅ The easiest way: open the same chat with your AI and type "Change … and deploy it to BrewInTH"
✅ Token expired (24 hours by default)? Press the button that creates a new link and token, and paste the message into the same chat
✅ Your current site stays up during the update, and if the new version fails, the current one stays online
✅ A new deploy leaves your database alone, and you can go back to an earlier version in one click
Why keep chatting in the same chat?
When you first gave the ready-made message to your AI, it read the project's guide. It knows which folder the code is in, which technology it uses and how the database is connected, and it has the deploy token in the chat. Keep chatting in that chat and the AI carries on straight away, without you explaining anything again.
Put simply, the same chat is the assistant that knows your project best.
Update your site on BrewInTH in 5 steps
- Open the same chat in the same AI tool, e.g. Claude Code, Codex or Cursor, opened in the same project folder.
- Say clearly what to change. Name the page, button or text. If you have a screenshot or an error message, attach it.
- Let the AI make the change and test it locally first. Most AIs test on their own; if yours doesn't, say "make sure it passes the tests first".
- Ask it to deploy to BrewInTH, e.g. "deploy this version to BrewInTH now".
- Open your site's link to check. If the page still looks the same, press
Ctrl+F5(Cmd+Shift+Ron a Mac) to reload without the cache.
💡 Set the AI's permission mode so it works without stopping, as for the first deploy, e.g. Bypass permissions in Claude Code. Otherwise the AI may stop to ask, or refuse the deploy command.
Prompts you can use right away
Add a feature
Please add a light/dark mode switch to the game and deploy it to BrewInTHChange text or details on a page
Change the opening hours on the contact page to 08:00-20:00 and deploy to BrewInTHFix a bug from a screenshot
Pressing the sign-up button shows the error in this screenshot. Find the cause, fix it and deploy againCheck your site's health
Show me how the current project on BrewInTH is doing: its status and statsThe last one gives you an overview of your site. The AI pulls data from BrewInTH and sums it up, such as the app's status, a live check of the site, the deploy history and the database size.
What if the token has expired?
A token from the project page lasts 24 hours. If you come back to edit after that, the AI will say it can't connect or that the token no longer works. Fixing it takes less than a minute:
- Sign in to the BrewInTH console and open your project page
- Press the green Create the AI link and token (automatic) button under the project name
- Press Copy the AI message
- Paste it into the same chat and add "Here is a new token, use it instead of the old one and carry on with the deploy"
💡 If you know you'll be editing over several days, press Custom permissions / lifetime under the same button and give the token anything from 1 hour to 7 days.
Can I start a new chat, switch computers or use a different AI?
Yes, but a new chat or a different AI doesn't know your project yet. Do this:
- Open the AI in the folder with your latest code. If you switch computers, copy the project folder across or pull it from Git.
- Create a new ready-made message on the project page and paste it to the AI.
- Say clearly: "This updates an existing project that is already live. Don't create a new project."
⚠️ A deploy replaces the live version with the code in the folder the AI has open. If the code on that computer is older, your site goes back to the older version. Make sure you open the folder with your latest changes.
Does my site stay up during an update?
Yes. BrewInTH builds the new version separately first, checks that it is ready, and then switches visitors to it automatically. Meanwhile, your current site keeps serving as usual. If the new version fails to build or doesn't start, your current site stays online, and the AI can read the log, fix it and deploy again.
The one exception is a project with persistent storage (/data) turned on: the platform stops the old version before switching, so the site pauses briefly during the deploy. If the new version has problems, use the rollback described below.
Will I lose data in the database or files?
- Your database is kept. A new deploy changes only the code; it doesn't delete members, orders or saved scores.
- Files written inside the app itself are replaced. If users upload pictures or files, have the AI store them in the database or in BrewInTH's persistent storage
/data(just tell the AI "store user uploads in /data"). - If the database structure has to change, tell the AI it must not delete existing data. If you've bought the backup add-on, the database is also backed up automatically every day.
Can I go back to an earlier version?
Yes. Every deploy is kept in the history. If a new version has problems, go to the project page → Releases tab and press Restore this release on the earlier version. It goes live again, and you can let the AI fix the problem in the chat without rushing.
Ask the AI about your site's status and stats
Besides editing, you can ask the AI in the same chat how your site is doing. It checks the app's status, opens the live site, and looks at the deploy history, the database size and what the app has stored, such as the number of members or saved scores, then sums it up for you. File storage and bandwidth figures are in the Usage menu of the console.
Other options if you prefer
- Git: if your code is on GitHub or GitLab, BrewInTH can pull it from the repository (for a private repository, save a token in the console).
- SFTP: edit files over SFTP with a program like FileZilla from the project's Files tab, then press Publish from SFTP.
For most people, though, carrying on in the same chat is still the fastest way, with the fewest mistakes.
Watch the video (in Thai)
▶ See your stats, edit your site and deploy, all with one prompt to the AI (1:42)
Watch on YouTube
Frequently asked questions
Do I need a new project every time I change my site?
No. Deploy again to the same project. The site's link stays the same, and the database keeps all its data.
How often can I update my site?
As often as you like, at no extra cost per deploy. Every version is kept in the release history.
The AI says the deploy is done, but my page hasn't changed
Reload without the cache (Ctrl+F5). If it still hasn't changed, ask the AI to "check the latest deploy status on BrewInTH", or open the Releases tab to see the status of the latest version.
I sent my token to someone by mistake
Revoke it right away in the AI connections menu, then create a new token for your AI.
Can I update my site from my phone?
Having the AI change code and deploy still needs a PC or Mac, just like the first time. Checking your site's status and going back to an earlier version work from a phone.
Summary
Updating your site on BrewInTH doesn't mean starting over. Open the same chat, say what to change, ask for a deploy and open the link to check. If the token has expired, create a new one and paste it into the same chat. Your site stays up during the update, your data stays put, and you can always go back to an earlier version.