conduit/docs/development.md

# Development

Information about developing the project. If you are only interested in using
it, you can safely ignore this section. If you plan on contributing, see the
[contributor's guide](contributing.md).

## Debugging with `tokio-console`

[`tokio-console`][1] can be a useful tool for debugging and profiling. To make
a `tokio-console`-enabled build of conduwuit, enable the `tokio_console` feature,
disable the default `release_max_log_level` feature, and set the
`--cfg tokio_unstable` flag to enable experimental tokio APIs. A build might
look like this:

```bash
RUSTFLAGS="--cfg tokio_unstable" cargo build \
    --release \
    --no-default-features \
    --features=systemd,element_hacks,gzip_compression,brotli_compression,zstd_compression,tokio_console
```

[1]: https://docs.rs/tokio-console/latest/tokio_console/
use `lib.makeScope` and files to organize packages Some of the improvements here include: * rocksdb can actually use jemalloc now instead of just pulling in a second rocksdb for no reason * "complement-runtime" factored back out into shell file * complement image no longer uses `mkDerivation` for `copyToRoot` because that's what `buildEnv` is for * complement image no longer sets `SERVER_NAME`, complement already does that * all packages were factored out into `callPackage`-able files for use with a custom `lib.makeScope pkgs.newScope` * new version of `mkPackage` has options that are easier to use and override such as `features` 2024-04-22 00:28:35 +02:00			`# Development`

			`Information about developing the project. If you are only interested in using`
add a contributing guide Signed-off-by: strawberry <strawberry@puppygock.gay> 2024-05-04 19:24:25 +02:00			`it, you can safely ignore this section. If you plan on contributing, see the`
			`[contributor's guide](contributing.md).`
add optional support for tokio-console This turned out to be quite hairy, mostly because we need to apply the config's log level filter to the actual logs (stdout and, optionally sentry), but do not want to filter out the tokio tracing events needed by the console_subscriber. I hit several edge cases in tracing getting this to work, and we now depend on a git version of tracing with a backported patch :( 2024-04-25 18:07:59 +02:00
			## Debugging with `tokio-console`

			[`tokio-console`][1] can be a useful tool for debugging and profiling. To make
docs: more improvements, fixes, cleanup, etc Signed-off-by: strawberry <strawberry@puppygock.gay> 2024-06-17 03:30:51 +02:00			a `tokio-console`-enabled build of conduwuit, enable the `tokio_console` feature,
add optional support for tokio-console This turned out to be quite hairy, mostly because we need to apply the config's log level filter to the actual logs (stdout and, optionally sentry), but do not want to filter out the tokio tracing events needed by the console_subscriber. I hit several edge cases in tracing getting this to work, and we now depend on a git version of tracing with a backported patch :( 2024-04-25 18:07:59 +02:00			disable the default `release_max_log_level` feature, and set the
			`--cfg tokio_unstable` flag to enable experimental tokio APIs. A build might
			`look like this:`

			```bash
			`RUSTFLAGS="--cfg tokio_unstable" cargo build \`
			`--release \`
			`--no-default-features \`
slight docs updates Signed-off-by: strawberry <strawberry@puppygock.gay> 2024-07-03 19:16:27 +02:00			`--features=systemd,element_hacks,gzip_compression,brotli_compression,zstd_compression,tokio_console`
add optional support for tokio-console This turned out to be quite hairy, mostly because we need to apply the config's log level filter to the actual logs (stdout and, optionally sentry), but do not want to filter out the tokio tracing events needed by the console_subscriber. I hit several edge cases in tracing getting this to work, and we now depend on a git version of tracing with a backported patch :( 2024-04-25 18:07:59 +02:00			```

			`[1]: https://docs.rs/tokio-console/latest/tokio_console/`