consider adding systemd file for the agent

[glimchb]

not everybody wants to run in a container...

[alchemicalkube]

I don't see why that would be a problem. To save having a tonne of config files you can use the command line tool to generate a unit file for you and move it into the necessary folder. This should be easily done. I'm happy to have a look into doing it?

[glimchb]

Go for it @Xeckt

[alchemicalkube]

I'll work on this now, feel free to assign this to me

Can you also tell me the requirements for the unit file - as it's clear that there are multiple options to run the agent with. Do we just create a template unit file for the user to amend or do we add options to the command to dynamically add information to the unit file?

[glimchb]

Can you also tell me the requirements for the unit file - as it's clear that there are multiple options to run the agent with. Do we just create a template unit file for the user to amend or do we add options to the command to dynamically add information to the unit file?

part of the task is to brainstorm on what we can/should do for users...

[alchemicalkube]

Sure. We can just give them a basic systemd unit file for them to amend themselves, or we give them a few options.

The only reason I opened a PR with the code to generate one from the agent CLI is so that they dont have to scour the git for it and can generate on the fly.

[glimchb]

We can package an rpm/deb file with go exec of the agent and systemd unit file and publish that in addition to the docker we publish today

[alchemicalkube]

By package you mean embed the deb file with the binary? Not sure I understand what you mean here.