Compare commits
2 Commits
92765e74db
...
77407998b5
Author | SHA1 | Date | |
---|---|---|---|
77407998b5 | |||
bcd1c5bff2 |
4
PKGBUILD
4
PKGBUILD
@ -1,7 +1,7 @@
|
|||||||
# Maintainer: NullBite <aur.archlinux@nullbite.com>
|
# Maintainer: NullBite <aur.archlinux@nullbite.com>
|
||||||
pkgname=mcserver
|
pkgname=mcserver
|
||||||
pkgver=0.0.1
|
pkgver=0.0.1
|
||||||
pkgrel=1
|
pkgrel=2
|
||||||
pkgdesc="Minecraft server manager"
|
pkgdesc="Minecraft server manager"
|
||||||
arch=("any")
|
arch=("any")
|
||||||
url="https://gitea.protogen.io/nullbite/mcserver"
|
url="https://gitea.protogen.io/nullbite/mcserver"
|
||||||
@ -11,7 +11,7 @@ changelog=
|
|||||||
source=(mcserver
|
source=(mcserver
|
||||||
mcserver@.service)
|
mcserver@.service)
|
||||||
sha256sums=('4a760cbb7848129cff4ca357d07b0a65c747f882a930d95e778b620739875ccb'
|
sha256sums=('4a760cbb7848129cff4ca357d07b0a65c747f882a930d95e778b620739875ccb'
|
||||||
'0e78d1f5832bd484043c5a3bec404ebeecae6e8394ca4e22669cdd5a93ce5cae')
|
'f4fbd63759bef7e99a6d0fbde67dd179817103b30d5486681b2390b8b5f047a7')
|
||||||
|
|
||||||
package() {
|
package() {
|
||||||
cd "$pkgdir"
|
cd "$pkgdir"
|
||||||
|
@ -4,12 +4,14 @@ tmux, in a way that makes it extremely easy to use with systemd.
|
|||||||
|
|
||||||
## instructions
|
## instructions
|
||||||
1. install systemd unit in /etc/systemd/system, change `User` option to preferred user
|
1. install systemd unit in /etc/systemd/system, change `User` option to preferred user
|
||||||
2. create minecraft server instances in `~/.local/share/mcserver/instances`
|
- On Arch Linux, the best option is to build and install the PKGBUILD and
|
||||||
|
manually change the user with `systemctl edit mcserver@.service`
|
||||||
|
3. create minecraft server instances in `~/.local/share/mcserver/instances`
|
||||||
- you can also symlink server directories from elsewhere on the system
|
- you can also symlink server directories from elsewhere on the system
|
||||||
- use `instance/` as a starting point. you need, at minimum, a `start.sh`
|
- use `instance/` as a starting point. you need, at minimum, a `start.sh`
|
||||||
startup script that executes the server jar, the server jar itself and a
|
startup script that executes the server jar, the server jar itself and a
|
||||||
`vars` file
|
`vars` file
|
||||||
3. `systemctl enable --now mcserver@instancename`
|
4. `systemctl enable --now mcserver@instancename`
|
||||||
|
|
||||||
## other info
|
## other info
|
||||||
there's a few other random things in the provided `instance` folder:
|
there's a few other random things in the provided `instance` folder:
|
||||||
|
@ -6,7 +6,7 @@ After=network.target
|
|||||||
[Service]
|
[Service]
|
||||||
Type=forking
|
Type=forking
|
||||||
ExitType=cgroup
|
ExitType=cgroup
|
||||||
User=change
|
User=nobody
|
||||||
ExecStart=/usr/bin/env mcserver start %i
|
ExecStart=/usr/bin/env mcserver start %i
|
||||||
ExecStop =/usr/bin/env mcserver stop %i
|
ExecStop =/usr/bin/env mcserver stop %i
|
||||||
RestartSec=5
|
RestartSec=5
|
||||||
|
Loading…
x
Reference in New Issue
Block a user