Installing Sylva the hard way
Installing Sylva from source has zero official support for end users. We only recommend this method for advanced users or those who plan to contribute to the project.
For the purposes of this document, it is assumed that the user is running Linux.
Overview
Sylva uses a PDM backend. There is no requirements.txt
file, and Issues should not be raised for this missing file.
Prerequisites
- Install PDM according to their documentation
- Chrome or Chromium
- xorg-x11-server-Xvfb (Fedora), xvfb (Debian), or your distribution's equivalent
Installing Sylva for development
Sylva is now installed in an isolated live environment. Changes made to the code should be reflected within this environment immediately.
All dependency groups are installed, including those for regression testing, MkDocs editing, etc.
Running within the venv
Users can enter the virtual environment by running source .venv/bin/activate
. The difficulty here is that global installs of the same package are known to interfere. If you have Sylva installed globally as well, you should defer to the next method.
Assuming you have entered the venv, you can run Sylva as you would normally.
Running via PDM
Due to the aforementioned complication, many developers may opt to run Sylva through PDM itself.
Installing Sylva globally
Warning
This is not an officially supported method of installation.
This method also lacks any means of automatic or assisted updates.
Building the Docker image
Sylva provides both the latest release (semver tagged and as latest) and the current state of master
(as preview) as a Docker image, available on both Docker Hub and the GitHub Container Registry.
If you'd rather build your own image, such as for development use or validation, you can do so with the provided multi-stage Dockerfile. The prerequisites mentioned earlier can be skipped you're only building the Docker image.
Build target cli-prod
is the standard command line target. Future targets may include web interfaces, or other added functionality.