Add a systemd unit file

[Ladicek]

Co-authored-by: Jim Kleine jimkleine@users.noreply.github.com

Fixes #205

[miry]

Hi @Ladicek

thank you for the contribution.
I changed a bit a releasing part.

Now there is Goreleaser.
The configuration for linux packages specified in https://goreleaser.com/customization/nfpm/

Here is an example: https://github.com/Shopify/toxiproxy/blob/master/.goreleaser.yml#L63

Is it possible to disable running service by default?

[Ladicek]

Sorry, I don't really know, I'm no systemd expert :-)

[jimkleine]

Hi @miry

If you can clarify your intent, I can take a look at this (I provided the original sample systemd service file), as there has just been another report of the service failing with an error on Ubuntu 24.04.

I think you are:

1. Proposing a PR to install the systemd service via .goreleaser.yml; and

2. Asking that the service be disabled by default. I might question if this is a reasonable user expectation? If yes, this implies that the documentation may also need to be updated.

Have I understood you correctly?

I don't often work with Go, so I will need a couple of days to get up to speed with Goreleaser.

Hi @Ladicek

thank you for the contribution.
I changed a bit a releasing part.

Now there is Goreleaser.
The configuration for linux packages specified in https://goreleaser.com/customization/nfpm/

Here is an example: https://github.com/Shopify/toxiproxy/blob/master/.goreleaser.yml#L63

Is it possible to disable running service by default?

[miry]

Proposing a PR to install the systemd service via .goreleaser.yml

yes

[jimkleine]

@miry Do you have current thoughts about my part two: whether the service should be installed in a disabled state?

Proposing a PR to install the systemd service via .goreleaser.yml

yes

[miry]

Asking that the service be disabled by default. I might question if this is a reasonable user expectation? If yes, this implies that the documentation may also need to be updated.

As far as I know, most packages I have used on Fedora require users to configure the desired behavior themselves.

[jimkleine]

@miry Thanks for your feedback. Your reference to Fedora led me to this guidance on default service starts. Toxiproxy might meet test #4 if it only listens on localhost by default.

I had been thinking about this through a developer lens, but there is a wider security implication to consider.

Asking that the service be disabled by default. I might question if this is a reasonable user expectation? If yes, this implies that the documentation may also need to be updated.

As far as I know, most packages I have used on Fedora require users to configure the desired behavior themselves.