Pubky Homeserver

A homeserver for Pubky. Stores and serves user data via HTTP APIs with public-key authentication.

For standalone deployment, see the install guide.

Development

Run the homeserver directly from the source tree:

cargo run -p pubky-homeserver -- --data-dir ~/.pubky

See config.sample.toml for all configuration options.

API Specifications

• Client API — user authentication, tenant storage, and event feeds.
• Admin API — homeserver administration and WebDAV operations.

Architecture

• PKARR republishing — cache-first resolution, network fallback, and retry behavior.

Library Usage

Use the homeserver as a library in other crates or for testing.

[dependencies]
pubky-homeserver = "0.x"  # replace with the latest version

HomeserverApp starts the full server stack (client server, admin server, metrics server, DHT republishers):

use pubky_homeserver::HomeserverApp;
use std::path::PathBuf;

#[tokio::main]
async fn main() -> anyhow::Result<()> {
    let app = HomeserverApp::start_with_persistent_data_dir_path(
        PathBuf::from("~/.pubky")
    ).await?;

    println!("Homeserver HTTP: {}", app.icann_http_url());
    println!("Homeserver Pubky TLS: {}", app.pubky_url());

    if let Some(admin) = app.admin_server() {
        println!("Admin server: http://{}", admin.listen_socket());
    }

    tokio::signal::ctrl_c().await?;
    Ok(())
}

For testing, use MockDataDir to create a temporary directory that is cleaned up on drop. Enable the testing feature:

[dev-dependencies]
pubky-homeserver = { version = "0.x", features = ["testing"] }

use pubky_homeserver::{HomeserverApp, MockDataDir, ConfigToml};

let config = ConfigToml::default_test_config();
let mock_dir = MockDataDir::new(config, None).unwrap();
let app = HomeserverApp::start_with_mock_data_dir(mock_dir).await.unwrap();

Binary

See Install and Run Pubky Homeserver for full setup instructions.

pubky-homeserver --data-dir ~/.pubky

Storage

/pub/ is public; /priv/ requires an authenticated session and a covering capability. See Private Storage for the full contract.

Caching and Proxies

Tenant-private responses must never be stored by shared caches. /priv/... data responses and /events-stream use Cache-Control: no-store and vary on pubky-host, Authorization, and Cookie; /pub/... file validators keep their existing tenant-aware caching behavior.

Note: CORS preflight OPTIONS is handled upstream by the CORS layer and carries no private body.