Quickstart

Get up and running with the Ennote CLI for your local development and headless CI/CD pipelines.

Local Development Setup

For local development, authenticate your machine against the Ennote Cloud using an OAuth 2.0 PKCE flow.

bash

ennote auth login

Once authenticated, you can specify your organization and workspace via the config command:

bash

ennote config set organization-id my-org-id
ennote config set workspace-id my-workspace-id

You can now inject secrets directly into your local development servers without writing a .env file:

bash

ennote secret get stripe-keys -- npm run dev

CI/CD Pipeline Integration (Headless)

For automated pipelines (GitHub Actions, GitLab CI), avoid the auth login command. Instead, provision a Machine Identity Token and inject it via the environment.

yaml

# Example: GitHub Actions
steps:
  - name: Run Database Migrations
    env:
      ENNOTE_TOKEN: ${{ secrets.ENNOTE_MACHINE_TOKEN }}
      ENNOTE_ORGANIZATION_ID: org_123
      ENNOTE_WORKSPACE_ID: wrk_prod
      ENNOTE_DO_NOT_TRACK: 1
    run: |
      ennote secret get db-credentials -- npm run migrate

Need Help?

If you encounter any issues or have questions, don’t hesitate to contact support. Our team is here to assist you with any challenges you might face.