fix: posts structure

content/posts/authelia-selfhosted-sso/index.md

@@ -6,7 +6,7 @@ slug: "authelia-selfhosted-sso"
 tags: ["tools", "sso"]
 ---
 
-First of all, what is an SSO?
+## What's an SSO ?
 
 > Single sign-on (SSO) is an authentication scheme that allows a user to log in with a single ID to any of several related, yet independent, software systems.
 
@@ -18,7 +18,7 @@ There are several advantages :
 - Add double authentification
 - Login regulation (Anti brute force)
 
----
+## Instalation
 
 Now that we have seen what an SSO is and the interest it can have in a Homelab, let's start the installation!
 
@@ -52,7 +52,7 @@ Let's start by generating the secret JWT. For that I use this [site](https://www
 jwt_secret: [example_secret]
 ```
 
-## Session
+### Session
 Several elements must be configured in this part:
 - **secret** : generate a password with the site of your choice
 - **domain** : indicate your domain (`ex. youdomain.com`)
@@ -76,7 +76,7 @@ session:
     minimum_idle_connections: 0
 ```
 
-## User
+### User
 It is in this part that you will have to add the users who will be able to connect to the SSO. No element has to be modified in the configuration file, but you will have to create a second file: `users_database.yml`. This file is composed as follows:
 
 ```
@@ -106,7 +106,7 @@ If this does not work you can manually create the hash using this [site](https:/
 
 <img class="thumbnailshadow" src="img/image-2.png"/>
 
-## Access control
+### Access control
 For the access policy we will do something simple with a single role. But nothing prevents you from creating several roles with different rights and access.
 So we are going to create a `user` group that will have to use the double authentication and will have access to all the subdomains. For this you have to modify the two `exemple.org` in the template file.
 
@@ -121,7 +121,7 @@ access_control:
       policy: two_factor
 ```
 
-## Storage
+### Storage
 For the storage part we will use our database created with Mysql. You have to modify the following values in the template:
 - **encryption_key** : generate a password with the site of your choice
 - **mysql** : indicate ip, port, database name, user and mysql password
@@ -137,7 +137,7 @@ storage:
     password: [mysql_password]
 ```
 
-## Regulation
+### Regulation
 For the anti brute force security, we will set up a regulation policy with 3 attempts maximum in 2 min before a ban of 5 min. This regulation is not the ultimate solution, it is always preferable to also set up a Fail2ban to complete this solution.
 
 ```
@@ -147,7 +147,7 @@ regulation:
   ban_time: 5m
 ```
 
-## Notification
+### Notification
 To set up email notifications, you must fill in the following part of the template. This part is not mandatory but it is used to reset your password in case you forget...
 
 ```
@@ -164,12 +164,12 @@ smtp:
   disable_html_emails: false
 ```
 
-## Double Authentification
+### Double Authentification
 For the double authentication several solutions are offered to you. The two most interesting celons me are the following:
 TOTP
 This is the most famous method, you just have to use an application like Google Auth to get a code that changes every 30 seconds. The configuration is very simple, just customize the `issuer` field with the name you want. This name will be displayed in your 
 
-### TOTP
+#### TOTP
 ```
 application.totp:
   issuer: [example.example.org]
@@ -177,7 +177,7 @@ application.totp:
   skew: 1
 ```
 
-### Duo Push Notification
+#### Duo Push Notification
 This is the most practical method, when you connect to your SSO, you will receive a notification that will allow you to validate your access. The configuration requires 3 elements that we will create directly on the [Duo](https://duo.com) website. In the Applications tab, click on Protect an Application and look for Partner Auth API. You can now retrieve the following elements and enter them in the Authelia configuration:
 - **Integration key**
 - **Secret Key**
@@ -194,7 +194,7 @@ duo_api:
 
 You can now start the Authelia docker, if all goes well there should be no errors. If this is the case you can go on, if not you can correct the problems until there are no more. To solve the problems you can use the Authelia [documentation](https://www.authelia.com/docs), but also their [github](https://github.com/authelia/authelia).
 
-## Nginx Proxy Manager
+## Integration with a reverse proxy
 First of all we will have to set up our Authelia subdomain so that it is accessible from the outside, but also protected with certificates. To do this, create an entry in your reverse proxy and add your subdomain, see:
 
 {{< article link="/posts/how-to-host-multiple-services-on-one-public-ip/" >}}
@@ -295,3 +295,7 @@ You can connect with one of the credencials you created in the `users_database.y
 To configure/modify the double authentication method, go to the subdomain you have configured for Authelia (`ex. auth.youdomain.com`). Then select `Methods`:
 
 <img class="thumbnailshadow" src="img/image-5.png"/>
+
+## Conclusion
+
+You now have SSO with dual authentication. This is particularly useful if you want to use the same account on several applications, add authentication to certain applications, or manage access rights to applications.

content/posts/how-to-host-multiple-services-on-one-public-ip/index.md

@@ -12,7 +12,7 @@ To solve this problem we will divide the problem in several parts. First, we wil
 
 ---
 
-## Dynamic IP
+## Dynamic/Static IP
 As described in the intro one of the big problems of self hosted on a non professional connection is that in general the external IP of the router is not fixed. That means that at each restart, the IP has a chance to change. This is a big problem, indeed to link a domain to our site for example, the DNS must know the server IP and more precisely the external IP of our network. A solution would be to manually change the IP at each change, but this is clearly not practical and makes our service infrastructure very unstable. But there is an automatic solution to this problem: DDNS.
 
 > Dynamic DNS (DDNS) is a method of automatically updating a name server in the Domain Name System (DNS), often in real time, with the active DDNS configuration of its configured hostnames, addresses or other information. 
@@ -160,6 +160,6 @@ Now let's configure our SSL certificate.
 
 Select the option "Request a new SSL Certificate" then the options "Force SSL", "HTTP/2 Support" and "HSTS Enabled". Then fill in our email and accept the terms of service. You can now save. After a few seconds you should see the status "Online" for your subdomain. If you have no errors you can now access your service with this subdomain! Using the same principle, you can setup other services.
 
----
+## Conclusion
 
 You now have a complete setup for a real selfhosting network.  But that's not all, it's a simple setup for which we can add other things. Nginx Proxy Manager already has other features, for example the "Access Lists" which allow a simple authentication system. We could also set up a SSO system to increase security, a proxy and fail2ban with CloudFlare, ... (articles coming soon will cover these topics).

content/posts/how-to-index-your-blog-on-google/index.md

@@ -6,6 +6,8 @@ slug: "how-to-index-your-blog-on-google"
 tags: ["indexing"]
 ---
 
+## What's indexation ?
+
 Today, if you want your blog/portfolio to be visible to others it is almost mandatory that it be listed on google. For your site to appear on the search engine, Google needs information!
 
 This information is usually collected automatically by a robot that Google has developed. This "Googlebot" wanders from site to site and from page to page to make a "map" of the web. This allows then to make the search engine of Google very relevant during your research.
@@ -14,7 +16,7 @@ If you want more details on how the Googlebot works, I let you see the documenta
 
 As I said above this process is automatic, but we can help it to do a better job and a more accurate scan of our site. This will allow us to be better referenced and potentially visible by more people!
 
----
+## Register your domain for indexation
 
 First we will have to add our domain to the Google Search Console site. To access the site you must be logged in with a Google account.
 
@@ -56,7 +58,7 @@ After a few minutes we notice that our sitemap index has been detected and that
 After this step, there is nothing left to do but wait. This can take from a few hours to several weeks in some cases.---
 
 
-EDIT :
+## Update
 After about 36 hours, my blog has been indexed on google and is now accessible with a simple search!
 
 <img class="thumbnailshadow" src="img/image-6.png"/>

content/posts/how-to-make-daily-backups-of-your-homelab/index.md

@@ -1,14 +1,14 @@
 ---
-title: "How to make daily backups of your HomeLab?"
+title: "How to make daily backups of your HomeLab with Rclone?"
 date: 2022-07-19
 draft: false
 slug: "how-to-make-daily-backups-of-your-homelab"
-tags: ["backup", "homelab"]
+tags: ["backup", "homelab", "tools"]
 ---
 
 You have your local homelab in which you store all your data. You have set up security measures to avoid data loss: parity disk, hot spare, cold spare, RAID, ... But in the event that your server burns down, a power surge fries your server and the data it contains, ... are you ready?
 
-In this article we will talk about the 3-2-1 Backup Rule. But what is it?
+## What's the 3-2-1 Backup Rule ?
 
 > The term 3-2-1 was coined by US photographer Peter Krogh while writing a book about digital asset management in the early noughties.
 > - 3: The rule said there should be three copies of data. One is the original or production copy, then there should be two more copies, making three.

content/posts/my-current-homelab/index.md

@@ -6,6 +6,8 @@ slug: "my-current-homelab"
 tags: ["homelab"]
 ---
 
+## What's a Homelab ?
+
 As you may or may not know, I have a homelab at home. For people who don't know what it is :
 
 > A home lab is essentially a compounded system that connects all your devices. Thus, creating an environment for you to experiment and build new projects at the comfort of your home!
@@ -16,8 +18,6 @@ Initially, my goal was to create a media server accessible from anywhere with Pl
 
 To present you all this I will first list the hardware, then the topology I used and the presentation of the services I host. And I will finish with a conclusion on the first 3 years of my homelab!
 
----
-
 ## Hardware
 Currently my homelab is composed of the following elements:
 ### Networking