Baguette
/
service
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Manpages update.

master
Luka Vandervelden 2019-11-16 18:04:23 +01:00
parent 8d5839724b
commit 3a502f0415
2 changed files with 15 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/service.1.scd
View File

@ -47,11 +47,20 @@ If the `--verbose` flag is provided, informations about what tokens a service pr
service start <id>
If a service that has dependencies is requested to be started, its dependencies will be started beforehand.
When *service* starts services, it also starts their dependencies.
If a service is depended on by a non-runnable service, the non-runnable services will have their configuration and deployable files generated once its last dependency is started.
An example for this is a static website that depends on a web server: if the web server is started, the static website’s files and possible configuration will be generated or installed where they will be served.
To force a service the use of a particular provider, the syntax token_id=service_id can be used.
If providers are guessed, those from the same environment as the service to be created are used first, if any.
Services from the *root* environment are tried next.
To force *not* using a token, the token_id=none syntax can be used.
The type=service_type syntax can be used to specify what kind of service is to be created if its name does not match a known service definition.
The domain=example.tld syntax can be used to specify domain names when creating services that require one.
## Stopping Services
service stop <id>
@ -82,7 +91,7 @@ Be careful, as this command also removes its configuration and data.
## Starting a Service
$ service start gitea
service start gitea
## Registering a Single Service
@ -99,7 +108,7 @@ Be careful, as this command also removes its configuration and data.
service add gitea http=nginx postgresql=postgresql domain=gitea.test
In this example, the dependencies of the “gitea” service could have been guessed automatically.
The following example does the exact same thing but lets `service` guess dependencies.
The following example does the exact same thing but lets *service* guess dependencies.
service add nginx
@ -109,7 +118,7 @@ The following example does the exact same thing but lets `service` guess depende
# SEE ALSO
*servîce*(7)
*service*(7)
# AUTHORS

4
doc/service.7.scd
View File

@ -6,9 +6,9 @@ service - services and applications management
# DESCRIPTION
The *service*(1) tool is used to manage services.
The *service*(1) tool manages services.
The *rc*(1) script is used to start the components of the system not handled by *init*(1).
The *rc*(1) script starts the components of the system not handled by *init*(1).
*rc* is usually the first application to call *service*.
# SERVICE IDS