diff options
| author |  Daenney <daenney@users.noreply.github.com> | 2023-06-13 16:30:09 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2023-06-13 16:30:09 +0200 |
| commit | 433b56d2f900bb53596b7a5965adfe6d93e6385b (patch) | |
| tree | 6b1febb0e66293293006cab3288ddcc06da5dea4 /docs/getting_started/index.md | |
| parent | [Frontend] Settings for profile fields (#1885) (diff) | |
| download | gotosocial-433b56d2f900bb53596b7a5965adfe6d93e6385b.tar.xz | |
[docs] Add certificates and firewalling to advanced (#1888)
* [docs] Add a certificates guide in Advanced
This adds some documentation about the process of getting certificates
through ACME in general. It also provides a number of links to
alternative clients and certbot deployment guides that are up to date.
Slightly restructure the NGINX and Apache reverse proxy documentation
and insert mentions to the Provisioning TLS certificates advanced
documentation in them.
* [docs] Add firewall section in Advanced
* [docs] Add new guides to section indexes
* [docs] Fix spelling issue
* [docs] Fix a few typos
Diffstat (limited to 'docs/getting_started/index.md')
| -rw-r--r-- | docs/getting_started/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/getting_started/index.md b/docs/getting_started/index.md index b9224b62c..0f42c5128 100644 --- a/docs/getting_started/index.md +++ b/docs/getting_started/index.md @@ -72,4 +72,4 @@ GoToSocial needs ports `80` and `443` open. If you can't leave `443` and `80` open on the machine, don't worry! You can configure these ports in GoToSocial, but you'll have to also configure port forwarding to properly forward traffic on `443` and `80` to whatever ports you choose. !!! tip - You should configure a firewall on your machine, as well as some protection against brute-force SSH login attempts and the like. A simple frontend to help you configure your firewall is [UFW](https://www.digitalocean.com/community/tutorials/how-to-set-up-a-firewall-with-ufw-on-ubuntu-18-04). You should also consider a tool like [Fail2Ban](https://linuxize.com/post/install-configure-fail2ban-on-ubuntu-20-04/) in order to automatically block malicious users. + You should configure a firewall on your machine, as well as some protection against brute-force SSH login attempts and the like. Take a look at our [firewall documentation](../advanced/security/firewall.md) for pointers on what to configure and tools that can help you out. |