Compare commits
No commits in common. "31a8f290b4ee63a6093e24b441354b6f51976a8b" and "4232531d3192d7b5af391a2e2ae414dcf5fca09b" have entirely different histories.
31a8f290b4
...
4232531d31
2
.github/workflows/blog.yaml
vendored
2
.github/workflows/blog.yaml
vendored
@ -1,5 +1,5 @@
|
||||
# Sample workflow for building and deploying a Hugo site to GitHub Pages
|
||||
name: Build and deploy site to GitHub Pages
|
||||
name: Deploy Hugo site to Pages
|
||||
|
||||
on:
|
||||
# Runs on pushes targeting the default branch
|
||||
|
@ -1,16 +1,12 @@
|
||||
# Kristian's Reproducible Website
|
||||
|
||||
[![GitHub Pages Status](https://github.com/Krsnik/blog/actions/workflows/blog.yaml/badge.svg)](https://github.com/Krsnik/blog/actions/workflows/blog.yaml)
|
||||
|
||||
This project is my personal website, using Hugo with asciidoc as a static site generator.
|
||||
The site is hosted on GitLab pages, using the supplied `.gitlab-ci.yaml` file, which just builds the `flake.nix` file.
|
||||
|
||||
## Development
|
||||
|
||||
To preview changes serve the website with `hugo serve -D`. This will build all content that has `draf: true` set in the header.
|
||||
This will also build the theme's content, if it includes one.
|
||||
If you are only interested how the published site will look do `hugo serve`.
|
||||
To preview changes serve the website with `hugo serve` and set `draft: false` in your blogpost.
|
||||
|
||||
## Deployment
|
||||
|
||||
This repo includes CI/CD configurations for GitHub and GitLab, so all you need to do is push any changes.
|
||||
Just push the changes to GitLab and the automatic CI/CD will build and deploy the website.
|
||||
|
Loading…
Reference in New Issue
Block a user