Conversation
| Description=CoredumpBot | ||
|
|
||
| [Service] | ||
| ExecStart=/home/%u/start_coredump_bot_prod.sh |
There was a problem hiding this comment.
Does the bot do anything relative to the current working directory? If yes, I'd set the WorkingDirectory too.
|
|
||
| [Service] | ||
| ExecStart=/home/%u/start_coredump_bot_prod.sh | ||
| User=non_privileged_user_change_me |
There was a problem hiding this comment.
Maybe adding Group= would also be good.
| @@ -0,0 +1,10 @@ | |||
| [Unit] | |||
| Description=CoredumpBot | |||
There was a problem hiding this comment.
If you want to make sure that it isn't launched before network is up, add After=network.target.
|
I updated all the depending crates without any conflict and prepared the next release. |
| ## [0.3.2] - 2017-02-12 | ||
|
|
||
| - Add systemd service unit `coredumpbot.service` | ||
| - Add new category `Update` |
There was a problem hiding this comment.
I don't think you need to add change to the changelog format to the version changelog :)
| env_logger = "^0.3" | ||
| env_logger = "^0.4" | ||
| telegram-bot = "^0.5" | ||
| #telegram-bot = { git = "https://github.com/dns2utf8/telegram-bot.git", branch = "api_2.0" } |
|
|
||
| # Install service file | ||
|
|
||
| sudo ln -s $HOME/coredumpbot.service /etc/systemd/system/multi-user.target.wants/coredumpbot.service |
There was a problem hiding this comment.
Why $HOME?
Also, you shouldn't symlinks service files manually like this. Instead, add them to /etc/systemd/system/ and use systemctl enable <service> instead.
2 participants
I would like to add something to the readme before the merge.