mirror of https://github.com/euzu/tuliprox.git synced 2026-10-10 01:42:30 +02:00

Files

T

euzuandGitHub f0459e7e14 Fix/hls connect m3u parsing probe resolve (#646 )

* Fix HLS session handling and disable retry for adaptive segment requests
* Resolve / probe vod task uses last modified date
* Resolve expiration date in input form
* fixed m3u parsing
* fixed wasm opt for frontend build

2026-03-15 23:32:09 +01:00

2.6 KiB

Raw Blame History

Deployment

Backend and frontend

Tuliprox consists of:

a Rust backend
a Yew/WebAssembly frontend
static assets served from the configured web root

Documentation delivery

The recommended documentation workflow is:

write docs as Markdown in docs/src
generate static HTML with mdBook into frontend/build/docs
copy the generated site into frontend/dist/static/docs during the web build

That gives you editable source files in Git without committing hand-written HTML.

Why `mdBook`

For this repository, mdBook is the most pragmatic choice because it:

keeps source in Markdown
generates static HTML
fits naturally into a Rust-based project
avoids the overhead of a full Node/React documentation stack

Main build commands

Build docs only:

make docs

Preview docs locally:

make docs-serve

Build frontend plus docs together:

make web-dist

This does:

mdbook build -> frontend/build/docs
trunk build -> frontend/dist
copy docs -> frontend/dist/static/docs

Docker build

Build the project image manually:

docker build --rm -f docker/Dockerfile -t tuliprox .

For the local development image, adapt your compose file to point to the locally built image.

Static binary builds

Recommended musl build:

cross build -p tuliprox --release --target x86_64-unknown-linux-musl

Manual prerequisite install on Debian or Ubuntu:

rustup update
sudo apt-get install pkg-config musl-tools libssl-dev
rustup target add x86_64-unknown-linux-musl

Then:

cargo build -p tuliprox --release --target x86_64-unknown-linux-musl

Multi-platform helper scripts

The repository ships helper scripts under bin/:

bin/build_docs.sh
bin/build_fe.sh
bin/build_local.sh
bin/build_docker.sh
bin/release.sh

bin/build_fe.sh is the shared entry point for docs plus frontend assets.

Wasm optimization is handled by Trunk during the build (via data-wasm-opt in index.html). Trunk requires a compatible wasm-opt in PATH.

Recommended local setup:

./bin/install_wasm_tools.sh 128
export PATH="$PWD/.tools/wasm-tools/version_128/bin:$PATH"
./bin/build_fe.sh release

Healthcheck

Tuliprox supports:

tuliprox --healthcheck

This can be wired into Docker healthchecks.

Cross-compilation notes

Windows:

rustup target add x86_64-pc-windows-gnu
cargo build -p tuliprox --release --target x86_64-pc-windows-gnu

Raspberry Pi / armv7:

cross build -p tuliprox --release --target armv7-unknown-linux-musleabihf

2.6 KiB Raw Blame History