Publish static website to DEPT.dev
HV Publish
==========
Within bitbucket pipelines:
``
yarn run build # build your site
npm install -g hv-publish
save2repo
hv-publish
Under the assumption of the build directory being at .
and save2repo)hv-publish and save2repo are very often used in conjunction, but the order may vary:
- hv-publish
- save2repo
or
- save2repo
- hv-publish
The first should be the normal case. But whatever the order, we want to get most out of the combination:
hv-publish should
- publish to Netlify
- save the website info to dept.dev
- save the commit info to dept.dev
- of the source repository
- and the build repository
save2repo should
- commit to another bitbucket git repository
- the commit message should include the dept.dev index + commit messages
To make sure this works for both order cases, let's take these steps:
- hv-publish
- publish to Netlify
- save to dept.dev --> .hv-publish.json
- save2repo
- save to repo, use info of --> .save2repo.json
- patch dept.dev
- save2repo
- save to repo, use only commit messages --> .save2repo.json
- hv-publish
- publish to Netlify
- save to dept.dev, use info of
- update commit message with info of hv-publish
- hv-publish
- publish to Netlify
- if .save2repo.json
- save to dept.dev with all info
- update commit message with info from dept.dev
- else
- save to dept.dev without build_repo info
- save result to
- save2repo
- if .hv-publish.json
- commit to repo with info from
- patch dept.dev with commit info
- else
- commit to repo without dept.dev info (no index)
- save commit info to