Add deployment settings for the frontend

[andrewtavis]

trafficstars

Terms

• [X] I have searched open and closed feature requests
• [X] I agree to follow activist's Code of Conduct

Description

This issue would look into and apply all needed settings such that the frontend can be deployed outside of a Netlify context. Going through the Nuxt docs for deployment would be the best place to start with this.

Contribution

I'll work on this, but getting support/suggestions would be welcome!

[andrewtavis]

Is anything actually needed for this at this point, @wkyoshida?

[wkyoshida]

..such that the frontend can be deployed outside of a Netlify context..

I'd say the scope for this issue has likely changed now, as we've since decided to stay on Netlify, but yea - we could use this issue still for the additional configurations we'd need. Not sure all that would actually be though, but at least one thing comes to mind:

• Configure so that we are not deploying production activist.org for every commit in main

---

Not sure if Netlify is able to base production deployments based on GitHub Releases, but it does look like:

• We are at least able to lock which build is live in production
  • [ref1]
  • This could be the interim solution
• Later though, we might be able to potentially implement this functionality ourselves by having a GitHub Action that triggers on GitHub Releases and does a manual production deployment via the Netlify CLI:
  • [ref2]
  • [ref3]