mirrors/copyparty
1
0
Fork 0
mirror of https://github.com/9001/copyparty.git synced 2025-08-17 09:02:15 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix spelling mistake, tweak commands

Browse source
This commit is contained in:
Daniel Lovegrove 2025-08-03 12:02:45 -05:00
parent cee03cac4e
commit 8c3d7fd59b
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
contrib/podman-systemd/README.md
View file

@ -2,7 +2,7 @@
Use this configuration if you want to run copyparty in a Podman container, with the reliability of running the container under a systemd service. Use this configuration if you want to run copyparty in a Podman container, with the reliability of running the container under a systemd service.
Documentation for `.container` files can be found in the [Container unit](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#container-units-container) docs. Systemd cannot does not understand `.container` files natively, so Podman converts these to `.service` files with a [systemd-generator](https://www.freedesktop.org/software/systemd/man/latest/systemd.generator.html). This process is transparent, but sometimes needs to be debugged in case your `.container` file is malformed. There are instructions to debug the systemd generator in the Troubleshooting section below. Documentation for `.container` files can be found in the [Container unit](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#container-units-container) docs. Systemd does not understand `.container` files natively, so Podman converts these to `.service` files with a [systemd-generator](https://www.freedesktop.org/software/systemd/man/latest/systemd.generator.html). This process is transparent, but sometimes needs to be debugged in case your `.container` file is malformed. There are instructions to debug the systemd generator in the Troubleshooting section below.
To run copyparty in this way, you must already have podman installed. To install Podman, see: https://podman.io/docs/installation To run copyparty in this way, you must already have podman installed. To install Podman, see: https://podman.io/docs/installation
@ -25,7 +25,7 @@ To install and start copyparty with Podman and systemd as the root user, run the
```shell ```shell
sudo mkdir -pv /etc/systemd/container/ /etc/copyparty/ sudo mkdir -pv /etc/systemd/container/ /etc/copyparty/
sudo cp -v copyparty.container /etc/systemd/containers/copyparty.container sudo cp -v copyparty.container /etc/systemd/containers/
sudo cp -v copyparty.conf /etc/copyparty/ sudo cp -v copyparty.conf /etc/copyparty/
sudo systemctl daemon-reload sudo systemctl daemon-reload
sudo systemctl start copyparty sudo systemctl start copyparty
@ -36,7 +36,7 @@ Note: You can't "enable" this kind of Podman service. The `[Install]` section of
You can see the status of the service with: You can see the status of the service with:
```shell ```shell
sudo systemctl status copyparty sudo systemctl status -a copyparty
``` ```
You can see (and follow) the logs with either of these commands: You can see (and follow) the logs with either of these commands:
@ -94,7 +94,7 @@ systemctl --user start copyparty
You can check the status of the user service with: You can check the status of the user service with:
```shell ```shell
systemctl --user status copyparty systemctl --user status -a copyparty
``` ```
You can see (and follow) the logs with: You can see (and follow) the logs with:
@ -126,7 +126,7 @@ Otherwise, you won't be able to access the copyparty server from anywhere other
## Updating copyparty ## Updating copyparty
To update the container, you can: To update the version of copyparty used in the container, you can:
```shell ```shell
# If root: # If root: