How to build standalone binary when using pytauri-wheel? #297
Replies: 1 comment
|
In fact, your frontend code is never truly secure 😥, even with the Rust version of Tauri (you can Google how to reverse-engineer frontend code from Tauri). |
|
In fact, your frontend code is never truly secure 😥, even with the Rust version of Tauri (you can Google how to reverse-engineer frontend code from Tauri). |
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone,
I’m new to PyTauri, but I already like it a lot especially because it bundles Tauri, which is stable and provides many ready-to-use APIs. I also really appreciate that the PyTauri team provides pytauri-wheel, allowing us to use PyTauri without installing Rust or a C compiler.
However, I couldn’t find any documentation or tutorials explaining how to build a standalone binary when using the pytauri-wheel variant. The current documentation seems to focus only on the standard PyTauri setup.
Does anyone have guidance or experience on how to properly build a standalone binary with pytauri-wheel?
My current approach is using PyInstaller, but it requires manually copying (or configuring via a .spec file) the following files into the _internal folder inside dist:
I’m not sure if this is the recommended or best approach, especially since it exposes Tauri internal configuration files and frontend static assets as plain files in the distribution.
Any advice or best practices would be greatly appreciated.
Thanks in advance,
Regards,
Naufal
All reactions