OceanLaunch docs

Build, ship and run your apps

Start here

Static sites

Publish HTML, CSS, JavaScript and images. Nothing is built: the files are served as they are, over HTTPS.

Upload

From Git

Give the repository's HTTPS address, the branch, and the folder to publish (for example public or docs/site; empty means the whole repository). The folder must contain index.html. Nothing is built (no npm): commit the finished files, or the output of your build. Private repositories and deploy on push work as for Java apps: see Git and deploy on push.

How pages are served

A site gets 128 MB of memory, which is plenty for nginx, on any plan.

Redirects and headers

Under the site's Settings, the box Maintenance mode, redirects and headers holds rules for the site's web server. Owners and admins change them; saving deploys the site again with them, which takes about a minute.

Redirects go one a line: the old address, then where it goes.

/old-page /new-page
/shop https://shop.example.com/ 302

Response headers go one a line as Name: value, and are sent with every answer of the site:

X-Frame-Options: DENY
Content-Security-Policy: default-src 'self'

Up to 20. Headers the web server sets itself, such as Content-Type, can't be changed, and X-Content-Type-Options: nosniff is always sent. A staging copy of a site takes its redirects and headers along.

Maintenance mode

Turn on Maintenance mode in the same box and every visitor gets a "back soon" page instead of the site, with status 503, so search engines come back later instead of dropping your pages. To show your own page, put a maintenance.html at the top of the site, with its styles and images inside that one file: nothing else is served meanwhile. Turning it on or off deploys the site again. Uptime checks pause while it's on.

Your own domain

Add your domain under the site's Domains tab, and make it primary so every other address, including the oceanlaunch.app one, redirects to it. See Custom domains.