Paul Trowbridge
e6a615bf70
deploy.sh is the idempotent rollout path: venv + deps, launcher,
/etc/pipekit/secrets.env skeleton (mode 0600), schema init, and
auto-register of every JDBC driver shipped with jrunner. systemd
unit is a template, not auto-installed — user copies it when ready
to cut over.
`pipekit secrets {list,set,unset}` manages /etc/pipekit/secrets.env
with atomic 0600 writes so passwords don't need sudoedit. Prompted
input by default; positional value allowed for scripting.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
30 lines
783 B
Desktop File
30 lines
783 B
Desktop File
# Pipekit systemd unit template.
|
|
#
|
|
# Install:
|
|
# sudo cp pipekit.service /etc/systemd/system/
|
|
# sudo systemctl daemon-reload
|
|
# sudo systemctl enable --now pipekit
|
|
#
|
|
# Runs as root by default. For a dedicated service account, create the
|
|
# user and uncomment User=/Group= below:
|
|
# sudo useradd --system --home-dir /opt/pipekit --shell /usr/sbin/nologin pipekit
|
|
# sudo chown -R pipekit:pipekit /opt/pipekit/pipekit.db /etc/pipekit
|
|
|
|
[Unit]
|
|
Description=Pipekit sync engine
|
|
After=network-online.target
|
|
Wants=network-online.target
|
|
|
|
[Service]
|
|
Type=simple
|
|
# User=pipekit
|
|
# Group=pipekit
|
|
WorkingDirectory=/opt/pipekit
|
|
EnvironmentFile=/etc/pipekit/secrets.env
|
|
ExecStart=/usr/local/bin/pipekit serve --host 0.0.0.0
|
|
Restart=on-failure
|
|
RestartSec=5s
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|