> For AI agents: the complete documentation index is available at /en/llms.txt, the full documentation bundle is available at /en/llms-full.txt.

# Getting started

From order to a live site takes about 15 minutes of your time. After that,
publishing happens automatically on every push.

## Step 1: Order \{#steg-1-bestall}

Order GetGeek Static in the portal:
**[https://portal.getgeek.se/index.php/cart/webbhosting/\&action=add\&id=931](https://portal.getgeek.se/index.php/cart/webbhosting/\&action=add\&id=931)**

In the order you fill in the following:

| Field                        | Example                             | Comment                                                                                                                                                                                                                                       |
| ---------------------------- | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| How do you publish the site? | _We build with Hugo from your repo_ | Three choices: _Upload a finished site from CI_ (the default), _We build with Hugo from your repo_ and _Pre-built branch in the repo_. See [Build it yourself](/en/static/egen-byggpipeline.md) for the two options where you build yourself. |
| Git repository (SSH address) | `git@gitlab.com:my-org/site.git`    | Only if you don't upload. The SSH address, not https. The repository may be private.                                                                                                                                                          |
| Branch                       | `main`                              | Empty = `main`. For _Pre-built branch in the repo_ empty = `gh-pages`.                                                                                                                                                                        |
| Hugo version                 | `0.165.0`                           | Empty = our standard version (currently 0.165.0). Only fill it in if you need a different version.                                                                                                                                            |
| Domain(s), max 5             | `www.example.com, example.com`      | The first one becomes the primary domain.                                                                                                                                                                                                     |
| Email for build errors       | `web@example.com`                   | Emails about failed builds are sent here. Empty = the account's email address.                                                                                                                                                                |

You can change all of this later, see [Manage your site in the portal](/en/static/portalen.md).

## Step 2: What you find in the portal \{#steg-2-det-har-far-du-av-oss}

Once the site is set up, you find the following on the service page in the portal (see [Manage your site in the portal](/en/static/portalen.md)):

1. **Status** — per domain whether it is verified, the current version and the
   result of the latest publication.
2. **A deploy key** (when we fetch from your repository) — a public SSH key that
   gives us _read access_ to your repository. It cannot change anything.
3. **A webhook address** (when we fetch from your repository), in the form
   `https://static.getgeek.se/hook/<site>/<token>`. It tells us that there is
   something new to build.
4. **An upload address** (when you upload a pre-built site from CI), see
   [Build it yourself](/en/static/egen-byggpipeline.md).
5. **A verification code** per domain, `gg-static-…`, which shows that the
   domain is yours (see step 4).

:::warning The webhook address is a secret
The last part of the address is a key. It can only start a build of what is
already in your repository — it can never change your site — but don't share it
unnecessarily. If you think it has leaked, press **Ny webhook- och uppladdningsnyckel** (new webhook and upload key) on the service page.
:::

## Step 3: Connect your repository \{#steg-3-koppla-ditt-repo}

Add the deploy key and the webhook in your git service. It differs slightly
between services:

- [GitLab](/en/static/gitlab.md) (with screenshots)
- [GitHub](/en/static/github.md)
- [Gitea, Forgejo, Codeberg, Bitbucket and others](/en/static/andra-git.md)

## Step 4: DNS \{#steg-4-dns}

Add two records for **each** domain at your DNS provider.

**Point the domain to us.** For a subdomain, for example `www.example.com`:

```
www.example.com.    CNAME   static.getgeek.se.
```

For a domain without a prefix (`example.com`) you cannot use a CNAME — the DNS
standard doesn't allow it at the apex of a zone. Add both addresses instead:

```
example.com.    A       94.142.251.165
example.com.    AAAA    2a12:5bc1::165
```

The addresses are fixed and will not change. Add both A and AAAA, so that the
site reaches visitors over both IPv4 and IPv6.

**Show that the domain is yours**, with the verification code you received in
step 2:

```
_getgeek-static.www.example.com.    TXT    "gg-static-…"
_getgeek-static.example.com.        TXT    "gg-static-…"
```

:::info Why a TXT record?
Without it, anyone could ask us to publish a site on _your_ domain if it happens
to point to us — for example an old CNAME that was left behind. The TXT record
proves that you control the domain's DNS. GitLab Pages and most similar services
use the same method. The code is unique to your site.

We check for the record automatically every ten minutes. When it is found, you
receive an email saying the domain is verified — you don't need to contact us.
After that the record doesn't need to stay, but it does no harm if it does.
:::

## Step 5: Push \{#steg-5-pusha}

Push something to your branch. Within a few seconds we:

1. receive the webhook,
2. fetch your repository with the deploy key,
3. build the site with Hugo,
4. publish it.

The first time your domain is used, we also fetch a certificate from Let's
Encrypt. That takes from half a minute to a few minutes — but only once the DNS
records have propagated. If you have just changed DNS, it can take up to an hour
or so, depending on how long the old answers are cached.

Done! From now on the site is published on every push. If a build fails you get
an email, and your site keeps showing the latest working version.
