About me
CV
Blog
Startups
BlogMarch 29, 2026

How to run IronValet with Docker or build it locally

A practical walkthrough of the documented setup paths behind IronValet / IRONVAULT.
SeyedAli Emami
How to run IronValet with Docker or build it locally

The two main paths

From the project documentation, IronValet / IRONVAULT supports two very practical ways to get started:
  1. local bootstrap + Flask runtime
  2. Docker-based deployment
There is also a third useful option: building a portable Windows package for delivery. IronValet login screen

Path 1: run it locally

This is the best path when you want to work directly with the project, test changes, or understand the setup flow in a more transparent way.

Install dependencies

Run the bootstrap wizard

The documentation describes start.py as the initial setup step. It prepares folders, the environment file, and database-related setup.

Start the Flask app

After bootstrap, the documented runtime flow is straightforward: That makes local iteration easy while preserving the setup logic in a dedicated first-run script.

Path 2: run it with Docker

IronValet vault list view This is the stronger option when you want a cleaner deployment model or a more production-oriented runtime.

Prepare the environment file

If .env does not exist yet, start from the example file and then replace the placeholder values with real secrets. The documentation specifically calls out values such as:
  • SECRET_KEY
  • DATABASE_URL
  • VAULT_ENCRYPTION_KEY
  • SECURE_COOKIES
and explains that the SQLite URL is intentionally kept relative for portability.

Build and start the containers

Check logs

Create the initial admin account

If the admin does not exist yet, the documented command is:

Portable Windows delivery path

There is also a delivery-focused path for Windows environments where a self-contained package is more convenient than a Python-based runtime. The documented output folder is:

Important deployment notes

Backup and persistence

The documented persistent paths are:
  • ./instance/ironvault.db
  • ./uploads/
  • .env
That is a good backup boundary because it captures both the application data and the secrets/configuration needed to restore the environment.

Final thought

What I like about this setup is that it gives you a clean answer whether you want to:
  • develop locally,
  • deploy with Docker,
  • or hand over a portable Windows package.
That flexibility is exactly what makes the project feel operationally mature.
Back to the IronValet project page
Share this post:

Recent posts

Thumbnail of Hummmm... Here We Go Again :))
SeyedAli Emami
August 17, 2026
Personal ProjectsHummmm... Here We Go Again :))Two personal projects, a lot of curiosity, and the small decision to share the process while it is still unfolding.I am spending this stretch of time building two personal projects: a simple money-management app and Nexa, an IoT system for rooms. Here is what I want to explore, share, and learn along the way.
Read article
Thumbnail of When No One Is Listening: Notes from an Internet Rights Meeting
SeyedAli Emami
August 17, 2026
Iran / Digital RightsWhen No One Is Listening: Notes from an Internet Rights MeetingI was in the room, but I chose not to speak. Sometimes the absence of a listener says more than another speech ever could.A personal account of attending a meeting about internet restrictions in Iran, the arguments around shutdowns and tiered access, and why I stayed silent when the people with the power to respond were not there.
Read article