Virola Server installation on Arch Linux

To install Virola Server on Arch Linux, follow these steps:

Update your Arch system. While this step isn't strictly required, it's recommended to help prevent potential issues. For optimal results, you might need to run the following commands multiple times:
```
sudo pacman -S gnupg
sudo pacman -S archlinux-keyring
sudo pacman -Syu
sudo reboot
```
Install wget if it hasn't been installed yet:
```
sudo pacman -S wget
```

Download the Virola Server installer:

wget https://virola.io/downloads/2.5.1.25040115/virola-server-arch-2.5.1.25040115_x86_64.pkg.tar.zst

Install the Virola Server:

sudo pacman -U ./virola-server-arch-2.5.1.25040115_x86_64.pkg.tar.zst

After installing the package, you'll be prompted to choose whether to automatically register Virola Server as a systemd service (daemon) or leave it unregistered and start it manually.

We recommend opting for the systemd option, as it allows the server to start automatically with the system and ensures smooth restarts.
To register Virola Server as a systemd service, follow these steps:
1. Respond Y to the prompt Do you want to configure Virola Server? and to all subsequent configuration questions.
2. Select the IP address your server will listen on, and enter it in response to Enter IP on which Virola Server will listen when running as Systemd service (0.0.0.0). You can use 0.0.0.0 to allow access from both intranet and internet, but make sure the server is properly secured.
3. Choose the port the server will use, and provide it when prompted: Enter PORT on which Virola Server will listen when running as Systemd service (7777).
4. Answer Y to Do you want to start Virola Server systemd service now?
  Once completed, the installer will configure the systemd service and launch the server automatically. You will then receive your administrator credentials, which you can use to log into the Virola Client app.

The Virola Client app is used for both communication and managing the server, teams, and workflows. Check out our video tutorials to learn how to set up your team, create chat rooms, manage permissions, and more.

The systemd service will be automatically restarted by the installer after each server update.

If you need to manually start or stop the service, modify its settings, or relocate the Virola Server database, refer to the systemd management instructions for Ubuntu/Debian systems.

You may not have access to the /home/virola directory, but you can still view its contents using the command sudo ls /home/virola, and access files inside the directory. For example, the command sudo nano /home/virola/start-virola-server.sh opens the file start-virola-server.sh in nano text editor.

If you choose not to register Virola Server as a systemd service

To skip registering Virola Server as a systemd service during installation, respond with n when prompted with Do you want to configure Virola Server? The installation will still complete successfully.

To start the server manually, use the following command:

virola-server --listen HOST:PORT

where

HOST is the IP address you want Virola Server to listen on
PORT is the port number you've selected

Example:
virola-server --listen 127.0.0.1:7777

If you decide to register Virola Server as a systemd service at a later time, just follow the provided instructions.

Important Notes

Make sure to change your default admin password to a more secure one as soon as possible. You can do this either from the Virola Client (Hamburger menu / My User Profile / User Account Settings / Change My User Password) or using the --change-password command line argument of the Virola server.

We strongly recommend to encrypt Linux machine on which Virola server is running. The best way is to encrypt it during Linux installation but it is also possible to encrypt the existing Linux instance. We've prepared a detailed instruction about disc encryption in Linux environment for you.

For any questions or additional assistance, our online support team is available to help. Click the live chat button to start a conversation with one of our support representatives.