mirror of
https://github.com/inspec/inspec
synced 2024-11-27 07:00:39 +00:00
19ab22f5e2
* wip: extend nginx_conf for http+servers+locations ... well `http` entries really, but we couldnt just call it `https`. the goal is to `nginx_conf.http` / `nginx_conf.servers` / `nginx_conf.locations` and then also have these calls cascaded down to simplify the access to these fields. the current pattern is rather tedious since we need to check for nil everywhere. * add test for new nginx accessors Signed-off-by: Dominik Richter <dominik.richter@gmail.com> * add docs for nginx-conf Signed-off-by: Dominik Richter <dominik.richter@gmail.com> * fix all incorrect NGINX spellings in docs * prevent edge-cases where nginx params are nil for location, http, and servers Signed-off-by: Dominik Richter <dominik.richter@gmail.com> * more descriptive to_s for nginx servers as suggested by @adamleff, thank you! Signed-off-by: Dominik Richter <dominik.richter@gmail.com> * add more descriptive to_s for nginx location Signed-off-by: Dominik Richter <dominik.richter@gmail.com> |
||
---|---|---|
.. | ||
resources | ||
shared | ||
.gitignore | ||
dsl_inspec.md | ||
dsl_resource.md | ||
habitat.md | ||
inspec_and_friends.md | ||
matchers.md | ||
migration.md | ||
plugin_kitchen_inspec.md | ||
profiles.md | ||
README.md | ||
ruby_usage.md | ||
shell.md |
InSpec documentation
This is the home of the InSpec documentation. This documentation provides an introduction to this mechanism and shows how to write custom tests.
The goal of this folder is for any community member to clone these docs, make the changes, check if they are valid, and contribute to the project.
How to build docs
We build docs by:
- Auto-generating docs from code
- Transforming markdown+snippets in this folder into pure markdown in
www/source/docs
- Rendering them to the website via instructions in
www/
For development, you only need step 1!
1 Generate docs
To generate all docs run:
bundle exec rake docs
You can run tasks individually. For a list of tasks run:
bundle exec rake --tasks docs
Stability Index
Every available InSpec resource will indicate its stability. As InSpec matures, certain parts are more reliable than others. Brand new features are likely to be redesigned and marked as such.
The stability indices are as follows:
Stability: Deprecated
- This features will be removed in future versions, because its known for being problematic. Do not rely on it.Stability: Experimental
- New features may change or are removed in future versionsStability: Stable
- API is well established and proofed. Maintaining compatibility is a high priorityStability: Locked
- Only security and performance fixes are allowed