chore: prepare for niployments

[limwa]

No description provided.

[netlify]

✅ Deploy Preview for tts-fe-preview ready!

Name	Link
🔨 Latest commit	e4bddd4
🔍 Latest deploy log	https://app.netlify.com/sites/tts-fe-preview/deploys/66bd28b673491a000824efc3
😎 Deploy Preview	https://deploy-preview-243--tts-fe-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[tomaspalma]

In terms of tts it is all right 🎉

In terms of the action, it looks correct but im no expert.

[limwa]

Ready to be merged, as soon as secret is set.

[thePeras]

@tomaspalma do your manager work on the secrets 🔨

[tomaspalma]

I have already added the TTS_FE_VARS_CONTENT secret 🎉 (hope I didnt mess up 🫠 ).

After this is merged, should I open a PR from develop to main to publish the image?

[limwa]

After this is merged, should I open a PR from develop to main to publish the image?

Yes!

[LuisDuarte1]

Do we want staging builds on tts though?

[tomaspalma]

Do we want staging builds on tts though?

I'm not sure if I understand the question, if the code that is on develop is deployed for everyone without the goal to test some of the users shouldn't it be on the main branch? Every feature is working despite a non-critical one that will be fixed soon.

[limwa]

Regarding the staging environments @LuisDuarte1 mentioned, you can think of it as a kind of beta version available on a separate URL. This way, you can test the current state of the develop branch before it is deployed to the production environment, with the main branch. Is the tts team interested in that? @tomaspalma

[tomaspalma]

Having two action runs?

• One that runs when there are merges to the main branches that pushes to the niployments image registry a production image that is served on the production url
• Another one that runs when there are merges to the development branch that updates a beta image that is behind another url in niployments for testing

[limwa]

Having two action runs?

• One that runs when there are merges to the main branches that pushes to the niployments image registry a production image that is served on the production url
• Another one that runs when there are merges to the development branch that updates a beta image that is behind another url in niployments for testing

Yes, that's the idea. In practice, it's the same action running on two different branches, but yes, the effect is the same.

[limwa]

@tomaspalma @LuisDuarte1 I've added the necessary changes for a staging environment. If it's not needed, please revert the commit and merge the PR. If you decide it is a good thing, go ahead and merge the PR. I'll do the same in the backend.

[tomaspalma]

I think it is a good idea, a nice to have but not strictly necessary (but it can be kept)

What I didn't understand is how will the develop and main builds be distinguished on the image registry in niployments? Does the action append the branch to the name?

[limwa]

They will have different tags. One will be niaefeup/tts-fe:main and the other will be niaefeup/tts-fe:develop.

[tomaspalma]

Understood, thank you!

[tomaspalma]

If you want you can merge this pr, so you get the merge commit

[limwa]

I can't merge the PR because I'm not authorized, but go ahead and merge when you think everything is okay.