waku-org
/
waku.org
mirror of https://github.com/waku-org/waku.org.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
190 Commits 18 Branches 0 Tags 600 MiB
Commit Graph

6 Commits

Author SHA1 Message Date
Jakub Sokołowski 64d5b7fbbe
feat: use two deploy branches for CI builds 
This way we have two branches on GitHub that reflect the state of the
website after CI build has finished and pushed. See README.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
 2024-02-20 10:14:31 +01:00
Jakub Sokołowski b0ff826302 ci: add genaration of build.json matadate file 
Useful for debugging missing deployments. Result:
```
 > curl -sL dev.waku.org/build.json

```

Signed-off-by: Jakub Sokołowski <jakub@status.im>
 2024-02-19 23:14:18 +09:00
Jakub Sokołowski 5d6220f327
ci: add GitHub token to query bounties (#58) 
Token has limited access to issues in this repo:
https://github.com/waku-org/bounties

Signed-off-by: Jakub Sokołowski <jakub@status.im>
 2023-11-17 18:07:34 +03:30
SWB 6dcd73c759
BREAKING CHANGE: implement docusaurus (#36) 
* BREAKING CHANGE: implement docusaurus
 2023-06-01 21:48:43 +01:00
SWB 72fcd1b4d4
fix: CNAME file issue (#29) 
CNAME file was located in ./static-assets, but it should be in the
`out` directory after the build stage because the `out` folder was
created in the `build` stage.
 2023-03-21 17:53:09 +00:00
swb 057b1512ab add jenkinsfile and CNAME file 
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 16:52:06 +01:00