Skip to content

Brick Work 1.0.1

Choose a tag to compare

@toni-dev-bot toni-dev-bot released this 10 Nov 16:44
Immutable release. Only release title and notes can be modified.
1c6fcd5

A fix release: fresh containers set themselves up on first start and no longer log the gunicorn control-socket error. The schema stays 4.2, so a 1.0.0 collection needs no upgrade step, and going back means starting 1.0.0 on the same file. The published image is ghcr.io/ulef1005/brick-work:1.0.1; a new container no longer needs the console brickwork setup step. Back up brickwork.db and secret.key before you upgrade, as always.

  • Containers set themselves up on first start (#266). A new container creates and seeds its missing collection automatically; existing installs are unchanged and the console brickwork setup step is no longer needed with this version. The new brickwork setup --if-missing flag skips any existing collection file.
  • No control server error at container start (#265). Gunicorn runs with its unused control socket disabled, removing the "Control server error" permission-denied line.
  • Facts for AI assistants. The Pages site now serves /llms.txt (the llmstxt.org convention), built by scripts/build_site.py from scripts/site/llms.md: what Brick Work is and is not for, requirements, install, data, keys, imports, API and MCP, what it contacts, with the release's version filled in and links to the docs as raw Markdown. The README has a short For AI assistants section that points to it. tests/test_llms_txt.py checks that every linked file exists and every placeholder is filled.
  • What it contacts names the picture downloads. The README's What it contacts now says that pictures of the items you add come from BrickLink and Rebrickable as plain downloads, with no key, as the note under its screenshots already did.
  • A video tour. A 1:36 walkthrough on YouTube (watch) shows the collection, Set Inspector, Part Runner and Matchmaker on the demo's invented collection, with a chapter card and captions for each. The README's link bar and its demo line link it, and the landing page has a Watch the tour button beside Try the demo. Its opening and closing scenes are generated with Google Veo, as the video and its description say.
  • Set cards show each copy's status again (#258). On Collection › Sets every card said Not checked, also for a copy that is complete, incomplete or sealed; the filter chips above the list were right. The card read the status in a form the list stopped sending with the 4.0 data model (0.6.0). It now shows Complete, Incomplete, Sealed or Not checked for each copy, one pill per status when a set has several copies.
  • Install on your computer with Docker Desktop. A new how-to, Install on your computer with Docker Desktop, takes a Windows or Mac user without a server or Git from installing Docker Desktop to the first sign-in: a folder, two files (compose.yaml of the release and data/.env with the password), three commands, and what to do when a step fails. Tested on macOS with Docker Desktop 4.75; Windows is not tested yet. The README's install section and the Pages landing page link it.
  • The README says who it is for on its first screen. The paragraph under the tagline now says who Brick Work is for, how it relates to Rebrickable and Brickset, and which sites and apps it brings a collection over from. The paragraph on the database files and ids it replaces moved, unchanged, to Works with the sites you already use.
  • Discussions with forms. The repository's Discussions are on, and three categories have their own form in .github/DISCUSSION_TEMPLATE/: Show and tell (your collection, where it runs, what you use, where you came from, what got in the way), Q&A (question, version, where it runs, what you tried) and Ideas (the job, which kind of collector, how you do it today; a clear idea becomes an enhancement issue). Each asks you to leave out personal data.
  • A social preview picture. docs/img/social/social-preview-1280x640.png is the picture GitHub shows when the repository link is shared: the lockup, the lead line and the README's Sets and Part Runner captures on the invented collection.
  • The install steps follow the release. tests/test_install_docs.py fails when the README's or the landing page's git clone --branch, or the Docker Desktop guide's compose.yaml link, names another version than brickwork/version.py, so a release commit bumps them with the image tag.
  • The check job runs in about a third of the time (#254). The tests run in parallel (pytest -n auto --dist loadgroup, pytest-xdist; the Chrome and screen-gate tests share one group), the screen gate runs on its own after them in one Chrome session, as its baselines were made, and a pull request that changes only documentation runs the docs check and the site build instead of the whole gate (scripts/check_scope.py). The standalone smoke test no longer runs twice. No test was removed or loosened; ADR 0024 has the numbers.