add content and modify gitignore
I decided to read the content for simplicity and data safety on my site. It's a website, so the content is out there anyway.
This commit is contained in:
parent
92696d28bb
commit
084cda3e07
63 changed files with 882 additions and 12 deletions
19
content/blog/_draft/secure-gitea-using-nginx.md
Executable file
19
content/blog/_draft/secure-gitea-using-nginx.md
Executable file
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
title: "Secure Gitea Using Nginx"
|
||||
author: "Vrifox"
|
||||
date: 2020-09-18T13:48:31+02:00
|
||||
featured_image:
|
||||
categories:
|
||||
tags:
|
||||
|
||||
draft: true
|
||||
type: "post"
|
||||
---
|
||||
|
||||
Gitea uses inline-scrips and -styles and sets non-secure cookies. It took me a while to figure out how to make both a non-issue.
|
||||
|
||||
To overcome the inline-issue and be able to set a secure [CSP](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) I discovered that you could allow specific scripts and styles as follows:
|
||||
|
||||
`add_header Content-Security-Policy "script-src 'self' 'sha256-woGzIu9yHD+ty6q2UlGmvvXbicNUyNzO4LJkj0U6B40=';";`
|
||||
|
||||
To get the value I used the console in chromium (Ctrl+Shift+I).
|
17
content/blog/_draft/why-i-use-hugo.md
Executable file
17
content/blog/_draft/why-i-use-hugo.md
Executable file
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
title: "The reason why I use Hugo"
|
||||
date: 2020-09-21T20:37:45+02:00
|
||||
slug: ""
|
||||
description: "The reason why I use Hugo."
|
||||
keywords: []
|
||||
draft: true
|
||||
tags: [hugo]
|
||||
math: false
|
||||
toc: false
|
||||
---
|
||||
This is an example blog post.
|
||||
|
||||
- my code got messier
|
||||
- I always wanted to start over
|
||||
- I wanted a more complex website
|
||||
- a menu on every page isn't easy to maintain for more than ~5 pages
|
3
content/blog/_index.md
Executable file
3
content/blog/_index.md
Executable file
|
@ -0,0 +1,3 @@
|
|||
---
|
||||
title: "Blog"
|
||||
---
|
25
content/blog/firefox-dark-mode.md
Executable file
25
content/blog/firefox-dark-mode.md
Executable file
|
@ -0,0 +1,25 @@
|
|||
---
|
||||
title: "Firefox Dark Mode"
|
||||
author: ""
|
||||
date: 2021-05-15T11:54:53+02:00
|
||||
categories:
|
||||
tags:
|
||||
|
||||
draft: false
|
||||
type: "post"
|
||||
description: ""
|
||||
---
|
||||
|
||||
This is how to enable the dark mode for all compatible websites in your Firefox.
|
||||
|
||||
## Firefox Config
|
||||
|
||||
To enable the Firefox Dark Mode open your Firefox' [about:config](https://support.mozilla.org/en-US/kb/about-config-editor-firefox) and add a **new** boolean `ui.systemUsesDarkTheme` and set it to `1`.
|
||||
|
||||
## Debugging
|
||||
|
||||
For debugging purposes you can switch between dark and light mode using the *Inspector* (right-click > Inspect):
|
||||
|
||||

|
||||
|
||||
You can test this right here on my website 🙂
|
17
content/blog/graphic-for-natenoms-blog.md
Executable file
17
content/blog/graphic-for-natenoms-blog.md
Executable file
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
title: "a »new« graphic for natenoms blog"
|
||||
author: ""
|
||||
date: 2020-08-29T12:12:53+02:00
|
||||
featured_image: "/upload/2020-09-20 fahrradteile v2.1.jpg"
|
||||
categories:
|
||||
- natenomsblog
|
||||
tags:
|
||||
- graphic
|
||||
- natenom
|
||||
|
||||
draft: false
|
||||
type: "post"
|
||||
description: "I did make a new iteration of this graphic for Natenoms Blog."
|
||||
---
|
||||
|
||||
I did make a new iteration of this graphic for [Natenoms Blog](https://blog.natenom.com/).
|
21
content/blog/indieauth-using-gpg.md
Executable file
21
content/blog/indieauth-using-gpg.md
Executable file
|
@ -0,0 +1,21 @@
|
|||
---
|
||||
title: "IndieAuth using gpg"
|
||||
author: ""
|
||||
date: 2021-05-14T11:38:53+02:00
|
||||
categories:
|
||||
tags:
|
||||
|
||||
draft: false
|
||||
type: "post"
|
||||
description: ""
|
||||
---
|
||||
|
||||
I rediscovered [IndieAuth](https://indieweb.org/IndieAuth) and wanted to try it finally.
|
||||
|
||||
As authentication method I decided to use [my gpg key](/gpg), because it's public anyway and something interesting and new to me (I actually never signed anything on the console before).
|
||||
|
||||
It took a little try and error before I found the following solution for signing the key:
|
||||
|
||||
`gpg --clearsign --default-key name@example.tld gpgmessage.txt`
|
||||
|
||||
It's not perfect; it requires to put the message that needs to be signed in a file and puts the signed message in a new file with an `.asc` ending. It would be much nicer if it would allow to do both directly on the console.
|
29
content/blog/optimizing-is-fun.md
Executable file
29
content/blog/optimizing-is-fun.md
Executable file
|
@ -0,0 +1,29 @@
|
|||
---
|
||||
title: "Simpler technology to bring knowledge and control"
|
||||
author: ""
|
||||
date: 2021-03-02T14:18:53+02:00
|
||||
categories:
|
||||
tags:
|
||||
- opensource
|
||||
- webdesign
|
||||
|
||||
draft: true
|
||||
type: "post"
|
||||
description: "My – also new – gitea theme appears to be usable, as long as you're not logged in."
|
||||
---
|
||||
|
||||
I've read so many interesting articles about a simpler, more efficient, content-oriented and privacy-friendly web in the last month and then even figured there already is such a thing: [The gemini protocol](https://gemini.circumlunar.space/).
|
||||
|
||||
So inspired by all this and driven by my already long-term interest in optimising to the point where I can actually understand what I am and especially my computer is doing to the last bit and
|
||||
|
||||
- learning python
|
||||
- optimizing vrifox.cc
|
||||
- replacing gitea with something simpler
|
||||
- advantages
|
||||
- better for environment
|
||||
- easier to understand and control
|
||||
- downsides
|
||||
- you have to be interested (at least for most some benefits)
|
||||
- Links / Read section
|
||||
- blogroll?
|
||||
- books read section?
|
27
content/blog/privacy-friendlier-nginx-logging.md
Executable file
27
content/blog/privacy-friendlier-nginx-logging.md
Executable file
|
@ -0,0 +1,27 @@
|
|||
---
|
||||
title: "Privacy friendlier Nginx logging"
|
||||
author: "Vrifox"
|
||||
date: 2021-05-15T21:49:54+02:00
|
||||
featured_image:
|
||||
categories:
|
||||
tags:
|
||||
|
||||
draft: true
|
||||
type: "post"
|
||||
---
|
||||
|
||||
Yesterday I changed the logging behaviour of my nginx. I did this to make it more privacy friendly and to declutter my log files. \
|
||||
The ip address anonymization part is taken from [Ascraues Privacy Policy ](https://ascraeus.org/page/privacy/).
|
||||
|
||||
```
|
||||
map $remote_addr $anon_remote_addr {
|
||||
~(?P<ip>\d+\.\d+)\. $ip.0.0;
|
||||
~(?P<ip>[^:]+:[^:]+): $ip::;
|
||||
default 0.0.0.0;
|
||||
}
|
||||
|
||||
log_format privacy '$anon_remote_addr [$time_local] '
|
||||
'"$request" $status $bytes_sent ';
|
||||
|
||||
access_log /var/log/nginx/access.log privacy;
|
||||
```
|
53
content/blog/pure-css-icons-gitea-theme.md
Executable file
53
content/blog/pure-css-icons-gitea-theme.md
Executable file
|
@ -0,0 +1,53 @@
|
|||
---
|
||||
title: "pure css icons for my gitea theme"
|
||||
author: ""
|
||||
date: 2020-10-05T12:14:51+02:00
|
||||
categories:
|
||||
- gitea-theme
|
||||
tags:
|
||||
- webdesign
|
||||
- code
|
||||
|
||||
draft: false
|
||||
type: "post"
|
||||
description: "I'm working on my gitea theme and just added a $nojavascript alternative for two icons with pure css. :)"
|
||||
---
|
||||
|
||||
**Update (2021-02-28):** The code is no longer in use due to changes to gitea.
|
||||
|
||||
I'm working on my gitea theme and just added a $nojavascript alternative for two icons with pure css. :)
|
||||
|
||||
[an image of how it actually looks](/upload/2020-10-05%20pure%20css%20icons%202.jpg)
|
||||
|
||||
# the code
|
||||
|
||||
```scss
|
||||
.svg {
|
||||
&.octicon-file-directory,
|
||||
&.octicon-file-submodule {
|
||||
fill: rgb(255, 130, 130);
|
||||
@if $nojavascript == true {
|
||||
background: rgb(255, 130, 130);
|
||||
border-radius: 0 1px 2px 2px;
|
||||
box-shadow: -4px -7px 0px -4px rgb(255, 130, 130);
|
||||
height: 10px;
|
||||
margin-left: 5px !important;
|
||||
margin-top: 4px;
|
||||
width: 14px;
|
||||
}
|
||||
}
|
||||
&.octicon-file {
|
||||
fill: rgb(215, 215, 225);
|
||||
@if $nojavascript == true {
|
||||
border: 1px solid rgb(215, 215, 225);
|
||||
border-radius: 0 5px 0 0;
|
||||
height: 13px;
|
||||
margin-left: 7px !important;
|
||||
margin-right: 6px !important;
|
||||
width: 10px;
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
A live version can be found on [code.cozy.town](https://code.cozy.town/vrifox/gitea-theme).
|
28
content/blog/the-broken-dns.md
Executable file
28
content/blog/the-broken-dns.md
Executable file
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
title: "The broken DNS"
|
||||
author: ""
|
||||
date: 2021-03-05T13:54:53+02:00
|
||||
categories:
|
||||
tags:
|
||||
- opensource
|
||||
|
||||
draft: true
|
||||
type: "post"
|
||||
description: "My – also new – gitea theme appears to be usable, as long as you're not logged in."
|
||||
---
|
||||
|
||||
I've read so many interesting articles about a simpler, more efficient, content-oriented and privacy-friendly web in the last month and then even figured there already is such a thing: [The gemini protocol](https://gemini.circumlunar.space/).
|
||||
|
||||
So inspired by all this and driven by my already long-term interest in optimising to the point where I can actually understand what I am and especially my computer is doing to the last bit and
|
||||
|
||||
- learning python
|
||||
- optimizing vrifox.cc
|
||||
- replacing gitea with something simpler
|
||||
- advantages
|
||||
- better for environment
|
||||
- easier to understand and control
|
||||
- downsides
|
||||
- you have to be interested (at least for most some benefits)
|
||||
- Links / Read section
|
||||
- blogroll?
|
||||
- books read section?
|
21
content/blog/theme-for-gitea.md
Executable file
21
content/blog/theme-for-gitea.md
Executable file
|
@ -0,0 +1,21 @@
|
|||
---
|
||||
title: "my new gitea theme appears to be usable"
|
||||
author: ""
|
||||
date: 2020-09-29T12:12:53+02:00
|
||||
categories:
|
||||
- natenomsblog
|
||||
tags:
|
||||
- gitea
|
||||
- opensource
|
||||
- webdesign
|
||||
|
||||
draft: false
|
||||
type: "post"
|
||||
description: "My – also new – gitea theme appears to be usable, as long as you're not logged in."
|
||||
---
|
||||
|
||||
My – [also new](https://vrifox.cc/blog/2020/vrifox.cc-rewritten-using-a-static-site-generator/) – gitea theme appears to be usable, as long as you're not logged in.
|
||||
|
||||
I wrote it from scratch in scss/sass, extra files for each page and sorted by **sub**page.
|
||||
|
||||
The source code can be found on my gitea instance: [git.vrifox.cc](https://git.vrifox.cc/vrifox/gitea-theme)
|
22
content/blog/vrifox.cc-rewritten-using-a-static-site-generator.md
Executable file
22
content/blog/vrifox.cc-rewritten-using-a-static-site-generator.md
Executable file
|
@ -0,0 +1,22 @@
|
|||
---
|
||||
title: "Vrifox.cc rewritten using a Static Site Generator"
|
||||
author: ""
|
||||
date: 2020-09-20T20:51:31+02:00
|
||||
categories:
|
||||
tags:
|
||||
- website
|
||||
- opensource
|
||||
|
||||
draft: false
|
||||
type: "post"
|
||||
description: "In the past I always preferred to make every bit myself (and disliked generators)."
|
||||
---
|
||||
|
||||
## Static Site Generator
|
||||
|
||||
In the past I always preferred to make every bit myself (and disliked generators). But I realized, that a static site generator might be the right thing for me, as I still make everything by myself, but can on the other hand make it more complex.
|
||||
|
||||
## Hugo
|
||||
|
||||
So I decided to learn [hugo](https://gohugo.io/) by just using it and this website is my first result.
|
||||
Still there lots of things to be done (content and design). :)
|
Loading…
Add table
Add a link
Reference in a new issue