Skip to content

Commit

Permalink
Lint markdown
Browse files Browse the repository at this point in the history
  • Loading branch information
Ndpnt committed Mar 8, 2024
1 parent 883193a commit 608dc76
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions content/collections/create.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,7 @@ For collections to be included in the Open Terms Archive organisation only. For
### Define the inventory

On your local machine:

- Clone the `<collection_id>-declarations` repository
- Update the following entries in the inventory file `deployment/inventory.yml`:
- `<host>` (example: `162.19.74.224`)
Expand Down Expand Up @@ -191,6 +192,7 @@ This key will enable automated deployment via GitHub Actions.
#### Back key up

On your local machine:

- Clone the [`engine.wiki`](https://github.com/OpenTermsArchive/engine/wiki)
- Open the shared passwords database `database.kdbx` with [KeePassXC](https://keepassxc.org)
- Create the `Collection: <collection_name>` folder
Expand Down Expand Up @@ -218,6 +220,7 @@ On your local machine:
#### Backup the token

On your local machine:

- Open the shared passwords database `database.kdbx` with [KeePassXC](https://keepassxc.org)
- Inside the `Collection: <collection_name>` folder, add an entry with the title `GitHub Token`
- Copy the previously generated token in the `Password` field
Expand All @@ -235,6 +238,7 @@ On your local machine:
#### Generate vault key

On your local machine:

- Open the shared passwords database `database.kdbx` with [KeePassXC](https://keepassxc.org)
- Inside the `Collection: <collection_name>` folder, add an entry with the title `Vault key`
- In the password field, click on the icon on the right to generate a new password
Expand All @@ -244,6 +248,7 @@ On your local machine:
#### Create vault key file

On your local machine:

- Go to the `<collection_id>-declarations` repository
- Go to `deployment` folder
- Create a `vault.key` file
Expand All @@ -258,6 +263,7 @@ On your local machine:
#### Encrypt token and update inventory

On your local machine:

- Go to the `<collection_id>-declarations` repository
- Go to `deployment` folder
- Encrypt token: `ansible-vault encrypt_string --name 'ota_engine_github_token' '<GitHub Token>'`
Expand All @@ -272,6 +278,7 @@ On your local machine:
#### Encrypt private key and update inventory

On your local machine:

- Go to the `<collection_id>-declarations` repository
- Go to `deployment` folder
- Encrypt token: `ansible-vault encrypt_string --name 'ota_engine_github_bot_private_key' '<SSH PRIVATE KEY content>'`
Expand All @@ -280,6 +287,7 @@ On your local machine:
#### Back key up

On your local machine:

- Inside the [`engine.wiki`](https://github.com/OpenTermsArchive/engine/wiki)
- Open the shared passwords database `database.kdbx` with [KeePassXC](https://keepassxc.org)
- Inside the `Collection: <collection_name>` folder, add an entry with the title `OTA-Bot GitHub SSH key`
Expand Down Expand Up @@ -309,6 +317,7 @@ Create an SMTP key to allow sending error notifications by email.
#### Backup key

On your local machine:

- Inside the [`engine.wiki`](https://github.com/OpenTermsArchive/engine/wiki)
- Open the shared passwords database `database.kdbx` with [KeePassXC](https://keepassxc.org)
- Inside the `Collection: <collection_name>` folder, add an entry with the title `SMTP Key`
Expand All @@ -318,6 +327,7 @@ On your local machine:
#### Encrypt key and update inventory

On your local machine:

- Go to the `<collection_id>-declarations` repository
- Go to `deployment` folder
- Encrypt token: `ansible-vault encrypt_string --name 'ota_engine_smtp_password' '<SMTP Key>'`
Expand Down

0 comments on commit 608dc76

Please sign in to comment.