parent
53998461d0
commit
75dc3ac5bc
GPG Key ID:
BC9D6AE1A3BE169A
@ -1,112 +0,0 @@
|
|||||||
+++
|
|
||||||
title = "Installing hugo on Linux"
|
|
||||||
summary = """This is how I install hugo nowadays. Although that routine might
|
|
||||||
change anytime."""
|
|
||||||
date = "2022-12-04T18:04:34+01:00"
|
|
||||||
lastmod = "2022-12-04T23:29:01+01:00"
|
|
||||||
categories = ["computerstuff"]
|
|
||||||
tags = ["linux","gohugo"]
|
|
||||||
|
|
||||||
draft = true
|
|
||||||
[sitemap]
|
|
||||||
priority = 1.0
|
|
||||||
|
|
||||||
+++
|
|
||||||
|
|
||||||
## Build from source
|
|
||||||
|
|
||||||
To build Hugo from source you must:
|
|
||||||
|
|
||||||
- Install Git
|
|
||||||
- Install Go version 1.18 or later
|
|
||||||
- Update your PATH environment variable as described in the Go documentation
|
|
||||||
|
|
||||||
The install directory is controlled by the GOPATH and GOBIN environment variables. If GOBIN is set, binaries are installed to that directory. If GOPATH is set, binaries are installed to the bin subdirectory of the first directory in the GOPATH list. Otherwise, binaries are installed to the bin subdirectory of the default GOPATH ($HOME/go or %USERPROFILE%\go).
|
|
||||||
|
|
||||||
Then build and test:
|
|
||||||
|
|
||||||
~~~console
|
|
||||||
$ go install -tags extended github.com/gohugoio/hugo@latest
|
|
||||||
$ hugo version
|
|
||||||
~~~
|
|
||||||
|
|
||||||
## Using hugo theme as module...
|
|
||||||
|
|
||||||
### Quick start using Hugo
|
|
||||||
|
|
||||||
Note: Ensure you have Go and Hugo installed, and that you have created a new Hugo project before proceeding.
|
|
||||||
|
|
||||||
From your project directory, initialise Hugo Modules:
|
|
||||||
|
|
||||||
~~~console
|
|
||||||
$ hugo mod init github.com/<username>/<repo-name>
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Create config/_default/module.toml and add the following:
|
|
||||||
|
|
||||||
~~~toml
|
|
||||||
[[imports]]
|
|
||||||
path = "github.com/jpanther/congo/v2"
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Start your server using hugo server and the theme will be downloaded automatically.
|
|
||||||
|
|
||||||
In the root folder of your website, delete the config.toml file that was generated by Hugo. Copy the *.toml config files from the theme into your config/_default/ folder.
|
|
||||||
|
|
||||||
{{< alert >}}
|
|
||||||
Note: Do not overwrite the module.toml file you created above!
|
|
||||||
{{< /alert >}}
|
|
||||||
|
|
||||||
You will find these theme config files in the Hugo cache directory, or download a copy from GitHub.
|
|
||||||
|
|
||||||
Follow the Getting Started instructions to configure your website.
|
|
||||||
|
|
||||||
## use Atom feeds
|
|
||||||
|
|
||||||
|
|
||||||
Define an appropriate media type and corresponding output format in config.toml:
|
|
||||||
|
|
||||||
```toml
|
|
||||||
[mediaTypes]
|
|
||||||
[mediaTypes."application/atom"]
|
|
||||||
suffix = "xml"
|
|
||||||
|
|
||||||
[outputFormats.Atom]
|
|
||||||
mediaType = "application/atom"
|
|
||||||
baseName = "index"
|
|
||||||
isPlainText = false
|
|
||||||
```
|
|
||||||
|
|
||||||
Tell Hugo to produce the home page in Atom and HTML formats, also in config.toml:
|
|
||||||
|
|
||||||
```toml
|
|
||||||
[outputs]
|
|
||||||
home = [ "HTML", "Atom" ]
|
|
||||||
```
|
|
||||||
|
|
||||||
Put an index.atom.xml template file in your layouts directory. You can use the attached one as a starting point, don't forget to edit the author element appropriately or make it take the values from your config.
|
|
||||||
|
|
||||||
```xml
|
|
||||||
<feed xmlns="http://www.w3.org/2005/Atom">
|
|
||||||
<title>{{ with .Title }}{{.}} on {{ end }}{{ .Site.Title }}</title>
|
|
||||||
<link rel="self" href="{{ .Permalink }}"/>
|
|
||||||
<updated>{{ .Date.Format "2006-01-02T15:04:05-0700" | safeHTML }}</updated>
|
|
||||||
<author>
|
|
||||||
<name>YOUR NAME HERE</name>
|
|
||||||
<email>YOUR EMAIL ADDRESS</email>
|
|
||||||
<uri>DEFINITIVE URI OF YOUR WEB SITE</uri>
|
|
||||||
</author>
|
|
||||||
<id>{{ .Permalink }}</id>
|
|
||||||
{{ range first 15 .Data.Pages }}
|
|
||||||
<entry>
|
|
||||||
<title>{{ .Title }}</title>
|
|
||||||
<link rel="alternate" href="{{ .Permalink }}"/>
|
|
||||||
<id>{{ .Permalink }}</id>
|
|
||||||
<published>{{ .Date.Format "2006-01-02T15:04:05-0700" | safeHTML }}</published>
|
|
||||||
<updated>{{ .Lastmod.Format "2006-01-02T15:04:05-0700" | safeHTML }}</updated>
|
|
||||||
<summary>{{ .Summary | html }}</summary>
|
|
||||||
</entry>
|
|
||||||
{{ end }}
|
|
||||||
</feed>
|
|
||||||
```
|
|
||||||
source: <https://gist.github.com/lpar/7ded35d8f52fef7490a5be92e6cd6937>
|
|
||||||
@ -0,0 +1,21 @@
|
|||||||
|
+++
|
||||||
|
title = "Tuxedo keyboard"
|
||||||
|
date = "2022-12-09T21:52:31+01:00"
|
||||||
|
|
||||||
|
draft = true
|
||||||
|
|
||||||
|
+++
|
||||||
|
|
||||||
|
check what kernel `uname -a` and install linux headers
|
||||||
|
|
||||||
|
sudo pacman -S linux515-headers
|
||||||
|
|
||||||
|
install tuxedo-keyboard
|
||||||
|
|
||||||
|
sudo pacman -S tuxedo-keyboard-dkms
|
||||||
|
|
||||||
|
source: <https://www.tuxedocomputers.com/de/Infos/Hilfe-Support/Anleitungen/Tastatur-Treiber-fuer-TUXEDO-Computers-Modelle-mit-RGB-Tastatur-nachinstallieren.tuxedo>
|
||||||
|
|
||||||
|
github: <https://github.com/tuxedocomputers/tuxedo-keyboard>
|
||||||
|
|
||||||
|
<https://github.com/tuxedocomputers/tuxedo-control-center>
|
||||||
|
After Width: | Height: | Size: 109 KiB |
@ -0,0 +1,233 @@
|
|||||||
|
+++
|
||||||
|
title = "My current website setup"
|
||||||
|
summary = """This is how I install hugo nowadays. Although that routine might
|
||||||
|
change anytime."""
|
||||||
|
date = "2022-12-10T22:56:16+01:00"
|
||||||
|
#lastmod = ""
|
||||||
|
categories = ["computerstuff"]
|
||||||
|
tags = ["linux", "gohugo", "reminders"]
|
||||||
|
|
||||||
|
draft = true
|
||||||
|
|
||||||
|
+++
|
||||||
|
|
||||||
|
I'll do a quick go-through of my actual website's installation procedure. The
|
||||||
|
website itself is hosted without my personal server---I'm using Cloudflare for
|
||||||
|
this to work. The content is saved in a github repository which gets then
|
||||||
|
fetched from Cloudflare. After half a minute the website is published and the
|
||||||
|
website cache on Cloudflare gets cleared automatically when I push new changes
|
||||||
|
to the repository.
|
||||||
|
|
||||||
|
## Install hugo from source
|
||||||
|
|
||||||
|
### Requirements
|
||||||
|
|
||||||
|
- Install Git
|
||||||
|
|
||||||
|
Depending on your <abbr title="Operating System">OS</abbr>, this might look
|
||||||
|
like one of those:
|
||||||
|
|
||||||
|
~~~console
|
||||||
|
$ sudo apt install git
|
||||||
|
~~~
|
||||||
|
|
||||||
|
~~~console
|
||||||
|
$ sudo pacman -S git
|
||||||
|
~~~
|
||||||
|
|
||||||
|
- Install Go version 1.18 or later
|
||||||
|
|
||||||
|
See above for the syntax, this package may be called `golang` on some
|
||||||
|
distributions (I think Ubuntu/Debian for example).
|
||||||
|
|
||||||
|
- Update your PATH environment variable as described in the Go documentation
|
||||||
|
|
||||||
|
Now, that looks like this:
|
||||||
|
|
||||||
|
~~~zsh
|
||||||
|
if [[ -d $HOME/go ]]; then
|
||||||
|
export GOPATH="$HOME/go"
|
||||||
|
path=(
|
||||||
|
$GOPATH/bin
|
||||||
|
$path
|
||||||
|
)
|
||||||
|
fi
|
||||||
|
~~~
|
||||||
|
|
||||||
|
_That is an example taken from my `.zprofile` file._
|
||||||
|
|
||||||
|
### Install hugo
|
||||||
|
|
||||||
|
~~~console
|
||||||
|
$ go install -tags extended github.com/gohugoio/hugo@latest
|
||||||
|
~~~
|
||||||
|
|
||||||
|
That installs the latest version of hugo into `$HOME/go/bin`. If your terminal
|
||||||
|
does not recognize the new binaries: `hash -r` or `rehash` might help...
|
||||||
|
|
||||||
|
Source: <https://gohugo.io/installation/linux/#build-from-source>
|
||||||
|
|
||||||
|
## Adding themes as hugo modules
|
||||||
|
|
||||||
|
Just to be more clear on this: I'm using the congo theme for hugo right here.
|
||||||
|
|
||||||
|
{{< alert >}}
|
||||||
|
Ensure you have Go and Hugo installed, and that you have created a new
|
||||||
|
hugo project before proceeding.
|
||||||
|
{{< /alert >}}
|
||||||
|
|
||||||
|
From your project directory, initialise hugo modules:
|
||||||
|
|
||||||
|
~~~console
|
||||||
|
$ hugo mod init github.com/<username>/<repo-name>
|
||||||
|
~~~
|
||||||
|
|
||||||
|
Create `config/_default/module.toml` and add the following:
|
||||||
|
|
||||||
|
~~~toml
|
||||||
|
[[imports]]
|
||||||
|
path = "github.com/jpanther/congo/v2"
|
||||||
|
~~~
|
||||||
|
|
||||||
|
Start your server using `hugo server` and the theme will be downloaded
|
||||||
|
automatically.
|
||||||
|
|
||||||
|
Remove the file `config.toml` from your website root directory (generaded by
|
||||||
|
`hugo site new...`). Copy the config files from the theme into `config/_default/`.
|
||||||
|
|
||||||
|
{{< alert >}}
|
||||||
|
Note: Do not overwrite the module.toml file you created above!
|
||||||
|
{{< /alert >}}
|
||||||
|
|
||||||
|
You will find these theme config files in the Hhgo cache directory, or download
|
||||||
|
[a copy from GitHub](https://github.com/jpanther/congo/tree/dev/config/_default).
|
||||||
|
|
||||||
|
Follow the [Getting Started instructions](https://jpanther.github.io/congo/docs/getting-started/)
|
||||||
|
to configure your website.
|
||||||
|
|
||||||
|
## Using Atom for feeds (replacing RSS)
|
||||||
|
|
||||||
|
Define an appropriate media type and corresponding output format in `config.toml`:
|
||||||
|
|
||||||
|
```toml
|
||||||
|
[mediaTypes]
|
||||||
|
[mediaTypes."application/atom"]
|
||||||
|
suffixes = ["xml"]
|
||||||
|
|
||||||
|
[outputFormats.Atom]
|
||||||
|
mediaType = "application/atom"
|
||||||
|
baseName = "index"
|
||||||
|
isPlainText = false
|
||||||
|
```
|
||||||
|
|
||||||
|
Tell hugo to produce the home page in Atom and HTML (and JSON) formats,
|
||||||
|
also append this in `config.toml`:
|
||||||
|
|
||||||
|
```toml
|
||||||
|
[outputs]
|
||||||
|
home = [ "HTML", "Atom", "JSON" ]
|
||||||
|
```
|
||||||
|
|
||||||
|
Put an `index.atom.xml` template file in your layouts directory. You can use the
|
||||||
|
attached one as a starting point, don't forget to edit the author element
|
||||||
|
appropriately or make it use the values from your config.
|
||||||
|
|
||||||
|
```xml
|
||||||
|
<feed xmlns="http://www.w3.org/2005/Atom">
|
||||||
|
<title>{{ with .Title }}{{.}} on {{ end }}{{ .Site.Title }}</title>
|
||||||
|
<link rel="self" href="{{ .Permalink }}"/>
|
||||||
|
<updated>{{ .Date.Format "2006-01-02T15:04:05-0700" | safeHTML }}</updated>
|
||||||
|
<author>
|
||||||
|
<name>YOUR NAME HERE</name>
|
||||||
|
<email>YOUR EMAIL ADDRESS</email>
|
||||||
|
<uri>DEFINITIVE URI OF YOUR WEB SITE</uri>
|
||||||
|
</author>
|
||||||
|
<id>{{ .Permalink }}</id>
|
||||||
|
{{ range first 15 .Data.Pages }}
|
||||||
|
<entry>
|
||||||
|
<title>{{ .Title }}</title>
|
||||||
|
<link rel="alternate" href="{{ .Permalink }}"/>
|
||||||
|
<id>{{ .Permalink }}</id>
|
||||||
|
<published>{{ .Date.Format "2006-01-02T15:04:05-0700" | safeHTML }}</published>
|
||||||
|
<updated>{{ .Lastmod.Format "2006-01-02T15:04:05-0700" | safeHTML }}</updated>
|
||||||
|
<summary>{{ .Summary | html }}</summary>
|
||||||
|
</entry>
|
||||||
|
{{ end }}
|
||||||
|
</feed>
|
||||||
|
```
|
||||||
|
|
||||||
|
Source: <https://gist.github.com/lpar/7ded35d8f52fef7490a5be92e6cd6937>
|
||||||
|
|
||||||
|
## Auto-clear cache on git push
|
||||||
|
|
||||||
|
### Requirements
|
||||||
|
|
||||||
|
- A **Cloudflare website** (not pages, well---yes, but a website that uses one
|
||||||
|
of your pages)
|
||||||
|
- An API token on Cloudflare to let git clear your website's cache (see below)
|
||||||
|
|
||||||
|
### Cloudflare setup
|
||||||
|
|
||||||
|
Create a file `.cloudflarerc` in your `$HOME` directory that contains those two
|
||||||
|
variables:
|
||||||
|
|
||||||
|
~~~bash
|
||||||
|
apikey=*********************************-******
|
||||||
|
id=********************************
|
||||||
|
~~~
|
||||||
|
|
||||||
|
You find them in your [Cloudflare dashboard](https://dash.cloudflare.com/).
|
||||||
|
Click on <kbd>Websites</kbd> and continue with clicking your domain name.
|
||||||
|
Scroll down a bit and find your `id` on the right sidebar. It is called
|
||||||
|
_Zonen-ID_ (within API). Below that is a link called _Ihr API-Token erhalten_.
|
||||||
|
Click it and create a user-defined API token. I'll show you a screenshot of
|
||||||
|
mine, edit yours to fit this example.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Click <kbd>Create token</kbd> and copy the resulting token into your
|
||||||
|
`.cloudflarerc` file.
|
||||||
|
|
||||||
|
### git repository setup
|
||||||
|
|
||||||
|
Now we need one last file in our git repository. Create `.git/hooks/pre-push` and
|
||||||
|
fill it with this:
|
||||||
|
|
||||||
|
~~~bash
|
||||||
|
#!/bin/bash
|
||||||
|
|
||||||
|
if ! [ -f ~/.cloudflarerc ] ; then
|
||||||
|
echo "No ~/.cloudflarerc file found. Cloudflare clear cache SKIPPED."
|
||||||
|
exit 0
|
||||||
|
fi
|
||||||
|
|
||||||
|
. ~/.cloudflarerc
|
||||||
|
|
||||||
|
echo -n "Clearing cloudflare cache..."
|
||||||
|
|
||||||
|
ret="$(curl -s -X DELETE "https://api.cloudflare.com/client/v4/zones/$id/purge_cache" \
|
||||||
|
-H "Authorization: Bearer $apikey" \
|
||||||
|
-H "Content-Type: application/json" \
|
||||||
|
--data '{"purge_everything":true}')"
|
||||||
|
|
||||||
|
if [ -n "$(echo $ret | grep success)" ] ; then
|
||||||
|
echo " Success!"
|
||||||
|
else
|
||||||
|
echo " *** FAILED ***"
|
||||||
|
echo "Could not clear cloudflare's cache. Update will not proceed."
|
||||||
|
# exit with 1, so the update does not proceed, so we will know
|
||||||
|
exit 1
|
||||||
|
fi
|
||||||
|
~~~
|
||||||
|
|
||||||
|
I found the script on
|
||||||
|
<https://www.supertechcrew.com/clear-cloudflare-cache-when-pushing-from-git-github-pages/>
|
||||||
|
---which is also a good read if my explanation won't work for you.
|
||||||
|
|
||||||
|
Don't forget to make this script executable:
|
||||||
|
|
||||||
|
~~~console
|
||||||
|
$ chmod +x .git/hooks/pre-push
|
||||||
|
~~~
|
||||||
|
|
||||||
|
Finished.
|
||||||
Loading…
Reference in new issue