91c6b1a6d2
Let's describe the state of things at a high level, independent of the tracking issue which has a lot more detail (and hence noise). This document keeps things at a high level and describes how to enable things today. |
||
|---|---|---|
| .. | ||
| _sass/color_schemes | ||
| _config.yml | ||
| adapting-existing.md | ||
| atomic-upgrades.md | ||
| buildsystem-and-repos.md | ||
| composefs.md | ||
| contributing-tutorial.md | ||
| CONTRIBUTING.md | ||
| deployment.md | ||
| formats.md | ||
| Gemfile | ||
| ima.md | ||
| index.md | ||
| introduction.md | ||
| prep-docs.sh | ||
| README-historical.md | ||
| README.md | ||
| related-projects.md | ||
| repo.md | ||
| repository-management.md | ||
This documentation is written in Jekyll format to be published on GitHub Pages. The rendered HTML will be automatically built and published, but you can also use Jekyll locally to test changes.
First you need to install Ruby and
RubyGems to get Jekyll and the other gem
dependencies. This is easiest using the distro's packages. On RedHat
systems this is rubygems and on Debian systems this is
ruby-rubygems.
Next Bundler is needed to install the gems using
the provided Gemfile. You can do this by running gem install bundler or using distro packages. On RedHat systems this is
rubygem-bundler and on Debian systems this is ruby-bundler.
Now you can prepare the Jekyll environment. Change to this directory and run:
bundle config set --local path vendor/bundle
bundle install
Finally, run the prep-docs.sh script and then render and serve the
site locally with Jekyll:
./prep-docs.sh
bundle exec jekyll serve