Installation

If you want to install binaries, see below. If you want to check out the source and build it yourself, please see the Development wiki page.

AWS

See the AWS ECS page for how to create a running Faktory service useable by any app deployed to AWS.

Render.com

If you are deploying your app to Render.com, you can quickly create a private Faktory service using this repository.

Linux

Faktory RPM/DEB binary packages are available at the releases page. They work with any 64-bit Linux using systemd. Install them like so:

# DEB distros like Ubuntu
dpkg -i <filename.deb>
# RPM distros like CentOS
yum install <filename.rpm>

macOS

> brew install contribsys/faktory/faktory
[2 minutes pass]
> faktory

Docker

A Docker image is available here: https://hub.docker.com/r/contribsys/faktory/.

docker pull contribsys/faktory

In production, you'll want to use a persistent volume so Docker doesn't clear your data when restarting the container. Decide where you want your Faktory database stored and map that into the Docker image when running the container. Here we create a ./data directory and then start Faktory.

mkdir data
docker run --rm -it \
  -v ./data:/var/lib/faktory/db \
  -e "FAKTORY_PASSWORD=some_password" \
  -p 127.0.0.1:7419:7419 \
  -p 127.0.0.1:7420:7420 \
  contribsys/faktory:latest \
  /faktory -b :7419 -w :7420 -e production

Faktory will create ./data/faktory.rdb with your persistent job data. You may wish to make regular backups of that file.

You can choose not to use a persistent volume so your job database will start empty on every Faktory restart, useful in development:

docker run --rm -it \
  -p 127.0.0.1:7419:7419 \
  -p 127.0.0.1:7420:7420 \
  contribsys/faktory:latest

Now visit http://localhost:7420/ in your browser to view the web dashboard. Note that Docker for Mac has a 2-3x performance penalty over running Faktory directly but it'll still handle 1000+ jobs/sec. Linux performance should be normal.