Caffoot Lite v2.1

Caffoot Lite v2.1 — Release Notes

Simplicity in everything. Your infrastructure. Your users. Your data.

These are the v2.1 release notes. For the confirmed publication status and downloads, consult the [official GitHub Releases page](https://github.com/Caffoot/Caffoot-Lite/releases). Public AMD64 and ARM64 images must be verified through the release workflow; website publication and deployment are separate decisions.

A Familiar Application With The Approved Interface

v2.1 replaces the previous presentation with the twelve pinned, owner-approved modular HTML designs. Shared navigation, responsive cards/forms, icons, light/dark themes and local Help & Guides use plain HTML, CSS and JavaScript with the existing Python/SQLite application. No replacement framework or new authoritative browser database is introduced. Sign In and About carry the approved tagline. The public source provenance remains pinned at c26db4a56bbc30f95b56201e81a7a76d13c6037b.

The Dashboard, Devices, IPAM, Network Racks, Users, My Account, Audit Trail and Settings & Data keep their existing responsibilities. Main navigation spacing, tab icons, accessible focus reveal and approved hierarchy corrections are included. The print mode remains an optional existing choice; it has not become the default.

Devices, Physical Hosts And Virtual Machines

• Add/Edit/Duplicate follows the approved form cards and grouping, with internal scrolling, accessible actions, local errors, useful focus and a Notes area that fills the available workspace. Duplicate uses its subtitle rather than an extra banner; all existing formatting actions and stored notes remain.
• Eligible physical servers expose the hosting checkbox on General. When enabled, dedicated hypervisor product/version selectors replace ordinary OS selection in that form. Hypervisor products are excluded from ordinary OS/Installed Software choices without deleting catalogue or historical assignments.
• Virtual Machine deployment uses eligible saved physical hosts, VM purpose and allocated CPU/RAM/storage/network resources. Inapplicable physical/rack/hardware controls are hidden. Existing eligibility, conditional fields, guest relationships and safety confirmations remain.
• Contextual OS/version/software choices refresh immediately and retain supported custom/historical records. Proxmox VE, Hyper-V and ESXi lists remain distinct. The approved catalogue and 100-character software/service name validation are consistent across create/edit/server boundaries.
• Rack selection can default Location Area while preserving saved values and deliberate overrides. Optional shelf associations, supported shelf creation, location display and reviewed atomic shelf removal/retirement retain existing permission and five-minute editing-reservation safeguards.
• The read-only Details header uses the approved accessible Close control; other accepted Details/Device screens are preserved.

Subnet-first IPAM

• Devices select a named subnet without first choosing VLAN. VLAN is derived and read-only, or Not assigned. Choose an Available IP appears above manual Primary IP; both use the same saved address and existing allocation/reservation checks.
• Newly created addressable subnets require a unique trimmed/case-insensitive name and explicit LAN, Management or VPN purpose. VLAN is optional. VPN may omit a gateway; any supplied gateway must be usable and unconflicted. LAN/Management and legacy unclassified records retain required gateways.
• Historical missing purposes and duplicated names are not silently migrated or renamed. Unrelated edits/import retain existing values and representations; a deliberate rename must meet uniqueness. Optional values are not fabricated as VLAN 0 or an invented gateway.
• Separate Add Single Subnet and Add Multiple Subnets actions retain the existing IP allocation Bulk Edit Range. Optional collapsed Address Block/private-range planning precedes subnet creation. Parent blocks may be broader; addressable children remain /23–/30.
• Capacity guidance explains theoretical equal-sized capacity and suitable child prefixes, accounting for Every 10th spacing. It does not silently change the selected prefix or imply that ranges are available. Users still choose according to device/address needs.
• Consecutive, Every 10th Subnet and Custom CIDRs use an editable preview with individual names, purposes, optional VLANs, descriptions and gateways. Manual gateways/custom drafts survive Back where applicable and are revalidated. Desktop tables and stacked mobile rows scroll with actions available.
• Creation is limited to 1–50 subnets per operation, not per installation. The server validates fresh state and commits the optional parent, all children, catalogue and attributed audit together, or saves none. Three disjoint batches totalling 150 are covered by tests.
• A block may strictly contain an independent unparented network without adopting it. Its IDs, parent absence, names, VLAN, devices and allocations remain unchanged; parent filters follow explicit links only. Real network overlaps, equal/partial ranges, unrelated blocks and ownership conflicts remain rejected. Empty block deletion cannot detach independent inventory; explicit children still protect a block.

Network Racks

Approved front/rear placement, U occupancy, dimensions, horizontal/vertical accessories, valid/invalid previews, keyboard controls, collision validation and saved positions remain. Remove Accessory styling and successful vertical-drop scroll preservation are restored without redesigning drag-and-drop. Shelf relationships and removal review work with linked devices and permissions. Existing rack printing and optional same-tab route remain; no speculative horizontal scrolling correction or default print-mode change is included.

Accounts, Email And Security

My Account provides the approved personal/profile, password/MFA, appearance, Help and About views. Users and system Settings & Data remain administrator-managed. New accounts have no inventory rights until granted; administrators and editors retain required MFA. Existing field-level cross-section editing checks and device reservations remain server-enforced.

Saved email is optional. Verification status and guided eight-digit confirmation make ownership visible. Forgot Password? remains username-only; requests return neutral responses and do not reveal eligibility or delivery. Recovery requires an active eligible account, verified email and configured delivery, retains MFA requirements and revokes existing sessions after a successful reset. It cannot recover loss of both an administrator password and authenticator.

Eight-digit proofs bind to opaque challenges, expire after fifteen minutes and work once. Five failed confirmations exhaust a challenge; the durable account/purpose failure budget survives resends and restarts. Existing throttles, concurrency and account isolation remain. Schema 10 deliberately invalidates outstanding old-format email proofs on upgrade; request a new code. SMTP delivery is operationally dependent and no previously missing message is claimed fixed without evidence of its cause.

The private account-email-secret.key, when created, belongs beside SQLite in /data. It is not part of a database-only copy. Back it up securely with the matching full installation; never replace a missing key while usable challenges exist.

Audit Trail And Settings & Data

Audit Trail places secondary navigation before relevant cards and retains metrics, filters, tables, tabs and security notices. Attributed events and inventory history remain bounded and permission-filtered. Bulk subnet summaries report the actual total/range while retaining omitted-detail notices; private information is not exposed to unrelated readers. The existing event-detail styling corrections are retained. Audit/history is not a database restore mechanism.

Settings & Data retains administrator inventory migration, safety checks, maintenance and optional SMTP configuration. My Account keeps personal appearance/help settings. Existing locally readable help works without fetching a public website; external full-guide links need network access. Canonical and legacy guide URLs remain byte-identical for older installed versions.

Upgrade, Backup And Compatibility

Follow [INSTALLATION.md](https://github.com/Caffoot/Caffoot-Lite/blob/main/INSTALLATION.md#upgrading-v203-to-v21). Stop and protect the entire existing /data mount, including SQLite/sidecars, TLS, private account-email key when present and all other installation files, with original ownership/modes. Preserve the current mount, environment, HTTPS origin and ports. Do not substitute a fresh volume or import JSON as an upgrade step.

The application applies additive migrations through schema 10. Existing inventory, accounts, MFA, permissions and history are retained. Rollback requires the complete matching pre-upgrade backup and old image; an older binary must not open the upgraded database. Post-backup changes are not recovered by that rollback.

Published standalone v1.3.3 JSON import remains one-way inventory migration with explicit review and transactional confirmation; it does not import accounts/MFA or replace external Docker backup. The owner successfully imported a genuine saved v1.3.3 backup privately. Two automated genuine private-fixture tests remain unrun, and that manual success is not counted as their pass.

Verification And Limits

Accepted application checkpoint e39e58d1a270afd9f4cdae114668f5e2bb1fe771 passed backend (494 run, 491 passed, three established skips), full Chromium/editor, Firefox, Linux WebKit, real AMD64 Docker lifecycle and full-history secret checks. Owner nativ...

Caffoot Lite v2.0.3

Caffoot Lite v2.0.3 — release notes

Infrastructure, Simplified. 🦔

Caffoot Lite v2.0.3 is a small maintenance release for the established Docker/SQLite application. It builds on the published v2.0.2 security correction, without introducing new inventory features or requiring a database migration.

What changed

• The About Caffoot Lite page identifies the correct v2.0.3 application version.
• The Development Guide's Function Index was refreshed to 494 named entries, including the history-permissions module introduced in v2.0.2.
• Existing browser regression checks now cover Rack front/rear switching and printing and virtual-machine host selection.
• The full user guides have a clearer home at docs/how-tos/features-and-instructions. The previous guide paths remain available and are checked against the new copies, so existing v2.0.2 installations retain working links.
• Installation instructions, the Portainer example and developer documentation have been updated for this release. Old release records stay available as history.

What stays the same

• Existing Devices, IPAM, Racks, Change History, users, permissions, MFA and inventory workflows.
• The Docker/SQLite architecture, database format, server-side security checks and supported platforms.
• The existing /data volume or host-directory mapping, containing the inventory database and HTTPS certificates. Do not replace that mapping during an upgrade.
• One-way import of supported published v1.3.3 standalone JSON backups; ongoing Docker backups remain an external responsibility.

Installing or upgrading

Only after the v2.0.3 GitHub Release and Docker image have been separately approved, built and published, use ghcr.io/caffoot/caffoot-lite:v2.0.3 on AMD64 or ARM64. For a new installation, see the v2.0.3 Portainer example and installation guide.

For an existing installation, first stop the application and make a verified external backup of all persistent /data files, including caffoot.sqlite3 and tls/. Update only the image tag in the same stack, keeping the existing volume or bind mount, address and port. Verify sign-in, inventory and the HTTPS certificate identity afterwards. Never create a replacement empty data volume to upgrade.

Read the upgrade instructions before changing a live system. The original v2.0.1 → v2.0.2 upgrade section remains available for older release links.

Release verification

Publishing a source pull request does not publish the application. The owner-approved Publish Caffoot Lite workflow runs release checks before creating the tag, publishing the AMD64/ARM64 image and issuing this GitHub Release. Check the successful Actions run and public image availability before installing. Website updates and production deployments remain separate decisions.

For security concerns, please report privately.

Caffoot Lite v2.0.2

Caffoot Lite v2.0.2 — Security Maintenance Release

Infrastructure, Simplified. 🦔

Caffoot Lite v2.0.2 is a focused security maintenance update for the established Docker/SQLite application.

What's included

• Server-side security correction for authenticated inventory access.
• Additional regression tests and security validation.
• Updated Docker image, Portainer stack and installation documentation.
• Multi-platform Docker support for AMD64 PCs and ARM64 systems, including Raspberry Pi 5.

Upgrading from v2.0.1

No database migration is required.

Before upgrading, stop your container and back up your existing /data directory, including the SQLite database and TLS certificates.

Update your existing stack's image tag to ghcr.io/caffoot/caffoot-lite:v2.0.2 once the image build is confirmed successful. Keep your existing volume mappings and stack identity unchanged.

Documentation

Full instructions and release notes are available in the repository:

https://github.com/Caffoot/Caffoot-Lite

Security advisory details will be published separately when appropriate.

Caffoot Lite v2.0.1

Caffoot Lite v2.0.1 — Infrastructure, Simplified. 🦔

Introducing Caffoot Lite v2.0.1, a refinement of our major v2.0 Docker and SQLite release.

This update focuses on delivering a cleaner, more professional repository and release package while preserving all the functionality introduced in v2.0.

What's changed in v2.0.1?

A cleaner, more organised application

• The Docker application, Python backend, Dockerfile, Compose configuration and tests now live directly in the repository root.
• The temporary next/ development directory has been removed.
• The previous standalone HTML application's source files are no longer included in this release.
• Installation instructions, documentation and source links have been updated for the new structure.
• The application now identifies itself as Caffoot Lite v2.0.1.

Everything you love about v2.0 remains

Caffoot Lite continues to provide:

• Central SQLite database storage.
• Device inventory, IP address management and network rack documentation.
• Administrator-managed user accounts and role-based access permissions.
• Multi-factor authentication.
• Simultaneous multi-user inventory access.
• Device editing reservations.
• Change History and established inventory safeguards.
• Docker Compose and Portainer support, including Raspberry Pi 5.

No inventory functionality or database behaviour has been redesigned or removed.

Docker installation

Official container image:

ghcr.io/caffoot/caffoot-lite:v2.0.1

Supports Linux AMD64 and ARM64, including Raspberry Pi 5.

Installation resources:

[Docker and Portainer installation guide](https://github.com/Caffoot/Caffoot-Lite/blob/v2.0.1/INSTALLATION.md)

[Ready-to-use Portainer stack](https://github.com/Caffoot/Caffoot-Lite/blob/v2.0.1/portainer-v2.0.1.yaml)

The container image is published automatically when the v2.0.1 release tag is created. Please confirm that the image build has completed before deploying.

Migrating from standalone v1.3.3

The original standalone HTML version remains available through its [v1.3.3 release](https://github.com/Caffoot/Caffoot-Lite/releases/tag/v1.3.3).

To migrate, export a fresh JSON inventory backup from published v1.3.3, install Caffoot Lite v2.0.1, complete the administrator account setup and use Settings & Data → Import Inventory to review and confirm your inventory migration.

The v1.3.3 JSON import is intended for one-way migration only. Ongoing Docker database backups must be managed externally.

Release verification

The v2.0.1 release candidate successfully passed backend tests, Chromium browser compatibility tests, real Docker Compose lifecycle and persistence testing, documentation verification and Git history security scanning.

The existing v2.0 and v1.3.3 releases remain unchanged and available.

---

Caffoot Lite — Infrastructure, Simplified. 🦔

Free, open source and built for home labs and small IT teams.

Caffoot Lite v2.0

Caffoot Lite v2.0 — Infrastructure, Simplified.

Introducing Caffoot Lite v2.0, the new Docker and SQLite edition of Caffoot Lite.

This major release brings the familiar Devices, IPAM, Network Racks and Change History experience to a central database, with administrator-managed users, role-based permissions, multi-factor authentication and simultaneous multi-user access.

Designed for home labs and small teams, v2.0 supports Docker Compose and Portainer installations, including Raspberry Pi 5.

Migrating from v1.3.3: Export a fresh JSON inventory backup from the published standalone v1.3.3 application. Import it through Settings & Data in v2.0, review the proposed changes and explicitly confirm replacement.

Protecting your data: v2.0 uses a persistent SQLite database. Ongoing backup and recovery are managed through your external Docker or server backup tools, not browser JSON exports.

The original standalone Caffoot Lite v1.3.3 remains available for those who prefer a single HTML file.

Documentation: See the repository README, Docker/Portainer installation guide and complete Features and Instructions user guides.

Caffoot Lite — Infrastructure, Simplified. 🦔

Caffoot Lite v1.3.3

Caffoot Lite v1.3.3

Status: Stable maintenance release

Caffoot Lite v1.3.3 is the final standalone HTML-only maintenance release before development moves towards the planned Docker and database-backed version.

This release focuses on completing agreed audit work, improving code clarity, correcting identified issues and bringing technical documentation into alignment.

What's included

• Clearer function and internal naming to make future development and maintenance easier.
• Corrections to virtual machine creation and device management behaviour.
• Improved regression coverage for rack inventory imports, including accessories, collisions and malformed data.
• Reconciliation of the master audit, findings register, technical documentation and test evidence.
• Release documentation and packaging checks to help ensure that published files contain the correct version information.

No unrelated new features have been introduced.

Upgrading and protecting your data

Caffoot Lite remains a standalone, browser-based application that stores inventory data locally.

Before upgrading:

1. Export a JSON backup of your existing inventory.
2. Keep a copy of your previous working HTML file.
3. Download and use the new v1.3.3 HTML file.
4. Confirm that your inventory is present and working correctly.
5. Retain your original backup until you are satisfied with the upgrade.

Important: Restoring a backup replaces the active inventory. Always retain a separate copy of your existing data.

Downloads

The release provides three files:

• Caffoot-Lite-1.3.3.zip — complete standalone release package with supporting documentation.
• Caffoot-Lite.html — standalone application.
• SHA256SUMS — checksums for verifying the downloads.

Testing and verification

This release builds on previously successful application, browser, backup, restore and compatibility testing.

Additional focused verification covered the changes introduced during v1.3.3 development. Release documentation, packaging and security checks were also completed.

Existing audit findings and known test coverage limitations remain documented. This release does not claim that every historical scenario has been retested or every outstanding finding has been resolved.

Looking ahead

v1.3.3 completes the planned standalone HTML-only maintenance series.

Future development is intended to move towards a Docker-based application with database-backed storage, while preserving as much of the existing user experience as practical.

Caffoot Lite remains under active development.

For technical details, outstanding findings and verification evidence, see [GitHub issue #108](#108).

Thank you for using Caffoot Lite!

Caffoot Lite v1.3.2

Caffoot Lite v1.3.2

Caffoot Lite v1.3.2 is a maintenance and usability release, improving device management, virtualisation support, catalogue editing and application appearance.

What's new

• Improved device catalogue editing while preserving historical software and server service assignments.
• Clearer physical server and virtual machine naming.
• Fixed device identity and improved virtual-device configuration.
• Host-aware virtual hardware presentation.
• Hypervisor hosting selection with effective operating system information in device details and charts.
• Preservation of the original host operating system when hypervisor hosting is disabled.
• Refined application colours and improved dark-mode readability.
• Inventory safety, recovery, rack management and IPAM usability improvements.

Compatibility and verification

Caffoot Lite remains a standalone offline HTML application.

The v1.3.2 release passed automated release validation, consolidated Chromium regression, documentation consistency and security scanning.

The release package passed version, contents and file integrity checks.

Manual acceptance included hypervisor behaviour, application appearance and successful import of an older v1.2.0 backup. This does not represent exhaustive verification of every historical inventory configuration.

Installation and upgrading

1. Download Caffoot-Lite-1.3.2.zip.
2. Extract the ZIP file.
3. Open Caffoot-Lite.html in a supported browser.
4. Continue using Caffoot Lite offline.

Important: Export and retain a JSON backup of your existing inventory before upgrading.

Release files

• Caffoot-Lite.html
• Caffoot-Lite-1.3.2.zip
• SHA256SUMS

Existing v1.3.1 downloads remain available through GitHub Releases.

For detailed development and verification records, see GitHub issue #107.

Caffoot Lite v1.3.1

Caffoot Lite v1.3.1 release notes

Status: Stable maintenance release v1.3.1
Previous stable release: v1.3.0
Release date: 26 October 2026

Overview

Caffoot Lite v1.3.1 builds on v1.3.0 with inventory safety, rack capacity, IP address management and physical hypervisor relationship improvements. The standalone HTML application remains the intended distribution format.

Changes in this release

• Inventory safety and recovery: Protect inventory and in-memory state when relevant saves fail, including device deletion, rack creation, location and graphics updates, import rollback and startup recovery. See issue #94 and its merged pull requests.
• Rack capacity: Vertical PDU and Vertical Cable Manager accessories do not consume numbered rack U capacity. Ordinary horizontal accessories still count. Existing stored accessory identifiers are preserved. See issue #140 and PR #142.
• IP address management: Preserve address notes and historical reservations during individual and relevant bulk address release operations and legacy import. See issue #92 and PR #123. This does not claim all future IPAM roadmap items are complete.
• Physical hypervisor and virtual machine relationships: Improve physical host and guest handling, explicit guest resolution safeguards and the placement of Add and Edit host controls under General. Preserve historical and custom host values where covered by the documented migration and browser checks. See issues #91, #93 and #134.

Compatibility and limitations

This release is designed to retain existing inventories and historical JSON backup compatibility. Existing user inventories must not be overwritten for testing. Unresolved wider workflow audit findings remain tracked in the central findings programme and are not implicitly certified by this maintenance release.

Verification

The final application revision debb040 passed standalone build and Chromium verification and release validation and package verification. Packaging verified the versioned ZIP, expected members, licences, embedded notices and extracted byte hashes, including legacy and schema-v1 backup fixture checks. The product owner also reported successful offline operation and JSON backup acceptance on an earlier correctly versioned candidate. These are distinct forms of evidence, and wider audit findings remain open.

The release includes the verified Caffoot-Lite-1.3.1.zip, standalone Caffoot-Lite.html, and SHA256SUMS for download verification.

Caffoot Lite v1.3.0 — Rack Management Modernisation

Caffoot Lite v1.3.0 — Rack Management Modernisation

Caffoot Lite v1.3.0 introduces major improvements to rack management, equipment placement and inventory visibility while retaining the standalone, offline-first application.

What's new

• Rack workspace: Dedicated Rack Overview, Rack Inventory and Rack Accessories pages.
• Rack insights: Capacity, equipment, location and rack-type summaries.
• Rack elevations: Front and rear equipment placement, rack-unit labels and collision prevention.
• Flexible rack configuration: Custom rack heights, rack types, optional dimensions and safer editing.
• Rack accessories: Improved management of power distribution, ventilation, cable management and environmental equipment, including supported 0U placements.
• Inventory improvements: Better device mounting, location handling and rack assignment workflows.

Backup compatibility and data safety

• Continued support for JSON backup and restore.
• Improved handling of legacy mounting and location values.
• Additional validation and recovery safeguards.

Important: Export and safely retain a JSON backup before upgrading or restoring inventory. Restoring a backup replaces the active inventory.

Caffoot Lite stores inventory locally in the browser. It is not an authenticated multi-user web service and should not be exposed directly to the public internet.

Testing

The final v1.3.0 release candidate passed the automated regression suite, security checks, standalone HTML verification and ZIP packaging checks on 21 October 2026.

Browser acceptance testing, including rack management and historical backup compatibility, was also completed.

What's next

v1.4.0 — Data & Architecture Foundations

The next development milestone will focus on storage architecture, data durability, migrations, deployment options and future multi-user security boundaries.

See ROADMAP.md for the development roadmap.

Caffoot Lite v1.2.1

Caffoot Lite v1.2.1 — Release Notes

Focus: Legacy backup import compatibility and rack-location display.

Fixes

• Restore compatibility for older backups containing a Desktop, Laptop or Tablet with the legacy Racked location but no rack assignment. Affected records are presented for explicit review before any changes are applied.
• Review eligible legacy computer devices marked Rack Mounted without an assigned rack or U position. Proposed corrections are shown before the final restore confirmation.
• Make the compatibility review clearer by showing the current mounting type, location and rack assignment alongside the proposed correction.
• In Device Inventory, correctly rack-mounted devices with an unknown physical room/site location no longer show the misleading red NEEDS ATTENTION indicator solely for that reason. Their physical location remains Unknown; the rack and U position are preserved.

Data safety and limitations

• The original JSON backup is not edited. Supported compatibility corrections require explicit approval; the user may cancel.
• Unknown or unsupported mounting values still fail validation. Other integrity checks remain in place, and an invalid import must not replace existing inventory.
• A pre-restore safety snapshot records the current browser inventory before a successful restore. If that inventory is empty, the snapshot can correctly contain zero devices; it is not a copy of the imported backup.
• Rack assignment and physical room/site location are distinct. This release does not automatically infer a device's physical location from its rack's location.
• Caffoot Lite remains a local, offline-first browser application. Back up your data before updating; inventory lives in browser storage rather than the HTML file. Moving or renaming the HTML file can affect access to stored inventory.

Verification

Owner-reported manual regression testing on the maintenance branch confirmed: original v1.1.2 tester backup import with explicit review; cancellation protection; preservation of two devices, IPs and a firewall at rack SV1-NR1 U40–U42; rejection of an invalid mounting value without replacing existing inventory; validation of three compatible desktop backup variants; and updated inventory warning behaviour.

Pending before publication: run the final v1.2.1 release pipeline, inspect the generated standalone HTML and ZIP, verify checksums and approve publication. These checks do not constitute a formal security certification.

Scope

This is a maintenance update based on v1.2.0. Rack Management Modernisation continues separately in v1.3.0.