Skip to content

lxd_web_servers.md, punctuation (e.g., ...) #1941

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 18, 2024
Merged

lxd_web_servers.md, punctuation (e.g., ...) #1941

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2895a0e
lxd_web_servers.md, punctuation (e.g., ...)
SergeCroise Mar 17, 2024
27ae99d
lxd_web_servers.md (E.g.,)
SergeCroise Mar 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/guides/containers/lxd_web_servers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ Create a new LVM pool? (yes/no) [default=yes]:
If you have a specific hard drive or partition you’d like to use for the whole storage pool, write “yes” next. If you’re doing all of this on a VPS, you’ll probably *have* to choose “no”.

```
`Would you like to use an existing empty block device (e.g. a disk or partition)? (yes/no) [default=no]:`
`Would you like to use an existing empty block device (e.g., a disk or partition)? (yes/no) [default=no]:`
```

Metal As A Service (MAAS) is outside the scope of this document. Accept the defaults for this.
Expand Down Expand Up @@ -315,7 +315,7 @@ Here’s the quick method for starting a container with Rocky Linux:
lxc launch images:rockylinux/8/amd64 my-container
```

Of course, that “my-container” bit at the end should be renamed to whatever container name you want, eg. “proxy-server”. The “/amd64” part should be changed to “arm64” if you’re doing all of this on something like a Raspberry Pi.
Of course, that “my-container” bit at the end should be renamed to whatever container name you want, e.g., “proxy-server”. The “/amd64” part should be changed to “arm64” if you’re doing all of this on something like a Raspberry Pi.

Now here’s the long version: to find the images you want, you can use this command to list every available image in the main LXC repositories:

Expand Down Expand Up @@ -792,7 +792,7 @@ Reload the server with `systemctl restart nginx`, then point your browser at wha

You can name the config files whatever you like. I'm using simplified names for the tutorials, but some sysadmins recommend names based on the actual domain, but backwards. It's an alphabetical order-based organization thing.

eg. "apache.server.test" would get a configuration file named `test.server.apache.conf`.
E.g., "apache.server.test" would get a configuration file named `test.server.apache.conf`.
#### Directing traffic to the Nginx server

Just kinda repeat the process. Create a file just like before:
Expand Down