StaXX 00.02.01_dev20260905 (development)

Development build 00.02.01_dev20260905, off the dev branch.

• The state chips on the main grid are now all the same size. A chip you can click, such as the one offering to find a health check, drew slightly larger than the plain ones beside it.
• The web page button now works for a stack imported from a template onto its own network (a br0-style address) or onto the server's network, where there is no port list to read. Import writes the plain port number into the address, the way the editor's Web page port field does, and a stack imported before this fix gets its button back without a visit to the editor.
• The Storage tab's "Where stacks may live" box is gone. The same choice now sits inside the Data store box as a switch, Protect me from myself: on, the folder picker greys out and refuses places that can lose or hide your stacks; off, it warns and lets you choose. Nothing you had set changes.
• The Container icons setting now shows a row of six sample icons under its dropdown, so you can see the kind of icon it fetches before you decide.

StaXX 00.02.00

00.02.00 — released 2026-09-03

• The shell in the Manage tab is now Unraid's own terminal, the same one the Console button opens, so nano, htop and anything else that draws a full screen work in it. When the shell ends the pane greys out with its last screen still readable, and Reconnect opens a fresh one.

• Put several services back to earlier versions in one go. The Versions tab has a "Put back several at once" mode: choose a version for each service, press once, and the stack is edited, saved to History and recreated in a single step rather than one service at a time.

• A stack outside any folder can now be placed above a folder, and starts in that order at boot. The top level used to draw every folder first, whatever you did.

• Refreshing the page reopens the stack you were editing. The open stack's name rides in the address bar, so a refresh, or a pasted link, lands back in the same editor.

• A log left open in a background tab now checks in every half-minute instead of every second, and catches up the moment you return to it.

• Fixed: the dimmed square shown over a stack's icon while it starts now fits the larger icon in the wide layout instead of sitting in its corner.

• Fixed: pressing "Write each one twice" on the dollar-sign dialog now closes the dialog as well as making the change.

• Fixed: in the wide table the state chips sit flush left under a left-aligned heading rather than floating in the middle of the column.

• The flash-drive copy of a stack now includes its .env file, and the switch that controls those copies is in the settings panel on the Storage tab. A copy restored from the flash drive is a complete definition again, not a compose file whose placeholders point at nothing.

• The page no longer scrolls behind an open dialog. Reaching the end of the editor or the settings panel used to scroll the stacks list underneath; the page now holds still, softly blurred, until the dialog closes.

• Fixed: pressing Discard on the settings panel’s "Discard changes?" question now closes the question as well as the panel.

• Settings can show a picture of what each option looks like. Under a setting's dropdown, a
  small screenshot of each option sits in a row, the chosen one outlined; clicking a picture picks
  that option. It starts with where StaXX appears in the menu.

• The Settings panel was reworked with Adrian's feedback. Each setting now sits in its own
  titled box, with the explanation above the control rather than below it; the Docker menu setting
  gained its own pair of pictures; several settings were reworded for clarity and brevity; Where
  stacks may live moved onto the Storage tab; and the Docker menu setting locks itself off, greyed
  out, while StaXX is shown as a Docker tab, since there is no top-level button for it to replace.
  Related settings now share one box — the update check's schedule, when an update installs itself,
  and Docker Hub sign-in; the "when to install" box folds away unless updates are set to install
  themselves; registries you run yourself are now added one at a time to a list rather than typed as
  a comma-separated line; the update-check figures now show as a table at the end of that tab instead
  of a paragraph part-way through it; and the StaXXCrypt setting now explains, in plain words, what is
  actually inside the little container it builds.

• The address column lists only ports that are actually reachable. It shows the ports Docker is
  forwarding, plus the one port a service's web page answers on. Stacks with their own network
  address, or on host networking, no longer carry a row of internal ports nothing outside can reach.

• The update status now lives at the top of the page, not above the table. Last checked, how
  many updates are waiting, and how many author-example findings there are now show as small tags
  next to "StaXX" — at the right end of the title bar when the page has one of its own, in Unraid's
  shared tab strip when its tabbed view is on and StaXX has none, and otherwise on their own line
  above the buttons. The explanatory paragraph that used to sit above the table is gone — the
  store's location is already on the Settings page — and the table now starts a little higher, so
  one more row fits on screen.

• On a tablet-sized window, the stack list is now a grid of cards instead of a squeezed table.
  Each stack gets its own card — icon, name, state, address and its little graphs, three across —
  and a folder becomes a heading above its own row of cards. A stack running several services shows
  a cubes button in its corner; tap it to see those services as cards of their own, without the page
  underneath changing shape.

• The stack table reads better on a wide screen. Ports now stand in their own column beside the
  address instead of running on in one long line; a stopped stack's dash lines up under its column
  heading instead of sitting off to one side; the line under the column headings is now one
  unbroken rule instead of breaking into pieces; stack rows are a little taller, with a bigger icon
  and bigger WebUI/Logs/Repo/CA buttons that are easier to click; and an update pill now always
  reads "update ready", with a small tag icon showing when it also knows exactly which version —
  hover it to see both.

• Hovering an update pill now shows a small card in the page's own style instead of the browser's
  plain tooltip. The running and available versions, when it was last checked, when it is next
  due and why it is checked as often as it is now lay out as a short table instead of one long
  sentence. An image whose first check already found an update pending — Radarr was the one that
  gave this away — now shows its running version too, read straight off the container rather than
  left blank.

• The page no longer grows a second scrollbar of its own. Collapsing a stack or a folder was
  leaving a sliver of invisible extra room on the page, on top of your browser's own scrollbar —
  fixed at the source, so both scroll the same amount again.

• Tidy no longer refuses a file over the commented example StaXX itself writes into it. A
  trailing note indented under a setting now travels with that setting instead of being treated as
  a stray line — so a freshly scaffolded stack tidies cleanly instead of being refused outright. Its
  result is also shown as a proper notice above the file, not just on the small status line below it.

• An image you haven't downloaded yet is no longer asked about at update checks. There was
  nothing on your server to compare a registry's answer against, so the question was always wasted —
  it is now skipped, and asked promptly as soon as the image is actually here.

• Checking for updates no longer spends any of your Docker Hub allowance. It asks for a build's
  headers only, which Hub does not count — the allowance is only spent when you actually install an
  update.

• Checking now runs every hour, asking only the images that are due, with a full look at every
  image at the time you chose. Choosing "Once a week" used to mean each image was only asked about
  weekly; it now means the once-a-week full look happens then, while how often any one image is
  actually asked is still decided by how often it tends to change.

• The settings panel now shows what each registry has actually been asked, and what it cost —
  under Image updates, next to the check schedule. Being refused by Docker Hub now means something
  else on your address spent the download allowance, since a check itself costs nothing, and StaXX
  tries again within the hour rather than waiting for the next pass; the refusal notice on the stacks
  page says so and links straight to the new figures. Hovering an update pill also now says when that
  image was last asked, when it is next due, and why.

• The wide bar of Intel and AMD graphics figures above the stack list is gone, and a stack
  whose file asks for a graphics card now carries a coloured badge on its own row instead — Intel
  blue, AMD red, NVIDIA green. That badge stays even while the stack is stopped, so you can see
  which stacks have hardware in them without starting them, which the old bar could never show.

• The user guide is now a manual rather than a description. It opens with a walk round the
  screen you land on — every button, column, mark and menu item named, with a close-up picture of
  each — and a matching walk round the editor and the settings panel. The rest of the pages are
  step-by-step: adding an app from the catalogue and bringing in a container you already run are
  written as numbered walkthroughs you can follow with the screen in front of you. Everything is
  written shorter and plainer, and where one page shows something another page explains, the two are
  now linked.

• The guide now covers removing a stack and the Manage tab — the log, shell and file browser
  inside a running container — and every picture across the guide was re-taken against the current
  screen.

• StaXX's own mark now sits in the corner of its page, in place of the stock icon Unraid gives
  any plugin, so the page says whose it is at a glance.

• A running container that nothing is checking can be offered a health check. A green row only
  ever meant the container was going, never that the app inside was working. Click the pill on such a
  row — or use the button in the editor's health check section — and StaXX works out a question worth
  asking that image: a check written against a known database's own documentation, one the project
  published itself, or a plain fetch of the app's web page. It tries the candidate inside the running
  container first, so a check that cannot run is never offered. Where it knows no real question, it
  says so and offers nothing, because a check that can only ever say yes turns "nobody knows" into
  "looks fine". Noth...

StaXX 00.02.00_dev20260904 (development)

Development build 00.02.00_dev20260904, off the dev branch.

• The shell in the Manage tab is now Unraid's own terminal, the same one the Console button opens, so nano, htop and anything else that draws a full screen work in it. When the shell ends the pane greys out with its last screen still readable, and Reconnect opens a fresh one.

• Put several services back to earlier versions in one go. The Versions tab has a "Put back several at once" mode: choose a version for each service, press once, and the stack is edited, saved to History and recreated in a single step rather than one service at a time.

• A stack outside any folder can now be placed above a folder, and starts in that order at boot. The top level used to draw every folder first, whatever you did.

• Refreshing the page reopens the stack you were editing. The open stack's name rides in the address bar, so a refresh, or a pasted link, lands back in the same editor.

• A log left open in a background tab now checks in every half-minute instead of every second, and catches up the moment you return to it.

• Fixed: the dimmed square shown over a stack's icon while it starts now fits the larger icon in the wide layout instead of sitting in its corner.

• Fixed: pressing "Write each one twice" on the dollar-sign dialog now closes the dialog as well as making the change.

• Fixed: in the wide table the state chips sit flush left under a left-aligned heading rather than floating in the middle of the column.

• The flash-drive copy of a stack now includes its .env file, and the switch that controls those copies is in the settings panel on the Storage tab. A copy restored from the flash drive is a complete definition again, not a compose file whose placeholders point at nothing.

• The page no longer scrolls behind an open dialog. Reaching the end of the editor or the settings panel used to scroll the stacks list underneath; the page now holds still, softly blurred, until the dialog closes.

• Fixed: pressing Discard on the settings panel’s "Discard changes?" question now closes the question as well as the panel.

• Settings can show a picture of what each option looks like. Under a setting's dropdown, a
  small screenshot of each option sits in a row, the chosen one outlined; clicking a picture picks
  that option. It starts with where StaXX appears in the menu.

• The Settings panel was reworked with Adrian's feedback. Each setting now sits in its own
  titled box, with the explanation above the control rather than below it; the Docker menu setting
  gained its own pair of pictures; several settings were reworded for clarity and brevity; Where
  stacks may live moved onto the Storage tab; and the Docker menu setting locks itself off, greyed
  out, while StaXX is shown as a Docker tab, since there is no top-level button for it to replace.
  Related settings now share one box — the update check's schedule, when an update installs itself,
  and Docker Hub sign-in; the "when to install" box folds away unless updates are set to install
  themselves; registries you run yourself are now added one at a time to a list rather than typed as
  a comma-separated line; the update-check figures now show as a table at the end of that tab instead
  of a paragraph part-way through it; and the StaXXCrypt setting now explains, in plain words, what is
  actually inside the little container it builds.

• The address column lists only ports that are actually reachable. It shows the ports Docker is
  forwarding, plus the one port a service's web page answers on. Stacks with their own network
  address, or on host networking, no longer carry a row of internal ports nothing outside can reach.

• The update status now lives at the top of the page, not above the table. Last checked, how
  many updates are waiting, and how many author-example findings there are now show as small tags
  next to "StaXX" — at the right end of the title bar when the page has one of its own, in Unraid's
  shared tab strip when its tabbed view is on and StaXX has none, and otherwise on their own line
  above the buttons. The explanatory paragraph that used to sit above the table is gone — the
  store's location is already on the Settings page — and the table now starts a little higher, so
  one more row fits on screen.

• On a tablet-sized window, the stack list is now a grid of cards instead of a squeezed table.
  Each stack gets its own card — icon, name, state, address and its little graphs, three across —
  and a folder becomes a heading above its own row of cards. A stack running several services shows
  a cubes button in its corner; tap it to see those services as cards of their own, without the page
  underneath changing shape.

• The stack table reads better on a wide screen. Ports now stand in their own column beside the
  address instead of running on in one long line; a stopped stack's dash lines up under its column
  heading instead of sitting off to one side; the line under the column headings is now one
  unbroken rule instead of breaking into pieces; stack rows are a little taller, with a bigger icon
  and bigger WebUI/Logs/Repo/CA buttons that are easier to click; and an update pill now always
  reads "update ready", with a small tag icon showing when it also knows exactly which version —
  hover it to see both.

• Hovering an update pill now shows a small card in the page's own style instead of the browser's
  plain tooltip. The running and available versions, when it was last checked, when it is next
  due and why it is checked as often as it is now lay out as a short table instead of one long
  sentence. An image whose first check already found an update pending — Radarr was the one that
  gave this away — now shows its running version too, read straight off the container rather than
  left blank.

• The page no longer grows a second scrollbar of its own. Collapsing a stack or a folder was
  leaving a sliver of invisible extra room on the page, on top of your browser's own scrollbar —
  fixed at the source, so both scroll the same amount again.

• Tidy no longer refuses a file over the commented example StaXX itself writes into it. A
  trailing note indented under a setting now travels with that setting instead of being treated as
  a stray line — so a freshly scaffolded stack tidies cleanly instead of being refused outright. Its
  result is also shown as a proper notice above the file, not just on the small status line below it.

• An image you haven't downloaded yet is no longer asked about at update checks. There was
  nothing on your server to compare a registry's answer against, so the question was always wasted —
  it is now skipped, and asked promptly as soon as the image is actually here.

• Checking for updates no longer spends any of your Docker Hub allowance. It asks for a build's
  headers only, which Hub does not count — the allowance is only spent when you actually install an
  update.

• Checking now runs every hour, asking only the images that are due, with a full look at every
  image at the time you chose. Choosing "Once a week" used to mean each image was only asked about
  weekly; it now means the once-a-week full look happens then, while how often any one image is
  actually asked is still decided by how often it tends to change.

• The settings panel now shows what each registry has actually been asked, and what it cost —
  under Image updates, next to the check schedule. Being refused by Docker Hub now means something
  else on your address spent the download allowance, since a check itself costs nothing, and StaXX
  tries again within the hour rather than waiting for the next pass; the refusal notice on the stacks
  page says so and links straight to the new figures. Hovering an update pill also now says when that
  image was last asked, when it is next due, and why.

• The wide bar of Intel and AMD graphics figures above the stack list is gone, and a stack
  whose file asks for a graphics card now carries a coloured badge on its own row instead — Intel
  blue, AMD red, NVIDIA green. That badge stays even while the stack is stopped, so you can see
  which stacks have hardware in them without starting them, which the old bar could never show.

• The user guide is now a manual rather than a description. It opens with a walk round the
  screen you land on — every button, column, mark and menu item named, with a close-up picture of
  each — and a matching walk round the editor and the settings panel. The rest of the pages are
  step-by-step: adding an app from the catalogue and bringing in a container you already run are
  written as numbered walkthroughs you can follow with the screen in front of you. Everything is
  written shorter and plainer, and where one page shows something another page explains, the two are
  now linked.

• The guide now covers removing a stack and the Manage tab — the log, shell and file browser
  inside a running container — and every picture across the guide was re-taken against the current
  screen.

• StaXX's own mark now sits in the corner of its page, in place of the stock icon Unraid gives
  any plugin, so the page says whose it is at a glance.

• A running container that nothing is checking can be offered a health check. A green row only
  ever meant the container was going, never that the app inside was working. Click the pill on such a
  row — or use the button in the editor's health check section — and StaXX works out a question worth
  asking that image: a check written against a known database's own documentation, one the project
  published itself, or a plain fetch of the app's web page. It tries the candidate inside the running
  container first, so a check that cannot run is never offered. Where it knows no real question, it
  says so and offers nothing, because a check that can only ever say yes turns "nobody knows"...

StaXX 00.01.00

00.01.00 — released 2026-08-30

The release that makes a folder row show you what is actually in it, gives a stack folder with no
compose file a way to get one, and keeps a copy of every compose file somewhere a dead pool cannot
take it.

• A copy of every compose file now lives on the boot volume. If the pool holding your stacks
  ever dies, the definition of every container you run dies with it unless you had your own backup.
  StaXX now keeps a plain copy of each stack's compose file at the top of the flash drive — which
  Unraid already backs up wholesale, and which is readable before the array has even started. It is
  a shelf, never a second opinion: StaXX never reads it while your store is there, never compares the
  two to work out which is newer, and nothing ever comes back on its own. Turning it off is one
  setting; it ships on, because the people it protects are the ones who would never go looking for
  it.
• A stack folder with no compose file can be given one. Until now the row said the file was
  missing and left you to fix it over a network share. It now offers the same starting file "Add
  stack" writes. It is a repair route, not a second way to make a stack, and it says so.
• Your first version is kept, not just your second. A stack's history used to hold only the
  version each save replaced, so a brand-new stack — or a file you dropped in by hand — had nothing
  kept until its second save. That window is closed: the file is kept the first time you open it,
  the first time you run it, and after every save as well as before one. If the file then goes
  missing, StaXX offers your last saved copy back, with the date, and loads it into the editor for
  you to look at rather than writing it anywhere.
• A folder row shows every service inside it. All the icons, grouped rather than shrunk to
  nothing, opening into a grid when you hover and naming whichever one is under the cursor. Each is
  a way into the stack it stands for, and the two kinds of broken — a stack with no compose file,
  and one compose cannot read — are drawn differently instead of both being a shrug.
• A stack shows the same picture everywhere. One place now decides a service's icon, so the row
  and the editor cannot disagree. The editor can work one out for you, and follows one you state the
  moment you state it.
• A container with its own address no longer pretends to publish ports. On a macvlan or ipvlan
  network the outer port is ignored by Docker entirely, so the box asking for it is gone and the
  recipe is shown instead. A port already written is kept as a note rather than deleted, and a stack
  whose ports cannot do anything says so on its row.
• The log and the shell share the width. A drag handle between them instead of taking turns, and
  the log keeps up, reads more easily and stays inside the dialog.
• Fixes: the takeover no longer asks whether it worked on top of the page that answers that; the
  glossary explains the two kinds of network and its ports section describes what ports now do; and
  a declined switch that changed nothing now says so rather than implying it did something.
• For the record: numbered releases install the ordinary Unraid way again. 1.2.0 shipped with a
  manifest naming a package that was never uploaded, so installing by plugin address failed. That is
  fixed, and the build now refuses to publish a release whose version, manifest and changelog do not
  all agree.

StaXX 00.02.00_dev20260831 (development)

Development build 00.02.00_dev20260831, off the dev branch.

• Point dev at 00.02.00, the version main is heading towards
• Say that the development channel builds itself most nights
• Cut a dev release each night, but only when dev has earned one
• Write a dollar sign twice, so a password hash survives the file
• Name every test suite, not the half somebody remembered
• Let each service own its picture, and stop the stack claiming one
• Say that alpha means minor releases and no migrations
• Write the release runbook down, so neither channel is cut from memory
• Stamp staxx.plg for v00.01.00
• Stop the sort gate counting the release it is publishing
• Pad every version component, and restart the count at 00.01.00
• Catch a manifest pointing at the wrong channel within a minute, not a release
• Give dev its own release channel, so it stops burning main's numbers
• Take the deploy script out of the readme entirely
• Lead with the plugin install, since that is now the way in
• Let somebody type their own password, and never leave a hash behind it
• Stamp staxx.plg for v1.3.0