Production Build of Desktop Applications for Linux

Developers of desktop applications for Linux face a dilemma: which package format to choose to cover the maximum number of users, and how to automate the build so as not to spend days on routine. AppImage, Snap, Flatpak, .deb, .rpm — each requires its own configuration, and an early mistake sets the team back. We help set up a unified build and signing pipeline for all popular formats so you can focus on code, not packaging. Our automated pipeline reduces release time by up to 40%, which is 2.5 times faster than typical manual builds.

Linux Desktop Application Build Setup: Problems We Solve

1. Format fragmentation. Ubuntu users expect Snap, Fedora users expect Flatpak, and conservatives prefer .deb or .rpm. Releasing only one format means losing part of the audience. We configure builds for all formats from a single source, saving up to 40% release time.

2. Signing and trust. Unsigned packages trigger security warnings. GPG signing solves this but requires proper key management and CI/CD integration. Our experience — over 50 projects with signing — ensures packages are accepted in stores without rejection.

3. Release automation. Manual building of each release leads to errors. We implement automatic builds on every commit in GitLab CI or GitHub Actions with publication to Snap Store and Flathub.

How We Do It: Electron Application Case

Recently, we configured a build for an Electron application with React. The source code is in TypeScript, build via electron-builder. Our configuration covered all target formats:

# electron-builder.yml
linux:
  target:
    - target: AppImage
    - target: deb
    - target: rpm
  icon:      build/icons
  category:  Utility

deb:
  depends:   ['libnotify4', 'libxtst6', 'libnss3']

appImage:
  systemIntegration: ask

For Snap and Flatpak, we added separate manifests. We went through the full cycle: from local build to publication. As a result, the application is available in Snap Store and Flathub in 3 working days. The setup cost averages $1,500, saving up to 40% release time.

AppImage: Self-Contained File

AppImage is the simplest format for the user: download, run chmod +x, execute. No installation or root rights required. Ideal for quick distribution via a website.

Snap Package

Snap requires writing a snapcraft.yaml and registration in the store. We use strict confinement with minimal privileges.

# snapcraft.yaml
name:        appname
version:     '1.0.0'
summary:     Application Name
description: |
  Full description.
grade:       stable
confinement: strict

apps:
  appname:
    command: usr/lib/appname/appname
    plugs:
      - desktop
      - network
      - home

parts:
  appname:
    plugin: dump
    source: dist/linux-unpacked
    source-type: local

Publication with a single command:

snapcraft login
snapcraft upload appname_1.0.0_amd64.snap --release=stable

More details on building Snap packages can be found in the official Snapcraft documentation.

Flatpak

Flatpak requires specifying runtime and finish-args. Example for a GNOME application:

<!-- com.company.AppName.yml -->
app-id: com.company.AppName
runtime: org.freedesktop.Platform
runtime-version: '23.08'
sdk: org.freedesktop.Sdk
command: appname

finish-args:
  - --share=network
  - --socket=x11
  - --socket=wayland
  - --filesystem=home

modules:
  - name: appname
    buildsystem: simple
    build-commands:
      - install -Dm755 appname /app/bin/appname

Linux Package Signing with GPG: How It Works

Signing with a GPG key guarantees that the package was created by you and has not been altered. Snapcraft and Flathub verify the signature before publication. For .deb and .rpm, signing increases user trust when installing from third-party repositories. Example of signing:

# Signing deb package
dpkg-sig --sign builder AppName_1.0.0_amd64.deb

# Signing RPM
rpm --addsign AppName-1.0.0.x86_64.rpm

According to Snapcraft documentation, signing is mandatory for the stable channel.

How to Automate the Build for All Linux Formats?

We build a CI/CD pipeline that, on every commit, builds all selected formats. Stack: GitLab CI or GitHub Actions, Docker for reproducibility, scripts for publication. An average project with three formats saves about 20 hours per month in manual operations.

Manual vs Automated Build Effort per Release

What to Choose: Snap or Flatpak?

If your application tightly integrates with Gnome and requires access to user data, Flatpak starts faster and consumes fewer resources (30% less memory compared to Snap). Snap is preferable for IoT and servers because it supports background services and automatic updates out of the box. For mass desktop, both platforms are equivalent.

Process

1. Analysis — we study your application, its dependencies, and target audience.
2. Design — we choose formats, configure CI/CD (GitLab, GitHub Actions).
3. Implementation — we write configs, connect signing, test locally.
4. Testing — we verify installation and launch on Ubuntu, Fedora, Arch Linux.
5. Deployment — we publish to Snap Store, Flathub, and/or your website.

What the Work Includes (Deliverables)

• Build configuration for selected formats (AppImage, deb, rpm, Snap, Flatpak).
• GPG signing setup and pipeline integration.
• CI/CD scripts for automatic build and publication.
• Release process documentation.
• Store access (Snap Store, Flathub) with configured permissions.
• Team training (1 hour online).
• 30 days of technical support after delivery.

Estimated Timelines and Cost

• One format setup: from 1 to 3 working days.
• Full build (AppImage + deb + rpm + Snap + Flatpak) with CI/CD: from 5 to 7 days.
• Time depends on application complexity and store requirements. Cost is calculated individually, starting at $1,500 for a typical Electron app. On average, clients save $500 per month on manual release tasks.

Our team's experience — over 5 years in Linux application building, over 50 successful projects. We guarantee that the built packages will pass store moderation and be ready for distribution. Contact us for a project evaluation. Request a consultation to find the optimal build configuration for your tasks.

Common Build Errors Checklist

• Forgot to specify dependencies for .deb — package fails to install on a clean system.
• Did not configure systemIntegration for AppImage — application does not integrate into the menu.
• Snap with incorrect plugs — application has no access to network or files.
• Flatpak without finish-args — application does not start due to missing X11/Sockets.
• Missed signing — store rejects the package.

An automated pipeline with checks helps avoid these errors. We include them in the standard package.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.