How do you implement your Front-end build & deploy process?

• s3-sync-action

  7 1,004 0.0 Shell

  🔄 GitHub Action to sync a directory with a remote S3 bucket 🧺

You can deploy your frontend build to S3, then point your domain to these files, for example with CloudFlare or Route53. We use a Github action to publish these for each deploy. This makes the frontend and backend effectively two different services.

• serve-static

  2 433 9.1 TypeScript

  Serve static websites (SPA's) using Nest framework (node.js) 🥦 (by nestjs)

  

Alternatively, you can serve your frontend from the backend using serve-static. Note that this doesn't actually require that your frontend source code is nested in the backend source code directory. You are just serving the build files, not the source, so only those build files need to end up in the `nest` directory. Our dev script just peaks a level up (IE `../frontend`), while our deploy GitHub action builds the frontend and moves the files into the backend before building `nest`.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project