Merge ~sergiodj/ubuntu-docker-images/+git/templates:delete-data-dir into ~ubuntu-docker-images/ubuntu-docker-images/+git/templates:main

[Sergio Durigan Junior]

We've been keeping each image's YAML data (used to generate the templates) inside their own repositories. Our 'data/' directory is a relic from when we used to keep everything in this repo.

This commit gets rid of it, and also updates the HACKING_docs.md template to make it clearer where the data is located.

[Athos Ribeiro (athos-ribeiro)]

LGTM

Thanks, Sergio

review: Approve

[Sergio Durigan Junior (sergiodj)]

On Monday, June 21 2021, Athos Ribeiro wrote:

> Review: Approve
>
> LGTM
>
> Thanks, Sergio

Thanks, Athos.

--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14

diff --git a/data/apache2.yaml b/data/apache2.yaml
deleted file mode 100644
index e95c47f..0000000
--- a/data/apache2.yaml
+++ /dev/null
@@ -1,43 +0,0 @@
-application: Apache2
-main: true
-repo: apache2
-description: >
-  The Apache HTTP Server Project's goal is to build a secure, efficient and extensible HTTP server as standards-compliant open source software. The result has long been the number one web server on the Internet. Read more on the [apache2 website](https://httpd.apache.org/).
-version: 2.4.41
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  parameters:
-    - -p 8080:80
-  access: Access your Apache2 server at `http://localhost:8080`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -p
-    value: 8080:80
-    description: Expose Apache2 on `localhost:8080`.
-  - type: -v
-    value: /local/path/to/website:/var/www/html
-    description: Mount and serve a local website.
-  - type: -v
-    value: /path/to/apache2.conf:/etc/apache2/apache2.conf
-    description: Local [configuration file](https://httpd.apache.org/docs/2.4/) `apache2.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf)).
-debug:
-  - nothing
-microk8s:
-  configmap:
-    files:
-      - key: apache2
-        name: apache2.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/apache2.conf
-      - key: apache2-site
-        name: index.html
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/config/html/index.html
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/apache2/plain/examples/apache2-deployment.yml
-    access: You will now be able to connect to the apache2 server on `http://localhost:30080`.
diff --git a/data/cortex.yaml b/data/cortex.yaml
deleted file mode 100644
index b3cd981..0000000
--- a/data/cortex.yaml
+++ /dev/null
@@ -1,44 +0,0 @@
-application: Cortex
-main: false
-repo: cortex
-description: |
-  Cortex provides horizontally scalable, highly available, multi-tenant, long term storage for Prometheus.
-
-  * Horizontally scalable: Cortex can run across multiple machines in a cluster, exceeding the throughput and storage of a single machine. This enables you to send the metrics from multiple Prometheus servers to a single Cortex cluster and run "globally aggregated" queries across all data in a single place.
-  * Highly available: When run in a cluster, Cortex can replicate data between machines. This allows you to survive machine failure without gaps in your graphs.
-  * Multi-tenant: Cortex can isolate data and queries from multiple different independent Prometheus sources in a single cluster, allowing untrusted parties to share the same cluster.
-  * Long term storage: Cortex supports Amazon DynamoDB, Google Bigtable, Cassandra, S3, GCS and Microsoft Azure for long term storage of metric data. This allows you to durably store data for longer than the lifetime of any single machine, and use this data for long term capacity planning.
-
-  Read more on the [Cortex website](https://cortexmetrics.io/).
-version: 1.4.0
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  parameters:
-    - -p 32709:9009
-  access: Access your Cortex server at `http://localhost:32709`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -p
-    value: 32709:9009
-    description: Expose Cortex on `localhost:32709`.
-  - type: -v
-    value: /my/local/cortex.yaml:/etc/cortex/cortex.yaml
-    description: Local [configuration file](https://cortexmetrics.io/docs/configuration/) `cortex.yaml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml)).
-debug:
-  - nothing
-microk8s:
-  configmap:
-    files:
-      - key: main-config
-        name: cortex.yaml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/config/cortex.yaml
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/cortex/plain/oci/examples/cortex-deployment.yml
-    access: You will now be able to connect to the Cortex server on `localhost:32709`.
diff --git a/data/grafana.yaml b/data/grafana.yaml
deleted file mode 100644
index 35e436f..0000000
--- a/data/grafana.yaml
+++ /dev/null
@@ -1,46 +0,0 @@
-application: Grafana
-main: false
-repo: grafana
-description: >
-  Grafana is a feature rich metrics dashboard and graph editor for Cloudwatch, Elasticsearch, Graphite, InfluxDB, OpenTSB, Prometheus, and Hosted Metrics. 
-  Read more on the [Grafana website](https://grafana.com/docs/).
-version: 7.2.0
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  parameters:
-    - -p 30000:3000
-  access: Access your Grafana server at `localhost:30000`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -p
-    value: 30000:3000
-    description: Expose Grafana on `localhost:30000`.
-  - type: -v
-    value: /path/to/grafana/provisioning/files/:/etc/grafana/provisioning/
-    description: Pass a directory with files to provision a Grafana `datasource` and `dashboard` (see [documentation](https://grafana.com/docs/grafana/latest/administration/provisioning/)).
-  - type: -v
-    value: /path/to/persisted/data:/var/lib/grafana
-    description: Persist data with a voulme instead of initializing a new database for each newly launched container.
-debug: None
-microk8s:
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/grafana-deployment.yml
-    access: You will now be able to connect to the Grafana on `http://localhost:30000`.
-  configmap:
-    files:
-    - key: grafana-datasource
-      name: datasource.yml
-      link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/datasource.yml
-    - key: grafana-dashboard-definition
-      name: dashboard.yml
-      link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/dashboard.yml
-    - key: grafana-dashboard
-      name: system-stats-dashboard.json
-      link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/grafana/plain/examples/config/system-stats-dashboard.json
diff --git a/data/memcached.yaml b/data/memcached.yaml
deleted file mode 100644
index 2c157d8..0000000
--- a/data/memcached.yaml
+++ /dev/null
@@ -1,71 +0,0 @@
-application: Memcached
-main: true
-repo: memcached
-description: >
-  Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering. It is a short-term memory for applications.
-  Memcached allows to take memory from parts of a system where you have more than you need and make it accessible to areas where you have less than you need. Read more on the [memcached website](https://memcached.org/).
-version: 1.5.22
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  nothing:
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -e
-    value: MEMCACHED_CACHE_SIZE=64MB
-    description: Determines the size of the cache.
-  - type: -e
-    value: MEMCACHED_MAX_CONNECTIONS=1024
-    description: Determines the maximum number of concurrent connections.
-  - type: -e
-    value: MEMCACHED_THREADS=4
-    description: Determines the number of threads to process requests.
-  - type: -e
-    value: MEMCACHED_PASSWORD
-    description: Define the password for the `root` user if another username is provided. By default the authentication is disabled but if this option is passed it becomes enabled.
-  - type: -e
-    value: MEMCACHED_USERNAME
-    description: Define a new user. If this option is passed a password is needed to authenticate the new user.
-  - type: -p
-    value: 11211
-    description: Memcached is exposed inside the container on port `11211`.
-debug:
-  text: |
-    <details>
-    <summary>You can access the Memcached instance with telnet from another container (click to expand).</summary>
-
-    ```sh
-    # Create a dedicated network
-    $ docker network create memcached-network
-    # Connect the main container to it
-    $ docker network connect memcached-network memcached-container
-    # Run an interactive container with the latest Ubuntu
-    $ docker run -it --rm --name telnet --network memcached-network ubuntu bash
-    # Install the telnet cli from within the container
-    > apt update && apt install telnet -y
-    # Connect to the memcached instance using telnet
-    > telnet memcached-container 11211
-    Trying 172.30.0.2...
-    Connected to memcached.
-    Escape character is '^]'.
-    ```
-    From there you can run `memcached` commands, as documented in [their wiki](https://github.com/memcached/memcached/wiki/Commands).
-
-    </details>
-
-    ```sh
-    $ telnet memcached-container 11211
-    ```
-
-    There are cases where one might want to pass some memcached command line flags that are not configurable via environment variables.
-    In this case you can append the flags themselves or a shell script to the run command.
-microk8s:
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/memcached/plain/examples/memcached-deployment.yml
-    access: Memcached will be listening on port `31211` in your host.
diff --git a/data/mysql.yaml b/data/mysql.yaml
deleted file mode 100644
index 7b91e51..0000000
--- a/data/mysql.yaml
+++ /dev/null
@@ -1,80 +0,0 @@
-application: MySQL
-main: true
-repo: mysql
-description: >
-  MySQL is a fast, stable and true multi-user, multi-threaded SQL database
-  server. SQL (Structured Query Language) is the most popular database query
-  language in the world. The main goals of MySQL are speed, robustness and ease
-  of use. Read more on the [MySQL website](https://dev.mysql.com/doc/refman/8.0/en/).
-version: 8.0.22
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - s390x
-docker:
-  parameters:
-    - -p 30306:3306
-    - -e MYSQL_ROOT_PASSWORD=My:S3cr3t/
-  access: Access your MySQL server at `localhost:30306`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -e
-    value: MYSQL_ROOT_PASSWORD=secret_for_root
-    description: Set the password for the `root` user. This option is **mandatory** and **must not be empty**.
-  - type: -e
-    value: MYSQL_PASSWORD=secret
-    description: Set the password for the `MYSQL_USER` user.
-  - type: -e
-    value: MYSQL_USER=john
-    description: Create a new user with superuser privileges. This is used in conjunction with `MYSQL_PASSWORD`.
-  - type: -e
-    value: MYSQL_DATABASE=db_test
-    description: Set the name of the default database.
-  - type: -e
-    value: MYSQL_ALLOW_EMPTY_PASSWORD=yes
-    description: Set up a blank password for the `root` user. **This is not recommended to be used in production, make sure you know what you are doing**.
-  - type: -e
-    value: MYSQL_RANDOM_ROOT_PASSWORD=yes
-    description: Generate a random initial password for the `root` user using `pwgen`. It will be printed in the logs, search for `GENERATED ROOT PASSWORD`.
-  - type: -e
-    value: MYSQL_ONETIME_PASSWORD=yes
-    description: Set `root` user as experide once initialization is complete, forcing a password change on first login.
-  - type: -e
-    value: MYSQL_INITSB_SKIP_TZINFO=yes
-    description: Timezone data is automatically loaded via entrypoint script, set this variable to any non-empty value to disable it.
-  - type: -p
-    value: 30306:3306
-    description: Expose MySQL server on `localhost:30306`.
-  - type: -v
-    value: /path/to/data:/var/lib/mysql
-    description: Persist data instead of initializing a new database every time you launch a new container.
-  - type: -v
-    value: /path/to/config/files/:/etc/mysql/mysql.conf.d/
-    description: Local [configuration files](https://dev.mysql.com/doc/refman/8.0/en/mysql-command-options.html) (try this [example my.cnf](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my.cnf)).
-debug:
-  extraparagraph: |
-    #### Initialization Scripts
-
-    One can also add initialization scripts to their containers. This includes `*.sql`, `.sql.gz`, and `*.sh` scripts, and you just need to put them inside the  `/docker-entrypoint-initdb.d` directory inside the container. After MySQL initialization is done and the default database and user are created, the scripts are executed in the following order:
-
-    * Run any `*.sql` files in alphabetically order. By default the target database is specified via `MYSQL_DATABASE`.
-    * Run any executable `*.sh` scripts in alphabetically order.
-    * Source any non-executable `*.sh` scripts in alphabetically order.
-
-    All of this is done before the MySQL service is started. Keep in mind if your database directory is not empty (contains pre-existing database) they will be left untouched.
-  network:
-    client: mysql
-    args: -hmysql-container -uroot -p
-    helper: The password will be asked and you can enter `My:S3cr3t/`. Now, you are logged in and can enjoy your new instance.
-microk8s:
-  configmap:
-    files:
-      - key: main-config
-        name: my-custom.cnf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/config/my-custom.cnf
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml
-    access: You will now be able to connect to the MySQL server on `localhost:30306`.
diff --git a/data/nginx.yaml b/data/nginx.yaml
deleted file mode 100644
index 63f8c21..0000000
--- a/data/nginx.yaml
+++ /dev/null
@@ -1,46 +0,0 @@
-application: Nginx
-main: true
-repo: nginx
-description: >
-  Nginx ("engine X") is a high-performance web and reverse proxy server created by Igor Sysoev. It can be used both as a standalone web server and as a proxy to reduce the load on back-end HTTP or mail servers. Read more on the [nginx website](https://www.nginx.com/).
-version: 1.18.0
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  parameters:
-    - -p 8080:80
-  access: Access your Nginx server at `http://localhost:8080`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -p
-    value: 8080:80
-    description: Expose Nginx on `localhost:8080`.
-  - type: -v
-    value: /local/path/to/website:/var/www/html
-    description: Mount and serve a local website.
-  - type: -v
-    value: /path/to/conf.template:/etc/nginx/templates/conf.template
-    description: Mount template files inside `/etc/nginx/templates`. They will be processed and the results will be placed at `/etc/nginx/conf.d`. (e.g. `listen ${NGINX_PORT};` will generate `listen 80;`).
-  - type: -v
-    value: /path/to/nginx.conf:/etc/nginx/nginx.conf
-    description: Local [configuration file](https://nginx.org/en/docs/) `nginx.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf)).
-debug:
-  - nothing
-microk8s:
-  configmap:
-    files:
-      - key: nginx
-        name: nginx.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/nginx.conf
-      - key: nginx-site
-        name: index.html
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/config/html/index.html
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/nginx/plain/examples/nginx-deployment.yml
-    access: You will now be able to connect to the nginx server on `http://localhost:31080`.
diff --git a/data/postgres.yaml b/data/postgres.yaml
deleted file mode 100644
index a772c6b..0000000
--- a/data/postgres.yaml
+++ /dev/null
@@ -1,74 +0,0 @@
-application: Postgres
-main: true
-repo: postgres
-description: >
-  PostgreSQL is a powerful, open source object-relational database system. It is fully ACID compliant, has full support for foreign keys, joins, views, triggers, and stored procedures (in multiple languages). It includes most SQL:2008 data types, including INTEGER, NUMERIC, BOOLEAN, CHAR, VARCHAR, DATE, INTERVAL, and TIMESTAMP. It also supports storage of binary large objects, including pictures, sounds, or video. It has native programming interfaces for C/C++, Java, .Net, Perl, Python, Ruby, Tcl, ODBC, among others, and exceptional documentation. Read more on the [PostgreSQL website](https://www.postgresql.org/docs/).
-version: "12.4"
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - s390x
-docker:
-  parameters:
-    - -p 30432:5432
-    - -e POSTGRES_PASSWORD=My:s3Cr3t/
-  access: Access your PostgreSQL server at `localhost:30432`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -e
-    value: POSTGRES_PASSWORD=secret
-    description: Set the password for the superuser which is `postgres` by default. Bear in mind that to connect to the database in the same host the password is not needed but to access it via an external host (for instance another container) the password is needed. This option is **mandatory** and **must not be empty**.
-  - type: -e
-    value: POSTGRES_USER=john
-    description: Create a new user with superuser privileges. This is used in conjunction with `POSTGRES_PASSWORD`.
-  - type: -e
-    value: POSTGRES_DB=db_test
-    description: Set the name of the default database.
-  - type: -e
-    value: POSTGRES_INITDB_ARGS="--data-checksums"
-    description: Pass arguments to the `postgres initdb` call.
-  - type: -e
-    value: POSTGRES_INITDB_WALDIR=/path/to/location
-    description: Set the location of the Postgres transaction log. By default it is stored in a subdirectory of the main Postgres data folder (`PGDATA`).
-  - type: -e
-    value: POSTGRES_HOST_AUTH_METHOD=trust
-    description: "Set the `auth-method` for `host` connections for `all` databases, `all` users, and `all` addresses. The following will be added to the `pg_hba.conf` if this option is passed: `host all all all $POSTGRES_HOST_AUTH_METHOD`."
-  - type: -e
-    value: PGDATA=/path/to/location
-    description: Set the location of the database files. The default is `/var/lib/postgresql/data`.
-  - type: -p
-    value: 30432:5432
-    description: Expose Postgres on `localhost:30432`.
-  - type: -v
-    value: /path/to/postgresql.conf:/etc/postgresql/postgresql.conf
-    description: Local [configuration file](https://www.postgresql.org/docs/12/index.html) `postgresql.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf)).
-  - type: -v
-    value: /path/to/persisted/data:/var/lib/postgresql/data
-    description: Persist data instead of initializing a new database every time you launch a new container.
-debug:
-  extraparagraph: |
-    #### Initialization Scripts
-
-    One can also add initialization scripts to their containers. This includes `*.sql`, `.sql.gz`, and `*.sh` scripts, and you just need to put them inside the  `/docker-entrypoint-initdb.d` directory inside the container. After Postgres initialization is done and the default database and user are created, the scripts are executed in the following order:
-
-    * Run any `*.sql` files in alphabetically order. It will be executed with `POSTGRES_USER`.
-    * Run any executable `*.sh` scripts in alphabetically order.
-    * Source any non-executable `*.sh` scripts in alphabetically order.
-
-    All of this is done before the Postgres service is started. Keep in mind if your `PGDATA` directory is not empty (contains pre-existing database) they will be left untouched.
-  network:
-    client: psql
-    args: -h postgres-container -U postgres
-    helper: The password will be asked and you can enter `My:s3Cr3t/`. Now, you are logged in and can enjoy your new instance.
-microk8s:
-  configmap:
-    files:
-      - key: main-config
-        name: postgresql.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/config/postgresql.conf
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/postgresql/plain/examples/postgres-deployment.yml
-    access: You will now be able to connect to the Postgres server on `localhost:30306`.
diff --git a/data/prometheus-alertmanager.yaml b/data/prometheus-alertmanager.yaml
deleted file mode 100644
index f02be88..0000000
--- a/data/prometheus-alertmanager.yaml
+++ /dev/null
@@ -1,40 +0,0 @@
-application: Prometheus Alertmanager
-main: false
-repo: prometheus-alertmanager
-description: >
-  The Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integration such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts. Read more on the [Prometheus Alertmanager website](https://prometheus.io/docs/alerting/latest/alertmanager/).
-version: 0.21.0
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  parameters:
-    - -p 30093:9093
-  access: Access your Prometheus Alertmanager server at `localhost:30093`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -p
-    value: 30093:9093
-    description: Expose Prometheus Alertmanager on `localhost:30093`.
-  - type: -v
-    value: /path/to/alertmanager.yml:/etc/prometheus/alertmanager.yml
-    description: Local [configuration file](https://www.prometheus.io/docs/alerting/latest/configuration/) `alertmanager.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/oci/examples/config/alertmanager.yml)).
-  - type: -v
-    value: /path/to/persisted/data:/alertmanager
-    description: "Persist data instead of initializing a new database for each newly launched container. **Important note**: the directory you will be using to persist the data needs to belong to `nogroup:nobody`. You can run `chown nogroup:nobody <path_to_persist_data>` before launching your container."
-debug:
-  - nothing
-microk8s:
-  configmap:
-    files:
-      - key: alertmanager
-        name: alertmanager.yml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/oci/examples/config/alertmanager.yml
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus-alertmanager/plain/oci/examples/alertmanager-deployment.yml
-    access: You will now be able to connect to the Prometheus Alertmanager server on `localhost:30093`.
diff --git a/data/prometheus.yaml b/data/prometheus.yaml
deleted file mode 100644
index 42f5e39..0000000
--- a/data/prometheus.yaml
+++ /dev/null
@@ -1,43 +0,0 @@
-application: Prometheus
-main: false
-repo: prometheus
-description: >
-  Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true. Read more on the [Prometheus website](https://prometheus.io/).
-version: 2.20.1
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  parameters:
-    - -p 30090:9090
-  access: Access your Prometheus server at `localhost:30090`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -p
-    value: 30090:9090
-    description: Expose Prometheus server on `localhost:30090`.
-  - type: -v
-    value: /path/to/prometheus.yml:/etc/prometheus/prometheus.yml
-    description: Local [configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `prometheus.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/config/prometheus.yml)).
-  - type: -v
-    value: /path/to/alerts.yml:/etc/prometheus/alerts.yml
-    description: Local [alert configuration file](https://prometheus.io/docs/prometheus/2.20/configuration/configuration/) `alerts.yml` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/config/alerts.yml)).
-debug:
-  - nothing
-microk8s:
-  configmap:
-    files:
-      - key: prometheus
-        name: prometheus.yml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/config/prometheus.yml
-      - key: prometheus-alerts
-        name: alerts.yml
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/config/alerts.yml
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/prometheus/plain/oci/examples/prometheus-deployment.yml
-    access: You will now be able to connect to the Prometheus on `http://localhost:30090`.
diff --git a/data/redis.yaml b/data/redis.yaml
deleted file mode 100644
index 74fba08..0000000
--- a/data/redis.yaml
+++ /dev/null
@@ -1,68 +0,0 @@
-application: Redis
-main: false
-repo: redis
-description: >
-  Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker. 
-  It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes with radius queries and streams. 
-  Redis has built-in replication, Lua scripting, LRU eviction, transactions and different levels of on-disk persistence, and provides high availability via Redis Sentinel and automatic partitioning with Redis Cluster. 
-  Read more on the [Redis website](https://redis.io/topics/introduction).
-version: 5.0.7
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  parameters:
-    - -p 30073:6379
-    - -e REDIS_PASSWORD=mypassword
-  access: Access your Redis server at `localhost:30073`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -e
-    value: ALLOW_EMPTY_PASSWORD
-    description: Set to `yes` to allow connections to `redis-server` without a password.  **This setting is not recommended in production environments**.
-  - type: -e
-    value: REDIS_PASSWORD
-    description: Set the desired password to be used.
-  - type: -e
-    value: REDIS_RANDOM_PASSWORD
-    description: Set this variable to `1` if you would like the entrypoint script to generate a random password for you.  You will be able to see the generated password in the logs (`docker logs`).
-  - type: -e
-    value: REDIS_ALLOW_REMOTE_CONNECTIONS=yes
-    description: Set to `no` to disallow remote connections to `redis-server` (i.e., make `redis-server` listen to `127.0.0.1` only).
-  - type: -e
-    value: REDIS_EXTRA_FLAGS
-    description: Specify extra flags to be passed to `redis-server` when initializing it.
-  - type: -p
-    value: 30073:6379
-    description: Expose redis on `localhost:30073`.
-  - type: -v
-    value: /path/to/redis.conf:/etc/redis/redis.conf
-    description: Local [configuration file](https://redis.io/topics/config) `redis.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf)).
-debug:
-  network:
-    client: redis-cli
-    args: -h redis-container
-    followup: |
-      ```
-      Now you can:
-      ```
-      redis:6379> AUTH mypassword
-      OK
-      redis:6379> PING
-      PONG
-      redis:6379>
-microk8s:
-  configmap:
-    name: redis-config
-    files:
-      - key: redis
-        name: redis.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/config/redis.conf
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/redis/plain/examples/redis-deployment.yml
-    access: You will now be able to connect to the Redis server on `localhost:30073`.
diff --git a/data/telegraf.yaml b/data/telegraf.yaml
deleted file mode 100644
index a63f5cd..0000000
--- a/data/telegraf.yaml
+++ /dev/null
@@ -1,37 +0,0 @@
-application: Telegraf
-main: false
-repo: telegraf
-description: >
-  Telegraf is an agent for collecting, processing, aggregating, and writing metrics. Design goals are to have a minimal memory footprint with a plugin system so that developers in the community can easily add support for collecting metrics. Read more on the [Telegraf website](https://www.influxdata.com/time-series-platform/telegraf/).
-version: 1.15.2
-base: Ubuntu 20.04 LTS
-architectures:
-  - amd64
-  - arm64
-  - ppc64el
-  - s390x
-docker:
-  parameters:
-    - -p 30273:9273
-  access: Access your Telegraf server at `localhost:30273`.
-parameters:
-  - type: -e
-    value: TZ=UTC
-    description: Timezone.
-  - type: -p
-    value: 30273:9273
-    description: Expose Telegraf on `localhost:30273`.
-  - type: -v
-    value: /path/to/telegraf.conf:/etc/telegraf/telegraf.conf
-    description: Local [configuration file](https://docs.influxdata.com/telegraf/) `telegraf.conf` (try [this example](https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf)).
-debug:
-    - nothing
-microk8s:
-  configmap:
-    files:
-      - key: main-config
-        name: telegraf.conf
-        link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/config/telegraf.conf
-  deploy:
-    link: https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/telegraf/plain/examples/telegraf-deployment.yml
-    access: You will now be able to connect to the Telegraf server on `localhost:30073`.
diff --git a/templates/HACKING_docs.md b/templates/HACKING_docs.md
index b1ca2d2..632f5c8 100644
--- a/templates/HACKING_docs.md
+++ b/templates/HACKING_docs.md
@@ -26,4 +26,4 @@ The repository containing the templates is located at:
 https://code.launchpad.net/~canonical-server/ubuntu-docker-images/+git/templates
 
 The specific data for this image's template can be found inside the
-`data/` directory.
+`data/` directory, in the image's own repository.