* feat(v3): add server mode for headless HTTP deployment Server mode allows Wails applications to run as pure HTTP servers without native GUI dependencies. Enable with `-tags server` build tag. Features: - HTTP server with configurable host/port via ServerOptions - WAILS_SERVER_HOST and WAILS_SERVER_PORT env var overrides - WebSocket event broadcasting to connected browsers - Browser clients represented as BrowserWindow (Window interface) - Health check endpoint at /health - Graceful shutdown with configurable timeout - Docker support with Dockerfile.server template and tasks Build and run: wails3 task build:server wails3 task run:server wails3 task build:docker wails3 task run:docker Documentation at docs/guides/server-build.mdx Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(v3): add server mode for headless HTTP deployment Server mode allows Wails applications to run as pure HTTP servers without native GUI dependencies. Enable with `-tags server` build tag. Features: - HTTP server with configurable host/port via ServerOptions - WAILS_SERVER_HOST and WAILS_SERVER_PORT env var overrides - WebSocket event broadcasting to connected browsers - Browser clients represented as BrowserWindow (Window interface) - Health check endpoint at /health - Graceful shutdown with configurable timeout - Docker support with Dockerfile.server template and tasks Build and run: wails3 task build:server wails3 task run:server wails3 task build:docker wails3 task run:docker Documentation at docs/guides/server-build.mdx Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: address CodeRabbit review comments - Fix corrupted test file with embedded terminal output - Fix module name mismatch in gin-routing (was gin-example) - Fix replace directive version mismatch in gin-service - Fix placeholder module name in ios example (was changeme) - Fix Dockerfile COPY path to work from both build contexts - Fix bare URL in README (MD034 compliance) - Fix comment accuracy in getScreens (returns error, not empty slice) - Remove deprecated docker-compose version field - Add port documentation in Taskfile template Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: address CodeRabbit review comments - Add note about healthcheck wget not being available in distroless images - Add !server build constraint to menu_windows.go and menu_darwin.go - Downgrade window-visibility-test go.mod from 1.25 to 1.24 to match CI Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build | ||
| frontend | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
| README.md | ||
| Taskfile.yml | ||
Welcome to Your New Wails3 Project!
Congratulations on generating your Wails3 application! This README will guide you through the next steps to get your project up and running.
Getting Started
-
Navigate to your project directory in the terminal.
-
To run your application in development mode, use the following command:
wails3 devThis will start your application and enable hot-reloading for both frontend and backend changes.
-
To build your application for production, use:
wails3 buildThis will create a production-ready executable in the
builddirectory.
Exploring Wails3 Features
Now that you have your project set up, it's time to explore the features that Wails3 offers:
-
Check out the examples: The best way to learn is by example. Visit the
examplesdirectory in thev3/examplesdirectory to see various sample applications. -
Run an example: To run any of the examples, navigate to the example's directory and use:
go run .Note: Some examples may be under development during the alpha phase.
-
Explore the documentation: Visit the Wails3 documentation for in-depth guides and API references.
-
Join the community: Have questions or want to share your progress? Join the Wails Discord or visit the Wails discussions on GitHub.
Project Structure
Take a moment to familiarize yourself with your project structure:
frontend/: Contains your frontend code (HTML, CSS, JavaScript/TypeScript)main.go: The entry point of your Go backendapp.go: Define your application structure and methods herewails.json: Configuration file for your Wails project
Next Steps
- Modify the frontend in the
frontend/directory to create your desired UI. - Add backend functionality in
main.go. - Use
wails3 devto see your changes in real-time. - When ready, build your application with
wails3 build.
Happy coding with Wails3! If you encounter any issues or have questions, don't hesitate to consult the documentation or reach out to the Wails community.