FilmCraft Web — Docker Image

A community-maintained Docker image for FilmCraft, bringing its WebAssembly-based video editor to a self-hosted web interface.
Automated weekly builds and image publication to GitHub Container Registry (GHCR).

Why this repository?

The upstream FilmCraft project provides a WebAssembly build that can be served as a static website. This repository automates building that web application from upstream source and packages the generated files into a small NGINX-based Docker image.

The goals are to:

• Build the web app from the current main branch of storytold/filmcraft.
• Include the shared font assets from storytold/craft-fonts.
• Rebuild the image automatically each week and publish it to GHCR.
• Provide a simple image that can later be offered through Unraid Community Applications.
• Keep this packaging project separate from the upstream FilmCraft source code.

This is an independent community packaging project. It is not an official FilmCraft release and is not affiliated with or endorsed by the PhotoCraft or ArtCraft maintainers.

How it works

FilmCraft's web application runs in the browser using WebAssembly. The container serves the compiled static web files through NGINX; it does not run a remote desktop.

• Browser-based editor: use FilmCraft through a modern browser.
• Local media: media files are handled by the browser application and are not uploaded to this container as a document-storage service.
• No remote desktop: no VNC session or Linux graphical desktop is required.
• Self-hosted: run the web app on your own server and access it over your local network or through a properly configured reverse proxy.

FilmCraft is in alpha and is under active development. Features, compatibility and behaviour may change between upstream builds. Test updates before relying on the application for important projects.

Docker image

The published image is:

ghcr.io/mikapst/filmcraft-web:latest

Quick start with Docker Compose

A docker-compose.yml file is provided at the repository root:

services:
  filmcraft-web:
    image: ghcr.io/mikapst/filmcraft-web:latest
    container_name: filmcraft-web
    ports:
      - "8080:8080"
    restart: unless-stopped

Start FilmCraft Web from the repository directory:

docker compose up -d

Then open:

http://YOUR_SERVER_IP:8080

Replace YOUR_SERVER_IP with the IP address or hostname of your server. On the same computer, use http://localhost:8080.

Run directly with Docker

docker run -d \
  --name filmcraft-web \
  --restart unless-stopped \
  -p 8080:8080 \
  ghcr.io/mikapst/filmcraft-web:latest

Useful commands

# View logs
docker compose logs -f

# Pull the latest image and recreate the container
docker compose pull
docker compose up -d

# Stop and remove the container
docker compose down

No .env file or persistent volume is required for the default configuration. The host port is 8080; to use a different host port, change the left-hand side of the port mapping, for example 8081:8080.

Reverse proxy and browser requirements

The NGINX configuration:

• serves .wasm files with the application/wasm MIME type;
• sends Cross-Origin-Opener-Policy: same-origin;
• sends Cross-Origin-Embedder-Policy: require-corp.

These headers provide the cross-origin isolation expected by the upstream web hosting guidance. If you expose the application outside your local network, use HTTPS through a reverse proxy such as Traefik and avoid exposing plain HTTP directly to the public Internet.

FilmCraft's browser build uses WebGPU with a WebGL2 fallback. Compatibility and performance depend on the browser, GPU and media being edited.

Automated builds

GitHub Actions builds the FilmCraft web application and publishes the container image automatically.

Published tags

• latest — the latest successful build.
• upstream-<commit> — identifies the exact FilmCraft source commit used for the build.

The image is published for linux/amd64 and linux/arm64. Since the container serves static web assets through NGINX, the compiled web files are architecture-independent.

A scheduled rebuild does not guarantee that upstream changes are compatible or stable. If a build fails, the previous published image remains available.

First-time GHCR setup: after the first successful publication, check the package's visibility in GitHub Packages. Set filmcraft-web to Public if you want users to pull the image without authenticating to GHCR.

Build pipeline

The workflow:

1. Checks out this repository.
2. Checks out FilmCraft and the shared craft-fonts repository.
3. Installs the Rust WebAssembly target and the matching wasm-bindgen-cli version from FilmCraft's lockfile.
4. Runs cargo xtask web to generate upstream/target/web/dist.
5. Packages the generated static site into an NGINX image and publishes it to GHCR.

The Dockerfile expects the generated dist/ folder created by the workflow. The repository is primarily intended as an automated image-build and publication pipeline; the normal way to consume it is to pull the published image.

Upstream project and attribution

• FilmCraft source code: storytold/filmcraft
• FilmCraft web build instructions: docs/web.md
• FilmCraft contribution and font-build instructions: docs/contributing.md
• Shared font assets: storytold/craft-fonts
• Official releases: FilmCraft releases

FilmCraft is open source and is dual-licensed under the MIT License or Apache License 2.0, at the user's option. Fonts included from craft-fonts have their own licenses and attribution notices; consult the upstream repositories for details. FilmCraft names, artwork and logos remain subject to the upstream project's trademark and usage terms.

The license for the upstream application does not automatically determine the license of the packaging files maintained in this repository. Select and include a separate LICENSE for this repository's own files before publishing if you want to grant reuse rights.