8 Commits

Include renames

Author	SHA1	Message	Date
bitdeals git user	2701c57200	cap total connections, and document the P2P port 8444 ... The daemon has always listened on 8444 and nothing published it, so every node built from this image was outbound-only. Publishing it is now a documented choice rather than an omission -- including the two things that are not obvious from the config: peers are told the port from `port` in keys.dat rather than the one you mapped it to (so only 8444:8444 works), and the node's own address is never configured at all, because every peer replaces the hardcoded 127.0.0.1 in the version message with the IP it sees on the socket. An open port needs a brake, hence BITMESSAGE_MAXTOTALCONNECTIONS. It defaults to the PyBitmessage stock 200, so nothing changes for existing users of the image. The key is inserted when the stock config lacks it instead of trusting the substitution: the PyBitmessage clone is unpinned, and a silent no-op would ship a node that looks capped and is not. The API port in the example compose moves to loopback, which is what the README already prescribed.	2026-08-02 14:48:01 +00:00
private-user	7761772dda	add registry	2025-03-19 14:12:45 +03:00
private-user	9a88767eaf	Docker fix	2024-08-14 17:08:57 +03:00
private-user	e270e0f616	Docker fix	2024-08-12 09:31:39 +03:00
private-user	0ed0c76954	Docker fix	2023-08-31 14:34:14 +03:00
private-user	655f13f50c	set stopresendingafterxdays	2023-01-31 11:09:25 +03:00
private-user	4a2404c4c9	Dockerfile	2022-10-19 05:09:12 -04:00
private-user	304a530df2	Dockerfile	2022-10-19 05:05:45 -04:00