laizy init

The init command sets up a new Laizy CMS project in your current directory. It handles authentication, project creation or selection, and generates the configuration files you need to start building.

Usage

pnpm laizy init

This is an interactive command with no flags. It walks you through the full setup process step by step.

What It Does

? Laizy CMS base URL: (http://localhost:3000)

Starting authentication...
Authentication successful!

? Where should we generate your client? (directory) (./generated/laizy)

? Select a project or create a new one:
  My Website (my-website)
  Blog Platform (blog-platform)
  + Create new project

? Project name: My First Project
? Project slug (URL-friendly): my-first-project
? Project description (optional):

NEXT_PUBLIC_LAIZY_TOKEN=laizy_eyJ...
NEXT_PUBLIC_LAIZY_BASE_URL=http://localhost:3000

{
  "baseUrl": "http://localhost:3000",
  "apiToken": "laizy_eyJhbGciOiJI...",
  "organizationId": "org_abc123",
  "schemaPath": "./laizy/schema.laizy",
  "outputPath": "./generated/laizy"
}

{
  "projectId": "abc123",
  "projectSlug": "my-first-project",
  "projectName": "My First Project",
  "linkedAt": "2024-01-15T10:30:00.000Z"
}

Files Created

After running laizy init, your project will have these new files:

your-project/
  laizy/
    schema.laizy          # Schema file with example models
  generated/              # Output directory for generated client
  .laizy/
    project.json          # Project context (auto-added to .gitignore)
  .env.local              # Updated with frontend token and base URL
  ~/.laizyrc              # Global config (in your home directory)

Example Schema

The generated laizy/schema.laizy file contains a working example:

model BlogPost {
  title: String {
    required: true
    maxLength: 200
  }

  content: String {
    required: true
  }

  status: String {
    default: "draft"
  }
}

model Author {
  name: String {
    required: true
    maxLength: 100
  }

  email: String {
    required: true
    unique: true
  }

  bio: String
}

This example demonstrates all constraint types and gives you a working schema to sync and generate a client from.

Re-initialization

If you run laizy init in a directory that already has a .laizyrc config, the CLI asks if you want to reinitialize:

Project is already initialized (.laizyrc exists)
? Do you want to reinitialize the project? (y/N)

Re-initializing overwrites your configuration and project link but does not delete your schema files or generated code.

Gitignore

The init command automatically ensures that .laizy/ is added to your .gitignore file. This prevents project-specific context (like project IDs) from being committed, which is important when team members work on different projects.

Troubleshooting

Authentication failed:

• Ensure the base URL is correct and the server is running
• Check that you have an active Laizy CMS account
• Try running laizy init again to restart the auth flow

Connection failed:

• Verify the base URL is accessible from your machine
• Check if a firewall or proxy is blocking the connection
• For local development, ensure pnpm run dev is running

Next Steps

After initialization, follow these steps:

1. Edit your schema: Modify laizy/schema.laizy with your content models
2. Sync to database: Run pnpm laizy sync to apply your schema
3. Generate client: Run pnpm laizy generate to create the TypeScript client

• Sync Command -- Apply your schema to the database
• Generate Command -- Create a TypeScript client from your schema
• Schema Syntax -- Full reference for the schema language