From 283cd6809e5a9e0b826ed27a98111e51591970d8 Mon Sep 17 00:00:00 2001 From: Daniel Berteaud Date: Wed, 4 Aug 2021 16:00:07 +0200 Subject: [PATCH] Update to 2021-08-04 16:00 --- roles/akeneo_pim/README.md | 34 ++++++++++++++++++++++++++++++++++ roles/diagrams/defaults/main.yml | 4 ++-- roles/metabase/defaults/main.yml | 4 ++-- 3 files changed, 38 insertions(+), 4 deletions(-) create mode 100644 roles/akeneo_pim/README.md diff --git a/roles/akeneo_pim/README.md b/roles/akeneo_pim/README.md new file mode 100644 index 0000000..e4f140b --- /dev/null +++ b/roles/akeneo_pim/README.md @@ -0,0 +1,34 @@ +# Akeneo PIM + +[Akeneo PIM](https://www.akeneo.com/) A Product Information Management (PIM) solution is aimed to centralize all the marketing data + +## Settings + +Akeneo requires a few settings at the host level. Something like this +``` +# This should be defined on the server which will host the database +# It's not mandatory to be on the same host as the PIM itself. But the important thing is that AKeneo PIM +# requires MySQL. It'll not work with MariaDB +mysql_engine: mysql + +# Prevent an error when checking system requirements. Note that this is only for the CLI +# as web access will use it's own FPM pool +php_conf_memory_limit: 512M + +# We need Elasticsearch 7. Same foir MySQL, it's not required to be on the same host +es_major_version: 7 + +# Define a vhost to expose the PIM. Note that this is a minimal example +# And you will most likely want to put a reverse proxy (look at the nginx role) in front of it +httpd_ansible_vhosts: + - name: pim.example.org + document_root: /opt/pim_1/app/public + +``` + +## Installation +Installation should be fully automatic + +## Upgrade +Major upgrades might require some manual steps, as detailed on https://docs.akeneo.com/5.0/migrate_pim/upgrade_major_version.html + diff --git a/roles/diagrams/defaults/main.yml b/roles/diagrams/defaults/main.yml index 156229c..6001ff6 100644 --- a/roles/diagrams/defaults/main.yml +++ b/roles/diagrams/defaults/main.yml @@ -1,11 +1,11 @@ --- # Veresion of diagrams to deploy -diagrams_version: 14.8.4 +diagrams_version: 14.9.3 # URL of the WAR file to deploy diagrams_war_url: https://github.com/jgraph/drawio/releases/download/v{{ diagrams_version }}/draw.war # Expected sha1 of the WAR file -diagrams_war_sha1: 60ccb0c76c5ea6af8879e9a8b4115466f05f7bcd +diagrams_war_sha1: 9d351ba93aacf4ed33e60998c864e494676c4cf0 # root directory of the installation diagrams_root_dir: /opt/diagrams # Should ansible manage upgrades, or just initial install ? diff --git a/roles/metabase/defaults/main.yml b/roles/metabase/defaults/main.yml index 1710e55..fab004e 100644 --- a/roles/metabase/defaults/main.yml +++ b/roles/metabase/defaults/main.yml @@ -1,11 +1,11 @@ --- # Version to deploy -metabase_version: 0.40.1 +metabase_version: 0.40.2 # URL to fetch the jar metabase_jar_url: https://downloads.metabase.com/v{{ metabase_version }}/metabase.jar # Expected sha1 of the jar -metabase_jar_sha1: e40a7fc2a5eeeb63df6a90d447139a6bb076d6f5 +metabase_jar_sha1: a955c2a94b05ba3c21510315c41ceba898c8bb4a # Should ansible handle upgrades ? If set to false, only the initial install (and the config) will be handled metabase_manage_upgrade: True