... | ... | @@ -74,7 +74,7 @@ When the *error* tag is defined, an *error* command is executed when the applica |
|
|
|
|
|
# Environment files
|
|
|
|
|
|
An application often depends on environment variables. When an application is launched on a local account, some specific environment variables may have been defined. However when the application is launched by a CAMEO server, it may not work, because some environment variables are missing. Indeed the environment is not the one of the local account even if the Cameo server is launched as a user service. The *environment files* are there to solve this problem.
|
|
|
An application often depends on environment variables. When an application is launched on a local account, some specific environment variables may have been defined. However when the application is launched by a CAMEO server, it may not work, because some environment variables are missing. Indeed the environment is not the one of the local account even if the CAMEO server is launched as a user service. The *environment files* are there to solve this problem.
|
|
|
|
|
|
An example with the *app.properties* file:
|
|
|
```
|
... | ... | @@ -91,10 +91,10 @@ One practical way to check the required environment variables is to launch the a |
|
|
|
|
|
# Log
|
|
|
|
|
|
The CAMEO server application is logging in the *cameo.log* file and it is also possible to log the standard error and output of the applications started by the Cameo server.
|
|
|
The CAMEO server application is logging in the *cameo.log* file and it is also possible to log the standard error and output of the applications started by the CAMEO server.
|
|
|
|
|
|
Indeed when you need to debug an application, the standard error and output may be useful.
|
|
|
CAMEO applications are started in background and it is possible to log the standard error and output. For that, you need to define the *log_directory* attribute of the application tag with a path that exists or the *default* value which is the location of the *cameo.log* file. Each running Cameo application has a unique id provided by the server and the produced log file is *<name>.<id>.log* for an app with the name *name* and id *id*. For instance it could be *App2.12.log*.
|
|
|
CAMEO applications are started in background and it is possible to log the standard error and output. For that, you need to define the *log_directory* attribute of the application tag with a path that exists or the *default* value which is the location of the *cameo.log* file. Each running CAMEO application has a unique id provided by the server and the produced log file is *<name>.<id>.log* for an app with the name *name* and id *id*. For instance it could be *App2.12.log*.
|
|
|
|
|
|
# Start the server
|
|
|
|
... | ... | @@ -102,7 +102,7 @@ Once the configuration file and its associated environment files have been defin |
|
|
|
|
|
# Registered and unregistered apps
|
|
|
|
|
|
CAMEO is very flexible and accepts different combinations for an application to be controlled by Cameo.
|
|
|
CAMEO is very flexible and accepts different combinations for an application to be controlled by CAMEO.
|
|
|
|
|
|
## *This* initialized with the *arguments* variable
|
|
|
|
... | ... | |