Skip to content
SKE

Quick Start

This guide takes you from a fresh SKE account to a running Laravel application. You need the CLI installed and a cloud account (AWS or GCP) ready.

1. Sign in

Section titled “1. Sign in”
Terminal window
ske login
Email: you@example.com
✓ Sign-in link sent. Check your email and click the link.
⠋ Waiting for sign-in...
✓ Signed in as you@example.com

2. Connect a cloud provider

Section titled “2. Connect a cloud provider”

Connect your AWS account or GCP project. SKE provisions all infrastructure inside your cloud account — it never hosts your application.

For AWS, create an IAM role with the required permissions (see AWS setup) and connect it:

Terminal window
ske provider:connect aws \
  --role-arn arn:aws:iam::123456789012:role/SKERole \
  --region us-east-1

For GCP, create a service account and connect it:

Terminal window
ske provider:connect gcp \
  --project-id my-gcp-project \
  --credentials ./service-account.json \
  --region us-central1

3. Create a project

Section titled “3. Create a project”
Terminal window
ske project:create --name my-laravel-app --runtime laravel
✓ Project "my-laravel-app" created

4. Create an environment

Section titled “4. Create an environment”
Terminal window
ske environment:create --project my-laravel-app --name production --provider aws --region us-east-1
✓ Environment "production" created

5. Initialize ske.yml

Section titled “5. Initialize ske.yml”

From your Laravel project directory, run ske init to link your local project to the SKE environment:

Terminal window
cd ~/projects/my-laravel-app
ske init
? Select a project: my-laravel-app
? Select an environment: production
✓ Created ske.yml

This creates an ske.yml file in your project root:

name: my-laravel-app
environments:
  production: {}

6. Set secrets

Section titled “6. Set secrets”

Your application needs at minimum an APP_KEY. Set it as a secret:

Terminal window
ske secret set APP_KEY
Value: ••••••••••••••••••••••••••••••••
✓ Secret APP_KEY set

Set any other secrets your app needs (database passwords, API keys, etc.):

Terminal window
ske secret set DB_PASSWORD --value "your-database-password"

7. Deploy

Section titled “7. Deploy”
Terminal window
ske deploy
⠋ Building container image...
✓ Image built (42s)
⠋ Pushing image to registry...
✓ Image pushed (18s)
⠋ Uploading assets...
✓ Assets uploaded (3s)
⠋ Provisioning infrastructure...
✓ Infrastructure ready (2m 14s)
⠋ Activating...
✓ Deployed successfully (3m 17s total)


  URL: https://production-my-laravel-app.example.ske.dev

What happened

Section titled “What happened”
  1. Build — SKE generated a Dockerfile for your Laravel app, built a container image locally using Docker, and pushed it to your cloud provider’s container registry (ECR on AWS, Artifact Registry on GCP).
  2. Assets — Static files from your public/ directory were uploaded to cloud storage for CDN delivery.
  3. Provision — Infrastructure was provisioned in your cloud account: compute (Lambda or Cloud Run), API gateway, and any configured resources.
  4. Activate — Traffic was routed to the new deployment. The previous version (if any) remains available for instant rollback.

Next steps

Section titled “Next steps”