| commit | 4c1bfdaafb8f0a17942383886dadb1e7743dfa34 | [log] [tgz] |
|---|---|---|
| author | John Interrante <interran@research.ge.com> | Tue Feb 21 15:21:56 2023 -0800 |
| committer | John Interrante <interran@research.ge.com> | Thu Feb 23 12:38:19 2023 -0800 |
| tree | 8871dde0751c4d75f240ed24c8558c539aa3187c | |
| parent | 04697b42d9d9d322a4e512bb9e8c1b10a1f4861e [diff] |
Rename daffodil-runtime2 Update places mentioning runtime2 as part of renaming daffodil-runtime2 to daffodil-codegen-c. 3.1.0.md, 3.2.0.md, 3.2.1.md, 3.3.0.md, 3.4.0.md: Say just "code generator" in some places. Update link to daffodilc-todos. cli.md: Rename runtime2 to codegen-c. daffodilc-todos.adoc: Rename from runtime2-todos.adoc. Rename runtime2 to codegen-c. Shorten arrays section since we have now implemented arrays with finite bounds and have only unbounded arrays left to do. DAFFODIL-2796
The Apache Daffodil website is based off of the Apache Website Template.
The website is generated using Jekyll and some plug-ins for it.
To improve reproducibility and to minimize the effects and variability of a users environment, it is recommended that changes to the site repo be tested locally with a container. To do so, run one of the following commands.
With docker:
docker run -it --rm \ --publish 127.0.0.1:4000:4000 \ --volume="$PWD:/srv/jekyll" \ docker.io/jekyll/jekyll:4.2.0 \ jekyll serve --watch --source site
With rootless podman:
podman run -it --rm \ --publish 127.0.0.1:4000:4000 \ --volume="$PWD:/srv/jekyll" \ --env JEKYLL_ROOTLESS=1 \ docker.io/jekyll/jekyll:4.2.0 \ jekyll serve --watch --source site
Then open http://localhost:4000 to view the site served by the Jekyll container. Changes to files in the site directory are automatically rebuilt and served.
Once satisfied, create a branch and open a pull request using the Daffodil project Code Conttributor Workflow but using the website repo instead of the code repo.
Daffodil uses gitpubsub for publishing to the website. The static content served via Apache must be served in the content directory on the asf-site orphan branch. When changes are merged into the main branch on GitHub, a GitHub action will automatically run and perform the necessary steps to publish the site.