Server

The server manages users, organizations, collaborations, tasks and results. In this section we'll explain how to configure and manage a server.

💻 Server Commands

In the section above we've utilized the vserver command a lot. The following sub-commands are available to manage the server(s). These commands can also be found by simply calling vserver .

Command	Description
vserver files	List the file locations of the server instance
vserver import	Import server entities as a batch
vserver list	List the available server instances
vserver new	Create a new server configuration
vserver shell	Run a server instance python shell
vserver start	Start a server configuration

🆕 (Re-)Configuring a Server

Servers are created from a configuration file. This file can be created through command vserver newor creating a YAML file manually. See this section on how to do this.

📥 Importing entities

When you start a new server or when you just want to enter a bunch of data in the server you can use the vserver import FILE command. See this section for more details.

🏤 Managing Server Data

Managing entities at the server (e.g. users, organizations, etc...) is usually done through the RESTful API. As administrator you also have access to a Python API by using the command vserver shell which opens an iPython shell in which all database models are available. To see what you can do with these models, see this page!

🏎️ Starting the server

Once the configuration is done and you created at least one user, you can start the server instance by using vserver start and then selecting the configuration you want to use. Or if you already know the name of the configuration you can use the --name flag to specify it. If you have a configuration file which is in a non-default location than you can specify this by the --config flag.

Note that having Docker installed is not strictly necessary to run the server. However, it is needed if you want to run a private registry on the same machine. See installation of Docker for details.

🧁 Deployment of a Production environment

We give some recommendations for deploying VANTAGE6-server in this section.

✍️ Logging

If logging to the console is enabled, starting the server or loading the fixtures should output some information that can be helpful in determining the cause of problems. For example, the output below shows:

• Which environment was used

• What configuration file was used

• Which database was used

################################################################################
#                                pytaskmanager                                 #
################################################################################
Started application 'vantage' with environment 'test'
Current working directory is '/home/test-user'
Succesfully loaded configuration from '/home/test-user/.config/vantage/server/default.yaml'
Logging to '/home/test-user/.cache/vantage/log/server/default.log'
Initializing the database
  driver:   sqlite
  host:     None
  port:     None
  database: /home/test-user/.local/share/vantage/server/default/test.sqlite
  username: None
Database initialized!