The vantage6-server requires a configuration file to run. This is a
yaml file with a specific format.
The next sections describes how to configure the server. It first provides a few quick answers on setting up your server, then shows an example of all configuration file options, and finally explains where your vantage6 configuration files are stored.
3.6.1. How to create a configuration file#
The easiest way to create an initial
configuration file is via:
vserver new. This allows you to configure the
basic settings. For more advanced configuration options, which are listed below,
you can view the example configuration file.
3.6.2. Where is my configuration file?#
To see where your configuration file is located, you can use the following command
This command will usually only work for local test deployments of the vantage6 server. If you have deployed the server on a remote server, this command will probably not work.
Also, note that on local deployments you may need to specify the
--user flag if you put your configuration file in the
You can create and edit this file
manually. To create an initial configuration file you can also use the
3.6.3. All configuration options#
The following configuration file is an example that intends to list all possible configuration options.
You can download this file here:
# Human readable description of the server instance. This is to help # your peers to identify the server description: Test # Should be prod, acc, test or dev. In case the type is set to test # the JWT-tokens expiration is set to 1 day (default is 6 hours). The # other types can be used in future releases of vantage6 type: test # IP adress to which the server binds. In case you specify 0.0.0.0 # the server listens on all interfaces ip: 0.0.0.0 # Port to which the server binds port: 5000 # API path prefix. (i.e. https://yourdomain.org/api_path/<endpoint>). In the # case you use a referse proxy and use a subpath, make sure to include it # here also. api_path: /api # The URI to the server database. This should be a valid SQLAlchemy URI, # e.g. for an Sqlite database: sqlite:///database-name.sqlite, # or Postgres: postgresql://username:firstname.lastname@example.org/database). uri: sqlite:///test.sqlite # This should be set to false in production as this allows to completely # wipe the database in a single command. Useful to set to true when # testing/developing. allow_drop_all: True # The secret key used to generate JWT authorization tokens. This should # be kept secret as others are able to generate access tokens if they # know this secret. This parameter is optional. In case it is not # provided in the configuration it is generated each time the server # starts. Thereby invalidating all previous distributed keys. # OPTIONAL jwt_secret_key: super-secret-key! # recommended but optional # Settings for the logger logging: # Controls the logging output level. Could be one of the following # levels: CRITICAL, ERROR, WARNING, INFO, DEBUG, NOTSET level: DEBUG # Filename of the log-file, used by RotatingFileHandler file: test.log # Whether the output is shown in the console or not use_console: True # The number of log files that are kept, used by RotatingFileHandler backup_count: 5 # Size in kB of a single log file, used by RotatingFileHandler max_size: 1024 # format: input for logging.Formatter, format: "%(asctime)s - %(name)-14s - %(levelname)-8s - %(message)s" datefmt: "%Y-%m-%d %H:%M:%S" # (optional) set the individual log levels per logger name, for example # mute some loggers that are too verbose. loggers: - name: urllib3 level: warning - name: socketIO-client level: warning - name: engineio.server level: warning - name: socketio.server level: warning - name: sqlalchemy.engine level: warning - name: requests_oauthlib.oauth2_session level: warning # Additional debug flags debug: # Set to `true` to enable debug mode for the socketio server socketio: false # Set to `true` to enable debug mode in the Flask app flask: false # Configure a smtp mail server for the server to use for administrative # purposes. e.g. allowing users to reset their password. # OPTIONAL smtp: port: 587 server: smtp.yourmailserver.com username: your-username password: super-secret-password # Set an email address you want to direct your users to for support # (defaults to the address you set above in the SMTP server or otherwise # to email@example.com) support_email: firstname.lastname@example.org # set how long reset token provided via email are valid (default 1 hour) email_token_validity_minutes: 60 # set how long tokens and refresh tokens are valid (default 6 and 48 # hours, respectively) token_expires_hours: 6 refresh_token_expires_hours: 48 # If you have a server with a high workload, it is recommended to use # multiple server instances (horizontal scaling). If you do so, you also # need to set up a RabbitMQ message service to ensure that the communication # between the server and the nodes is handled properly. Then, fill out the # RabbitMQ connection URI below to connect the server to it. Also, set the # start_with_server flag to true to start RabbitMQ when you start the server. rabbitmq: uri: amqp://myuser:mypassword@myhostname:5672/myvhost start_with_server: false # If algorithm containers need direct communication between each other # the server also requires a VPN server. (!) This must be a EduVPN # instance as vantage6 makes use of their API (!) # OPTIONAL vpn_server: # the URL of your VPN server url: https://your-vpn-server.ext # OATH2 settings, make sure these are the same as in the # configuration file of your EduVPN instance redirect_url: http://localhost client_id: your_VPN_client_user_name client_secret: your_VPN_client_user_password # Username and password to acccess the EduVPN portal portal_username: your_eduvpn_portal_user_name portal_userpass: your_eduvpn_portal_user_password # specify custom Docker images to use for starting the different # components. # OPTIONAL images: server: harbor2.vantage6.ai/infrastructure/server:cotopaxi ui: harbor2.vantage6.ai/infrastructure/ui:cotopaxi # options for starting the User Interface when starting the server ui: # set this to true to start the UI when starting the server with # `vserver start` enabled: true # port at which the UI will be available on your local machine port: 3456
3.6.4. Configuration file location#
The directory where to store the configuration file depends on you operating system (OS). It is possible to store the configuration file at system or at user level. At the user level, configuration files are only available for your user. By default, server configuration files are stored at system level.
The default directories per OS are as follows:
vserver looks in certain directories by default. It is
possible to use any directory and specify the location with the
flag. However, note that using a different directory requires you to specify
--config flag every time!
Similarly, you can put your server configuration file in the user folder
by using the
--user flag. Note that in that case, you have to specify
--user flag for all
Logging is enabled by default. To configure the logger, look at the
section in the example configuration in All configuration options.
vserver files: shows you where the log file is stored
vserver attach: show live logs of a running server in your current console. This can also be achieved when starting the server with
vserver start --attach