# BrickTracker

BrickTracker is a self-hosted business & finance app. A web application for organizing and tracking LEGO sets, parts, and minifigures. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/2680/bricktracker

## Description

A web application for organizing and tracking LEGO sets, parts, and minifigures. Uses the Rebrickable API to fetch LEGO data and allows users to track missing pieces and collection status.

## Platform availability

Available on 2 of 10 platforms: Unraid, Any server.

## Links

- Official website: https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker
- Unraid: https://ca.unraid.net/apps/bricktracker-0xtkiwe0rcv2ka?q=BrickTracker
- Documentation: https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker/wiki

## Common questions

### How do I fix permission issues for BrickTracker's .env file when using a mounted data folder?

Check that the host file permissions allow the container to read the mounted data folder, since the configuration is stored in /app/data/.env. You can verify it with docker exec BrickTracker ls -la /app/data/.env.

### What should I check when I see "socket disconnected" on the Add or Bulk add pages?

It may mean the application stopped or was restarted. Confirm that the application is still running and review its logs for errors.

### Can orphaned parts block a BrickTracker database upgrade?

Yes, orphaned parts can block a database upgrade. The repository includes a fix for this in the legacy compose setup.

### Where does BrickTracker get building instructions from?

It scrapes LEGO.com for building instructions instead of using Rebrickable.

### Can BrickTracker track missing and damaged parts across multiple sets?

Yes, it tracks individual parts, missing pieces, and damaged components across your sets collection.

---
Source: Our Local Host (https://ourlocalhost.com/app/2680/bricktracker), the self-hosted and open-source app directory.
