Build from Git source

Apache HTTP

Apache HTTP Server 2.4 for static websites. Point it at a Git repository; the platform builds a container image from your files and serves them over an HTTPS route.

Source-to-Image build
Stateless · scales horizontally
Rebuild on Git push
Runs as non-root

Deploy from Git Talk to an engineer

No credit card required · Free during the Alpha phase · View pricing

Overview

A static web server, built and deployed from your repository.

Static sites

HTML, CSS, JavaScript and assets — documentation sites, static-site-generator output, single-page app bundles and landing pages.

Content from Git

The repository is the source of truth. Repository files are copied into the document root at build time; nothing is edited on a running container.

Configurable

Add .conf files under httpd-cfg/ in the repository to extend the server configuration — redirects, headers, caching rules.

Deployment

Source-to-Image (S2I): the httpd builder image turns a Git repository into a runnable image.

Git repository

Your static files and optional httpd-cfg/

BuildConfig

S2I build on the httpd builder image

ImageStream

Built image, tagged and stored in the cluster

Deployment + Route

Pods serve on port 8080 behind a Service and Route

Web console — Add → Import from Git. Paste the repository URL, choose the httpd builder image and a name; the console creates the build, image stream, Deployment, Service and Route.
CLI — oc new-app with the httpd~ syntax creates the same objects; oc expose adds the Route.
Rebuilds — trigger a build with oc start-build, or add the BuildConfig's webhook URL to your Git provider to rebuild on every push. A new image rolls out to the Deployment automatically.
Stateless — content is baked into the image, so no persistent volume is needed and replicas are interchangeable.

bash — oc

# build and deploy a static site from Git
$ oc new-app httpd~https://github.com/sclorg/httpd-ex.git \
    --name=my-site

# publish it on an HTTPS route
$ oc create route edge my-site --service=my-site

# rebuild after a change, then scale out
$ oc start-build my-site --follow
$ oc scale deployment/my-site --replicas=2

Platform integration

Standard Kubernetes objects in your own project.

Your namespace — the build, image and pods run in your project, under its quotas and role bindings. Builds run on cluster nodes; no external CI service is required.
Restricted security context — the image runs as an arbitrary non-root user and listens on 8080, so it is admitted under OpenShift's default restricted security constraints without extra privileges.
Ingress — traffic enters through an OpenShift Route; TLS terminates at the router (edge) or passes through to the pod.
CI/CD — for multi-step builds or tests before deploy, drive the same build from Tekton Pipelines or GitLab CI.
Dynamic sites — for server-side code, use the Node.js runtime with the same Git-based build flow.

Deploy a static site from your repository.

Import from Git in the console, or run one oc new-app command.

Deploy from Git Talk to an engineer

Hosted in the Netherlands · EU data residency · 100% renewable energy

Far far away, behind the word moun tains, far from the countries Vokalia and Consonantia, there live the blind texts. Separated they live in Bookmarksgrove right at the coast of

759 Pinewood Avenue
Marquette, Michigan
info@domain.com
Online Support
906-624-2565
Mon-Fri 8am-5pm

Purchase Now