versia-pub/server
2
0
Fork 0
mirror of https://github.com/versia-pub/server.git synced 2026-03-13 05:49:16 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

refactor: 🚚 Point everything to the new GitHub org

Browse source
This commit is contained in:
Jesse Wierzbinski 2024-08-27 21:40:42 +02:00
parent 47c666894c
commit f9023893af
No known key found for this signature in database
13 changed files with 66 additions and 66 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/database.md
View file

@ -4,4 +4,4 @@ Versia Server uses a special PostgreSQL extension called `pg_uuidv7` to generate
## Using the Docker image
Versia Server offers a pre-made Docker image for PostgreSQL with the extension already installed. Use `ghcr.io/lysand-org/postgres:main` as your Docker image name to use it.
Versia Server offers a pre-made Docker image for PostgreSQL with the extension already installed. Use `ghcr.io/versia-pub/postgres:main` as your Docker image name to use it.

12
docs/installation.md
View file

@ -20,7 +20,7 @@ Docker is the recommended way to run Versia Server (Podman also works). To run V
1. Download the `docker-compose.yml` file from the repository
> [!NOTE]
> You may need to change the image from `ghcr.io/lysand-org/server:latest` to `ghcr.io/lysand-org/server:main` if you want to use the latest changes from the `main` branch. Make sure to use the config template from the same branch as the server.
> You may need to change the image from `ghcr.io/versia-pub/server:latest` to `ghcr.io/versia-pub/server:main` if you want to use the latest changes from the `main` branch. Make sure to use the config template from the same branch as the server.
> [!CAUTION]
> The `latest` tag on the Docker image refers to the latest release (currently `v0.6.0`), not the latest commit on the `main` branch.
@ -28,16 +28,16 @@ Docker is the recommended way to run Versia Server (Podman also works). To run V
> **Do not mix configurations from different branches, or everything will break with confusing errors!**
```bash
curl -o docker-compose.yml https://raw.githubusercontent.com/lysand-org/server/main/docker-compose.yml
curl -o docker-compose.yml https://raw.githubusercontent.com/versia-pub/server/main/docker-compose.yml
```
1. Edit the `docker-compose.yml` file to set up the database connection and other settings
2. Download the `config.example.toml` file from the repository
```bash
# From main branch
curl -o config.example.toml https://raw.githubusercontent.com/lysand-org/server/main/config/config.example.toml
curl -o config.example.toml https://raw.githubusercontent.com/versia-pub/server/main/config/config.example.toml
# For a specific release (e.g. v0.6.0)
curl -o config.example.toml https://raw.githubusercontent.com/lysand-org/server/v0.6.0/config/config.example.toml
curl -o config.example.toml https://raw.githubusercontent.com/versia-pub/server/v0.6.0/config/config.example.toml
```
4. Edit the `config.example.toml` file to set up the database connection and other settings, rename it to `config.toml`, then place it inside `config/` (create the `config/` directory if it does not exist)
5. Run the following command to start the server:
@ -51,14 +51,14 @@ docker compose up
You may need root privileges to run Docker commands.
To check server logs, run `docker compose logs lysand`. The server will likely stop if there is an error, so you can check the logs to see what went wrong.
To check server logs, run `docker compose logs versia`. The server will likely stop if there is an error, so you can check the logs to see what went wrong.
## From Source
1. Clone this repository
```bash
git clone https://github.com/lysand-org/server.git
git clone https://github.com/versia-pub/server.git
```
2. Install the dependencies