chore: address operator trial feedback - laundry list of suggested nwaku improvements

[jm-clius]

Background

We recently recently launched a Waku operator trial, where core contributors and community volunteers configure and run their own nwaku nodes and provide feedback about their experiences.

This issue serves as a "catch all" for suggestions and issues raised during the trial (both from operators and our own findings). More substantial suggestions are reported in separate issues.

Details

Most voted:

• Docker guide. Tracked in separate issue here: docs: instruction manual for running nwaku in a docker #1207
• Simplified config/config file example: feat: configuration via environment variables #1198

Laundry list:

• Discv5 reporting (e.g. "discovered node count") should distinguish between bootstrap peers vs external nodes actually discovered via discv5
• Add a guide on how to configure nwaku for use with a VPN + port forwarding (specifically Mullvad, Wireguard)
• Simplify static resource management (nim-waku external files and resources #798)
• Guide should include REST commands that people can use to do basic health checks

[alrevuelta]

Extending on Discv5 reporting (e.g. "discovered node count") should distinguish between bootstrap peers vs external nodes actually discovered via discv5 I would relate it to #622. If we add a source field for each peer in the peerstore with [discv5, bootstrap, ...] we can get this information from there.

Also related #1354 to that.

[SionoiS]

Laundry list:

• Add a guide on how to configure nwaku for use with a VPN + port forwarding (specifically Mullvad, Wireguard)
• Simplify static resource management (nim-waku external files and resources #798)
• Guide should include REST commands that people can use to do basic health checks

@LordGhostX Would that be useful?

[LordGhostX]

Laundry list:

• Add a guide on how to configure nwaku for use with a VPN + port forwarding (specifically Mullvad, Wireguard)
• Simplify static resource management (nim-waku external files and resources #798)
• Guide should include REST commands that people can use to do basic health checks

@LordGhostX Would that be useful?

@SionoiS Yup, I'll add these under my radar too 👍

[Ivansete-status]

Hey @jm-clius !
Do you think we should keep this opened? It seems as if all the related tasks are closed already

[jm-clius]

Let's close!

[Ivansete-status]

Let's close!

Thanks for confirmation @jm-clius !