Skip to content

Application Management Overview

An application in Appliku connects your Git repository to a server, with configuration for how the code is built, deployed, and run.

Application Lifecycle

1. Create

Connect a Git repository (GitHub, GitLab, or custom), select a branch and server, and create the application.

2. Configure

After creation, Appliku opens the setup wizard. Use it to set up your application: - Build settings — Choose a build image or Dockerfile, set build commands - Processes — Define what commands to run (web, release, workers) - Environment variables — Configure secrets and settings - Databases — Provision PostgreSQL, Redis, etc. with auto-injected connection URLs - Domains — Add custom domains with automatic SSL - Volumes — Attach persistent storage - Cron jobs — Schedule recurring tasks

3. Deploy

Push to Git or trigger a manual deploy. Appliku builds a Docker image, runs release commands, and starts your processes.

4. Manage

Monitor deployments, view logs, scale processes, and update configuration as needed.

Creating an Application

You can create applications from: - GitHub — OAuth integration for accessing your repositories - GitLab — Token-based integration - Custom Git — Any Git repository accessible via HTTPS or SSH

During creation, you provide: - Application name - Repository and branch - Server (standalone) or cluster to deploy to - Whether the app is a static site

Application Configuration

All configuration is available in the Application Settings, organized into tabs:

Tab What it controls
Build Settings Build image, Dockerfile, build command, container port
Processes Web, release, and worker commands
Environment Variables App configuration and secrets
Domains Custom domains and SSL
Volumes Persistent storage mounts
Cron Jobs Scheduled tasks
Webhook External deployment trigger URL
YAML Config appliku.yml import/export

appliku.yml

You can define your entire application configuration in an appliku.yml file in your repository. This includes build settings, processes, databases, volumes, environment variables, and cron jobs. Changes are applied automatically on deploy.