Raspberry Pi Server Deployment

[ohjah]

Hello, i want to build a dioxus server executable that should run as a service on my rpi.

I have a problem with building the executable. doesent matter wich build command i use, non of them works.
i cannot tell if this is a me problem or a dioxus problem.
i also cannot tell what command is technicly the correct one but i guess its dx build --platform server

[package]
name = "server"
version = "0.1.0"
edition = "2021"

[dependencies]
dioxus = { version = "0.7.10", default-features = false, features = ["router", "fullstack"] }
dioxus-primitives = { git = "https://github.com/DioxusLabs/components", version = "0.0.1", default-features = false }
serde = { version = "1", features = ["derive"] }
wasm-bindgen = {version = "0.2.127"}


[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
axum-extra = "^0.10.1"
dioxus-liveview = "0.7.10"

[features]
default = ["server"]
server = ["dioxus/server", "dioxus/fullstack"]
web = ["dioxus/web"]
desktop = ["dioxus/desktop"]
mobile = ["dioxus/mobile"]

[profile.wasm-dev]
inherits = "dev"
opt-level = 1

[profile.server-dev]
inherits = "dev"

[profile.android-dev]
inherits = "dev"

when i do dx build --platform server i get:

1.341s  INFO Compiled [401/512]: dioxus_primitives
8.975s  INFO Compiled [402/512]: server
9.469s  INFO Bundling app...
9.562s  INFO Client build completed successfully! 🚀 path="/home/user/Development/server/target/dx/server/debug/web"

/home/user/Development/server/target/dx/server/debug/web/server 
2026-08-19T00:10:43.580912Z  WARN dioxus_server::config: No index.html found in public directory, using default index.html
2026-08-19T00:10:43.581333Z  INFO dioxus_server::server: Registering: GET /meaning/

when i do dx build --platform web i get:

1.125s  INFO Compiled [401/512]: dioxus_primitives
9.293s  INFO Compiled [402/512]: server
9.810s  INFO Bundling app...
10.189s INFO Client build completed successfully! 🚀 path="/home/user/Development/server/target/dx/server/debug/web"

/home/user/Development/server/target/dx/server/debug/web/server 
2026-08-19T09:25:19.949425Z  WARN dioxus_server::config: No index.html found in public directory, using default index.html
2026-08-19T09:25:19.949864Z  INFO dioxus_server::server: Registering: GET /meaning/

when i do cargo build --release --features server i get:

Compiling dioxus-attributes v0.1.0 (https://github.com/DioxusLabs/components#bf007c15)
Compiling num-integer v0.1.47
Compiling dioxus-liveview v0.7.10
Compiling server v0.1.0 (/home/user/Development/server)
Finished `release` profile [optimized] target(s) in 7m 08s

/home/user/Development/server/target/release/server 
2026-08-19T09:36:25.268316Z  WARN dioxus_server::config: No index.html found in public directory, using default index.html
2026-08-19T09:36:25.268461Z  INFO dioxus_server::server: Registering: GET /meaning/

thread 'main' (185751) panicked at /home/user/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/dioxus-server-0.7.10/src/server.rs:409:29:
Couldn't read public directory at "/home/user/Development/server/target/release/public": No such file or directory (os error 2)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[tt-a1i]

The first two commands are actually succeeding. The log shows the bundle finishing, and the generated server starts and registers your route. The important part is that a Dioxus fullstack deployment is a directory, not a standalone server binary.

For a production build, use:

dx bundle --web --release

Then deploy the whole target/dx/server/release/web directory. It should contain both items next to each other:

web/
  server
  public/

Dioxus 0.7.10 looks for static files at public beside the running executable. That explains the cargo build result: Cargo produced target/release/server, but it did not create the companion public directory, so the binary panics on startup. DIOXUS_PUBLIC_PATH can override that location, but copying the complete bundle is simpler.

The remaining Raspberry Pi detail is the CPU target. Build on the Pi itself, or cross-compile the server for the Pi architecture, usually aarch64-unknown-linux-gnu on a 64-bit OS. Copying an x86_64 server binary will not work even if the public directory is present. For a systemd service, also set IP=0.0.0.0 and the desired PORT if the server must be reachable from another machine.