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

​
πŸ†•
(Re-)Configuring a (New) Server

After installing the necessary elements, we need to create and configure a server.
Servers are created from a configuration file. This file can be generated through the command vserver newor manually from a YAML file manually, as explained in this section.

​
πŸ“₯
Importing entities

After configuring the server, we need to define the users, organizations, collaborations, etc. This can be done using the vserver import command, as explained in this section.
Notice that we need to follow the same steps when loading/importing new data.

​
🏀
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. If you know the name of the configuration, you can use the flag --name to specify it. Use vserver start --help to see all options.
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 Docker registry for details.

​
πŸ’»
Server Commands

As a reference, these are the sub-commands available to manage the server(s). These commands can also be found by simply calling vserver . To see which options are available for each of the individual commands, use vserver CMD --help.
Command
Description
vserver attach
Attach the logs from the Docker container to the terminal
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 the server
vserver stop
Stop a or all running server
vserver version
Shows the current version of the running server

​
✍
Logging

If you attach the log to the current console, you can see a information about the server. You can either attach the logs when you start the server vserver start --attach or you can attach to an already running server by using vserver attach and select the server you want to see the log files from.
For example, the output below shows:
1
- ---------------------------------------------
2
- Welcome to
3
- _ __
4
- | | / /
5
- __ ____ _ _ __ | |_ __ _ __ _ ___ / /_
6
- \ \ / / _` | '_ \| __/ _` |/ _` |/ _ \ '_ \
7
- \ V / (_| | | | | || (_| | (_| | __/ (_) |
8
- \_/ \__,_|_| |_|\__\__,_|\__, |\___|\___/
9
- __/ |
10
- |___/
11
-
12
- --> Join us on Discord! https://discord.gg/rwRvwyK
13
- --> Docs: https://docs.vantage6.ai
14
- --> Blog: https://vantage6.ai
15
- ---------------------------------------------
16
- Started application vantage6 with environment application
17
- Current working directory is '/'
18
- Succesfully loaded configuration from '/mnt/config/Dave-A.yaml'
19
- Logging to '/mnt/log/dave-a.log'
20
- Common package version '2.1.0'
21
- vantage6 version '2.1.0'
22
- Node package version '2.1.0'
23
- Connecting server: https://trolltunga.vantage6.ai:443
Copied!

​
🧁
Deployment of a Production environment

We give some recommendations for deploying a vantage6 server in this section.
Last modified 8mo ago