convert pgn into webp + start hugo migration article
All checks were successful
Build Blog Docker Image / build docker (push) Successful in 1m1s

This commit is contained in:
2024-02-20 20:12:33 +01:00
parent b2a0e46d4e
commit 052a6334cb
20 changed files with 207 additions and 51 deletions

View File

@ -18,7 +18,7 @@ As described in the intro one of the big problems of self hosted on a non profes
> 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.
> — <cite>[Wikipedia](https://en.wikipedia.org/wiki/Dynamic_DNS)</cite>
![DDNS schematic](img/image-1.png)
![DDNS schematic](img/image-1.webp)
The operation of DDNS is separated into 3 parts:
@ -36,11 +36,11 @@ If you have a fixed IP with your internet provider, you do not need to do the fo
In my case I decided to use [DuckDNS](https://www.duckdns.org), it's a free service and easily configurable. First you will have to create an account with the service of your choice. Then you have to get your token, it's your unique identifier that will allow DuckDNS to identify you.
![DuckDNS token page](img/image-2.png)
![DuckDNS token page](img/image-2.webp)
You will now have to create a sub domain to the duckdns.org domain. To do this, simply fill in the "sub domain" field and click on "add domain".
![DuckDNS add domain](img/image-3.png)
![DuckDNS add domain](img/image-3.webp)
Then go to your docker manager to install the [linuxserver/duckdns](https://hub.docker.com/r/linuxserver/duckdns) docker. The docker compose is quite simple, you just have to indicate the two following elements:
@ -51,7 +51,7 @@ TOKEN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
You can then launch the docker, if all is well configured you can return to DuckDNS and verify that it has received your IP:
![DuckDNS current IP](img/image-4.png)
![DuckDNS current IP](img/image-4.webp)
## Sub-domain creation
Now that we have a domain at DuckDNS, we will have to link our personal domain/sub-domain to the DuckDNS sub-domain.
@ -65,7 +65,7 @@ To do the redirection you have to create DNS entries of type CNAME.
To create a CNAME entry, all you need is a sub-domain and a target :
![OVH DNS zone setup](img/image-5.png)
![OVH DNS zone setup](img/image-5.webp)
In this example I create a sub-domain "www.d3vyce.fr" which redirects to the DuckDNS domain "xxxx.duckdns.org". Once the information is propagated on the different DNS servers, I should be able to access the IP of my box via this sub-domain.
@ -96,7 +96,7 @@ To do this we will set up a Reserve Proxy.
> A reverse proxy server is a type of proxy server that typically sits behind the firewall in a private network and directs client requests to the appropriate backend server.
> — <cite>[Nginx.com](https://www.nginx.com/resources/glossary/reverse-proxy-server)</cite>
![Reverse Proxy schematic](img/image-6.png)
![Reverse Proxy schematic](img/image-6.webp)
Globally the reverse proxy will inspect the source domain to determine which local IP/Port to redirect the request to.
@ -144,7 +144,7 @@ Password: changeme
After creating a user, we can add our first service! To do this go to the Hosts -> Proxy Hosts tab. Now click on "Add Proxy Host".
![NginxProxyManager new proxy host](img/image-7.png)
![NginxProxyManager new proxy host](img/image-7.webp)
This is where we will have to fill in our sub-domain, local IP of the service and its port. In the example above, I configure the sub-domain "test.d3vyce.fr" with the local web server which is at the address 192.168.1.10:80.
@ -156,7 +156,7 @@ The "Websockets Support" option can be the cause of problems for some applicatio
Now let's configure our SSL certificate.
![NginxProxyManager new proxy host SSL options](img/image-8.png)
![NginxProxyManager new proxy host SSL options](img/image-8.webp)
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.