Documenting code, one commit at a time.
This post details a recent cleanup in the ERP-1st project, focusing on optimizing the Tauri build process.
The tauri.conf.json file, the configuration hub for Tauri applications, had accumulated some unnecessary baggage. Specifically, the beforeBuildCommand and some unused resources were lingering, potentially adding complexity and overhead to the build process.
When building cross-platform applications with Tauri, one challenge is packaging backend resources efficiently. We recently tackled this in the ERP-1st project, ensuring that our application bundles included necessary backend components and handled platform-specific fallbacks.
This post details our approach to bundling backend resources and providing a Python fallback mechanism
This post details the process of generating an NSIS (Nullsoft Scriptable Install System) installer for a Tauri application, allowing for easy distribution and installation on Windows.
NSIS is a script-driven installer authoring tool for Windows. It's a popular choice for creating installers because it's free, flexible, and supports a wide range of features.
Ever struggled with CORS errors in your Tauri application? Configuring Cross-Origin Resource Sharing (CORS) can be tricky, especially when dealing with local development and production deployments. Let's explore a common issue and its solution within a Tauri v2 environment.
Tauri, by default, enforces strict CORS policies for enhanced security.