Live Reload
WebSocket-based live reload for a fast development workflow.
Starting the dev server
Run the development server with:
tulip serveThis starts a local HTTP server and watches your project for changes.
How it works
- tulip starts an HTTP server serving the build output
- A WebSocket connection is established between the browser and the server
- tulip watches all project files (templates, content, static assets, configuration)
- When a file changes, tulip rebuilds the project
- After the rebuild completes, a reload signal is sent over the WebSocket
- The browser automatically refreshes the page
What is watched
The file watcher monitors all project files, including:
- Template files (
.tulip) - Markdown content (
.md) - Static assets (images, CSS, JS)
- Configuration (
tulip.toml) - Custom styles (
styles.css)
Port configuration
By default, the dev server runs on port 3000. You can specify a different port:
tulip serve --port 8080Or configure it in tulip.toml:
[dev]
port = 8080Auto-rebuild
Every file change triggers a rebuild. Edit a template, save, and the browser updates instantly.