Skip to main content

IO

No SDKs
·156 words·1 min
No third-party SDKs are used by IO to call networked APIs.
Use SCP and SFTP
·86 words·1 min
Use SCP and SFTP to configure and observe IO.
Use SSH to connect to IO
·94 words·1 min
Use SSH to make the IO TUI available to remote users.
Use Vault
·94 words·1 min
Build Vault integration and use Vault to manage secrets.
Internalize Protobuf Codegen
·116 words·1 min
All protobuf support code that IO uses is generated within the project.
Build ATProto OAuth Support
·103 words·1 min
Build support for AT Protocol Authorization directly into IO.
Build OAuth Support
·92 words·1 min
Build support for OAuth into IO.
Use Nomad
·74 words·1 min
Build Nomad integration and use Nomad to manage containers.
Use HCL
·92 words·1 min
Configure IO with the Hashicorp Configuration Language.
Build ACME Support
·81 words·1 min
Build support for the ACME protocol into IO to automatically provision SSL certificates.
Use SQLite
·92 words·1 min
Use SQLite for IO internal storage and general data persistence.
Use Bubble Tea
·77 words·1 min
Use Bubble Tea to build a terminal user interface for IO.
Name the proxy "IO"
·39 words·1 min
Use “IO” to clearly assert the project’s goals.
Use Linux Abstract Sockets
·56 words·1 min
Use Linux Abstract Sockets for local communication.
Build an Envoy Controller
·83 words·1 min
IO is an Envoy controller and Envoy is a core component of IO.