Don't reserve 'service' name to make it able be used in config file as a dependency key

proposal

#1

From @ilgooz https://github.com/mesg-foundation/core/issues/420

or raise a validation error from importer.

service name currently reserved for service configuration.


now, I think that reserving service name for the mesg service can be something good. Because an nginx dependency may want to route http requests to service, in this case something like http://service:3000 should be placed into the conf file of nginx.


#2

I think it’s good to reserve the name.

But I think the core currently doesn’t raise any error if a dependency is using service as name.
Let’s investigate.