andurel

command module
v1.0.0-rc.1 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Jul 6, 2026 License: MIT Imports: 6 Imported by: 0

README

andurel-logo

Andurel - Rails-like Web Framework for Go

Go Version License Go Reference Go Report Card Coverage


Andurel is a comprehensive web development framework for Go. It prioritizes development speed. Inspired by Ruby on Rails, it uses just enough conventions to let you build full-stack web applications incredibly fast.

Join the discord here

Platform Support

Andurel currently supports Linux and macOS only. Windows is not supported at this time.

If you'd like to help bring Windows support to Andurel, please see issue #382 - contributions are welcome!


Why Andurel?

Development speed is everything. Andurel eliminates boilerplate and lets you focus on building features:

  • Instant Scaffolding - Generate complete CRUD resources with one command
  • Live Reload - Hot reloading for Go, templates, and CSS with andurel run powered by Shadowfax
  • Type Safety Everywhere - Bun for SQL, Templ/Vue for HTML, Go for logic
  • Batteries Included — Echo, Datastar, background jobs, sessions, CSRF protection, telemetry, email support, authentication, optional extensions (docker, aws-ses, css-components)
  • Dependency Injection — Declarative application wiring with go.uber.org/fx
  • Two Frontend Options — Server-rendered HTML with Templ + Datastar for hypermedia interactivity, or Inertia SPA with Vue 3 or React + Vite for a reactive single-page app
  • Production Build — One command (andurel build) to compile everything: Templ, Tailwind CSS, Vite assets, and Go binary
  • Just enough Convention - Convention over configuration is great to a certain point. Andurel provides just enough sensible defaults that just work and get out of your way.
  • PostgreSQL-Backed - Built on PostgreSQL with River job queues, pgx driver, and UUID support

The core philosophy around resource generation in andurel, is that it should be a one-time operation that creates everything you need for a fully functional CRUD interface. After that, you can modify and extend the generated code as needed but it's yours to manage going forward.

Core Technologies

  • Echo - High-performance HTTP framework
  • Tailwind CSS - Utility-first CSS tooling
  • Bun - Type-safe SQL ORM and query builder
  • Templ - Type-safe HTML templates
  • Datastar - Hypermedia-driven frontend interactivity
  • River - PostgreSQL-backed background jobs and workflows
  • OpenTelemetry - Built-in observability
  • PostgreSQL - Powerful open-source database with pgx driver and native UUID support
  • Shadowfax - Andurel-specific app runner
  • go.uber.org/fx - Dependency injection framework
  • gonertia - Inertia.js Go adapter (optional, --inertia vue or --inertia react; append /pnpm, /bun, or /yarn to set JS runtime)
  • Vue.js / React - JavaScript UI adapters (optional, via Inertia)
  • Vite - Next-generation frontend build tool (optional, via Inertia)

Quick Start

Installation
go install github.com/mbvlabs/andurel@v1.0.0-beta.5
Create Your First Project

Andurel gives you choices when creating a new project:

# Create a new project (PostgreSQL + Tailwind CSS)
andurel new myapp

# Add extensions for additional features:
andurel new myapp -e docker              # Add Dockerfile for containerization
andurel new myapp -e aws-ses             # Add AWS SES email integration

# Choose your frontend approach:
andurel new myapp --inertia vue           # Inertia SPA with Vue 3 + Vite (JS runtime: npm)
andurel new myapp --inertia react/pnpm    # Inertia SPA with React + Vite (JS runtime: pnpm)
andurel new myapp --inertia vue/bun       # Inertia SPA with Vue 3 + Vite (JS runtime: bun)

# Combine options:
andurel new myapp --inertia vue -e docker

cd myapp

# Sync tools
andurel tool sync

# Configure environment
cp .env.example .env

# Note: you need to edit .env with your database details

# Install JS dependencies (only if using --inertia vue/react)
andurel new prints the correct package manager command based on the configured runtime (npm/pnpm/bun/yarn)

# Apply database migrations
andurel database migrate up

# Run the development server (with live reload)
andurel run

Your app is now running on http://localhost:8080

Database Lifecycle Commands

Andurel provides commands to manage your database lifecycle:

# Create the configured database
andurel database create                    # Requires .env to be filled out with DB credentials

# Drop the configured database (prompts for confirmation)
andurel database drop
andurel database drop --force              # Allow dropping system databases

# Drop and recreate the database
andurel database nuke
andurel database nuke --force              # Allow nuking system databases

# Full rebuild: drop, recreate, migrate, and seed
andurel database rebuild
andurel database rebuild --force           # Allow rebuilding system databases
andurel database rebuild --skip-seed       # Skip seeding after migrations
Generate Your First Resource
# Create a migration and add the columns you need. Resource generation requires
# an `id` primary key (uuid/serial/bigserial/string-supported types). `created_at`
# and `updated_at` are optional but recommended.
andurel database migrate new create_products_table

# Create a complete resource with model, controller, views, and routes
andurel generate scaffold Product

This single command creates everything you need for a full CRUD interface: model, factory, controller, Templ views, and resource routes. Pass --inertia when you want the generated resource/controller views as Inertia pages instead (reads the adapter from andurel.lock).

CLI Commands

andurel new — Create a new project

Scaffolds a complete Andurel project with the given name.

andurel new (alias: n) [project-name] [flags]
Flag Description
-e, --extensions Comma-separated extensions to enable (e.g. docker,aws-ses,css-components)
--inertia Frontend adapter: vue or react. Optionally append /npm, /pnpm, /bun, or /yarn to set JS runtime (default: npm). Example: --inertia vue/pnpm
andurel generate — Code generation

Generate models, controllers, and scaffolds from your existing database migrations.

andurel generate (alias: g) model NAME [flags]
andurel generate view (alias: v)
andurel generate controller (alias: c) NAME [action ...] [flags]
andurel generate scaffold (alias: s) NAME [flags]
andurel generate job (alias: j) NAME [flags]
andurel generate email (alias: e) NAME

generate model — Creates a model from a database migration, or updates an existing one. Fields, types, and timestamps are read from the migration automatically.

Flag Description
--skip-factory Skip generating a factory file
--table-name Override the default table name (e.g. --table-name=people_data)
--update Update an existing model from migration changes
--yes Apply changes without prompting for confirmation (use with --update)
--primary-key Specify the primary key column (skips interactive detection)

generate controller — Creates a controller for a resource. With no actions, it generates the full standard CRUD controller, views, and routes. With one or more standard CRUD actions (index, show, new, create, edit, update, destroy), it generates only those resource actions; partial CRUD views are self-contained and only link to companion actions that are also present. Generated resource/controller views default to Templ in every project; pass --inertia to generate Inertia pages (uses the adapter from andurel.lock).

Non-CRUD actions create standalone/custom controller actions. They add empty controller methods, matching Templ components by default or Inertia pages with --inertia, and conventional GET routes:

andurel generate controller Dashboard overview

Generates:

Artifact Example
Controller method controllers/dashboards.go: Dashboards.Overview
Templ view views/dashboards_resource.templ: DashboardOverview()
Route variable router/routes/dashboards.go: DashboardOverview
Route registration GET /dashboards/overview named dashboards.overview

Custom-only controller generation does not require a model or migration. If any CRUD action is requested, generation is model-backed and still requires an existing model/migration.

Use --model-name when the controller/resource name should differ from the model it is backed by:

andurel generate controller Dashboard --model-name User
andurel generate controller Dashboard index overview --model-name User

In this mode, controller/UI artifacts use Dashboard (controllers/dashboards.go, views/dashboards_resource.templ, /dashboards routes), while model calls and entity types use User (models.User.Paginate, models.User.Find, models.UserEntity, models.CreateUserData, models.UpdateUserData). This is only for generate controller; generate scaffold keeps the existing one-resource-name behavior.

Use --api to generate a JSON API controller instead. The controller is placed under controllers/api with echo.JSON responses and no views:

andurel generate controller Users --api
andurel generate controller admin/Widget export --api

When --api is set, the namespace is forced to "api" (overriding any namespace segment in the name), and the default action set excludes new and edit. Custom actions create etx.JSON(http.StatusOK, map[string]any{}) stubs.

Flag Description
--model-name Use a different existing model for model-backed controller generation
--inertia Generate Inertia views using the adapter configured in andurel.lock
--api Generate a JSON API controller under controllers/api without views

generate view — Generates Go code from .templ template files (runs templ generate).

generate scaffold — Convenience command that runs generate model + generate controller with full CRUD actions (index, show, new, create, edit, update, destroy). By default generates Templ views, including in projects created with Inertia; pass --inertia for Inertia views (reads the adapter from andurel.lock).

Flag Description
--skip-factory Skip generating a factory file
--table-name Override the default table name
--inertia Generate Inertia views using the adapter configured in andurel.lock
--api Generate a JSON API controller under controllers/api without views
--primary-key Specify the primary key column (skips interactive detection)
andurel fmt — Format source files

Formats Go and Templ source files in the project.

andurel fmt (alias: f) [flags]
Flag Description
--check Check formatting without modifying files (CI-friendly)
--skip-templ Skip Templ formatting
--skip-go Skip Go formatting (go fmt and golines)

Runs go fmt ./..., golines -w -m 100 ., and templ fmt on views/ and email/ directories.

andurel database — Database management

Manage the full database lifecycle.

andurel database (aliases: d, db)
andurel database create
andurel database drop [--force]
andurel database nuke [--force]
andurel database rebuild [--force] [--skip-seed]
andurel database seed
andurel database migrate (aliases: m, mig)

database migrate subcommands:

Subcommand Description
new [name] (alias: n) Create a new SQL migration file
up Apply all pending migrations
down Roll back the most recently applied migration
status (alias: st) Show current migration version and status
fix Re-number migrations to close gaps
reset (alias: rs) Roll back all migrations, then re-apply them
up-to [version] (alias: upto) Apply migrations up to a specific version
down-to [version] (alias: downto) Roll back migrations down to a specific version
andurel build — Production build

Build the application binary and compile all assets for production deployment.

andurel build [--version]

Runs Templ generation, minifies Tailwind CSS, installs NPM dependencies and builds Vite assets (if using Inertia), downloads Go dependencies, and compiles a static Linux binary.

Flag Description
--version Set the application version (injected via ldflags)
andurel run — Development server

Starts the development server with live reload (powered by Shadowfax).

andurel run (alias: r)
andurel console — Database console

Opens an interactive database console (usql) using connection details from .env.

andurel console (alias: c)
andurel tool — Project tools and binaries

Manage CLI tools and binaries used by your project. Tools are defined in andurel.lock and downloaded to bin/.

andurel tool (alias: t)
andurel tool sync
andurel tool set-version <tool> <version>
andurel tool dblab (alias: d)
andurel tool mailpit (alias: m)
Subcommand Description
sync (alias: s) Download and validate binaries specified in andurel.lock
set-version (alias: sv) Set a specific tool version (e.g. templ 0.3.977)
dblab (alias: d) Open the dblab database UI in the browser
mailpit (alias: m) Run the Mailpit email testing server (SMTP :1025, HTTP :8025)
andurel extension — Project extensions

Add and list optional framework features. Adding an extension to an existing project generates its code files, updates framework-managed files (config.go, .env.example, main.go, etc.), and records it in andurel.lock. Commit or create a branch before adding an extension, as it modifies files in place.

andurel extension (aliases: ext, e)
andurel extension add (alias: a) [extension-name]
andurel extension list (alias: ls)

Available extensions: docker, aws-ses, css-components.

andurel upgrade — Framework upgrade

Upgrade framework-managed files and tool versions to the latest.

andurel upgrade (alias: up) [--dry-run]

Commit or create a branch before upgrading — this command modifies files in place.

andurel doctor — Project diagnostics

Run comprehensive diagnostic checks (Go version, config, code quality, code generation).

andurel doctor (alias: doc) [--verbose]

Alias Reference
Full Command Alias(es)
andurel new n
andurel generate g
andurel generate model m
andurel generate view v
andurel generate controller c
andurel generate scaffold s
andurel generate job j
andurel generate email e
andurel fmt f
andurel database d, db
andurel database create crt
andurel database seed s
andurel database rebuild rb
andurel database migrate m, mig
andurel database migrate new n
andurel database migrate status st
andurel database migrate reset rs
andurel database migrate up-to upto
andurel database migrate down-to downto
andurel run r
andurel console c
andurel tool t
andurel tool sync s
andurel tool set-version sv
andurel tool dblab d
andurel tool mailpit m
andurel extension ext, e
andurel extension add a
andurel extension list ls
andurel upgrade up
andurel doctor doc

Project Structure

Andurel generates a complete project based on your chosen options. Below is the default structure, followed by what changes with each option.

Default Project
myapp/
├── assets/                  # Static assets (served at /assets/)
│   ├── assets.go
│   ├── css/
│   │   └── style.css       # Compiled Tailwind output
│   └── js/
│       ├── datastar_1-0-1.min.js
│       └── scripts.js
├── clients/
│   └── email/
│       └── mailpit.go       # Mailpit email client
├── cmd/
│   └── app/
│       └── main.go          # Application entry point with fx wiring
├── config/
│   ├── config.go            # Main config aggregator
│   ├── app.go               # Sessions, tokens, security
│   ├── auth.go              # Authentication config
│   ├── database.go          # Database connection config
│   ├── email.go             # Email configuration
│   └── telemetry.go         # Logging, tracing, metrics
├── controllers/
│   ├── controller.go        # Controller module setup
│   ├── api.go
│   ├── assets.go
│   ├── cache.go             # Cache control utilities
│   ├── confirmations.go
│   ├── pages.go
│   ├── registrations.go
│   ├── reset_passwords.go
│   └── sessions.go
├── css/
│   ├── base.css             # Tailwind CSS source input
├── database/
│   ├── database.go          # Database connection helper
│   ├── test_helper.go       # Test database setup
│   ├── migrations/          # SQL migration files (goose)
│   └── seeds/
│       └── main.go          # Database seeder
├── email/
│   ├── email.go
│   ├── base_layout.templ
│   ├── components.templ
│   ├── reset_password.templ
│   └── verify_email.templ
├── internal/
│   ├── hypermedia/          # HTML-over-the-wire helpers
│   │   ├── broadcaster.go
│   │   ├── core.go
│   │   ├── helpers.go
│   │   ├── options.go
│   │   ├── render.go
│   │   ├── script.go
│   │   ├── signals.go
│   │   └── sse.go
│   ├── request/
│   │   ├── context.go
│   │   └── request.go
│   ├── routing/
│   │   ├── definitions.go
│   │   └── routes.go
│   ├── server/
│   │   └── server.go
│   └── storage/
│       ├── psql.go
│       └── queue.go
├── models/
│   ├── model.go
│   ├── errors.go
│   ├── token.go
│   ├── user.go
│   └── factories/           # Model factories for testing
│       ├── factories.go
│       ├── token.go
│       └── user.go
├── queue/
│   ├── queue.go
│   ├── jobs/
│   │   ├── send_marketing_email.go
│   │   └── send_transactional_email.go
│   └── workers/
│       ├── workers.go
│       ├── send_marketing_email.go
│       └── send_transactional_email.go
├── router/
│   ├── router.go            # Main router setup
│   ├── cookies/
│   │   ├── cookies.go
│   │   └── flash.go
│   ├── middleware/
│   │   ├── middleware.go
│   │   └── auth.go
│   └── routes/
│       ├── api.go
│       ├── assets.go
│       ├── pages.go
│       └── users.go
├── services/
│   ├── authentication.go
│   ├── registration.go
│   └── reset_password.go
├── telemetry/
│   ├── telemetry.go
│   ├── options.go
│   ├── logger.go
│   ├── log_exporters.go
│   ├── metrics.go
│   ├── metric_exporters.go
│   ├── tracer.go
│   ├── trace_exporters.go
│   └── helpers.go
├── views/                    # Templ templates
│   ├── layout.templ
│   ├── head.templ
│   ├── home.templ
│   ├── bad_request.templ
│   ├── confirm_email.templ
│   ├── internal_error.templ
│   ├── login.templ
│   ├── not_found.templ
│   ├── registration.templ
│   ├── reset_password.templ
│   └── components/
├── .env.example
├── .gitignore
├── andurel.lock              # Tool version lock file
├── go.mod
└── go.sum
Inertia Mode (--inertia vue or --inertia react)

When using the Inertia SPA frontend, these files are added:

myapp/
├── resources/
│   └── js/
│       ├── app.ts/app.tsx       # Vue/React + Inertia app entry point
│       └── Pages/
│           └── Welcome.vue/tsx  # Home page component
├── views/
│   ├── root.go.html             # Inertia root HTML shell
│   └── (no home.templ — replaced by Vue Welcome page)
├── internal/
│   └── inertia/
│       ├── render.go            # Inertia response helpers
│       └── vite.go              # Vite dev/prod manifest resolver
├── vite.config.ts
├── package.json
├── tsconfig.json

The controllers/pages.go uses Inertia rendering instead of Templ, and cmd/app/main.go initializes internal/inertia. Run the configured package manager's install command after scaffolding (the andurel new output shows the right command based on the configured runtime). Later resource/controller generation still defaults to Templ; pass --inertia to andurel generate controller or andurel generate scaffold for Inertia resource pages (reads the adapter from andurel.lock).

When using --inertia vue or --inertia react, controllers can render Inertia pages alongside Templ.

You can specify the JS runtime by appending /npm, /pnpm, /bun, or /yarn to the adapter name:

  • --inertia vue — uses npm (default)
  • --inertia vue/pnpm — uses pnpm
  • --inertia react/bun — uses bun
  • --inertia react/yarn — uses yarn

The runtime is stored in andurel.lock as javascriptRuntime.

Real Example: Controller to Vue Component

Here's how a controller passes data to a Vue component via Inertia, from route definition to rendered page.

Route Definition
// router/routes/pages.go
var HomePage = routing.NewSimpleRoute("/", "pages.home", "")
Route Registration
// controllers/pages.go
func (p Pages) RegisterRoutes(r *router.Router) error {
    _, err := r.AddRoute(echo.Route{
        Method:  http.MethodGet,
        Path:    routes.HomePage.Path(),
        Name:    routes.HomePage.Name(),
        Handler: p.Home,
    })
    return err
}
Controller
// controllers/pages.go
func (p Pages) Home(etx *echo.Context) error {
    return inertia.Page(etx, "Welcome", inertia.Props{
        "appName": "MyApp",
    })
}
Vue Component
<!-- resources/js/Pages/Welcome.vue -->
<script setup lang="ts">
import { Head } from '@inertiajs/vue3'

defineProps<{
  appName: string
}>()
</script>

<template>
  <Head :title="appName" />
  <div class="min-h-screen flex items-center justify-center bg-gray-50">
    <div class="text-center">
      <h1 class="mb-4 text-4xl font-bold text-gray-900">{{ appName }}</h1>
      <p class="text-gray-600">Built with Andurel + Inertia + Vue</p>
    </div>
  </div>
</template>
CRUD Index Example

For paginated list views, the controller queries data and passes it as props:

// controllers/widgets.go
func (w Widgets) Index(etx *echo.Context) error {
    page := int64(1)
    if p := etx.QueryParam("page"); p != "" {
        if parsed, err := strconv.Atoi(p); err == nil && parsed > 0 {
            page = int64(parsed)
        }
    }
    perPage := int64(25)

    widgets, err := models.Widget.Paginate(
        etx.Request().Context(), w.db.Executor(), page, perPage,
    )
    if err != nil {
        return inertia.Page(etx, "Errors/InternalError", inertia.Props{})
    }

    return inertia.Page(etx, "Widget/Index", inertia.Props{
        "items": widgets.Widgets,
    })
}
<!-- resources/js/Pages/Widget/Index.vue -->
<script setup lang="ts">
import { Head, Link } from '@inertiajs/vue3'

defineProps<{
  items: Array<Record<string, unknown>>
}>()
</script>

<template>
  <Head title="Widgets" />
  <div>
    <h1>Widgets</h1>
    <Link :href="'/widgets/create'">New Widget</Link>
    <table>
      <tr v-for="item in items" :key="item.id">
        <td>{{ item.name }}</td>
        <td>
          <Link :href="`/widgets/${item.id}`">View</Link>
          <Link :href="`/widgets/${item.id}/edit`">Edit</Link>
        </td>
      </tr>
    </table>
  </div>
</template>

Flash messages set via cookies.AddFlash() in the controller are automatically injected into Inertia props as flash and displayed as toast notifications in the Vue app entry point.

Contributing

Contributions are welcome! Here's how to get started:

  1. Fork the repository
  2. Create a feature branch: git checkout -b feature/amazing-feature
  3. Make your changes and add tests
  4. Run quality checks: go vet ./... and golangci-lint run
  5. Commit your changes: git commit -m 'Add amazing feature'
  6. Push to the branch: git push origin feature/amazing-feature
  7. Open a Pull Request
Development Setup
git clone https://github.com/mbvlabs/andurel
cd andurel
go mod download
go test ./...

License

This project is licensed under the MIT License - see the LICENSE file for details.

Tech Stack

Andurel is built on top of excellent open-source projects:

  • Echo - High-performance HTTP router and framework
  • Bun - Type-safe SQL ORM and query builder
  • Templ - Type-safe Go templates
  • Datastar - Hypermedia-driven frontend interactivity (RC6)
  • River - Fast PostgreSQL-backed job queue and workflows
  • OpenTelemetry - Observability framework for logs, traces, and metrics
  • pgx - PostgreSQL driver and toolkit
  • Tailwind CSS - Utility-first CSS tooling
  • Cobra - CLI framework

Acknowledgments

Inspired by Ruby on Rails and its philosophy that developer happiness and productivity matter. Built for developers who want to move fast without sacrificing type safety or code quality.


Sites build with Andurel

Here is a collection of sites and projects, I've built with this framework:

If you build something cool with Andurel, let me know and I will add it to the list (or open a PR)!


Author

Created by Morten Vistisen

Feel free to reach out to me on:

If you have any questions!

Documentation

The Go Gopher

There is no documentation for this package.

Directories

Path Synopsis
cli
Package cli provides the command-line interface for the Andurel framework.
Package cli provides the command-line interface for the Andurel framework.
output
Package output defines the shared CLI response contract for agent-friendly output modes.
Package output defines the shared CLI response contract for agent-friendly output modes.
e2e
Package layout provides functionality to scaffold a new Go web application project
Package layout provides functionality to scaffold a new Go web application project
blueprint
Package blueprint provides structured types for scaffold configuration that support additive merges from multiple extensions without conflicts.
Package blueprint provides structured types for scaffold configuration that support additive merges from multiple extensions without conflicts.
cmds
Package cmds holds commands being used for scaffolding
Package cmds holds commands being used for scaffolding
extensions
Package extensions provides the framework for registering and applying extensions to the scaffold generation process.
Package extensions provides the framework for registering and applying extensions to the scaffold generation process.
pkg

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL