Go to file
SWB c1dcf59684
add jenkinsfile and CNAME file (#102)
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.
2023-03-16 12:04:50 +01:00
.github Update labels.yml 2022-08-02 16:17:14 +08:00
_data/authors update franck's socials 2022-11-08 14:39:53 +11:00
research i cannt spel 2022-11-18 12:40:22 +08:00
static-assets add jenkinsfile and CNAME file (#102) 2023-03-16 12:04:50 +01:00
.gitignore Staging (#67) 2022-06-10 13:52:01 +01:00
Jenkinsfile add jenkinsfile and CNAME file (#102) 2023-03-16 12:04:50 +01:00
README.md add jenkinsfile and CNAME file (#102) 2023-03-16 12:04:50 +01:00
config.json disable auto embedding of youtube videos. 2022-11-07 17:50:00 +03:30
contribute.md contribute pseudonymously (#92) 2022-08-30 10:34:34 +02:00
media.md Feat/update copy (#79) 2022-08-02 12:32:48 +08:00
open-problems.md Fix peer scoring comment 2022-11-30 16:38:44 +01:00
principles.md Update copy (#85) 2022-08-05 14:42:11 +08:00
projects.md Update copy (#85) 2022-08-05 14:42:11 +08:00
publications.md Update copy (#85) 2022-08-05 14:42:11 +08:00
research-areas.md Add/research areas roadmaps (#87) 2022-08-25 10:48:44 +02:00
vac.md Update copy (#85) 2022-08-05 14:42:11 +08:00

README.md

Vac.dev Website

Made and deployed with logos site-builder.

Continuous Deloyment

Change Process

  1. Create a new working branch from develop: git checkout develop; git checkout -b my-changes;
  2. Proceed with changes, push to origin and open a Pull Request against develop;
  3. Once approved, merge pull request, check changes on dev.vac.dev;
  4. 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.