Skip to content

NodePit/runner

Repository files navigation

NodePit Runner – Workflows Around the Clock!


NodePit Runner is the perfect complement to the KNIME Analytics Platform and allows you to deploy, execute and monitor your KNIME workflows in the cloud or on-premises as easy as running them locally. Get more information on features, pricing and how to start your free trial period on NodePit.

⏱️ Get Started in 60 Seconds

Docker and Docker Compose is the simplest way to run NodePit Runner on a single server or local machine.

  1. Install Docker and Docker Compose
  2. Download the docker-compose.yml file (right click the link and “Save as” to an arbitrary location on your computer)
  3. Open a terminal and change to the directory where you saved the docker-compose.yml file
  4. Start NodePit Runner with docker compose up -d
  5. Open your browser and navigate to http://localhost:8080 and follow the instructions to create your initial admin account

For configuration options (public URL, secrets, scaling executors, …) and everything else, see Installation and Configuration in the docs.

To upgrade an already running instance, run docker compose pull followed by docker compose up -d. Database migrations happen automatically.

📚 Documentation

The full manual — installation, configuration, guides and the API reference — lives at docs.nodepit.com/runner.

🧩 Extensions

The extensions/ directory has optional add-ons, each a self-contained Compose file you layer on top of docker-compose.yml with -f. Some need their own settings — copy .env.example to .env (next to docker-compose.yml) and fill in what’s needed:

  • extensions/nginx — HTTPS reverse proxy with automatic Let’s Encrypt certificates.
  • extensions/watchtower — automatically pulls and restarts containers when new images are released.
  • extensions/backup — daily database and workflow-data backups, stored locally and optionally shipped to an S3-compatible bucket.
  • extensions/portainer — a web UI for managing the Docker stack without the CLI.

Mix and match as needed, for example:

docker compose \
  -f docker-compose.yml \
  -f extensions/nginx/docker-compose.yml \
  -f extensions/watchtower/docker-compose.yml \
  up -d

🤗 Get Involved

Unsure if NodePit Runner is for you? Drop us a mail and we answer your questions and even better get you access to our cloud version of NodePit Runner for testing.

  • Give a ⭐️ for this repo
  • Questions? Just drop us a mail

📖 License

NodePit Runner is licensed under the NodePit Runner: Terms and Conditions. By installing and/or using NodePit Runner, you agree and acknowledge the terms and conditions.

🤓 Advanced Topics

Show more

Changing secrets and settings

docker-compose.yml works out of the box with built-in default secrets. To change one — e.g. the shared API key or a public WEB_BASE_URL — clone this repo, copy .env.example to .env, and edit the values there. Because .env is read by every service that needs a given value, you only need to change it in one place.

The MongoDB password is a special case: setting MONGO_ROOT_PASSWORD in .env only takes effect when the database is first initialized, not on a running installation. See Configuration in the docs for how to rotate it safely.

Combining extensions without repeating -f flags

Instead of passing multiple -f flags every time, set COMPOSE_FILE in .env:

COMPOSE_FILE=docker-compose.yml:extensions/nginx/docker-compose.yml:extensions/watchtower/docker-compose.yml

and then just run docker compose up -d.

Vagrant

If you use Vagrant, there’s a Vagrantfile to run a Debian box with Docker preinstalled. Start and connect to the box as follows:

vagrant up
vagrant ssh

The project directory is mounted to /vagrant within the box. From there, you can continue with docker compose up -d


Created by nodepit.com, 2023, 2024, 2025, 2026.

About

NodePit Runner – Workflows Around the Clock! Deploy, execute and monitor your KNIME workflows in the cloud or on-premises as easily as running them locally!

Topics

Resources

Stars

16 stars

Watchers

4 watching

Forks

Packages

 
 
 

Contributors