aynish/commoncomputing-nix
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Activity
77 Commits 4 Branches 0 Tags
main
Commit Graph
77 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Commons Computer 0eb1323a44 auto-update: flake inputs 2026-09-28T00:09:31-07:00 2026-09-28 00:09:31 -07:00
aynish 6172de2297 Merge pull request 'asusmini: remove public Caddy vhosts + drop 80/443 (edge moved to pve Caddy LXC)' (#3) from caddy-edge-strip-pl63 into main 
Reviewed-on: #3
Reviewed-by: Anish Lakhwara <anish@lakhwwara.com>
 2026-09-28 04:20:22 +00:00
aynish 2bae941f4a Merge pull request 'asusmini: open service ports via allowedTCPPorts (fix #1 — extraInputRules no-op on iptables backend)' (#2) from caddy-edge-iptables-backend into main 
Reviewed-on: #2
Reviewed-by: Anish Lakhwara <anish@lakhwwara.com>
 2026-09-28 04:20:17 +00:00
hausgeist 65494e9b67 asusmini: strip public Caddy vhosts + drop 80/443 — public edge moved to pve Caddy LXC (205.250.24.44 -> .1.11), verified live 2026-09-28 2026-09-27 19:15:34 -07:00
hausgeist 315d1316c3 asusmini: open 5555/5556/6555/3030 via allowedTCPPorts (extraInputRules was nft-backend-only, no-op on iptables backend — PR #1 did not open the ports) 2026-09-27 19:04:37 -07:00
aynish 4ab392bc45 Merge pull request 'asusmini: open 5555/5556/6555/3030 to the LAN (CC edge Caddy on pve)' (#1) from caddy-edge-firewall-open into main 
Reviewed-on: #1
 2026-09-28 01:31:06 +00:00
boris be87dea4f5 asusmini: allow LAN (192.168.1.0/24) access to pds/knot/spindle/automerge service ports 
Commons computer edge is moving to a Caddy LXC on pve (192.168.1.11);
the public 80/443 forwards follow shortly. The box firewall currently
only opens 22/80/443 on the wired interface, so the edge cannot reach
the 5555/5556/6555/3030 service ports. Allow them from the LAN only;
tailnet traffic already bypasses the firewall.

Follow-up PR: strip the public Caddy vhosts after the UDM flip.
 2026-09-27 17:41:30 -07:00
Commons Computer c152c08540 auto-update: flake inputs 2026-09-21T00:15:06-07:00 2026-09-21 00:15:06 -07:00
Commons Computer 47caa97b59 auto-update: flake inputs 2026-09-14T00:04:06-07:00 2026-09-14 00:04:06 -07:00
Commons Computer 11c290c8cf auto-update: flake inputs 2026-09-07T00:08:33-07:00 2026-09-07 00:08:33 -07:00
Commons Computer 9d7274e288 auto-update: flake inputs 2026-08-31T00:24:20-07:00 2026-08-31 00:24:20 -07:00
Commons Computer 0b5d2ba841 auto-update: flake inputs 2026-08-24T00:46:35-07:00 2026-08-24 00:46:35 -07:00
Anish Lakhwara 32e6a55d35 remove DNS push from auto-update 2026-08-18 19:59:04 -07:00
Commons Computer ddadf10f95 auto-update: flake inputs 2026-08-18T19:38:12-07:00 2026-08-18 19:38:12 -07:00
Anish Lakhwara e7793a6cef run PDS on Node 22 2026-08-18 19:36:13 -07:00
Commons Computer 4faea62689 auto-update: flake inputs 2026-08-17T00:07:37-07:00 2026-08-17 00:07:37 -07:00
Anish Lakhwara 8466f2503d use upstream bluesky PDS package 2026-08-15 19:18:52 -07:00
Commons Computer ea2dc5e4e7 auto-update: flake inputs 2026-08-15T19:06:31-07:00 2026-08-15 19:06:31 -07:00
Anish Lakhwara 52c852dfbb preserve unmanaged DNS records 2026-08-15 19:05:01 -07:00
Anish Lakhwara 694d8013ed fix PDS auto-update build 2026-08-15 17:08:56 -07:00
Anish Lakhwara 4c3c2a761c add automerge repo sync server 2026-08-13 21:19:27 -07:00
Commons Computer 74c5216423 auto-update: flake inputs 2026-08-10T00:25:38-07:00 2026-08-10 00:25:38 -07:00
Commons Computer d071dc1827 auto-update: flake inputs 2026-08-03T00:25:39-07:00 2026-08-03 00:25:39 -07:00
Commons Computer 0f7050a623 auto-update: flake inputs 2026-07-27T00:29:20-07:00 2026-07-27 00:29:20 -07:00
Commons Computer 924f073c21 auto-update: flake inputs 2026-07-20T00:12:16-07:00 2026-07-20 00:12:16 -07:00
Commons Computer f8b0ee82f2 auto-update: flake inputs 2026-07-13T00:44:16-07:00 2026-07-13 00:44:16 -07:00
Commons Computer 0028c0160f auto-update: flake inputs 2026-07-06T00:41:20-07:00 2026-07-06 00:41:20 -07:00
Commons Computer 883f533409 auto-update: flake inputs 2026-06-29T00:01:01-07:00 2026-06-29 00:01:01 -07:00
Commons Computer 93418bc258 auto-update: flake inputs 2026-06-22T00:02:40-07:00 2026-06-22 00:02:40 -07:00
Commons Computer 4f550caf0d auto-update: flake inputs 2026-06-15T00:05:57-07:00 2026-06-15 00:05:57 -07:00
Commons Computer 4953358b14 auto-update: flake inputs 2026-06-01T00:22:51-07:00 2026-06-01 00:22:51 -07:00
Commons Computer 271c372b02 auto-update: flake inputs 2026-05-25T00:21:55-07:00 2026-05-25 00:21:55 -07:00
Commons Computer a67318a0ba auto-update: flake inputs 2026-05-18T00:09:37-07:00 2026-05-18 00:09:37 -07:00
Commons Computer ae6488910a auto-update: flake inputs 2026-05-11T00:41:50-07:00 2026-05-11 00:41:50 -07:00
Commons Computer 305be99530 auto-update: flake inputs 2026-05-04T00:26:54-07:00 2026-05-04 00:26:54 -07:00
Commons Computer a8b5834828 auto-update: flake inputs 2026-04-27T00:26:42-07:00 2026-04-27 00:26:42 -07:00
Anish Lakhwara b7da25d6f5 Bump tangled to latest master (post-v1.13.0-alpha) and pin in auto-update 
The tangled core was on rev 956f97c (v1.11.0-alpha) and v1.13.0-alpha
introduces automatic DID minting for repositories which we want.

Master HEAD (6a27cd2) is post-v1.13.0-alpha and includes the DID
auto-mint migration. After deploy, retry verification on the knot
dashboard at https://tangled.org/settings/knots.

Note: the build's reported version string is hardcoded to 1.11.0-alpha
in nix/pkgs/knot-unwrapped.nix upstream -- this is a stale label, but
the actual code includes v1.13.0-alpha features (DID minting schema in
knotserver/db/db.go).

Also add an explicit `nix flake update tangled` to auto-update.nix so
tangled is always tracked, independent of how other inputs are pinned.
 2026-04-26 16:34:10 -07:00
Anish Lakhwara a8ddc2ef34 Bump bluesky-pds to v0.4.219 and fix tangled service options 
The deployed PDS was on v0.4.182 with a 50 MB blob upload limit, causing
upload failures for large images. Add an overlay that overrides bluesky-pds
to v0.4.219 (the latest tag in the bluesky-social/pds repo, ahead of
nixpkgs-unstable's 0.4.204) and set PDS_BLOB_UPLOAD_LIMIT explicitly to
100 MB.

Also fix `services.tangled-{knot,spindle}` -> `services.tangled.{knot,spindle}`
to match the option names exposed by the official tangled.org/@tangled.org/core
flake we import. The hyphenated names came from an older third-party flake
and have been causing every auto-update to fail since the tangled rev bumped
on Apr 20.
 2026-04-26 16:24:59 -07:00
Commons Computer 2c0d8a278f auto-update: flake inputs 2026-04-20T00:09:18-07:00 2026-04-20 00:09:18 -07:00
Commons Computer 15a1358db7 auto-update: flake inputs 2026-04-13T00:52:03-07:00 2026-04-13 00:52:03 -07:00
Commons Computer c60cb263e9 auto-update: flake inputs 2026-04-06T00:30:04-07:00 2026-04-06 00:30:04 -07:00
Commons Computer 6a4ed09fcb auto-update: flake inputs 2026-03-30T00:21:26-07:00 2026-03-30 00:21:26 -07:00
Commons Computer 691531f3d9 auto-update: flake inputs 2026-03-23T00:35:50-07:00 2026-03-23 00:35:50 -07:00
Commons Computer 9633c2d898 auto-update: flake inputs 2026-03-16T00:32:00-07:00 2026-03-16 00:32:00 -07:00
Commons Computer b526611262 auto-update: flake inputs 2026-03-09T00:38:16-07:00 2026-03-09 00:38:16 -07:00
Commons Computer 0a20545f5a auto-update: flake inputs 2026-03-02T00:17:06-08:00 2026-03-02 00:17:06 -08:00
Commons Computer 1083b64960 auto-update: flake inputs 2026-02-23T00:41:13-08:00 2026-02-23 00:41:13 -08:00
Commons Computer 317c7070d7 auto-update: flake inputs 2026-02-16T00:06:00-08:00 2026-02-16 00:06:00 -08:00
Commons Computer 37f16ba664 auto-update: flake inputs 2026-02-09T00:47:31-08:00 2026-02-09 00:47:31 -08:00
Commons Computer 5db846096a auto-update: flake inputs 2026-02-02T00:15:37-08:00 2026-02-02 00:15:37 -08:00