comparison · c_9f86dde118e5 (tommy-mor) vs c_a4b313331fd6 (tommy-mor)
Side B delivers a concrete, functional deployment path (Dockerfile, fly.toml, supervisord, entrypoint, JDBC URL normalization/SSL handling, DB connection retry logic) that provides tangible new production capability. Side A is mostly a rename/refactor (navigate_panel->input_panel) plus removal of an unused vote_panel feature and minor CSS tweaks, which is smaller in scope and largely churn/cleanup rather than new lasting functionality.
B adds lasting production capability: multi-stage Docker image, fly.toml, supervisord/entrypoint, SSL-aware JDBC URL parsing, pool tuning, PORT env handling, and DB connect retries. A is mostly UI churn—deleting vote_panel/parser_render, folding navigate into input_panel, tiny CSS, and a local bb watch task—useful cleanup but not comparable operational substance.
Side B adds production deployment infrastructure (Fly.io Dockerfile, supervisord, entrypoint, fly.toml) and improves runtime robustness by supporting both postgresql:// and postgres:// URLs, SSL configuration, PORT overrides, and retrying database connections for external Postgres. Side A mainly refactors the UI by moving the parser panel into the HTML module, removing the vote panel, adding a development watch task, and making small presentation tweaks, which are useful but have less enduring architectural impact.
comparison · c_a4b313331fd6 (tommy-mor) vs c_7074f7a7bb57 (tommy-mor)
Side A adds substantive production infrastructure (Dockerfile, fly.toml, supervisord, entrypoint script) plus real bugfixes to JDBC URL parsing (handling postgresql:// scheme and query params), SSL config, and DB connection retry logic in Rust—concrete lasting deployment capability. Side B is a small, somewhat regressive UI tweak that removes pin-form functionality for unpinned items and only adds one CSS line, offering far less durable value.
A ships lasting production infrastructure (multi-stage Dockerfile, fly.toml, supervisord) plus real compatibility fixes: JDBC URL/SSL parsing, smaller pools, PORT env handling, and rustsorter DB connect retries. B only tweaks CSS (display:flex) and removes pin/vote-preview UI surface area—small polish with little enduring project value.
Side A adds substantial production infrastructure and runtime robustness: a Fly.io deployment (Dockerfile, supervisor, entrypoint, fly.toml), support for managed PostgreSQL with SSL URL handling, PORT environment support, and retry logic for Rust database connections. Side B is a small UI cleanup, removing pin controls and a preview section while adding a single CSS display rule, with far less lasting architectural impact.