2024-10-31 15:43:10 -04:00
## Notes
2024-10-31 21:13:36 -04:00
This is in active development and not in working order yet. It is highly unstable and will fluctuate in changes.
2024-10-31 15:43:10 -04:00
2024-10-29 20:57:35 -04:00
## TO DO
2024-10-31 20:28:33 -04:00
- [X] Lifecycle startup + shutdown
- [X] Volume for each router
- [X] Shared Volume
2024-10-29 20:57:35 -04:00
- [ ] Port forwarding
2024-10-31 20:28:33 -04:00
- [X] Readline interface
2024-10-29 20:57:35 -04:00
- [ ] Reseed via file
2024-10-31 20:28:33 -04:00
- [ ] Reseed via node (i2pd)
- [ ] Reseed via node (i2p java)
2024-10-31 23:26:51 -04:00
- [X] go-i2p node (basic startup)
- [X] i2pd node (basic startup)
- [ ] i2p java router node (basic startup)
2024-11-12 12:40:23 -05:00
- [ ] Force netdb synchronization
2024-10-31 15:43:10 -04:00
- Config
- [X] go-i2p node
2024-10-31 23:26:51 -04:00
- [X] i2pd node
2024-10-31 15:43:10 -04:00
- [ ] i2p java router node
2024-11-12 12:40:23 -05:00
- Metrics
- [ ] TCP connection with daemon to relay router information
2024-10-31 20:25:37 -04:00
2024-10-31 20:04:57 -04:00
## Verbosity ##
2024-10-31 20:25:59 -04:00
Logging can be enabled and configured using the DEBUG_TESTNET environment variable. By default, logging is disabled.
2024-10-31 20:04:57 -04:00
There are three available log levels:
- Debug
```shell
export DEBUG_TESTNET=debug
```
- Warn
```shell
export DEBUG_TESTNET=warn
```
- Error
```shell
export DEBUG_TESTNET=error
```
2024-10-31 20:25:37 -04:00
If DEBUG_TESTNET is set to an unrecognized variable, it will fall back to "debug". Note, that this only accounts for verbosity in the testnet program itself, and not the nodes.
