It's a shame there's no way to easily create a systemd service unit, like, I type
create-service-unit /path/to/app
and whatever magic happens spits out a service file with the correct template stuff around, maybe even figuring out the Service.type itself.
(writing init.d scripts is no fun either!)

#systemd #linux

@uvok To do that robustly you basically need the service to specify what it needs in some rough abstract terms.

There isn't really a standard way of doing that and if you try to formalize something I'd say there is a large chance it would look a lot like the information included in unit files today.

To have a convention of services starting to provide that by default in some known locations would help a lot.