Skip to main content

Deployment flow

When you run jelou functions deploy, the platform:
  1. Reads jelou.json to find the slug and entrypoint
  2. Collects all deployable files from the directory
  3. Displays a summary with names and sizes
  4. Uploads the files and runs the deployment
  5. Renames your entrypoint to user-function.ts
  6. Generates a main.ts wrapper that imports your code and starts the server
  7. Injects your secrets as environment variables
The deploy doesn’t generate any runtime token — the function is protected by default and only accepts calls authenticated with a platform API key. Create one in the app configuration section (apps.jelou.ai) and send it as Authorization: Bearer <key>. See the authentication guide for details.

File limits

What is automatically excluded

  • node_modules/
  • .git/
  • .env
  • dist/
  • .jelou/
  • Hidden files (starting with .)

Skip confirmation

For automated deployments, use --no-confirm:

Rollback

If you need to revert to a previous version, use jelou functions rollback.
Without arguments, it shows a menu with recent deployments:

CI/CD with GitHub Actions

deploy.yml
Use --json in pipelines to get structured output you can parse with jq. The format is always { "ok": true, "data": ... } on stdout.

Exposed routes