The next-generation file converter. Open source, fully local* and free forever.
Go to file
azurejelly cc8145d576
docs(docker): add instructions on how to serve over HTTPS
* Added a script to generate a self-signed certificate
* Added *.pem, *.key and *.crt files to .gitignore and .dockerignore
* Stopped setting PUB_PLAUSIBLE_URL to https://plausible.example.com on Docker Compose builds by default
* Modified "Building on Production" to mention that HTTPS is required on most cases
* Added a base HTTPS config for nginx
2025-04-26 15:45:41 -04:00
.github/workflows support arm64 2025-04-19 10:24:05 -03:00
.vscode feat: dark mode (#7) 2024-11-13 19:33:16 +00:00
nginx docs(docker): add instructions on how to serve over HTTPS 2025-04-26 15:45:41 -04:00
src fix: wording 2025-04-26 18:20:53 +01:00
static feat: documents support 2025-04-12 23:18:50 +01:00
.dockerignore docs(docker): add instructions on how to serve over HTTPS 2025-04-26 15:45:41 -04:00
.env.example fix: use PUB_VERTD_URL 2025-04-13 23:43:52 +01:00
.gitignore docs(docker): add instructions on how to serve over HTTPS 2025-04-26 15:45:41 -04:00
.npmignore feat: ready for bytecrush! 2025-04-16 21:56:15 +01:00
.prettierignore feat: initial commit 2024-11-11 13:16:06 +00:00
.prettierrc feat: initial commit 2024-11-11 13:16:06 +00:00
Dockerfile docs(docker): add instructions on how to serve over HTTPS 2025-04-26 15:45:41 -04:00
LICENSE Create LICENSE 2024-11-12 19:01:37 +01:00
README.md docs(docker): add instructions on how to serve over HTTPS 2025-04-26 15:45:41 -04:00
_headers fix: netlify serve HTTP headers for libvips 2025-02-11 12:32:23 +03:00
bun.lock fix: build?? 2025-04-15 16:34:23 +01:00
docker-compose.yml docs(docker): add instructions on how to serve over HTTPS 2025-04-26 15:45:41 -04:00
eslint.config.js feat: initial commit 2024-11-11 13:16:06 +00:00
package.json feat: ready for bytecrush! 2025-04-16 21:56:15 +01:00
postcss.config.js feat: initial commit 2024-11-11 13:16:06 +00:00
svelte.config.js Reapply "fix: navigation issues (#57)" 2025-04-13 13:50:48 +01:00
tailwind.config.ts feat: document colours! 2025-04-12 23:49:00 +01:00
tsconfig.json feat: initial commit 2024-11-11 13:16:06 +00:00
vite.config.ts fix: dev 2025-04-15 16:52:18 +01:00

README.md

VERT's logo

VERT.sh

VERT is a file conversion utility that uses WebAssembly to convert files on your device instead of a cloud. Check out the live instance at vert.sh.

VERT is built in Svelte and TypeScript.

Features

  • Convert files directly on your device using WebAssembly *
  • No file size limits
  • Supports multiple file formats
  • User-friendly interface built with Svelte

* Non-local video conversion is available with our official instance, but the daemon is easily self-hostable to maintain privacy and fully local functionality.

Getting Started

Prerequisites

Make sure you have the following installed:

Installation

# Clone the repository
$ git clone https://github.com/VERT-sh/vert.git
$ cd vert

# Install dependencies
$ bun i

Running Locally

To run the project locally, run bun dev.

This will start a development server. Open your browser and navigate to http://localhost:5173 to see the application.

Building for Production

Before building for production, make sure you create a .env file in the root of the project with the following content:

PUB_HOSTNAME=example.com # change to your domain, only gets used for Plausible (for now)
PUB_PLAUSIBLE_URL=https://plausible.example.com # can be empty if not using Plausible
PUB_ENV=production # "production", "development" or "nightly"
PUB_VERTD_URL=https://vertd.vert.sh # default vertd instance

To build the project for production, run bun run build

This will build the site to the build folder. You should then use a web server like nginx to serve the files inside that folder.

If using nginx, you can use the default-ssl.conf file (or default.conf if you don't need to serve the site over HTTPS) as a starting point. Make sure you keep cross-origin isolation enabled, which requires HTTPS on most cases.

With Docker

Clone the repository, then build a Docker image with:

$ docker build -t vert-sh/vert \
	--build-arg PUB_ENV=production \
	--build-arg PUB_HOSTNAME=vert.sh \
	--build-arg PUB_PLAUSIBLE_URL=https://plausible.example.com \
	--build-arg PUB_VERTD_URL=https://vertd.vert.sh .

You can then run it by using:

$ docker run -d \
	--restart unless-stopped \
	-p 3000:80 \
	--name "vert" \
	vert-sh/vert

This will do the following:

  • Use the previously built image as the container vert, in detached mode
  • Continuously restart the container until manually stopped
  • Map 3000/tcp (host) to 80/tcp (container)

We also have a docker-compose.yml file available. Use docker compose up if you want to start the stack, or docker compose down to bring it down. You can pass --build to docker compose up to rebuild the Docker image (useful if you've changed any of the environment variables) as well as -d to start it in detached mode. Feel free to read more about Docker Compose in general here.

Pulling instead of building

While there's an image you can pull instead of cloning the repo and building the image yourself, you will not be able to update any of the environment variables (e.g. PUB_PLAUSIBLE_URL) as they're baked directly into the image and not obtained during runtime. If you're okay with this, you can simply run this command instead:

$ docker run -d \
	--restart unless-stopped \
	-p 3000:80 \
	--name "vert" \
	ghcr.io/vert-sh/vert:latest

Serving the site over HTTPS

If you're running the container in your local machine and accessing it from localhost, this isn't really required. However, any other origin will cause cross-origin isolation to be disabled unless you serve the site over HTTPS, which in turn will cause image conversions to fail. There are a few options to get around this:

  • Using something like Tailscale's HTTPS feature
  • Using a self-signed certificate (not recommended for public instances and your browser will likely yell at you)
  • Using Let's Encrypt or Cloudflare as a TLS proxy with your own domain

If you want to use a self-signed certificate, there's a little script you can run in order to generate one. Make sure you have openssl installed, then run:

$ cd ./nginx/
$ ./setup-self-signed.sh

This will generate the following files inside ./ssl/:

$ ls ./ssl
self-signed.crt  self-signed.key

If you don't want to use a self-signed certificate, simply copy your own key and certificate files into ./nginx/ssl/ instead. Make sure to then modify the default SSL config under ./nginx/default-ssl.conf to match the file names:

server {
    ...

    ssl_certificate     /etc/ssl/vert/self-signed.crt;
    ssl_certificate_key /etc/ssl/vert/self-signed.key;

    ...
}

Finally, update your Docker Compose configuration:

services:
  vert:
    # ...
    ports:
      # map to port 443 instead of 80
      - "${PORT:-3000}:443"
    volumes:
      # map the ssl folder with our certificates to /etc/ssl/vert in read-only mode
      - "./nginx/ssl:/etc/ssl/vert:ro"

      # overwrite the default HTTP configuration of the container
      - "./nginx/default-ssl.conf:/etc/nginx/conf.d/default.conf"

For docker run, use:

$ docker run ... \
	-p 3000:443 \
	-v "./nginx/ssl:/etc/ssl/vert" \
	-v "./nginx/default-ssl.conf:/etc/nginx/conf.d/default.conf" \
	...

License

This project is licensed under the AGPL-3.0 License, please see the LICENSE file for details.