Skip to content
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.

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

Change sudo nano to sudoedit #1165

Merged
merged 6 commits into from
Oct 28, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docs/general/installation/linux.md
Original file line number Diff line number Diff line change
Expand Up @@ -384,7 +384,7 @@ sudo apt install -f
Due to the number of command line options that must be passed on to the Jellyfin binary, it is easiest to create a small script to run Jellyfin.

```sh
sudo nano jellyfin.sh
sudoedit jellyfin.sh
```

Then paste the following commands and modify as needed.
Expand Down
4 changes: 2 additions & 2 deletions docs/general/networking/fail2ban.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Jellyfin produces logs that can be monitored by Fail2ban to prevent brute-force
You need to create a jail for Fail2ban. If you're on Ubuntu and use nano as editor, run:

```bash
sudo nano /etc/fail2ban/jail.d/jellyfin.local
sudoedit /etc/fail2ban/jail.d/jellyfin.local
```

Add this to the new file, replacing `/path_to_logs` with the path to the log files above, e.g. `/var/log/jellyfin/`:
Expand Down Expand Up @@ -57,7 +57,7 @@ Note:
The filter contains a set of rules which Fail2ban will use to identify a failed authentication attempt. Create the filter by running:

```bash
sudo nano /etc/fail2ban/filter.d/jellyfin.conf
sudoedit /etc/fail2ban/filter.d/jellyfin.conf
```

Paste:
Expand Down