Commit b6d26f8a authored by Lee Garrett's avatar Lee Garrett

typo fixes

parent 89b7beba
......@@ -14,7 +14,7 @@ DebOps is primarly developed using GitHub pull requests. After forking the main
project repository to your own GitHub account, you should create a branch for
a new feature or a bugfix; this helps separate your work on different parts of
the repository. You can read the `DEVELOPMENT.rst <https://github.com/debops/debops/blob/master/DEVELOPMENT.rst>`__
file for tips about managing your forked repository and commiting code.
file for tips about managing your forked repository and committing code.
GPG-signed commits are preferred
......
......@@ -78,7 +78,7 @@ for more details about using DebOps in a Docker container.
Installation
------------
DebOps requires a Python 2.7 environment and Ansiible 2.3+ to work correctly.
DebOps requires a Python 2.7 environment and Ansible 2.3+ to work correctly.
Read the `INSTALL.rst <https://github.com/debops/debops/blob/master/INSTALL.rst>`__
file for specific installation instructions.
......
......@@ -127,7 +127,7 @@ systems:
## (supports Jinja templating as usual):
# content: |
# # {{ ansible_managed }}
# # smplyer security profile.
# # smplayer security profile.
# noblacklist ${HOME}/.config/smplayer
# # And so on.
......
......@@ -48,7 +48,7 @@ x2go_server__deploy_state: 'present'
# Use ``{{ omit }}`` to omit the key fingerprint fetch all together. For
# example, using PPAs does automatically fetch the correct PGP public key
# somehow.
# Refer to the `official X2Go Dokumentation <http://wiki.x2go.org/doku.php/wiki:repositories:debian>`__ for details.
# Refer to the `official X2Go documentation <http://wiki.x2go.org/doku.php/wiki:repositories:debian>`__ for details.
x2go_server__apt_repo_key_fingerprint_map:
'Ubuntu': '{{ omit }}'
'Linuxmint': '{{ omit }}'
......
......@@ -12,7 +12,7 @@ them.
applies there, please.
.. note:: This section of the documentation might not be fully up-to-date. If
there is something missing you are encurraged to cross-check with
there is something missing you are encouraged to cross-check with
debops.nginx_ docs and enhance the documentation.
.. contents::
......
......@@ -22,7 +22,7 @@ release or available archive areas.
The difference between debops.apt_ and ``debops.apt_install`` Ansible roles
is that the former role is used to configure the APT package manager itself,
and latter just installs packages using APT package manager, dependng on its
and latter just installs packages using APT package manager, depending on its
configuration.
Similar Ansible roles
......
......@@ -21,7 +21,7 @@ The ``avahi__daemon_conf_*`` variables are used to specify what parameters
should be present in the :file:`/etc/avahi/avahi-daemon.conf` configuration
file. Each pair of variables manages one section of the INI file. The "default"
variable is combined with the custom variable therefore it's possible to change
the vaule of a parameter without the need to copy the entire variable over to
the value of a parameter without the need to copy the entire variable over to
the Ansible inventory.
Each variable is a YAML dictionary with keys representing the available
......@@ -41,7 +41,7 @@ avahi__services
The ``avahi__*_services`` variables define the services published by Avahi on
its ``.local`` domain. The variables are either YAML dictionaries or YAML lists
of dictionaries that are combined togeter in the
of dictionaries that are combined together in the
:envvar:`avahi__combined_services` in the order they appear in the
:file:`defaults/main.yml` file.
......@@ -86,7 +86,7 @@ specific parameters:
``type``
A string similar to a `SRV record <https://en.wikipedia.org/wiki/SRV_record>`_
that defines the service type and protocol (it's similar in a way that only
the service name and procotol are relevant, other parts of the SRV record
the service name and protocol are relevant, other parts of the SRV record
shouldn't be used). Example service types are ``_ssh._tcp``, ``_http._tcp``.
The list of possible service names can be found in the `Service Name and Transport Protocol Port Number Registry <https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml>`_ maintained by `IANA <https://www.iana.org/>`_.
......
......@@ -55,7 +55,7 @@ can configure Avahi services as well as CNAME aliases if necessary.
See :ref:`avahi__ref_services` for more details about supported parameters.
If advanced control over CNAME aliases published by Avahi is not needed, you
can make the process simplier by including the tasks that configure an Avahi
can make the process simpler by including the tasks that configure an Avahi
service directly in your own role, for example:
.. literalinclude:: examples/avahi-tasks.yml
......
......@@ -72,7 +72,7 @@ Each entry is a YAML dictionary with specific parameters:
``home_mode``
Optional. If set, the home directory of a given user account will have the
specified premissions. If not set, the home directories of existing user
specified permissions. If not set, the home directories of existing user
accounts won't be modified. New accounts will have their home directories
permissions set based on the :envvar:`bootstrap__admin_home_mode` variable.
......
......@@ -119,7 +119,7 @@ Added
- Add kernel parameter configuration and shared memory configuration.
Amount of shared memory limits starting with Linux kernel 3.16 is ridiculusly
Amount of shared memory limits starting with Linux kernel 3.16 is ridiculously
high by default. This configuration limits the shared memory size to
reasonable amounts depending on available system RAM. More information:
https://git.kernel.org/cgit/linux/kernel/git/mhocko/mm.git/commit/include/uapi/linux/shm.h?id=060028bac94bf60a65415d1d55a359c3a17d5c31
......
......@@ -71,7 +71,7 @@ variables that can be used:
Dictionary which should be defined in ``inventory/host_vars/*/``
for a particular host.
The key specifies the name of a variable in the ``asible_local.core.*`` namespace, with
The key specifies the name of a variable in the ``ansible_local.core.*`` namespace, with
value being it's value. You can use normal YAML variables as values, even lists
and dictionaries.
......@@ -182,7 +182,7 @@ them.
System administrator accounts
-----------------------------
Common featue in various services is creation of an administrator account. The
Common feature in various services is creation of an administrator account. The
``debops.core`` role provides two Ansible local facts which can be used by
other roles to make creation of these accounts easier.
......@@ -272,12 +272,12 @@ incorrectly. For example, current Debian Testing release is not detected at
all, and the ``ansible_distribution_release`` variable is set to ``NA`` which,
if used in the roles, can break a lot of existing configuration.
The ``debops.core`` role provides alrernative set of the
The ``debops.core`` role provides alternative set of the
``ansible_distribution`` and ``ansible_distribution_release`` variables through
Ansible local facts, accessible as ``ansible_local.core.distribution`` and
``ansible_local.core.distribution_release``. They use the original Ansible
facts if they are not ``NA`` and refer to the ``ansible_lsb`` otherwise; they
can also be overriden through Ansible inventory. By using these local facts in
can also be overridden through Ansible inventory. By using these local facts in
your roles, you can have a centralized place to control these facts if
necessary.
......
......@@ -143,7 +143,7 @@ Changed
the mode. [ypid_]
- Set :envvar:`cryptsetup__cipher` explicitly to ``aes-xts-plain64`` and use it also
in plain mode which has a different complied-in default than LUKS mode. [ypid_]
in plain mode which has a different compiled-in default than LUKS mode. [ypid_]
- Update documentation. [ypid_]
......
......@@ -583,7 +583,7 @@ mapped to the real clear text block device
:file:`/dev/mapper/vault` on which a filesystem will be created
and which will be mounted as usual.
This is surely a more extrem example but it has been tested in a lab
This is surely a more extreme example but it has been tested in a lab
environment and the setup seems to work just fine. Also automatic
mapping/mounting of all layers works seamlessly on system boot if configured to
do so (which is the default).
......
......@@ -35,7 +35,7 @@ Added
Changed
~~~~~~~
- Support newer Ansible local build methos using ``local_deb``. [drybjed_]
- Support newer Ansible local build methods using ``local_deb``. [drybjed_]
`debops.debops v0.2.2`_ - 2016-07-31
......
......@@ -11,7 +11,7 @@ Reading custom facts
The ``debops.debops_fact`` role uses two INI files to store the custom facts,
one "public" and readable by every user on the system, and one "private" and
readable only by specific system group (``root`` by default). Contents of the
files are merged into one variable tree. There are three typese of facts
files are merged into one variable tree. There are three types of facts
managed by the role, stored in different INI sections.
The ``[default]`` section, available through Ansible local facts as
......
......@@ -411,11 +411,11 @@ if it's defined, 'hba' will be omitted by configuration template.
Default value: ``10``
Optional field are mostly desribed in ``dhcpd.conf`` man page:
Optional field are mostly described in ``dhcpd.conf`` man page:
``port``
Specifies port on which primary and secondary nodes will listen for failover
connection. Diffirent ports for primary and secondary is currently
connection. Different ports for primary and secondary is currently
unsupported.
Default value: ``647``
......
......@@ -49,7 +49,7 @@ Changed
- List of tasks in the role is reorganized and cleaned up. [drybjed_]
- Default list of DokuWiki plugins and templates are moved to separate
variables, so that ``dokuwiki_plugins`` and ``dokuwki_templates`` can be used
variables, so that ``dokuwiki_plugins`` and ``dokuwiki_templates`` can be used
in inventory. [drybjed_]
- The ``dokuwiki_main_domain`` variable is now a string instead of a list.
......
......@@ -87,7 +87,7 @@ The Debian Archive contains the `heartbeat <https://packages.debian.org/search?k
package which provides the ``heartbeat`` service which is a part of the
`Linux High-Availability Stack <http://www.linux-ha.org/wiki/Main_Page>`_.
This creates a conflict in the APT package manager database. The Elastcsearch
This creates a conflict in the APT package manager database. The Elasticsearch
BV. developers `are aware of the issue <https://github.com/elastic/beats/issues/3765>`_
and are considering a number of options to resolve it. In the meantime,
a proposed solution is to `use APT pinning to change APT preferences <https://github.com/elastic/beats/issues/3765#issuecomment-289924787>`_
......
......@@ -86,7 +86,7 @@ a ``name`` key. The dictionaries support specific parameters:
the primary key, and value being their values. This parameter can be used to
group several similar configuration options together in the generated
configuration file, for readability. When this parameter is used, the "leaf"
part of the main configuration name is discared, and only used as a marker
part of the main configuration name is discarded, and only used as a marker
for these parameters. An example configuration:
.. code-block:: yaml
......
......@@ -77,7 +77,7 @@ The Elasticsearch main configuration file
`does not support an include statement or conf.d directory <https://github.com/elastic/elasticsearch/issues/11362>`_.
To mitigate that and allow multiple Elasticsearch configuration sources from
other Ansible roles, the ``debops.elasticsearch`` role supports operation as
a dependent role. This fuctionality can be used by other Ansible roles to
a dependent role. This functionality can be used by other Ansible roles to
better manage Elasticsearch plugins or extend the cluster configuration without
the need to implement the entire role again and with preserved idempotency.
......
......@@ -5,7 +5,7 @@ Introduction
`Elasticsearch <https://en.wikipedia.org/wiki/Elasticsearch>`_ is a distributed
search engine and storage system, also a part of the Elasticsearch, Logstash,
Kibana (ELK) stack. The software is developed by `Elastic <https://eastic.co/>`_.
Kibana (ELK) stack. The software is developed by `Elastic <https://elastic.co/>`_.
The ``debops.elasticsearch`` Ansible role can be used to deploy and manage
Elasticsearch instances on one or more (3+) hosts. The role can be used as
......
......@@ -23,7 +23,7 @@ ansigenome_info:
synopsis: |
[Elasticsearch](https://en.wikipedia.org/wiki/Elasticsearch) is a distributed
search engine and storage system, also a part of the Elasticsearch, Logstash,
Kibana (ELK) stack. The software is developed by [Elastic](https://eastic.co/).
Kibana (ELK) stack. The software is developed by [Elastic](https://elastic.co/).
The `debops.elasticsearch` Ansible role can be used to deploy and manage
Elasticsearch instances on one or more (3+) hosts. The role can be used as
......
......@@ -11,7 +11,7 @@ Default configuration
---------------------
The role will detect presence of a MariaDB database server and use it if
available. If not, a SQLite databse will be automatically configured on the
available. If not, a SQLite database will be automatically configured on the
server. You can configure MariaDB database using the debops.mariadb_server_
Ansible role.
......
......@@ -56,11 +56,11 @@ List of local ``fail2ban`` filters that should be present or absent when configu
Required. Name of the filter.
``after``
Optional. Specify an addtional filter configuration file that ``fail2ban`` will
Optional. Specify an additional filter configuration file that ``fail2ban`` will
read after reading this filter configuration filer.
``before``
Optional. Specify an addtional filter configuration file that ``fail2ban`` will
Optional. Specify an additional filter configuration file that ``fail2ban`` will
read before reading this filter configuration file.
``definitions``
......@@ -73,7 +73,7 @@ List of local ``fail2ban`` filters that should be present or absent when configu
regular expression should be on its own line. Refer to the `examples`_ section.
``filename``
Optional. Alternative name of the filter configuration file. If not specfied, it
Optional. Alternative name of the filter configuration file. If not specified, it
will use the ``name`` of the filter.
``ignoreregex``
......
......@@ -11,8 +11,8 @@ Initial configuration
instance. In its place you will be able to create per-user ``fcgiwrap``
instances, each with their own socket, running as an unprivileged user.
Each instance will make sure that specified user account and group exist, you
can specify additional configurtion to create accounts wich specific shell or
Each instance will make sure that specified user account and group exists, you
can specify additional configuration to create accounts with a specific shell or
home directory. By default system accounts (UID/GID < 1000) are used.
This role requires ``debops.core`` role to configure local fact which provides
......
......@@ -223,7 +223,7 @@ Changed
- Update documentation and Changelog. [drybjed_]
- The ``debops.gitlab`` role now requies at least Ansible 2.1 due to the
- The ``debops.gitlab`` role now requires at least Ansible 2.1 due to the
requirements of the LDAP modules used by the role. [drybjed_]
- Update the Redis support to automatically configure password authentication
......@@ -304,7 +304,7 @@ Changed
~~~~~~~
- Migration to debops.mariadb_ role. [scibi_]
If you have exisitng setup you have to move some files in secrets directory:
If you have existing setup you have to move some files in secrets directory:
.. code-block:: none
......
......@@ -435,7 +435,7 @@ gitlab_runner__ssh_password: ''
# Docker executor configuration [[[
# ---------------------------------
# You should referer to the `Doccker executor documentation <https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md#the-runnersdocker-section>`_
# You should refer to the `Docker executor documentation <https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md#the-runnersdocker-section>`_
# for information about what can be configured and what's the specific syntax
# of each option.
......@@ -536,7 +536,7 @@ gitlab_runner__docker_allowed_services: []
# Docker Machine and autoscaling [[[
# ----------------------------------
# You should referer to the `GitLab Runner autoscaling documentation <https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md#the-runnersmachine-section>`_
# You should refer to the `GitLab Runner autoscaling documentation <https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md#the-runnersmachine-section>`_
# for information about what can be configured and what's the specific syntax
# of each option.
......@@ -605,7 +605,7 @@ gitlab_runner__machine_options: []
# Distributed cache configuration [[[
# -----------------------------------
# You should referer to the `GitLab Runner cache documentation <https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md#the-runnerscache-section>`_
# You should refer to the `GitLab Runner cache documentation <https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md#the-runnerscache-section>`_
# for information about what can be configured and what's the specific syntax
# of each option.
......
......@@ -55,7 +55,7 @@ The Runner instances can be configured with variables specified as the keys of
the dictionary that holds the specific Runner configuration. If any required
keys are not specified, the value of the global variable will be used instead.
Some of the variables will be added togeher (Docker volumes, for example), so
Some of the variables will be added together (Docker volumes, for example), so
that you can define a list of global values included in all of the Runner
instances.
......
......@@ -42,6 +42,6 @@ The password will be hashed and salted on the Ansible controller and only the
salted hash will be configured in the GRUB configuration.
With this change, GRUB will require authentication when attempting to change
boot options or invoking a recovery shell. Booting menu entires will not
boot options or invoking a recovery shell. Booting menu entries will not
require authentication so this configuration should be safe for normal
operation.
......@@ -14,7 +14,7 @@ Gunicorn server is broadly compatible with various web frameworks, simply
implemented, light on server resources, and fairly speedy.
The `debops.gunicorn` Ansible role uses the [Debian package configuration structure](https://chris-lamb.co.uk/posts/sysadmin-friendly-deployment-gunicorn-debian)
to manage multiple `gunicorn` applications as a signle service. This can be
to manage multiple `gunicorn` applications as a single service. This can be
used to deploy applications that use either a system Python installation, or
a `virtualenv` Python environment.
......
......@@ -113,7 +113,7 @@ used to modify the internal service configuration.
Optional. Specify an absolute path to the file with the PID of the main Green
Unicorn process.
If not specified, the role will creata PID file in the path:
If not specified, the role will create a PID file in the path:
.. code-block:: none
......
......@@ -7,7 +7,7 @@ Gunicorn server is broadly compatible with various web frameworks, simply
implemented, light on server resources, and fairly speedy.
The ``debops.gunicorn`` Ansible role uses the `Debian package configuration structure <https://chris-lamb.co.uk/posts/sysadmin-friendly-deployment-gunicorn-debian>`_ on older Debian and Ubuntu releases
to manage multiple ``gunicorn`` applications as a signle service. This can be
to manage multiple ``gunicorn`` applications as a single service. This can be
used to deploy applications that use either a system Python installation, or
a ``virtualenv`` Python environment.
......
......@@ -39,7 +39,7 @@ should be present in the ``virtualenv`` environment:
Next, in your role task list, include set of tasks that will create the
``virtualenv`` environment and install the required modules inside (the example
below requies Ansible 2.1+ to work):
below requires Ansible 2.1+ to work):
.. code-block:: yaml
......
......@@ -23,6 +23,6 @@ ansigenome_info:
implemented, light on server resources, and fairly speedy.
The `debops.gunicorn` Ansible role uses the [Debian package configuration structure](https://chris-lamb.co.uk/posts/sysadmin-friendly-deployment-gunicorn-debian)
to manage multiple `gunicorn` applications as a signle service. This can be
to manage multiple `gunicorn` applications as a single service. This can be
used to deploy applications that use either a system Python installation, or
a `virtualenv` Python environment.
......@@ -108,7 +108,7 @@ The ``debops.hashicorp`` role maintains a set of Ansible local facts with
information about the installed applications. Other roles can use these facts
in an idempotent way to prepare their own configuration. These facts are:
``ansble_local.hashicorp.installed``
``ansible_local.hashicorp.installed``
Boolean. If ``True``, the role has been correctly configured.
``ansible_local.hashicorp.applications``
......
Enchancements to ifupdown in systemd
====================================
Enhancements to ifupdown in systemd
===================================
.. include:: includes/all.rst
......
......@@ -49,7 +49,7 @@ List of optional LVM parameters:
``lvm_vg``
Name of a LVM Volume Group which should be created using all iSCSI LUNs
presented by a given iSCSI Target. Should only have alphanumeric characters
and underscores. Do not use hypens (``-``) in the name.
and underscores. Do not use hyphens (``-``) in the name.
``lvm_state``
Specifies if a given Volume Group should exist (``present``) or not
......@@ -112,7 +112,7 @@ List of required parameters:
``lv``
Name of a Logical Volume, should only have alphanumeric characters and
underscores. Do not use hypens (``-``) in the name.
underscores. Do not use hyphens (``-``) in the name.
``vg``
Name of a Volume Group which should be used to create a given Logical Volume.
......@@ -147,7 +147,7 @@ List of optional filesystem parameters:
Additional options passed to ``mkfs``.
``fs_force``
Bool. If present and ``True``, allows Ansible to reformat already exising
Bool. If present and ``True``, allows Ansible to reformat an already existing
filesystem. Use with caution.
List of optional mount parameters:
......
......@@ -11,7 +11,7 @@
[Kibana](https://en.wikipedia.org/wiki/Kibana) is a web-based dashboard which
can be used to display and analyze data stored in an Elasticsearch cluster. It
is a part of the Elasticsearch, Logstash, Kibana (ELK) stack. The software is
developed by [Elastic](https://eastic.co/).
developed by [Elastic](https://elastic.co/).
The `debops.kibana` Ansible role can be used to deploy Kibana behind an
`nginx` reverse proxy which connects to a local or remote Elasticsearch
......
......@@ -20,7 +20,7 @@ kibana__configuration
The ``kibana__*_configuration`` variables define the Kibana configuration
options that are set in the :file:`/etc/kibana/kibana.yml` configuration file.
The main Kiana configuration file format is YAML.
The main Kibana configuration file format is YAML.
The `reference documentation <https://www.elastic.co/guide/en/kibana/current/settings.html>`_
defines two YAML formats recognized by Kibana, hierarchical (YAML dictionary
keys are indented), or flat (YAML dictionary keys are separated by dots). This
......@@ -85,7 +85,7 @@ a ``name`` key. The dictionaries support specific parameters:
the primary key, and value being their values. This parameter can be used to
group several similar configuration options together in the generated
configuration file, for readability. When this parameter is used, the "leaf"
part of the main configuration name is discared, and only used as a marker
part of the main configuration name is discarded, and only used as a marker
for these parameters. An example configuration:
.. code-block:: yaml
......
......@@ -59,7 +59,7 @@ The Kibana main configuration file
`does not support an include statement or conf.d directory <https://github.com/elastic/elasticsearch/issues/11362>`_.
To mitigate that and allow multiple Kibana configuration sources from other
Ansible roles, the ``debops.kibana`` role supports operation as a dependent
role. This fuctionality can be used by other Ansible roles to better manage
role. This functionality can be used by other Ansible roles to better manage
Kibana plugins or extend the configuration without the need to implement the
entire role again and with preserved idempotency.
......@@ -69,7 +69,7 @@ See the :ref:`kibana__ref_dependency` for more details.
Example inventory
-----------------
To deploy Kiana, you can add the host to the
To deploy Kibana, you can add the host to the
``[debops_service_kibana]`` Ansible inventory group. By default Kibana expects
an Elasticsearch instance on the same host to leverage the cluster load
balancing. To install an ES node in a load balancer configuration, include the
......
......@@ -6,7 +6,7 @@ Introduction
`Kibana <https://en.wikipedia.org/wiki/Kibana>`_ is a web-based dashboard which
can be used to display and analyze data stored in an Elasticsearch cluster. It
is a part of the Elasticsearch, Logstash, Kibana (ELK) stack. The software is
developed by `Elastic <https://eastic.co/>`_.
developed by `Elastic <https://elastic.co/>`_.
The ``debops.kibana`` Ansible role can be used to deploy Kibana behind an
``nginx`` reverse proxy which connects to a local or remote Elasticsearch
......
......@@ -19,7 +19,7 @@ ansigenome_info:
[Kibana](https://en.wikipedia.org/wiki/Kibana) is a web-based dashboard which
can be used to display and analyze data stored in an Elasticsearch cluster. It
is a part of the Elasticsearch, Logstash, Kibana (ELK) stack. The software is
developed by [Elastic](https://eastic.co/).
developed by [Elastic](https://elastic.co/).
The `debops.kibana` Ansible role can be used to deploy Kibana behind an
`nginx` reverse proxy which connects to a local or remote Elasticsearch
......
......@@ -268,7 +268,7 @@ Create a NFS-based storage pool on remote ``libvirt`` host::
libvirt__pools:
- name: 'nfs-pool'
type: 'nfs'
host: 'nfs.exmmple.org'
host: 'nfs.example.org'
src: '/srv/nfs'
path: '/media/nfs/libvirt'
uri: 'vm-host'
......
......@@ -19,7 +19,7 @@ The current role maintainer_ is drybjed_
Changed
~~~~~~~
- Mostly automated update to the lastest DebOps Standards Version. [ypid_]
- Mostly automated update to the latest DebOps Standards Version. [ypid_]
Fixed
~~~~~
......
......@@ -117,7 +117,7 @@ List of optional filesystem parameters:
filesystem. Use with caution.
``fs_resizefs``
Boolean. If present and ``True``, and if the block device and filessytem size
Boolean. If present and ``True``, and if the block device and filesystem size
differ, grow the filesystem into the space. Note, XFS Will only grow if mounted.
Use with caution especially if you shrink the volume.
......
......@@ -130,7 +130,7 @@ Changed
- Update documentation. [drybjed_]
- Reorder the fastcgi parameters in :program:`nginx` configuration to fix issue with
`fcgiwrap interpreting the first occurence <http://mailman.nginx.org/pipermail/nginx/2012-June/034224.html>`_
`fcgiwrap interpreting the first occurrence <http://mailman.nginx.org/pipermail/nginx/2012-June/034224.html>`_
of the variable instead of the last. [drybjed_]
Removed
......
......@@ -25,7 +25,7 @@ role are impacted under the following conditions:
**AND**
- For thos hosts the :envvar:`mariadb__delegate_to` variable is not defined
- For those hosts the :envvar:`mariadb__delegate_to` variable is not defined
in the Ansible inventory which means the default value is used during role
execution.
......
......@@ -285,7 +285,7 @@ keys:
Required for the main options. Name of the option to add.
``section``
Required for the definiton of a configuration section. Create new section of
Required for the definition of a configuration section. Create new section of
the configuration file, written in square brackets.
``state``
......
......@@ -58,7 +58,7 @@ keys:
Required for the main options. Name of the option to add.
``section``
Required for the definiten of a configuration section. Create new section of
Required for the definition of a configuration section. Create new section of
the configuration file, written in square brackets.
``state``
......
......@@ -36,7 +36,7 @@ netbox__domain: '{{ ansible_local.core.domain
# .. envvar:: netbox__base_packages [[[
#
# List of APT packages which are requied by the NetBox application.
# List of APT packages which are required by the NetBox application.
netbox__base_packages:
- 'git'
- 'build-essential'
......
......@@ -46,7 +46,7 @@ Internal application server
---------------------------
The ``debops.netbox`` role can deploy NetBox with either a system-wide
``gunicorn`` service (default), or with an iternal ``gunicorn`` application
``gunicorn`` service (default), or with an internal ``gunicorn`` application
sever using its own ``netbox`` ``systemd`` unit file. The role automatically
detects if the ``debops.gunicorn`` role has been deployed on a host and
switches between these modes as needed.
......
......@@ -98,7 +98,7 @@ NSS services defined as strings
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Each element of a YAML service list can be a string, which is a name of the NSS
service which should be enabled for a given databse. This service will be
service which should be enabled for a given database. This service will be
enabled when a corresponding string is found in the
:envvar:`nsswitch__combined_services` variable. For example, the configuration
below will only enable file-based user and group lookups:
......@@ -262,5 +262,5 @@ define a variable in Ansible inventory like this:
With this configuration in place, system should ask the DNS database before
looking in local :file:`/etc/hosts` file. If you plan to change a database
service lookup order, make sure that you include all of the relevant services
in your customized variable, since it will mask the default dataabse list as
in your customized variable, since it will mask the default database list as
a whole.
......@@ -81,7 +81,7 @@ Changed
NTP server as usual, by specifying it using :envvar:`ntp__daemon` variable. The
current installations won't be changed. [drybjed_]
- Move the :command:`dpkg-reconfigre` task after the NTP installation and
- Move the :command:`dpkg-reconfigure` task after the NTP installation and
configuration tasks to avoid issues with idempotency on Ubuntu. [drybjed_]
- Move the NTP daemon installation condition to a new :envvar:`ntp__daemon_enabled`
......
......@@ -27,7 +27,7 @@ The ``nullmailer`` service does not provide support for local mail - all mail
is forwarded to the configured SMTP servers for further processing. If you need
more advanced SMTP configuration, you should check out the debops.postfix_
role which can configure the Postfix MTA. This also means that in a new
environment, you should perpare at least 1 host as the central mail hub for
environment, you should prepare at least 1 host as the central mail hub for
your network, or use an already existing SMTP server for relaying mail
messages.
......
......@@ -53,7 +53,7 @@ the current host domain, or a YAML dictionary with specific parameters:
:envvar:`opendkim__default_key_size` will be used.
``type``
Optional. The private key tyle (``rsa`` or ``dsa``) which should be generated
Optional. The private key style (``rsa`` or ``dsa``) which should be generated
by the :command:`openssl` command. Currently only ``rsa`` makes sense.
``state``
......@@ -98,7 +98,7 @@ opendkim__signing_table
The ``opendkim__*_signing_table`` variables define a mapping between the
contents of the ``From:`` header field in a mail message and the DomainKey used
to sign the message. The format of the ``From:`` hader interpreted by OpenDKIM
to sign the message. The format of the ``From:`` header interpreted by OpenDKIM
depends on the type of the table used (see :manpage:`opendkim.conf(5)`). The
role by default maps the entire domain, without specifying any users.
......
......@@ -9,7 +9,7 @@ v0.1.0
- Add Changelog. [drybjed]
- Move OpenVZ repository variables from ``vars/main.yml`` to
``defaults/main.yml`` so that they can be overriden if necessary. [drybjed]
``defaults/main.yml`` so that they can be overridden if necessary. [drybjed]
- Expand admin account variables to allow for system admin accounts with more
configuration options like default shell, multiple system groups, different
......
......@@ -57,7 +57,7 @@ Changed
and has already been updated in the `debops-playbooks repository <https://github.com/debops/debops-playbooks>`_
for feature parity with Ansible version in the future. [drybjed_]
- Fix typo in variable name by renaming ``owncloud__theme_entitiy_name`` to
- Fix typo in variable name by renaming ``owncloud__theme_entity_name`` to
:envvar:`owncloud__theme_entity_name`. [jbicha]
- Derive LDAP port from :envvar:`owncloud__ldap_port`. [ypid_]
......@@ -153,7 +153,7 @@ Added
:envvar:`owncloud__app_documents_enabled` to ``True``. [ypid_]
- Enabled in memory caching using `APCu <https://pecl.php.net/package/APCu>`_
by default according to the `official ownCloud Dokumentation
by default according to the `official ownCloud documentation
<https://doc.owncloud.org/server/9.0/admin_manual/configuration_server/caching_configuration.html>`_. [ypid_]
- Support fully automated ownCloud security updates (disabled by default). [ypid_]
......