Commit 223e597e authored by yala's avatar yala

initialisation with content from 442f205a

from Witzenhausen with ♥
type: "page"
# Hello, meet Ecobytes
We are your friendly, community-led internet service provider.
type: "page"
title: "Association"
weight: 10
creatordisplayname: "Jon RICHTER"
creatoremail: ""
lastmodifierdisplayname: "Jon RICHTER"
lastmodifieremail: ""
# Ecobytes Association
title: "Commons"
type: "page"
weight: 20
# Ecobytes Commons
title: "Lab"
type: "page"
weight: 40
# Ecobytes Lab
title: "Building static websites with Hugo"
date: 2018-04-29T02:51:11+02:00
draft: false
This documentation covers building a landing page like or setting up a knowledge repository like with a static site generator. We chose [Hugo]( which is configured via YAML-files.
## Create repositories
Two `git` repositories within your home git community are being used: one for the theme and the other for content and menu configuration.
- theme
- content + configuration
## Install Hugo and create a new site
### Install Theme
1. Fork the chosen Hugo-theme on GitHub.
2. Create a repository on
3. Clone the forked theme from GitHub.
cd themes
git clone myforkedtheme
cd myforkedtheme
### Find a new home for your fork on your home git community
For the sake of completeness the repo on GitHub is kept. So that we can push into two repos at once we add them to the new remote "both".
git remote add both
git remote set-url --add --push both
git remote set-url --add --push both git@gitlab.domain.tld:gitname/project/website-theme.git
Push to both repos simultaneously is done via:
git push both
## Clone existing site
- [``](
- [``](
git clone
# or
cd website/
git submodule update --init --recursive --remote
## Display an existing site
Verify with by running
hugo serve
and opening http://localhost:1313 in your browser.
## Edit existing site
In your `tmux` session ...
# one pane for
hugo serve
# and another for
vim ...
# with live reload
### Deploy to staging
Sometimes one wishes to deploy a site in development to a staging environment. Assuming you know and use Dokku, the repositories are prepared to work with it. You can push your site to it with:
cd public
git remote add stage
# or
git push -u stage deploy:master
cd ..
### Deploy to production
Assuming you wish to deploy `master` to a `production` instance, simply issue
## branching model
- `master`
- untouchable manually, this can only be mutated by Merge Requests
- `stage`
- issue for issues (ideally branch from the issues on gitlab to have them automatically linked)
- merge request from the branch once finished, review by peers and merge
title: "Studios"
type: "page"
weight: 30
# Ecobytes Studios
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment