From f06ad3bf9cd9b8d36a80ae3137d5cec5d7be6370 Mon Sep 17 00:00:00 2001 From: Inex Code Date: Fri, 20 Jan 2023 13:39:57 +0300 Subject: [PATCH] chore(translations): Add languages to md files --- assets/markdown/about-be.md | 12 ++++++++++ assets/markdown/about-cs.md | 12 ++++++++++ assets/markdown/about-de.md | 12 ++++++++++ assets/markdown/about-es.md | 12 ++++++++++ assets/markdown/about-fr.md | 12 ++++++++++ assets/markdown/about-it.md | 12 ++++++++++ assets/markdown/about-ja.md | 12 ++++++++++ assets/markdown/about-ka.md | 12 ++++++++++ assets/markdown/about-nl.md | 12 ++++++++++ assets/markdown/about-pl.md | 12 ++++++++++ assets/markdown/about-sk.md | 12 ++++++++++ assets/markdown/about-th.md | 12 ++++++++++ assets/markdown/about-uk.md | 12 ++++++++++ assets/markdown/how_backblaze-be.md | 8 +++++++ assets/markdown/how_backblaze-cs.md | 8 +++++++ assets/markdown/how_backblaze-de.md | 8 +++++++ assets/markdown/how_backblaze-es.md | 8 +++++++ assets/markdown/how_backblaze-fr.md | 8 +++++++ assets/markdown/how_backblaze-it.md | 8 +++++++ assets/markdown/how_backblaze-ja.md | 8 +++++++ assets/markdown/how_backblaze-ka.md | 8 +++++++ assets/markdown/how_backblaze-nl.md | 8 +++++++ assets/markdown/how_backblaze-pl.md | 8 +++++++ assets/markdown/how_backblaze-sk.md | 8 +++++++ assets/markdown/how_backblaze-th.md | 8 +++++++ assets/markdown/how_backblaze-uk.md | 8 +++++++ assets/markdown/how_cloudflare-be.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-cs.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-de.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-es.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-fr.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-it.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-ja.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-ka.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-nl.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-pl.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-sk.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-th.md | 17 ++++++++++++++ assets/markdown/how_cloudflare-uk.md | 17 ++++++++++++++ assets/markdown/how_digital_ocean-be.md | 12 ++++++++++ assets/markdown/how_digital_ocean-cs.md | 12 ++++++++++ assets/markdown/how_digital_ocean-de.md | 12 ++++++++++ assets/markdown/how_digital_ocean-es.md | 12 ++++++++++ assets/markdown/how_digital_ocean-fr.md | 12 ++++++++++ assets/markdown/how_digital_ocean-it.md | 12 ++++++++++ assets/markdown/how_digital_ocean-ja.md | 12 ++++++++++ assets/markdown/how_digital_ocean-ka.md | 12 ++++++++++ assets/markdown/how_digital_ocean-nl.md | 12 ++++++++++ assets/markdown/how_digital_ocean-pl.md | 12 ++++++++++ assets/markdown/how_digital_ocean-sk.md | 12 ++++++++++ assets/markdown/how_digital_ocean-th.md | 12 ++++++++++ assets/markdown/how_digital_ocean-uk.md | 12 ++++++++++ assets/markdown/how_fallback_old-be.md | 3 +++ assets/markdown/how_fallback_old-cs.md | 3 +++ assets/markdown/how_fallback_old-de.md | 3 +++ assets/markdown/how_fallback_old-es.md | 3 +++ assets/markdown/how_fallback_old-fr.md | 3 +++ assets/markdown/how_fallback_old-it.md | 3 +++ assets/markdown/how_fallback_old-ja.md | 3 +++ assets/markdown/how_fallback_old-ka.md | 3 +++ assets/markdown/how_fallback_old-nl.md | 3 +++ assets/markdown/how_fallback_old-pl.md | 3 +++ assets/markdown/how_fallback_old-sk.md | 3 +++ assets/markdown/how_fallback_old-th.md | 3 +++ assets/markdown/how_fallback_old-uk.md | 3 +++ assets/markdown/how_fallback_ssh-be.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-cs.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-de.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-es.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-fr.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-it.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-ja.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-ka.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-nl.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-pl.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-sk.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-th.md | 19 +++++++++++++++ assets/markdown/how_fallback_ssh-uk.md | 19 +++++++++++++++ assets/markdown/how_fallback_terminal-be.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-cs.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-de.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-es.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-fr.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-it.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-ja.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-ka.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-nl.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-pl.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-sk.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-th.md | 26 +++++++++++++++++++++ assets/markdown/how_fallback_terminal-uk.md | 26 +++++++++++++++++++++ assets/markdown/how_hetzner-be.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-cs.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-de.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-es.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-fr.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-it.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-ja.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-ka.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-nl.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-pl.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-sk.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-th.md | 23 ++++++++++++++++++ assets/markdown/how_hetzner-uk.md | 23 ++++++++++++++++++ 104 files changed, 1560 insertions(+) create mode 100644 assets/markdown/about-be.md create mode 100644 assets/markdown/about-cs.md create mode 100644 assets/markdown/about-de.md create mode 100644 assets/markdown/about-es.md create mode 100644 assets/markdown/about-fr.md create mode 100644 assets/markdown/about-it.md create mode 100644 assets/markdown/about-ja.md create mode 100644 assets/markdown/about-ka.md create mode 100644 assets/markdown/about-nl.md create mode 100644 assets/markdown/about-pl.md create mode 100644 assets/markdown/about-sk.md create mode 100644 assets/markdown/about-th.md create mode 100644 assets/markdown/about-uk.md create mode 100644 assets/markdown/how_backblaze-be.md create mode 100644 assets/markdown/how_backblaze-cs.md create mode 100644 assets/markdown/how_backblaze-de.md create mode 100644 assets/markdown/how_backblaze-es.md create mode 100644 assets/markdown/how_backblaze-fr.md create mode 100644 assets/markdown/how_backblaze-it.md create mode 100644 assets/markdown/how_backblaze-ja.md create mode 100644 assets/markdown/how_backblaze-ka.md create mode 100644 assets/markdown/how_backblaze-nl.md create mode 100644 assets/markdown/how_backblaze-pl.md create mode 100644 assets/markdown/how_backblaze-sk.md create mode 100644 assets/markdown/how_backblaze-th.md create mode 100644 assets/markdown/how_backblaze-uk.md create mode 100644 assets/markdown/how_cloudflare-be.md create mode 100644 assets/markdown/how_cloudflare-cs.md create mode 100644 assets/markdown/how_cloudflare-de.md create mode 100644 assets/markdown/how_cloudflare-es.md create mode 100644 assets/markdown/how_cloudflare-fr.md create mode 100644 assets/markdown/how_cloudflare-it.md create mode 100644 assets/markdown/how_cloudflare-ja.md create mode 100644 assets/markdown/how_cloudflare-ka.md create mode 100644 assets/markdown/how_cloudflare-nl.md create mode 100644 assets/markdown/how_cloudflare-pl.md create mode 100644 assets/markdown/how_cloudflare-sk.md create mode 100644 assets/markdown/how_cloudflare-th.md create mode 100644 assets/markdown/how_cloudflare-uk.md create mode 100644 assets/markdown/how_digital_ocean-be.md create mode 100644 assets/markdown/how_digital_ocean-cs.md create mode 100644 assets/markdown/how_digital_ocean-de.md create mode 100644 assets/markdown/how_digital_ocean-es.md create mode 100644 assets/markdown/how_digital_ocean-fr.md create mode 100644 assets/markdown/how_digital_ocean-it.md create mode 100644 assets/markdown/how_digital_ocean-ja.md create mode 100644 assets/markdown/how_digital_ocean-ka.md create mode 100644 assets/markdown/how_digital_ocean-nl.md create mode 100644 assets/markdown/how_digital_ocean-pl.md create mode 100644 assets/markdown/how_digital_ocean-sk.md create mode 100644 assets/markdown/how_digital_ocean-th.md create mode 100644 assets/markdown/how_digital_ocean-uk.md create mode 100644 assets/markdown/how_fallback_old-be.md create mode 100644 assets/markdown/how_fallback_old-cs.md create mode 100644 assets/markdown/how_fallback_old-de.md create mode 100644 assets/markdown/how_fallback_old-es.md create mode 100644 assets/markdown/how_fallback_old-fr.md create mode 100644 assets/markdown/how_fallback_old-it.md create mode 100644 assets/markdown/how_fallback_old-ja.md create mode 100644 assets/markdown/how_fallback_old-ka.md create mode 100644 assets/markdown/how_fallback_old-nl.md create mode 100644 assets/markdown/how_fallback_old-pl.md create mode 100644 assets/markdown/how_fallback_old-sk.md create mode 100644 assets/markdown/how_fallback_old-th.md create mode 100644 assets/markdown/how_fallback_old-uk.md create mode 100644 assets/markdown/how_fallback_ssh-be.md create mode 100644 assets/markdown/how_fallback_ssh-cs.md create mode 100644 assets/markdown/how_fallback_ssh-de.md create mode 100644 assets/markdown/how_fallback_ssh-es.md create mode 100644 assets/markdown/how_fallback_ssh-fr.md create mode 100644 assets/markdown/how_fallback_ssh-it.md create mode 100644 assets/markdown/how_fallback_ssh-ja.md create mode 100644 assets/markdown/how_fallback_ssh-ka.md create mode 100644 assets/markdown/how_fallback_ssh-nl.md create mode 100644 assets/markdown/how_fallback_ssh-pl.md create mode 100644 assets/markdown/how_fallback_ssh-sk.md create mode 100644 assets/markdown/how_fallback_ssh-th.md create mode 100644 assets/markdown/how_fallback_ssh-uk.md create mode 100644 assets/markdown/how_fallback_terminal-be.md create mode 100644 assets/markdown/how_fallback_terminal-cs.md create mode 100644 assets/markdown/how_fallback_terminal-de.md create mode 100644 assets/markdown/how_fallback_terminal-es.md create mode 100644 assets/markdown/how_fallback_terminal-fr.md create mode 100644 assets/markdown/how_fallback_terminal-it.md create mode 100644 assets/markdown/how_fallback_terminal-ja.md create mode 100644 assets/markdown/how_fallback_terminal-ka.md create mode 100644 assets/markdown/how_fallback_terminal-nl.md create mode 100644 assets/markdown/how_fallback_terminal-pl.md create mode 100644 assets/markdown/how_fallback_terminal-sk.md create mode 100644 assets/markdown/how_fallback_terminal-th.md create mode 100644 assets/markdown/how_fallback_terminal-uk.md create mode 100644 assets/markdown/how_hetzner-be.md create mode 100644 assets/markdown/how_hetzner-cs.md create mode 100644 assets/markdown/how_hetzner-de.md create mode 100644 assets/markdown/how_hetzner-es.md create mode 100644 assets/markdown/how_hetzner-fr.md create mode 100644 assets/markdown/how_hetzner-it.md create mode 100644 assets/markdown/how_hetzner-ja.md create mode 100644 assets/markdown/how_hetzner-ka.md create mode 100644 assets/markdown/how_hetzner-nl.md create mode 100644 assets/markdown/how_hetzner-pl.md create mode 100644 assets/markdown/how_hetzner-sk.md create mode 100644 assets/markdown/how_hetzner-th.md create mode 100644 assets/markdown/how_hetzner-uk.md diff --git a/assets/markdown/about-be.md b/assets/markdown/about-be.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-be.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-cs.md b/assets/markdown/about-cs.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-cs.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-de.md b/assets/markdown/about-de.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-de.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-es.md b/assets/markdown/about-es.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-es.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-fr.md b/assets/markdown/about-fr.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-fr.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-it.md b/assets/markdown/about-it.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-it.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-ja.md b/assets/markdown/about-ja.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-ja.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-ka.md b/assets/markdown/about-ka.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-ka.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-nl.md b/assets/markdown/about-nl.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-nl.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-pl.md b/assets/markdown/about-pl.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-pl.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-sk.md b/assets/markdown/about-sk.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-sk.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-th.md b/assets/markdown/about-th.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-th.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/about-uk.md b/assets/markdown/about-uk.md new file mode 100644 index 00000000..3963aa6e --- /dev/null +++ b/assets/markdown/about-uk.md @@ -0,0 +1,12 @@ +### About us + +More and more corporations want to control our data. +We want to have full control of our **data** on our own. + +### Our mission + +Digital independence and privacy, available to everyone + +### Target + +Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours. \ No newline at end of file diff --git a/assets/markdown/how_backblaze-be.md b/assets/markdown/how_backblaze-be.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-be.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-cs.md b/assets/markdown/how_backblaze-cs.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-cs.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-de.md b/assets/markdown/how_backblaze-de.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-de.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-es.md b/assets/markdown/how_backblaze-es.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-es.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-fr.md b/assets/markdown/how_backblaze-fr.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-fr.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-it.md b/assets/markdown/how_backblaze-it.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-it.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-ja.md b/assets/markdown/how_backblaze-ja.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-ja.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-ka.md b/assets/markdown/how_backblaze-ka.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-ka.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-nl.md b/assets/markdown/how_backblaze-nl.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-nl.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-pl.md b/assets/markdown/how_backblaze-pl.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-pl.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-sk.md b/assets/markdown/how_backblaze-sk.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-sk.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-th.md b/assets/markdown/how_backblaze-th.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-th.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_backblaze-uk.md b/assets/markdown/how_backblaze-uk.md new file mode 100644 index 00000000..b1e341d1 --- /dev/null +++ b/assets/markdown/how_backblaze-uk.md @@ -0,0 +1,8 @@ +### How to get Backblaze API Token +1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm +2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory. +3. Click on the blue **Generate New Master Application Key** button. +4. In the appeared pop-up window confirm the generation. +5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager. + +![Backblaze token setup](resource:assets/images/gifs/Backblaze.gif) diff --git a/assets/markdown/how_cloudflare-be.md b/assets/markdown/how_cloudflare-be.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-be.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-cs.md b/assets/markdown/how_cloudflare-cs.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-cs.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-de.md b/assets/markdown/how_cloudflare-de.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-de.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-es.md b/assets/markdown/how_cloudflare-es.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-es.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-fr.md b/assets/markdown/how_cloudflare-fr.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-fr.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-it.md b/assets/markdown/how_cloudflare-it.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-it.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-ja.md b/assets/markdown/how_cloudflare-ja.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-ja.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-ka.md b/assets/markdown/how_cloudflare-ka.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-ka.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-nl.md b/assets/markdown/how_cloudflare-nl.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-nl.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-pl.md b/assets/markdown/how_cloudflare-pl.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-pl.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-sk.md b/assets/markdown/how_cloudflare-sk.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-sk.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-th.md b/assets/markdown/how_cloudflare-th.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-th.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_cloudflare-uk.md b/assets/markdown/how_cloudflare-uk.md new file mode 100644 index 00000000..61fb4b4e --- /dev/null +++ b/assets/markdown/how_cloudflare-uk.md @@ -0,0 +1,17 @@ +### How to get Cloudflare API Token +1. Visit the following link: https://dash.cloudflare.com/ +2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile** +3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**. +4. Click on **Create Token** button. +5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side. +6. In the **Token Name** field, give your token a name. +7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**. +8. Next, right under this line, click Add More. Similar field will appear. +9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**. +10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it. +11. Flick to the bottom and press the blue **Continue to Summary** button. +12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*. +13. Click on **Create Token**. +14. We copy the created token, and save it in a reliable place (preferably in the password manager). + +![Cloudflare token setup](resource:assets/images/gifs/CloudFlare.gif) diff --git a/assets/markdown/how_digital_ocean-be.md b/assets/markdown/how_digital_ocean-be.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-be.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-cs.md b/assets/markdown/how_digital_ocean-cs.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-cs.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-de.md b/assets/markdown/how_digital_ocean-de.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-de.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-es.md b/assets/markdown/how_digital_ocean-es.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-es.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-fr.md b/assets/markdown/how_digital_ocean-fr.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-fr.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-it.md b/assets/markdown/how_digital_ocean-it.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-it.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-ja.md b/assets/markdown/how_digital_ocean-ja.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-ja.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-ka.md b/assets/markdown/how_digital_ocean-ka.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-ka.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-nl.md b/assets/markdown/how_digital_ocean-nl.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-nl.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-pl.md b/assets/markdown/how_digital_ocean-pl.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-pl.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-sk.md b/assets/markdown/how_digital_ocean-sk.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-sk.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-th.md b/assets/markdown/how_digital_ocean-th.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-th.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_digital_ocean-uk.md b/assets/markdown/how_digital_ocean-uk.md new file mode 100644 index 00000000..dc6355c2 --- /dev/null +++ b/assets/markdown/how_digital_ocean-uk.md @@ -0,0 +1,12 @@ +### How to get Digital Ocean API Token +1. Visit the following [link](https://cloud.digitalocean.com/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Go to the "API" link on the left bar. +4. Click on the "Generate New Token". +5. Enter any name for the token. +6. Put expiration time to "No expiry". +7. Check the "Write (optional)" checkbox. +8. Now click on the "Generate Token" button. +9. After that, the token will be shown. Store it in any reliable place, preferably a password manager. \ No newline at end of file diff --git a/assets/markdown/how_fallback_old-be.md b/assets/markdown/how_fallback_old-be.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-be.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-cs.md b/assets/markdown/how_fallback_old-cs.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-cs.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-de.md b/assets/markdown/how_fallback_old-de.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-de.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-es.md b/assets/markdown/how_fallback_old-es.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-es.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-fr.md b/assets/markdown/how_fallback_old-fr.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-fr.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-it.md b/assets/markdown/how_fallback_old-it.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-it.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-ja.md b/assets/markdown/how_fallback_old-ja.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-ja.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-ka.md b/assets/markdown/how_fallback_old-ka.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-ka.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-nl.md b/assets/markdown/how_fallback_old-nl.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-nl.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-pl.md b/assets/markdown/how_fallback_old-pl.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-pl.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-sk.md b/assets/markdown/how_fallback_old-sk.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-sk.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-th.md b/assets/markdown/how_fallback_old-th.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-th.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_old-uk.md b/assets/markdown/how_fallback_old-uk.md new file mode 100644 index 00000000..c12504e7 --- /dev/null +++ b/assets/markdown/how_fallback_old-uk.md @@ -0,0 +1,3 @@ +In the next window, enter the token obtained from the console of the previous version of the application. + +Enter it without the word *Bearer*. diff --git a/assets/markdown/how_fallback_ssh-be.md b/assets/markdown/how_fallback_ssh-be.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-be.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-cs.md b/assets/markdown/how_fallback_ssh-cs.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-cs.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-de.md b/assets/markdown/how_fallback_ssh-de.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-de.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-es.md b/assets/markdown/how_fallback_ssh-es.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-es.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-fr.md b/assets/markdown/how_fallback_ssh-fr.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-fr.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-it.md b/assets/markdown/how_fallback_ssh-it.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-it.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-ja.md b/assets/markdown/how_fallback_ssh-ja.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-ja.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-ka.md b/assets/markdown/how_fallback_ssh-ka.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-ka.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-nl.md b/assets/markdown/how_fallback_ssh-nl.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-nl.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-pl.md b/assets/markdown/how_fallback_ssh-pl.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-pl.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-sk.md b/assets/markdown/how_fallback_ssh-sk.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-sk.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-th.md b/assets/markdown/how_fallback_ssh-th.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-th.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_ssh-uk.md b/assets/markdown/how_fallback_ssh-uk.md new file mode 100644 index 00000000..ce90e76a --- /dev/null +++ b/assets/markdown/how_fallback_ssh-uk.md @@ -0,0 +1,19 @@ +Login as root user to your server and look at the contents of the file `/etc/nixos/userdata/tokens.json` + +```sh +cat /etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-be.md b/assets/markdown/how_fallback_terminal-be.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-be.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-cs.md b/assets/markdown/how_fallback_terminal-cs.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-cs.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-de.md b/assets/markdown/how_fallback_terminal-de.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-de.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-es.md b/assets/markdown/how_fallback_terminal-es.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-es.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-fr.md b/assets/markdown/how_fallback_terminal-fr.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-fr.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-it.md b/assets/markdown/how_fallback_terminal-it.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-it.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-ja.md b/assets/markdown/how_fallback_terminal-ja.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-ja.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-ka.md b/assets/markdown/how_fallback_terminal-ka.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-ka.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-nl.md b/assets/markdown/how_fallback_terminal-nl.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-nl.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-pl.md b/assets/markdown/how_fallback_terminal-pl.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-pl.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-sk.md b/assets/markdown/how_fallback_terminal-sk.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-sk.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-th.md b/assets/markdown/how_fallback_terminal-th.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-th.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_fallback_terminal-uk.md b/assets/markdown/how_fallback_terminal-uk.md new file mode 100644 index 00000000..77c97efa --- /dev/null +++ b/assets/markdown/how_fallback_terminal-uk.md @@ -0,0 +1,26 @@ +In the Hetzner server control panel, go to the **Rescue** tab. Then, click on **Enable rescue & power cycle**. + +In *Choose a Recue OS* select **linux64**, and in *SSH Key* select your key if it has been added to your Hetzner account. + +Click **Enable rescue & power cycle** and wait for the server to reboot. The login and password will be displayed on the screen. Login to the root user using your login and password information. + +Mount your server file system and see the contents of the token file: + +```sh +mount /dev/sda1 /mnt +cat /mnt/etc/nixos/userdata/tokens.json +``` + +This file will have a similar construction: + +```json +{ + "tokens": [ + { + "token": "token_to_copy", + "name": "device_name", + "date": "date" + } +``` + +Copy the token from the file and paste it in the next window. diff --git a/assets/markdown/how_hetzner-be.md b/assets/markdown/how_hetzner-be.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-be.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-cs.md b/assets/markdown/how_hetzner-cs.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-cs.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-de.md b/assets/markdown/how_hetzner-de.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-de.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-es.md b/assets/markdown/how_hetzner-es.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-es.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-fr.md b/assets/markdown/how_hetzner-fr.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-fr.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-it.md b/assets/markdown/how_hetzner-it.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-it.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-ja.md b/assets/markdown/how_hetzner-ja.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-ja.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-ka.md b/assets/markdown/how_hetzner-ka.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-ka.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-nl.md b/assets/markdown/how_hetzner-nl.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-nl.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-pl.md b/assets/markdown/how_hetzner-pl.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-pl.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-sk.md b/assets/markdown/how_hetzner-sk.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-sk.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-th.md b/assets/markdown/how_hetzner-th.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-th.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif) diff --git a/assets/markdown/how_hetzner-uk.md b/assets/markdown/how_hetzner-uk.md new file mode 100644 index 00000000..6f859c18 --- /dev/null +++ b/assets/markdown/how_hetzner-uk.md @@ -0,0 +1,23 @@ +### How to get Hetzner API Token +1. Visit the following [link](https://console.hetzner.cloud/) and sign + into newly created account. +2. Enter into previously created project. If you haven't created one, + then please proceed. +3. Hover side panel with mouse cursor. Panel should expand and show us + a menu. We're interested in the last one — **Security** (icon of a + key). +4. Next, in the upper part of an interface, we can see approximately + the following: **SSH Keys, API Tokens, Certificates, Members.** You + need **API Tokens**. Click on it. +5. In the right part of the interface, there should be **Generate API + token** button. If you're using mobile version og a webpage, in the + lower right corner you'll see **red cross**. Push that button. +6. In the **Description** field, give our token a name (this can be any + name that you like. It doesn't influence the essence. +7. Under the **Description** field we can see a possibility to choose + **permissions**. Pick **Read & Write**. +8. Click **Generate API Token.** +9. After that, our key will be shown. Store it in the reliable place, + or in the password manager, which is better. + +![Hetzner token setup](resource:assets/images/gifs/Hetzner.gif)