Skip to content

04-deploy.md

Latest commit

 

History

History
59 lines (38 loc) · 2.09 KB

04-deploy.md

File metadata and controls

59 lines (38 loc) · 2.09 KB

Deploy to Firebase

  1. Create Firebase account and login into Firebase CLI:

      npx firebase login

  2. Select the Firebase project to deploy to

      npx firebase use <projectId>

  3. Build and deploy with /config/production.json

      npm run deploy

    or to deploy with a custom config pass the name of the config file. For example with /config/custom.json

      BUILD_ENV=custom npm run deploy

    The URL to your live site is listed in the output.

Continuous integration with Github Actions

In the .github/workflows folder, you can find two workflows to help you develop and deploy Hoverboard to Firebase:

  • pre-merge.yaml Builds the project, runs the linter and the tests on every Pull Request
  • deploy.yaml Deploys the project to Firebase after every merge to main.

The pre-merge workflow is already configured and will work out of the box, once you fork the hoverboard repo. To run the deploy on your instance instead, you need to do a small setup:

Deploying to Firebase wiht Github Actions

First, make sure that you're able to deploy locally correctly with the command:

npm run deploy

If the deploy is successful, you can then configure Github Actions to do it for you. You need to generate a login token for the CI with the following command:

npx firebase login:ci

Once you obtained the token, you need to store it as a secret called FIREBASE_TOKEN in the settings of your repository. Additionally you need to set your Firebase project-id as a secret called FIREBASE_PROJECT_ID. More details on this process can be found here: Creating and storing encrypted secrets.

Push this change to main, and Github Actions will deploy your project to Firebase after every commit.

Enjoy