Skip to content

Commit

Permalink
Merge pull request #8 from chairulakmal/main
Browse files Browse the repository at this point in the history
fix: clarify README to state that users only need to add secrets
  • Loading branch information
grod220 authored Oct 24, 2024
2 parents e958b16 + 27a8a90 commit a4f5fb0
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,11 @@ This GitHub Action automates the build and deployment process for [Minifront](ht

1. **Fork this repository** to your own GitHub account.

2. **Customize the Action**. Modify the `.github/workflows/deploy-minifront.yml` file:
- Fill in environment variables for your desired hosting providers. You can use as many as you like, they will all be deployed sequentially.
- Update the secrets in your GitHub repository accordingly.
2. **Add Environment Secrets**. You do not need to customize the `.github/workflows/deploy-minifront.yml` file. Simply add the necessary environment [secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions) in your GitHub repository for your desired hosting providers:
- You can use as many as you like, they will all be deployed sequentially.
- Providers without configured secrets won't run.
- Github Pages are deployed automatically, but need to be enabled in your repository settings.
- Change cron frequency as desired (given github free tier, you can deploy at most every 4 hours)
- Change cron frequency as desired (given GitHub free tier, you can deploy at most every 4 hours).

3. **Enable GitHub Actions**. Make sure GitHub Actions are enabled in your forked repository (Settings > Actions > General).

Expand Down

0 comments on commit a4f5fb0

Please sign in to comment.