Installation help
Install OpenConstructionERP
Pick how you want to run it, follow the numbered steps, and if anything looks wrong, find the message you see in the problem list below. None of the warnings during installation put your projects at risk.
Not sure which one you need?
- You use Windows 10 or 11Windows installer (.exe)
- You have a Mac with an M1, M2, M3 or M4 chipmacOS (.dmg, Apple Silicon)
- You have an Intel Macpip or Docker (there is no Intel Mac app)
- You use Ubuntu, Debian or Linux MintLinux .deb
- You use Fedora, RHEL or Rocky LinuxLinux .rpm
- You use another Linux distributionLinux AppImage
- You already have Python 3.12 or newer, or you want it on a serverpip
- You run Docker, or you set it up for a teamDocker
Watch first
How to install OpenConstructionERP
Video walkthrough on Windows, recorded with version 17.7.1. Some screens look different in 18.5, and the waiting time during installation is shortened in the video.
Windows
- 1
Download
OpenConstructionERP_18.5.0_x64-setup.exefrom the release page.You seeA file of about 800 MB in your Downloads folder.
- 2
Double-click it. If a blue window says "Windows protected your PC", click More info, check that the file name starts with OpenConstructionERP, then click Run anyway.
You seeWindows asks for administrator permission. Click Yes.
- 3
Choose the installer language, accept the licence and keep the suggested folder
C:\Program Files\OpenConstructionERP.You seeA progress bar, then a Finish page.
- 4
Click Finish, or start OpenConstructionERP from the Start menu.
You seeA loading screen "Starting the application" with a checklist: starting the backend, starting the local database, preparing the database, starting the application server, opening the app.
- 5
Wait on the very first start. Do not close the window.
You see"First run sets up your local database. This can take a minute or two, please wait." Later starts are much faster.
- 6
Choose how to open it: as an app window (recommended) or in your normal browser.
You see"How would you like to open OpenConstructionERP?" and then the sign-in page.
- 7
Sign in with the demo account: email demo@openconstructionerp.com, password DemoPass1234!. You can create your own account and projects from there.
You seeThe app. The demo projects are created in the background on the first start, so the project list can say they are on their way for a short moment.
- 8
On a fresh installation the administrator is asked once which modules you will use. Tick what you need and continue. You can change it later with the Background services button in the top bar.
You seeA one-time list of modules with the memory they need.
If you see a message
InstallA blue window "Windows protected your PC".
It means The installer is not code signed yet, so Windows does not know the publisher. It is a warning, not a virus finding.
Do Click More info, check the file name starts with OpenConstructionERP, then click Run anyway.
InstallSmart App Control blocked the app, with no button to continue.
It means Windows 11 Smart App Control refuses unsigned programs.
Do Smart App Control cannot allow a single app. To keep it on, run OpenConstructionERP with Docker Desktop or in WSL (Microsoft's built-in Linux), which Smart App Control does not check. Step-by-step instructions: docs/desktop/WINDOWS_BLOCKED.md in the repository.
Install"Please choose an installation folder whose path uses only Latin letters, digits and spaces. The built-in database cannot start from a folder with other characters in its path"
It means The folder you picked has Cyrillic, Chinese, accented or other non-Latin letters in its path.
Do Keep the suggested C:\Program Files\OpenConstructionERP, or pick a folder like C:\OpenConstructionERP. A silent install (/S) exits with code 3 and writes the reason to %TEMP%\OpenConstructionERP-install-error.log.
InstallThe installer stops with an error about WebView2.
It means Windows refused to install Microsoft WebView2, the component that draws the app window. It is included in the installer, so no internet is needed; the failure comes from Windows itself (policy, a pending update, or a damaged earlier WebView2).
Do Restart the computer and run the installer again. If it fails again, install "Microsoft Edge WebView2 Runtime" from Microsoft, then run our installer once more.
InstallYour antivirus deletes or quarantines a file during installation or on first start.
It means The program is new and unsigned, and some antivirus products are suspicious of that.
Do Restore the file from quarantine and add these two folders as exclusions: the program folder C:\Program Files\OpenConstructionERP and your data folder C:\Users\<your name>\.openestimate. Then run the installer again over the existing installation. If you are not sure the file is genuine, write to us first.
UpgradeA screen asking whether to write over the installed version or remove it first, with a line suggesting to remove it.
Do Keep the option that is already selected (write over it). Your projects are kept. The first start after an upgrade can take longer while the database updates itself.
UpgradeYou also run OpenConstructionERP from pip or a terminal on the same computer, and it stops during the upgrade.
It means Both use the same .openestimate folder and database. The installer stops that database to replace the program. When upgrading from 18.4.0, the old uninstaller also closes any program named openconstructionerp.exe.
Do Stop the terminal version (Ctrl+C) before installing or upgrading and start it again afterwards.
StartThe loading screen stays for a minute or more on the very first start.
It means The app is creating its local database. This happens once.
Do Wait and do not close the window. On a slow or nearly full disk it can take longer. Later starts are fast.
StartA box "OpenConstructionERP failed to start" that names a log file.
It means The app could not open its window at all.
Do Start it once more. If the box comes back, send us the log file it names.
Start"The backend started, but the local database is not answering, so the app cannot open."
It means The local database did not come up, often after a run that did not close cleanly.
Do Restart the computer and start the app again. If it repeats, send us desktop-launcher.log and the database log (see Logs).
Start"The backend started, but this installation is missing the application files it serves"
It means Part of the program folder is missing, usually removed by antivirus.
Do Check your antivirus quarantine, then run the installer again over the existing installation. Your projects are not touched.
Start"The application backend did not start in time", or "The application backend stopped responding while preparing the local database" (or another step).
It means The start took longer than the app waits. The message names the step it was on.
Do Close the window and start again. Free some disk space first if the disk is nearly full. If it stops at the same step again, send us desktop-launcher.log.
Start"The drive ran out of space while the application was starting" or "There is not enough free space to start the application".
It means Exactly that. The message names the folder and the free space left.
Do Free space on that drive and start again.
StartA message that the folder for the local database "sits too deep in the filesystem", with two numbers.
It means Windows limits path length and your data folder path is too long for the database files. Switching on long paths in Windows does not help.
Do Set the user environment variable OE_DATA_DIR to a short path such as C:\OpenConstructionERP\data (Start, type "environment variables", Edit environment variables for your account, New), then start again.
StartYour Windows user name has non-Latin letters (for example Cyrillic or Chinese) and you look for your database.
It means The built-in database cannot run from such a path, so since 18.5.0 the app keeps the database in C:\ProgramData\OpenConstructionERP\clusters\<id>\pgdata. Before 18.5.0 the app could not start at all for such accounts.
Do Nothing to fix. The file pgdata.location in your .openestimate folder names the exact database folder. For backups copy both folders.
Running"The application backend stopped, restarting" and the window reloads.
It means The background part of the app stopped unexpectedly and the app restarted it. Saved work is kept. It does this at most twice in 30 minutes.
Do Carry on. If it repeats, or you see "The application backend has stopped", send us desktop-launcher.log and logs/backend-crash.log.
StartEvery time you start the app you are signed out and the language is back to English.
It means Another program uses port 8732, the port the app normally uses. Version 18.5.0 then picks a random free port on each start, and the window treats every new port as a new site, so the sign-in and the language are not found.
Do Close or reconfigure the other program that uses port 8732 (on Windows, run netstat -ano | findstr :8732 in a terminal to see its process ID). Your projects are not affected, only the sign-in and the language choice.
StartYou worry the app conflicts with a PostgreSQL you already run on port 5432.
It means It does not. The built-in database on Windows takes a random free local port, and on macOS and Linux it listens on a local socket only, not on a TCP port.
Do Nothing to do.
Where the logs are
desktop-launcher.logC:\Users\<your name>\.openestimate\desktop-launcher.logEverything the desktop app did while starting. Always in your home folder, even if you moved the data folder.backend-crash.logC:\Users\<your name>\.openestimate\logs\backend-crash.logDetails of an unexpected stop. Lives in the data folder, so it moves withOE_DATA_DIR.database log folderC:\Users\<your name>\.openestimate\pgdata\log (or <folder frompgdata.location>\log)Why the built-in database did not start.OpenConstructionERP-install-error.log%TEMP%\OpenConstructionERP-install-error.log(type%TEMP%in the Explorer address bar)Why the Windows installer refused the install folder.
To open the folder, paste this into the Explorer address bar:
%USERPROFILE%\.openestimatemacOS
- 1
Download
OpenConstructionERP_18.5.0_aarch64.dmgand open it.You seeA window with the OpenConstructionERP app icon.
- 2
Drag OpenConstructionERP into Applications.
You seeThe app appears in your Applications folder.
- 3
Open Terminal once and run.
xattr -dr com.apple.quarantine /Applications/OpenConstructionERP.appYou seeNo output. That is correct. This clears the download mark, because the app is not notarized by Apple yet.
- 4
Open OpenConstructionERP from Applications.
You seeThe loading screen "Starting the application". The first start sets up the local database and takes a minute or two.
- 5
Choose app window or browser.
You seeThe sign-in page.
- 6
Sign in with the demo account: email demo@openconstructionerp.com, password DemoPass1234!. You can create your own account and projects from there.
You seeThe app. The demo projects are created in the background on the first start, so the project list can say they are on their way for a short moment.
- 7
On a fresh installation the administrator is asked once which modules you will use. Tick what you need and continue. You can change it later with the Background services button in the top bar.
You seeA one-time list of modules with the memory they need.
If you see a message
StartThe loading screen stays for a minute or more on the very first start.
It means The app is creating its local database. This happens once.
Do Wait and do not close the window. On a slow or nearly full disk it can take longer. Later starts are fast.
Start"The backend started, but the local database is not answering, so the app cannot open."
It means The local database did not come up, often after a run that did not close cleanly.
Do Restart the computer and start the app again. If it repeats, send us desktop-launcher.log and the database log (see Logs).
Start"The backend started, but this installation is missing the application files it serves"
It means Part of the program folder is missing, usually removed by antivirus.
Do Check your antivirus quarantine, then run the installer again over the existing installation. Your projects are not touched.
Start"The application backend did not start in time", or "The application backend stopped responding while preparing the local database" (or another step).
It means The start took longer than the app waits. The message names the step it was on.
Do Close the window and start again. Free some disk space first if the disk is nearly full. If it stops at the same step again, send us desktop-launcher.log.
Start"The application never finished unpacking itself, so its backend never started." or "The application could not unpack itself into the temporary folder it uses."
It means On macOS and Linux the app unpacks its backend on every start. A slow or full drive, or antivirus locking the files, stops that. (The Windows app no longer unpacks itself since 18.5.)
Do Free space on the drive with your temporary folder, or allow the app in your antivirus, then start again.
Start"The drive ran out of space while the application was starting" or "There is not enough free space to start the application".
It means Exactly that. The message names the folder and the free space left.
Do Free space on that drive and start again.
Running"The application backend stopped, restarting" and the window reloads.
It means The background part of the app stopped unexpectedly and the app restarted it. Saved work is kept. It does this at most twice in 30 minutes.
Do Carry on. If it repeats, or you see "The application backend has stopped", send us desktop-launcher.log and logs/backend-crash.log.
StartEvery time you start the app you are signed out and the language is back to English.
It means Another program uses port 8732, the port the app normally uses. Version 18.5.0 then picks a random free port on each start, and the window treats every new port as a new site, so the sign-in and the language are not found.
Do Close or reconfigure the other program that uses port 8732 (on Windows, run netstat -ano | findstr :8732 in a terminal to see its process ID). Your projects are not affected, only the sign-in and the language choice.
StartYou worry the app conflicts with a PostgreSQL you already run on port 5432.
It means It does not. The built-in database on Windows takes a random free local port, and on macOS and Linux it listens on a local socket only, not on a TCP port.
Do Nothing to do.
Install"OpenConstructionERP is damaged and can't be opened".
It means The app is not notarized by Apple yet and still carries the download mark. The app is not damaged.
Do Only this helps: in Terminal run once xattr -dr com.apple.quarantine /Applications/OpenConstructionERP.app, then open the app normally.
Install"OpenConstructionERP cannot be opened because the developer cannot be verified" (or Apple could not verify it is free of malware).
It means The app is signed ad hoc but not notarized by Apple yet.
Do Run the same xattr command, or open System Settings, Privacy & Security, scroll down and click Open Anyway. You do this only once.
InstallThe app does not run on your Mac at all.
It means The Mac build is for Apple Silicon (M1 and newer) only. There is no Intel build.
Do On an Intel Mac use pip (Python 3.12 or newer) or Docker.
Where the logs are
desktop-launcher.log~/.openestimate/desktop-launcher.logEverything the desktop app did while starting. Always in your home folder, even if you moved the data folder.backend-crash.log~/.openestimate/logs/backend-crash.logDetails of an unexpected stop. Lives in the data folder, so it moves withOE_DATA_DIR.database log folder~/.openestimate/pgdata/logWhy the built-in database did not start.
To open the folder from a terminal:
open ~/.openestimateLinux
Linux: .deb (Ubuntu, Debian, Mint)
- 1
Download
OpenConstructionERP_18.5.0_amd64.deb.You seeA file of about 830 MB.
- 2
In a terminal in the download folder run.
sudo apt install ./OpenConstructionERP_18.5.0_amd64.debYou seeapt lists the package and any libraries it needs, then installs them. The ./ in front of the file name matters.
- 3
Start OpenConstructionERP from your applications menu.
You seeThe loading screen. The first start takes a minute or two.
- 4
Sign in with the demo account: email demo@openconstructionerp.com, password DemoPass1234!. You can create your own account and projects from there.
You seeThe app. The demo projects are created in the background on the first start, so the project list can say they are on their way for a short moment.
- 5
On a fresh installation the administrator is asked once which modules you will use. Tick what you need and continue. You can change it later with the Background services button in the top bar.
You seeA one-time list of modules with the memory they need.
Linux: .rpm (Fedora, RHEL, Rocky)
- 1
Download
OpenConstructionERP-18.5.0-1.x86_64.rpm.You seeA file of about 850 MB.
- 2
Run.
sudo dnf install ./OpenConstructionERP-18.5.0-1.x86_64.rpmYou seednf resolves dependencies and installs.
- 3
Start OpenConstructionERP from your applications menu.
You seeThe loading screen. The first start takes a minute or two.
- 4
Sign in with the demo account: email demo@openconstructionerp.com, password DemoPass1234!. You can create your own account and projects from there.
You seeThe app. The demo projects are created in the background on the first start, so the project list can say they are on their way for a short moment.
- 5
On a fresh installation the administrator is asked once which modules you will use. Tick what you need and continue. You can change it later with the Background services button in the top bar.
You seeA one-time list of modules with the memory they need.
Linux: AppImage (any distribution)
- 1
Download
OpenConstructionERP_18.5.0_amd64.AppImage.You seeA file of about 910 MB.
- 2
Make it executable.
chmod +x OpenConstructionERP_18.5.0_amd64.AppImageYou seeNo output.
- 3
Run it.
./OpenConstructionERP_18.5.0_amd64.AppImageYou seeThe loading screen. The first start takes a minute or two.
- 4
Sign in with the demo account: email demo@openconstructionerp.com, password DemoPass1234!. You can create your own account and projects from there.
You seeThe app. The demo projects are created in the background on the first start, so the project list can say they are on their way for a short moment.
- 5
On a fresh installation the administrator is asked once which modules you will use. Tick what you need and continue. You can change it later with the Background services button in the top bar.
You seeA one-time list of modules with the memory they need.
If you see a message
StartThe loading screen stays for a minute or more on the very first start.
It means The app is creating its local database. This happens once.
Do Wait and do not close the window. On a slow or nearly full disk it can take longer. Later starts are fast.
Start"The backend started, but the local database is not answering, so the app cannot open."
It means The local database did not come up, often after a run that did not close cleanly.
Do Restart the computer and start the app again. If it repeats, send us desktop-launcher.log and the database log (see Logs).
Start"The backend started, but this installation is missing the application files it serves"
It means Part of the program folder is missing, usually removed by antivirus.
Do Check your antivirus quarantine, then run the installer again over the existing installation. Your projects are not touched.
Start"The application backend did not start in time", or "The application backend stopped responding while preparing the local database" (or another step).
It means The start took longer than the app waits. The message names the step it was on.
Do Close the window and start again. Free some disk space first if the disk is nearly full. If it stops at the same step again, send us desktop-launcher.log.
Start"The application never finished unpacking itself, so its backend never started." or "The application could not unpack itself into the temporary folder it uses."
It means On macOS and Linux the app unpacks its backend on every start. A slow or full drive, or antivirus locking the files, stops that. (The Windows app no longer unpacks itself since 18.5.)
Do Free space on the drive with your temporary folder, or allow the app in your antivirus, then start again.
Start"The drive ran out of space while the application was starting" or "There is not enough free space to start the application".
It means Exactly that. The message names the folder and the free space left.
Do Free space on that drive and start again.
Running"The application backend stopped, restarting" and the window reloads.
It means The background part of the app stopped unexpectedly and the app restarted it. Saved work is kept. It does this at most twice in 30 minutes.
Do Carry on. If it repeats, or you see "The application backend has stopped", send us desktop-launcher.log and logs/backend-crash.log.
StartEvery time you start the app you are signed out and the language is back to English.
It means Another program uses port 8732, the port the app normally uses. Version 18.5.0 then picks a random free port on each start, and the window treats every new port as a new site, so the sign-in and the language are not found.
Do Close or reconfigure the other program that uses port 8732 (on Windows, run netstat -ano | findstr :8732 in a terminal to see its process ID). Your projects are not affected, only the sign-in and the language choice.
StartYou worry the app conflicts with a PostgreSQL you already run on port 5432.
It means It does not. The built-in database on Windows takes a random free local port, and on macOS and Linux it listens on a local socket only, not on a TCP port.
Do Nothing to do.
InstallThe .deb asks for libwebkit2gtk-4.1-0, or dpkg reports unmet dependencies.
It means The app needs WebKitGTK 4.1 to draw its window. dpkg -i does not install dependencies.
Do Install with sudo apt install ./OpenConstructionERP_18.5.0_amd64.deb, which pulls the library in. If your distribution has no libwebkit2gtk-4.1-0 (Ubuntu older than 22.04, Debian older than 12), use pip.
InstallThe AppImage does nothing when you double-click it.
It means The file is not marked as a program yet.
Do Run chmod +x OpenConstructionERP_18.5.0_amd64.AppImage and start it again.
InstallAn AppImage error that mentions FUSE or libfuse.so.2.
It means Newer distributions no longer install the FUSE 2 library that AppImages use.
Do Install it (sudo apt install libfuse2, on Ubuntu 24.04 sudo apt install libfuse2t64), or use the .deb, .rpm or pip.
Where the logs are
desktop-launcher.log~/.openestimate/desktop-launcher.logEverything the desktop app did while starting. Always in your home folder, even if you moved the data folder.backend-crash.log~/.openestimate/logs/backend-crash.logDetails of an unexpected stop. Lives in the data folder, so it moves withOE_DATA_DIR.database log folder~/.openestimate/pgdata/logWhy the built-in database did not start.
To open the folder from a terminal:
xdg-open ~/.openestimatepip
- 1
Run.
pip install --upgrade openconstructionerpYou seepip downloads the package and its dependencies.
- 2
Run.
openconstructionerpYou seeA short welcome. On the first run it asks whether to load the demo projects and whether to open your browser.
- 3
Wait while it sets up the local database.
You see"Database: embedded PostgreSQL 16 (no Docker)" and then the server starts. Your browser opens http://127.0.0.1:8080 (the same as http://localhost:8080).
- 4
Sign in. With demo data you can use demo@openconstructionerp.com / DemoPass1234!
You seeThe dashboard.
- 5
On a fresh installation the administrator is asked once which modules you will use. Tick what you need and continue. You can change it later with the Background services button in the top bar.
You seeA one-time list of modules with the memory they need.
- 6
To stop, press Ctrl+C in the terminal. Next time just run openconstructionerp again.
You seeThe server stops. Your data stays in the
.openestimatefolder in your home folder.
Useful commands
The command openconstructionerp is not found
python -m openconstructionerpSomething does not work: checks Python, the port, the data folder and the database and says what to do
openconstructionerp doctorPort 8080 is taken by another program
openconstructionerp serve --port 8081Other computers on your network should reach it
openconstructionerp serve --host 0.0.0.0 --port 8080You need to tell us your version
openconstructionerp --versionIf you see a message
Installpip says no matching distribution was found, or that it requires a different Python.
It means OpenConstructionERP needs Python 3.12 or newer.
Do Install Python 3.12 or newer and run python3.12 -m pip install --upgrade openconstructionerp (on Windows: py -3.12 -m pip install --upgrade openconstructionerp).
Installerror: externally-managed-environment (Ubuntu 23.04+, Debian 12+).
It means The system Python does not allow pip to install into it.
Do Use pipx install openconstructionerp, or create a virtual environment first: python3 -m venv ~/oe && ~/oe/bin/pip install openconstructionerp.
Start"openconstructionerp" is not recognized, or command not found.
It means The folder where pip puts commands is not on your PATH (common on Windows).
Do Run python -m openconstructionerp instead. It works on every system without touching PATH.
Start"Port 8080 is already in use. Try: openconstructionerp serve --port 8081"
It means Another program uses port 8080.
Do Run the suggested command and open the address it prints.
Start"Embedded PostgreSQL could not start".
It means The built-in database failed to start. The message prints the path of its log.
Do Run openconstructionerp doctor. If that does not help, reinstall with pip install --upgrade --force-reinstall openconstructionerp and send us the log it names.
Where the logs are
terminal outputthe terminal window (pip);docker compose logs app(Docker)For pip and Docker, copy what the terminal printed and the output ofopenconstructionerp doctor.
Docker
- 1
In an empty folder, download the two compose files.
curl -fsSL https://raw.githubusercontent.com/datadrivenconstruction/OpenConstructionERP/main/docker-compose.quickstart.yml -o docker-compose.ymlcurl -fsSL https://raw.githubusercontent.com/datadrivenconstruction/OpenConstructionERP/main/docker-compose.quickstart.image.yml -o docker-compose.override.ymlYou seeTwo files in the folder.
- 2
Create the secrets file once.
echo "POSTGRES_PASSWORD=$(openssl rand -base64 24)" > .envecho "JWT_SECRET=$(openssl rand -hex 32)" >> .envYou seeA
.envfile. Keep it: it holds the database password and the sign-in secret. - 3
Start it.
docker compose pull app && docker compose up -dYou seeTwo containers start: postgres and app.
- 4
Open http://localhost:8080 and sign in with demo@openconstructionerp.com / DemoPass1234!
You seeThe sign-in page. The first start can take a minute while the database is prepared.
- 5
On a fresh installation the administrator is asked once which modules you will use. Tick what you need and continue. You can change it later with the Background services button in the top bar.
You seeA one-time list of modules with the memory they need.
Useful commands
Check that both containers run and are healthy
docker compose psSee why the app does not start
docker compose logs appPort 8080 on your machine is taken
OE_PORT=8081 OE_ALLOWED_ORIGINS=http://localhost:8081 docker compose up -dThis compose setup is for evaluation and local use. For a production server see docs/INSTALL_LINUX.md and docker-compose.prod.yml in the repository.
If you see a message
StartCompose stops with "POSTGRES_PASSWORD must be set" or "JWT_SECRET must be set".
It means The .env file with the two secrets is missing or not in the same folder.
Do Create the .env file as in step 2, in the folder with docker-compose.yml.
Starthttp://localhost:8080 does not open.
It means The container is not running yet, or port 8080 is taken.
Do Run docker compose ps and docker compose logs app. To use another port: OE_PORT=8081 OE_ALLOWED_ORIGINS=http://localhost:8081 docker compose up -d, then open http://localhost:8081.
InstallOn an Apple Silicon Mac or another ARM machine, Docker warns that the image platform linux/amd64 does not match, or the app runs very slowly.
It means The published image is built for x86-64 only.
Do Build from source with make quickstart, or use pip.
Where the logs are
terminal outputthe terminal window (pip);docker compose logs app(Docker)For pip and Docker, copy what the terminal printed and the output ofopenconstructionerp doctor.
Your data, upgrades and uninstall
- Windows
C:\Users\<your name>\.openestimatePlusC:\ProgramData\OpenConstructionERP\clusters\<id>\pgdataif your user name has non-Latin letters;pgdata.locationnames it. - macOS~/
.openestimate(hidden; press Cmd+Shift+. in Finder) - Linux~/
.openestimate - pip~/
.openestimate, the same folder as the desktop app, unless you pass--data-diror setOE_DATA_DIR - Dockerthe Docker volumes <folder>_pg_data (database) and <folder>_app_data (files), where <folder> is the name of the folder with
docker-compose.yml
Upgrade
Install the new version over the old one. Your .openestimate folder is not part of the program, so projects, users and settings stay. The first start after an upgrade can take longer while the database updates itself.
Uninstall
Uninstalling removes the program and keeps your projects. On Windows the uninstaller offers "Delete the application data": that removes only the app window's stored sign-in and language (in %APPDATA% and %LOCALAPPDATA%\io.openconstructionerp.desktop), not your projects. To start from scratch, uninstall, copy .openestimate somewhere safe, then delete it.
Backup
Close the app and copy the .openestimate folder (and the ProgramData folder named in pgdata.location, if there is one).
Still stuck? We will help
Please include:
- the version (it is in the name of the file you downloaded; pip:
openconstructionerp --version; Docker: the image tag) and how you installed (Windows installer, .dmg, .deb, .rpm, AppImage, pip or Docker) - your system (Windows: Start, type
winver; macOS: Apple menu, About This Mac; Linux: the distribution and version) - the exact text of the message, or a screenshot
- the log files listed above
Log files can contain your user name and folder names. Look through them before posting publicly; send them by email if you prefer.
Next steps after installing
The full text is also on GitHub in English, Deutsch and Русский.