Leo
will put subtasks to this. Troy
, Leo will be following up with you. We discussed adding a staging environment to this app along with a regular cadence between updates and the corresponding QA. Please bring me ( Brandon
) in for this whenever you need my help!
Subtasks
Access to Vercel/Create new Daryle AI Vercel Account Ann L.,
Troy P.
Setup a new Supabase instance (clone the one we have from a snapshot) Troy P.
Create a new branch for production (and ci/cd pipeline this to vercel) Troy P.
Setup credentials, env variables and configurations Troy P.
Re-setup DNS to point production to the Vercel instance Troy P.
Re-setup DNS to point staging on the Lovable instance Troy P.
Sign off with QA that both staging and production still works as expected. (Probably in conjuction of creating a QA golden path flow so everytime we have new changes, we have a template of what needs to always be tested per run). Add QA testers if needed on this subtask Troy P.
Leo Mark Castro
._.
Edited
Hello Troy
, feel free to message on this log or contact if you have insights or suggestions , or something you need. But I would create subtasks based on what I think should be done here initially.
Ideally we also do the tests on midnight EST time or low traffic times to avoid hiccups if some things doesn't go smoothly
Leo Mark Castro
._.
Might need Ms.Ann
's insight and help here, hehe. Especially on the assets and if I forgot something to point out.
Brandon Butz
General Manager
Ann
this is now overdue by a day. Does this need to get re-prioritized in light of the huge QA sprint we are doing for Daryle.AI? Does it need a new date?
Leo
Troy
Red
CC
Troy Pastoral
AI Whisperer
I am working now on vercel + lovable so we can have staging and production setup for the app
Troy Pastoral
AI Whisperer
Edited
Hi team
I have already setup both staging + production workflow for Daryle. Here's the flow
1. On my end, any code I touch (branch) -> goes directly to staging
2. Lovable will run the app on staging. We can basically make mistakes, play around. Because lovable will deploy to staging.daryle.ai anyway
3. Once staging is good, then we ship everything on the staging (lovable) directly to vercel (production). So that's three passes, dev -> staging -> production.
This should prevent any last minute bugs, errors or issues with the app because by the time the app reaches production, it should be nearly perfect already :)
Next steps: - How to test: changes on lovable (ideally suitable and reflective of features that we need). -> ship to prod
Hello
Troy
, feel free to message on this log or contact if you have insights or suggestions , or something you need. But I would create subtasks based on what I think should be done here initially.
Ideally we also do the tests on midnight EST time or low traffic times to avoid hiccups if some things doesn't go smoothly
Might need Ms.
Ann
's insight and help here, hehe. Especially on the assets and if I forgot something to point out.
I am working now on vercel + lovable so we can have staging and production setup for the app
Hi team
I have already setup both staging + production workflow for Daryle. Here's the flow
1. On my end, any code I touch (branch) -> goes directly to staging
2. Lovable will run the app on staging. We can basically make mistakes, play around. Because lovable will deploy to staging.daryle.ai anyway
3. Once staging is good, then we ship everything on the staging (lovable) directly to vercel (production). So that's three passes, dev -> staging -> production.
This should prevent any last minute bugs, errors or issues with the app because by the time the app reaches production, it should be nearly perfect already :)
Next steps:
- How to test: changes on lovable (ideally suitable and reflective of features that we need). -> ship to prod