From 4c1dcfeb5e77df4cc93180d0e2a615126bba41f6 Mon Sep 17 00:00:00 2001 From: Caleb Braaten Date: Tue, 6 Feb 2024 17:29:19 -0800 Subject: [PATCH] Fix Hyperlinks in Markdown Documenation --- README.md | 2 -- nomad_jobs/{REAMDE.md => README.md} | 2 +- nomad_jobs/services/gitea/readme.md | 4 ++-- nomad_jobs/services/postgres/readme.md | 6 +++--- 4 files changed, 6 insertions(+), 8 deletions(-) rename nomad_jobs/{REAMDE.md => README.md} (98%) diff --git a/README.md b/README.md index ba08d15..f92de4f 100644 --- a/README.md +++ b/README.md @@ -50,5 +50,3 @@ Be aware, that if you have an error it could cause the service to fail to start ### Nomad Jobs This is where the nomad job specs are stored. You can learn more about the job specs in the [nomad_jobs readme](./nomad_jobs/README.md). - - diff --git a/nomad_jobs/REAMDE.md b/nomad_jobs/README.md similarity index 98% rename from nomad_jobs/REAMDE.md rename to nomad_jobs/README.md index fb00e59..272699b 100644 --- a/nomad_jobs/REAMDE.md +++ b/nomad_jobs/README.md @@ -1,6 +1,6 @@ # Nomad Job Specs -This directory contains two sub-directories: `apps` and `services`. If you are going to ignore this README you should at least read how this repository [Manages Secrets](#Managing%20Secrets). +This directory contains two sub-directories: `apps` and `services`. If you are going to ignore this README you should at least read how this repository [Manages Secrets](#managing-secrets). ## Apps Directory diff --git a/nomad_jobs/services/gitea/readme.md b/nomad_jobs/services/gitea/readme.md index 6f8bc2b..57ecb9a 100644 --- a/nomad_jobs/services/gitea/readme.md +++ b/nomad_jobs/services/gitea/readme.md @@ -7,7 +7,7 @@ Gitea should be configured to not utilize SSH as the job spec does not support i You will need to modify the job spec items listed under [TODO](./readme.md#TODO) but there are no Gitea specific adjustments needed. If you run it, it will register with consul and be available to Traefik for routing. If the domain name is configured correctly, you should be able to reach the Gitea setup page to make the needed configuration changes. ## Service Dependencies -- A Valid [Host Volume](../../../host_init/README.md#Storage%20and%20ZFS) +- A Valid [Host Volume](../../../host_init/README.md#storage-and-zfs) - [Postgres](../postgres/readme.md) ## TODO @@ -23,4 +23,4 @@ If you want to deploy this, you will need to verify you have a valid host volume ## Configuring Gitea There is no need to embed secrets in the nomad job spec. When you first visit the domain name you configured, you will be prompted to configure Gitea. Postgres should be mounted to the container on the standard `5432` port so you can select postgres as the database type and use `127.0.0.1:5432` as the address and input the username, password, and database name you created for Gitea to use. -If you need help making those credentials, take a look at the [postgres readme](../postgres/readme.md#Make%20a%20New%20Database). \ No newline at end of file +If you need help making those credentials, take a look at the [postgres readme](../postgres/readme.md#make-a-new-database). \ No newline at end of file diff --git a/nomad_jobs/services/postgres/readme.md b/nomad_jobs/services/postgres/readme.md index 0915936..68ffeaa 100644 --- a/nomad_jobs/services/postgres/readme.md +++ b/nomad_jobs/services/postgres/readme.md @@ -7,7 +7,7 @@ Nomad requires a Host Volume to persist data across restarts. This will limit th Postgres will have a default user which is a good one to use for making application specific users and databases. These are defined through environment variables in the nomad job spec so you only need to edit the job spec to meet your requirements. If you run it, it will register with consul but be hidden to Traefik meaning you can only access it through the service mesh. ## Service Dependencies -- A Valid [Host Volume](../../../host_init/README.md#Storage%20and%20ZFS) +- A Valid [Host Volume](../../../host_init/README.md#storage-and-zfs) ## TODO If you want to deploy this, you will need to verify you have a valid host volume and set the initial postgres root credentials. @@ -16,8 +16,8 @@ If you want to deploy this, you will need to verify you have a valid host volume | --- | --- | --- | | 17 | `source = "postgres"` | Change `postgres` to a valid host volume name | | 38 | `volume = "postgres-data"` | Change `postgres-data` to the host volume defined on line 15 if applicable | -| 48 | `"POSTGRES_USER"="op://InfraSecrets/Postgres Root/username"` | Change the value to the root username you want. By default, this is a 1password path. See [Managing Secrets](../../REAMDE.md#Managing_Secrets) for more information | -| 49 | `"POSTGRES_PASSWORD"="op://InfraSecrets/Postgres Root/password"` | Change the value to the root password you want. By default, this is a 1password path. See [Managing Secrets](../../REAMDE.md#Managing_Secrets) for more information | +| 48 | `"POSTGRES_USER"="op://InfraSecrets/Postgres Root/username"` | Change the value to the root username you want. By default, this is a 1password path. See [Managing Secrets](../../README.md#managing-secrets) for more information | +| 49 | `"POSTGRES_PASSWORD"="op://InfraSecrets/Postgres Root/password"` | Change the value to the root password you want. By default, this is a 1password path. See [Managing Secrets](../../README.md#managing-secrets) for more information | ## Make a New Database