manage node as service by systemd

[bertux]

to make it lighter than using Docker and downloading at every start
it should make possible to run dozens of nodes natively on the host without requiring much

[aesedepece]

Hey @bertux this is looking good.

What do you think about providing a README file explaining how to use the service? I know it should be obvious for most modern GNU/Linux users. However I think it would be super nice to have some instructions on the big picture, I mean how to download the binary and all the needed files for this service to work.

[aesedepece]

Just found out this is totally related to issue #1043 !

[bertux]

Just found out this is totally related to issue #1043 !

Thank you I will base the README.md from this content and will correct the location of the service file.

I will also a link to this README in https://github.com/witnet/witnet-rust/blob/master/docs/get-started/installation/from-source.md to contribute to the documentation.

[bertux]

@aesedepece it's finally ready for review, I've kept the README minimal by referencing the documentation of installation from source where I have added to install the systemd service with a dedicated user. Happy to reply your questions about it.

[aesedepece]

This is great! 💪

[aesedepece]

BTW, @bertux what do you think about backporting #1140 into the runner.sh here once #1140 it is merged?

[bertux]

BTW, @bertux what do you think about backporting #1140 into the runner.sh here once #1140 it is merged?

I didn't want to delay this pull request by backporting it already but when both will be merged then I can create a new pull request for this backport.

[aesedepece]

BTW, @bertux what do you think about backporting #1140 into the runner.sh here once #1140 it is merged?

I didn't want to delay this pull request by backporting it already but when both will be merged then I can create a new pull request for this backport.

I agree that's the better option.

Please take a look at the contributing guide for specific instructions about commit messages and PGP signing your commits.

[bertux]

BTW, @bertux what do you think about backporting #1140 into the runner.sh here once #1140 it is merged?

I didn't want to delay this pull request by backporting it already but when both will be merged then I can create a new pull request for this backport.

I agree that's the better option.

Please take a look at the contributing guide for specific instructions about commit messages and PGP signing your commits.

I have followed the contributing guide and now my public GPG key is shared at https://keys.openpgp.org/ and I've followed https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request to squash my commits into one signed commit to be able to merge it with the commit message below :
feat(systemd): added systemd integration
@aesedepece would you suggest a better commit message ? is feat(integration) better ?

[aesedepece]

Approved!

[bertux]

Approved!

But I can't still merge it myself so I guess @aesedepece will merge it when he will feel it's the right timing. I hope I won't need to rebase it again by this time.

[aesedepece]

Please accept the write access invite here:
https://github.com/witnet/witnet-rust/invitations

Then you'll be able to push to master like the gods of git do 😎

[bertux]

Please accept the write access invite here:
https://github.com/witnet/witnet-rust/invitations

Then you'll be able to push to master like the gods of git do 😎

thank you for the invitation, I've accepted it now and when I've tried my first merge here it proposed only "Rebase and merge" which then failed with error message "Merge attempt failed
Base branch requires signed commits. Rebase merges cannot be automatically signed by GitHub"
So I guess I will need to rebase it again before being able to merge.

[aesedepece]

Yes, it sounds like some other PR was merged in the meanwhile, so you need to rebase again and merge right after that. Welcome to open development! 😛

[bertux]

Yes, it sounds like some other PR was merged in the meanwhile, so you need to rebase again and merge right after that. Welcome to open development! 😛

thank you for the confirmation, that's what I'm redoing now. I love to be able to contribute directly to your open development :-)