Fix documentation build issues and add _build/ to .gitignore

This commit is contained in:
bomanaps
2025-08-31 02:01:39 +01:00
parent 526b65e1d5
commit 9a06ee429f
2 changed files with 9 additions and 6 deletions

3
.gitignore vendored
View File

@ -178,3 +178,6 @@ env.bak/
#lockfiles #lockfiles
uv.lock uv.lock
poetry.lock poetry.lock
# Sphinx documentation build
_build/

View File

@ -1,5 +1,5 @@
Multiple Connections Per Peer Multiple Connections Per Peer
============================ =============================
This example demonstrates how to use the multiple connections per peer feature in py-libp2p. This example demonstrates how to use the multiple connections per peer feature in py-libp2p.
@ -35,7 +35,7 @@ The feature is configured through the `ConnectionConfig` class:
) )
Load Balancing Strategies Load Balancing Strategies
------------------------ -------------------------
Two load balancing strategies are available: Two load balancing strategies are available:
@ -74,7 +74,7 @@ The new API provides direct access to multiple connections:
single_conn = swarm.get_connection(peer_id) single_conn = swarm.get_connection(peer_id)
Backward Compatibility Backward Compatibility
--------------------- ----------------------
Existing code continues to work through backward compatibility features: Existing code continues to work through backward compatibility features:
@ -89,10 +89,10 @@ Existing code continues to work through backward compatibility features:
Example Example
------- -------
See :doc:`examples/doc-examples/multiple_connections_example.py` for a complete working example. A complete working example is available in the `examples/doc-examples/multiple_connections_example.py` file.
Production Configuration Production Configuration
----------------------- -------------------------
For production use, consider these settings: For production use, consider these settings:
@ -121,7 +121,7 @@ For production use, consider these settings:
) )
Architecture Architecture
----------- ------------
The implementation follows the same architectural patterns as the Go and JavaScript reference implementations: The implementation follows the same architectural patterns as the Go and JavaScript reference implementations: