Projects

A project represents a single application on SKE. It has a name, a runtime, and one or more environments where the application is deployed.

Creating a project

Projects are created in the dashboard, within the current workspace: go to Projects, select New project and fill in:

Field	Description
Name	Display name; the slug is generated from it
Runtime	The application’s runtime: Laravel
Repository URL	Optional link to your git repository
Default region	A fallback region; each environment picks its own when it is created
Description	Optional description

Create and continue opens the project’s setup page. Create this environment there creates the first environment, and the page lists the commands to link a repository and set up a pipeline that deploys on every push.

Linking a repository

From the repository root, run ske link to link the directory to the project and a default environment:

ske link

Select a project:
  1. My App (my-app)
Enter number: 1
Select a default environment:
  1. production (production)
  2. staging (staging)
Enter number: 1
Linked to acme-corp/default/my-app (default environment: production)
Added .ske/ to .gitignore.

The link is saved in .ske/project.json and kept out of git. In scripts and CI, pass both up front with ske link --project my-app --env production, or set SKE_PROJECT and SKE_ENV instead of linking.

An environment’s settings (memory, timeouts, queues, deploy hooks and so on) are kept in SKE, not in the repository: change them under the environment’s Settings in the dashboard.

Listing projects

The Projects page in the dashboard lists the workspace’s projects and their environments. The CLI has no project commands.

In this section

• Environments — create and manage deployment targets
• Secrets — manage sensitive values per environment
• Environment Variables — configuration vs. secrets