diff --git a/docs/books/lxd_server/00-toc.md b/docs/books/lxd_server/00-toc.md index 65e7ff9ccd..0998c2a609 100644 --- a/docs/books/lxd_server/00-toc.md +++ b/docs/books/lxd_server/00-toc.md @@ -20,7 +20,7 @@ LXD is best described on the [official website](https://linuxcontainers.org/lxd/ It is very powerful, and with the right hardware and set up, can be leveraged to run a lot of server instances on a single piece of hardware. If you pair that with a snapshot server, you also have a set of containers that you can spin up almost immediately in the event that your primary server goes down. -(You should not think of this as a traditional backup. You still need a regular backup system of some sort, like [rsnapshot](../backup/rsnapshot_backup.md).) +(You should not think of this as a traditional backup. You still need a regular backup system of some sort, like [rsnapshot](../../guides/backup/rsnapshot_backup.md).) The learning curve for LXD can be a bit steep, but this book will attempt to give you a wealth of knowledge at your fingertips, to help you deploy and use LXD on Rocky Linux. diff --git a/docs/books/lxd_server/04-firewall.md b/docs/books/lxd_server/04-firewall.md index f4a4090dfd..8adbe4e9cb 100644 --- a/docs/books/lxd_server/04-firewall.md +++ b/docs/books/lxd_server/04-firewall.md @@ -19,7 +19,7 @@ As with any server, you need to make sure that it is secured from the outside wo Starting with Rocky Linux 9.0, `iptables` and all of the associated utilities are officially deprecated. This means that in future versions of the OS, perhaps as early as 9.1, they will disappear altogether. For this reason, you should skip down to the `firewalld` procedure below before continuing. -Before continuing, you will want a firewall set up on your server. This example is using _iptables_ and [this procedure](../security/enabling_iptables_firewall.md) to disable _firewalld_. If you prefer to use _firewalld_, simply substitute in _firewalld_ rules using the instructions below this section. +Before continuing, you will want a firewall set up on your server. This example is using _iptables_ and [this procedure](../../guides/security/enabling_iptables_firewall.md) to disable _firewalld_. If you prefer to use _firewalld_, simply substitute in _firewalld_ rules using the instructions below this section. Create your firewall.conf script: @@ -54,7 +54,7 @@ iptables -A INPUT -p udp -j REJECT --reject-with icmp-port-unreachable ## Firewall Set Up - firewalld -For _firewalld_ rules, we need to use [this basic procedure](../security/firewalld.md) or be familiar with those concepts. Our assumptions are the same as with the _iptables_ rules above: LAN network of 192.168.1.0/24 and a bridge named lxdbr0. To be clear, you might have multiple interfaces on your LXD server, with one perhaps facing your WAN as well. We are also going to create a zone for the bridged and local networks. This is just for zone clarity sake, as the other names do not really apply. The below assumes that you already know the basics of _firewalld_. +For _firewalld_ rules, we need to use [this basic procedure](../../guides/security/firewalld.md) or be familiar with those concepts. Our assumptions are the same as with the _iptables_ rules above: LAN network of 192.168.1.0/24 and a bridge named lxdbr0. To be clear, you might have multiple interfaces on your LXD server, with one perhaps facing your WAN as well. We are also going to create a zone for the bridged and local networks. This is just for zone clarity sake, as the other names do not really apply. The below assumes that you already know the basics of _firewalld_. ``` firewall-cmd --new-zone=bridge --permanent diff --git a/docs/guides/containers/.pages b/docs/guides/containers/.pages index 7d93ebba77..667dc80b52 100644 --- a/docs/guides/containers/.pages +++ b/docs/guides/containers/.pages @@ -1,4 +1,4 @@ --- nav: - - LXD Server: https:/docs.rockylinux.org/books/lxd_server/00-toc.md/ + - LXD Server: https://docs.rockylinux.org/books/lxd_server/00-toc/ - ... diff --git a/docs/guides/containers/lxd_web_servers.it.md b/docs/guides/containers/lxd_web_servers.it.md index 7bc68884cd..b6d1f20cb7 100644 --- a/docs/guides/containers/lxd_web_servers.it.md +++ b/docs/guides/containers/lxd_web_servers.it.md @@ -9,7 +9,7 @@ update: 28-Feb-2022 ## Introduzione -Okay, così abbiamo già [una guida per l'installazione di LXD/LXC su Rocky Linux](lxd_server.md), ma questo è stato scritto da qualcuno che sa cosa sta facendo, e voleva costruire una rete containerizzata di server e/o applicazioni su una macchina fisica sulla sua rete locale. È fantastico, e ne ruberò subito dei pezzi per non dover scrivere tanto. +Okay, così abbiamo già [una guida per l'installazione di LXD/LXC su Rocky Linux](../../books/lxd_server/00-toc.md), ma questo è stato scritto da qualcuno che sa cosa sta facendo, e voleva costruire una rete containerizzata di server e/o applicazioni su una macchina fisica sulla sua rete locale. È fantastico, e ne ruberò subito dei pezzi per non dover scrivere tanto. Ma se avete appena sentito parlare di Linux Containers e non avete ancora capito bene come funzionano, ma volete ospitare qualche sito web, questa è la guida che fa per voi. *Questo tutorial vi insegnerà come ospitare siti web di base con LXD e LXC su qualsiasi sistema, compresi i server privati virtuali e il cloud hosting.* diff --git a/docs/guides/containers/lxd_web_servers.md b/docs/guides/containers/lxd_web_servers.md index 6457a38272..aae81139c9 100644 --- a/docs/guides/containers/lxd_web_servers.md +++ b/docs/guides/containers/lxd_web_servers.md @@ -9,7 +9,7 @@ update: 28-Feb-2022 ## Introduction -Okay, so we already have [a guide on installing LXD/LXC on Rocky Linux](lxd_server.md), but that was written by someone who knows what he’s doing, and wanted to build a containerized network of servers and/or apps on a physical machine on his local network. It’s great, and I’ll be straight up stealing bits of it so I don’t have to write as much. +Okay, so we already have [a guide on installing LXD/LXC on Rocky Linux](../../books/lxd_server/00-toc.md), but that was written by someone who knows what he’s doing, and wanted to build a containerized network of servers and/or apps on a physical machine on his local network. It’s great, and I’ll be straight up stealing bits of it so I don’t have to write as much. But, if you’ve just heard about Linux Containers, and don’t really understand how they work yet, but you want to host some websites, this is the guide for you. *This tutorial will teach you how to host basic websites with LXD and LXC on any system, including virtual private servers and cloud hosting.* diff --git a/docs/guides/contribute/mkdocs_lsyncd.it.md b/docs/guides/contribute/mkdocs_lsyncd.it.md index 01d0a3f869..d7c8072d39 100644 --- a/docs/guides/contribute/mkdocs_lsyncd.it.md +++ b/docs/guides/contribute/mkdocs_lsyncd.it.md @@ -22,7 +22,7 @@ Alcune cose che dovresti avere/conoscere/essere: * Familiarità e comfort con la riga di comando * Essere a proprio agio con l'uso di strumenti per l'editing, SSH e la sincronizzazione, o essere disposti a seguire e imparare -* Faremo riferimento a LXD - c'è un lungo documento su come costruire e usare LXD su un server [qui](../containers/lxd_server.md), ma noi useremo solo un'installazione di base sulla nostra postazione Linux. Questo documento presuppone che stiate già usando LXD per altre cose, e non copre la costruzione e l'inizializzazione di LXD. +* Faremo riferimento a LXD - c'è un lungo documento su come costruire e usare LXD su un server [qui](../../books/lxd_server/00-toc.md), ma noi useremo solo un'installazione di base sulla nostra postazione Linux. Questo documento presuppone che stiate già usando LXD per altre cose, e non copre la costruzione e l'inizializzazione di LXD. * Useremo `lsyncd` per il mirroring dei file, e puoi trovare la documentazione a riguardo [qui](../backup/mirroring_lsyncd.md) * Avrete bisogno di chiavi pubbliche generate per il vostro utente e per l'utente "root" sulla vostra postazione locale usando [questo documento](../security/ssh_public_private_keys.md) * La nostra interfaccia bridge è in esecuzione su 10.56.233.1 e il nostro container è in esecuzione nei nostri esempi qui sotto su 10.56.233.189. diff --git a/docs/guides/contribute/mkdocs_lsyncd.md b/docs/guides/contribute/mkdocs_lsyncd.md index 6cd76feb5f..f52d77a89e 100644 --- a/docs/guides/contribute/mkdocs_lsyncd.md +++ b/docs/guides/contribute/mkdocs_lsyncd.md @@ -22,7 +22,7 @@ A few things you should have/know/be: * Familiarity and comfort with the command-line * Comfortable using tools for editing, SSH, and synchronization, or willing to follow along and learn -* We will reference LXD - there's a long document on [building and using LXD on a server here](../containers/lxd_server.md), but we will be using just a basic install on our Linux workstation. This document assumes that you are already using LXD for other things, and does not cover the build and initialization of LXD. +* We will reference LXD - there's a long document on [building and using LXD on a server here](../../books/lxd_server/00-toc.md), but we will be using just a basic install on our Linux workstation. This document assumes that you are already using LXD for other things, and does not cover the build and initialization of LXD. * We will be using `lsyncd` for mirroring files, and you can find [documentation on that here](../backup/mirroring_lsyncd.md) * You will need public keys generated for your user and the "root" user on your local workstation using [this document](../security/ssh_public_private_keys.md) * Our bridge interface is running on 10.56.233.1 and our container is running on 10.56.233.189 in our examples below.