rhysonlin / vibe-website

Source that generates https://vibe.us

Vibe Website

This repo generates files for static hosted website: https://vibe.us.

How to deploy (for devs)

Beta environment

Commits to master branch automatically deploys to https://vibe-beta.com.

To deploy your own branch to https://vibe-beta.com, use command below. Note since we only have one beta environment, it is possible someone deploying from Slack app overrides your deployment.

curl -X POST \
https://api.github.com/repos/vibeus/vibe-website/deployments \
-H "Content-Type: application/json" \
-H "Accept: application/vnd.github.v3+json" \
-H "Authorization: token YOUR_PERSONAL_ACCESS_TOKEN" \
-d '{"required_contexts": [], "auto_merge": false, "environment": "staging", "ref": "your_branch_name_or_sha"}'

If you want to reference to a non-master hugo-common branch:

hugo mod get -u github.com/vibeus/hugo-common/v2@your_branch_name_or_sha

Please always point to master hugo-common before merging your branch into master branch.

Prod environment

It's recommended to use Slack app to deploy production, to reduce human errors. See details below.

How to deploy (for non-devs)

Use "Vibe Admin" Slack app, as shown below.

Notes:

1. When task is set to sync-blogs, deployment will fail if blog post contains PNG image that are larger than 3MB. Either reduce the image size (e.g. use smaller size, or convert it to JPG), or contact @jiulongw to override this limit.
2. If sync-blogs or sync-videos was used to deploy to staging, there is no need to add them in production deployment after validating in the beta environment.