main.yml

# Defaults variables for role wp / wordpress
# Do we want local or remote mysql db ?
wp_use_remote_mysql_host: False
wp_mysql_host: localhost

# Mysql db
wp_db_name: wordpress
wp_db_user: wordpress
wp_db_pass: Fq7R0m9WitoRjmbL3U

# blog instance configuration
wp_local_path: /var/www/wordpress
wp_public_name: my blog
wp_release: 5.1 # ideal to switch to latest

# Do we want to install plugins ?
# Can be an empty list too
wp_plugins:
  - name: openid
    version: 3.5.0

# openid configuration : do we want to configure which IdP to use automatically ?
# Has to be manually enabled by admin on first install though
wp_openid_redirect: False
wp_openid_idp_url: https://id.centos.org/idp/openid

# httpd settings
wp_httpd_hostname: "{{ inventory_hostname }}"
wp_httpd_tls: False # if True, redirect to https in vhost and needs proper TLS x509 cert,key based on wp_httpd_hostname

# ===============================================================================
# httpd_assets_url - Set assets url (without trailing slash).
#
# Here is were css, images and js files will be retrieved from. This is
# normally "https://www.centos.org" in production and
# "https://www.dev.centos.org" in development. When we change the main site
# design all other sites based on it will be changed as well and there won't be
# necessary to maintain separated files. In order for this to work, origin
# domains must be specified in httpd_www_cors option.
#
# This variable should be defined in a high scope location (e.g., under
# `group_vars/all.yml`, or `group_vars/webistes.yml`) so all website-related
# playbooks you run can take advantage of it reducing the number of places you
# need to change.
# ===============================================================================
httpd_assets_url: "https://www.centos.org"


# ===============================================================================
# httpd_navbar - Set website navigation bar.
#
# The navigation bar is visible on the very top of each CentOS website, where
# the CentOS logo and the top-level-always-visible links are placed. The navbar
# can contain both links and menu of links so you can group them. Menus by
# default are hidden and are visible when the user clicks the item that has the
# arrow pointing down on right side.
#
# The navigation bar the httpd_navbar variable defines is re-used in different
# website templates (e.g., mailman, wordpress-theme).  For consistency, it must
# match the content the `_data/centos/navbar.yml` file provides in
# www.centos.org site.
#
# This variable should be defined in a high scope location (e.g., under
# `group_vars/all.yml`, or `group_vars/webistes.yml`) so all website-related
# playbooks you run can take advantage of it reducing the number of places you
# need to change.
#
# When you define link inside the navbar, use `httpd_assets_url` variable as
# much as possible to keep navigability among different environments (e.g.,
# www.dev.centos.org and www.centos.org).  See `httpd_assets_url` block in this
# file to know more.
# ===============================================================================
httpd_navbar:
  - name: "Download"
    icon: "fas fa-download"
    link: "{{ httpd_assets_url }}/download"
    menu: []
  - name: "About"
    icon: "fas fa-info-circle"
    link: "#"

# ===============================================================================
# Blog theme configuration.
#
# Themes are being installed in accumulative way to avoid conflicts between
# different theme versions (e.g., because files were added or removed). You can
# switch from one theme version to another using the wordpress graphical user
# interface, after performing a live preview verification. As new themes are
# installed, older themes are available as backup mechanism.
#
# New theme releases can be found in:
# - https://gitlab.com/CentOS/artwork/centos-web/wordpress-theme-centos/-/releases
# ===============================================================================
wp_theme_name: wordpress-theme-centos
wp_theme_version: "1.0.20"