From a schema to a running app.

You define your data

Every app begins with a resource definition: the fields for one kind of thing. A grocery list has grocery items. That's the whole job.

// grocery-item
fields: {
  name:     { type: 'string', required: true },
  quantity: { type: 'number' },
  category: { type: 'string' },
  bought:   { type: 'boolean' },
}

Homestead builds the backend

On boot it creates a SQLite database on your machine and a REST API for every resource: the usual create, read, update, delete. Users and auth come built in.

POST/api/aep/grocery-items
GET/api/aep/grocery-items
GET/api/aep/grocery-items/{id}
PATCH/api/aep/grocery-items/{id}
DELETE/api/aep/grocery-items/{id}

Read and write from anywhere

Everything goes through that one authenticated API: call it over REST, drive it from the CLI (handy for agents), or just ask the built-in chatbot.

# CLI
$ homestead resources grocery-item create --name "Milk" --quantity 2
$ homestead resources grocery-item list

# REST
$ curl $HOMESTEAD/api/aep/grocery-items \
    -H "Authorization: Bearer $TOKEN"

React apps on top

Homestead builds and serves the React apps that sit on top of that API: the interface your household actually opens. Change them, or write your own.