Windows binary support

[lukebelbina]

On the readme it says there are windows binaries on the releases but I noticed after 1.0 there are no longer windows binaries.

Do you know if this is a mistake or have you dropped support for deploying windows binaries?

Thanks for all the work!

[Propfend]

thats true, i can try to add it.

[mcharytoniuk]

@lukebelbina We intially supported Windows binaries before rewriting the project to Rust + Pingora for better networking features. We planned to add it back, but just didn't do that yet.

@Propfend Thanks a lot. :)

[lukebelbina]

Awesome sounds good. Any idea on the ETA? No rush on my end, I have a spare windows gaming machine lying around I'd like to throw into my cluster.

[Propfend]

whats "ETA"?

[mcharytoniuk]

@Propfend

whats "ETA"?

Estimated time of arrival/estimated time on how long it will take to finish the task.

@lukebelbina

We need to reconfigure the GitHub workflow and add some cross-compile scripts to generate downloadable .exe files, but from what we tested, it works fine under Windows. Idk, it will maybe take a day or two.

You can also try compiling the project on your own in the meantime - you only need Rust (and Node if you need the web dashboard). Just cloning the repo and running cargo build should be enough.

If you need the web dashboard, then you first need to create front-end assets with this:

paddler/Makefile

Lines 29 to 48 in 9eb79e3

	npm exec esbuild -- \
	--bundle \
	--asset-names="./[name]" \
	--entry-names="./[name]" \
	--format=esm \
	--loader:.jpg=file \
	--loader:.otf=file \
	--loader:.svg=file \
	--loader:.ttf=file \
	--loader:.webp=file \
	--metafile=esbuild-meta.json \
	--minify \
	--outdir=static \
	--sourcemap \
	--splitting \
	--target=safari16 \
	--tree-shaking=true \
	resources/css/reset.css \
	resources/css/page-dashboard.css \
	resources/ts/controller_dashboard.tsx \

Then cargo build --features web_dashboard later.

[Propfend]

Yes, and the cross compiling to MacOS is really a pain, its toolchain is not provided, so we just cant include this OS as target on the workflow. And what we have are some very hard workarounds like osxcross, which after building, may still fail in a MacOS device. I wonder how thats done in golang though.