æʃliŋ, purrepurrocessor @aescling@cat.family

@alyssa good question! i’ll need a minute fur that one

@packbat everything about it lol. kit!me would despise that i catify shit

@Lady @Satsuma 95 is right in that border where i don’t really know which generation is accurate fur me but too real regardless

@Lady i assume you've already started (or finished?) but if you ever wanna stream it i'd be down

@Lady been interested in watching it

@monorail that would do it

@monorail what the hell. lmao

@monorail we're still in some awkward hybrid of 3.5 and 4.x over here; ny'all could be doing worse

@amy "not fucking neopets" we get it, you're ace

@amy f u c k o f f lmao

@monorail is the joke that they were on good terms as far the the historical record shows us

@MindmeshLink an arguable cheat is ExecStart=fish -c "[whatever the venv command is, i furget]; exec [final command]. i think that should work

@MindmeshLink

• under the service section, WorkingDirectory=/path/to/desired/working/directory; if your script picks up configs from the current directory this will make setup simpler
• to run as a user who is not root, User=username, in the same section
• if needed, you can specify as many Environment="ENV_VAR=whatever" lines as required under that same section
• (you can also specify an environment file with EnvironmentFile=/path/to/file; the syntax is in VAR="contents" furmat)

@MindmeshLink the trivial systemd script fur daemons that are Just A Purrocess You Simply Run From The Command Line is

$ cat /etc/systemd/system/my-unit-name.service
[Unit]
Description=name of this service

[Install]
WantedBy=multi-user.target

[Service]
Type=simple
ExecStart=[command line here (you can use spaces)]

# the following make systemd automatically re-up the service every time it downs, which is usually desirable behavior
Restart=always
RestartSec=1 # you usually want some throttling in case it keeps exiting immediately

then run systemctl daemon-reload, and then systemctl enable my-unit-name.service (.service is optional). use systemctl status my-unit-name.service if you want confurmation that it worked fine.

standard output and error should automatically get logged to the systemd journal; you can view that output with journalctl -u my-unit-name.service

@Lady ok

@Lady i don't understand the post

@xenon are you complimenting me or mae. not fishing fur one; i genuinely can’t tell