mirror of
https://github.com/vacp2p/vac.dev.git
synced 2026-01-08 06:13:57 -05:00
c1dcf59684
The current implementation of the site builder requires content
repo to be submited as a zip file for production using env vars
`CONTENT_SOURCE_TYPE=git` and `CONTENT_SOURCE_URL=repo-link.zip`
which is not considered a best practice. Due to this, a race
condition may occur during the build process if another commit
is made while the build is in progress which may lead a security
flow. To work around this,first, we checkout into `src` using
`checkoutToSubdirectory('src')`. Then, we use `local_folder`
mode using `CONTENT_SOURCE_TYPE=local_folder` and
`CONTENT_SOURCE_URL=..src` env vars, just like a local develop.
`local_folder` mode copies the website files from `src` into
`docs` because the site builder is incapable of copying it.
We checkout the builder into the `builder` directory and run
the `install` and `build` commands inside of that directory.
Finally, for publish stages, we copy the `out` directory into
the site repo, since the out directory is in the wrong repo.
978 B
978 B
Vac.dev Website
Made and deployed with logos site-builder.
Continuous Deloyment
masterbranch is deployed to https://vac.dev by CI
developbranch is deployed to https://dev.vac.dev by CI
Change Process
- Create a new working branch from
develop:git checkout develop; git checkout -b my-changes; - Proceed with changes, push to
originand open a Pull Request againstdevelop; - Once approved, merge pull request, check changes on dev.vac.dev;
- Once ready to promote to live website, rebase master on staging:
git checkout master; git pull master; git rebase origin/develop; git push.
Copyright
For all research posts under https://vac.dev/research, copyright and related rights are waived via CC0.