Fix some dead links
This commit is contained in:
parent
31b395d308
commit
8d2b58e03c
7 changed files with 8 additions and 8 deletions
|
@ -70,7 +70,7 @@ Now start the containers, and you should be set!
|
||||||
|
|
||||||
Yes, yes it does! Duplicati can back up remotes now, which is great! Unfortunately backups are now very network intensive, which means the backups can be a lot slower than just reading off the local filesystem, but that's mostly fine. For that reason I wouldn't recommend this for huge datasets. If you're running Duplicati on a fast network connection, it's probably fine, but best test before relying on it!
|
Yes, yes it does! Duplicati can back up remotes now, which is great! Unfortunately backups are now very network intensive, which means the backups can be a lot slower than just reading off the local filesystem, but that's mostly fine. For that reason I wouldn't recommend this for huge datasets. If you're running Duplicati on a fast network connection, it's probably fine, but best test before relying on it!
|
||||||
|
|
||||||
I'm running it right now for some backups, take a look at [my setup](https://github.com/RealOrangeOne/infrastructure/tree/master/ansible/roles/intersect-docker/files/duplicati).
|
I'm running it right now for some backups, take a look at [my setup](https://github.com/RealOrangeOne/infrastructure/tree/master/ansible/roles/duplicati).
|
||||||
|
|
||||||
## _"But what about other backup tools, like Restic?"_
|
## _"But what about other backup tools, like Restic?"_
|
||||||
|
|
||||||
|
|
|
@ -20,7 +20,7 @@ To build the sensor, you'll need a few things:
|
||||||
|
|
||||||
And a few components:
|
And a few components:
|
||||||
|
|
||||||
- [ESPHome-compatible](https://esphome.io/#devices) board (I'm using a NodeMCU from [amazon.co.uk](https://www.amazon.co.uk/MakerHawk-Internet-Development-Wireless-Micropython/dp/B07M8Q38LK))
|
- [ESPHome-compatible](https://esphome.io/#devices) board (I'm using a NodeMCU from [amazon.co.uk](https://www.amazon.co.uk/s?k=nodemcu))
|
||||||
- DHT11 (DHT22 is significantly nicer, but more expensive)
|
- DHT11 (DHT22 is significantly nicer, but more expensive)
|
||||||
- Jumper cables (often come with the DHT)
|
- Jumper cables (often come with the DHT)
|
||||||
|
|
||||||
|
|
|
@ -9,7 +9,7 @@ tags: [linux, arch]
|
||||||
As a software engineer and perfectionist, I have my machines set up in a very specific way, so I can do my job properly and have everything just the way I like it. Thanks to my [dotfiles]({{< relref "projects/dotfiles" >}}), I have everything syncing up between machines, meaning the tools I use are configured correctly, the same, everywhere.
|
As a software engineer and perfectionist, I have my machines set up in a very specific way, so I can do my job properly and have everything just the way I like it. Thanks to my [dotfiles]({{< relref "projects/dotfiles" >}}), I have everything syncing up between machines, meaning the tools I use are configured correctly, the same, everywhere.
|
||||||
|
|
||||||
# OS
|
# OS
|
||||||
My current distro of choice is [Arch](https://www.archlinux.org/), specifically [Antergos](https://antergos.com/). My main reason for choosing arch is the [AUR](https://aur.archlinux.org/). Almost every package I can think of is packaged there, often by the community. It's great to be able to install things through one method and have everything update in a single command. Antergos is also far easier to install than raw arch, and has little to no bloat that comes with it.
|
My current distro of choice is [Arch](https://www.archlinux.org/), specifically [Antergos](https://web.archive.org/web/20190903082315/https://antergos.com/). My main reason for choosing arch is the [AUR](https://aur.archlinux.org/). Almost every package I can think of is packaged there, often by the community. It's great to be able to install things through one method and have everything update in a single command. Antergos is also far easier to install than raw arch, and has little to no bloat that comes with it.
|
||||||
|
|
||||||
## Desktop
|
## Desktop
|
||||||
My current desktop of choice is [i3](https://i3wm.org/). After spending a lot of time using [Gnome](https://www.gnome.org/), and always having windows either full screen or split, I tried out i3 in an attempt to use fewer resources, and it's amazing. Admittedly i3 doesn't look quite as nice, but it's far cleaner, and structured, and that's enough for me!
|
My current desktop of choice is [i3](https://i3wm.org/). After spending a lot of time using [Gnome](https://www.gnome.org/), and always having windows either full screen or split, I tried out i3 in an attempt to use fewer resources, and it's amazing. Admittedly i3 doesn't look quite as nice, but it's far cleaner, and structured, and that's enough for me!
|
||||||
|
@ -31,7 +31,7 @@ Whilst I use [ZSH](https://www.zsh.org/), I'm not a fan of the [super fancy them
|
||||||
|
|
||||||
![My shell prompt](shell-prompt.png)
|
![My shell prompt](shell-prompt.png)
|
||||||
|
|
||||||
I do have a fair number of plugins and aliases, thanks to both [oh my ZSH](http://ohmyz.sh/) and [my custom config](https://github.com/RealOrangeOne/dotfiles/tree/master/modules/shell/files).
|
I do have a fair number of plugins and aliases, thanks to both [oh my ZSH](http://ohmyz.sh/) and [my custom config](https://github.com/RealOrangeOne/dotfiles/tree/master/files/zshrc).
|
||||||
|
|
||||||
## Terminal Emulator
|
## Terminal Emulator
|
||||||
[Terminator](https://gnometerminator.blogspot.co.uk/p/introduction.html) is a really fast, simple terminal emulator, with features like pane splitting, resizing, and many colour customizations. I do plan to move over to [Alacritty](https://github.com/jwilm/alacritty) just as soon as it gets [scrollback support](https://github.com/jwilm/alacritty/pull/657), because it renders things a lot nicer, and uses far fewer resources. I'm also very partial to things written in rust!
|
[Terminator](https://gnometerminator.blogspot.co.uk/p/introduction.html) is a really fast, simple terminal emulator, with features like pane splitting, resizing, and many colour customizations. I do plan to move over to [Alacritty](https://github.com/jwilm/alacritty) just as soon as it gets [scrollback support](https://github.com/jwilm/alacritty/pull/657), because it renders things a lot nicer, and uses far fewer resources. I'm also very partial to things written in rust!
|
||||||
|
|
|
@ -10,7 +10,7 @@ Last year, I wrote [_My stack 2017_]({{< relref "posts/my-stack-2017" >}}), and
|
||||||
|
|
||||||
# OS
|
# OS
|
||||||
|
|
||||||
I'm still an [Antergos](https://antergos.com/) user, and have no sign of changing. I've had a few instabilities, but the [AUR](https://aur.archlinux.org/) and [Arch Wiki](https://wiki.archlinux.org/) are just fantastic!
|
I'm still an [Antergos](https://web.archive.org/web/20190903082315/https://antergos.com/) user, and have no sign of changing. I've had a few instabilities, but the [AUR](https://aur.archlinux.org/) and [Arch Wiki](https://wiki.archlinux.org/) are just fantastic!
|
||||||
|
|
||||||
## Desktop
|
## Desktop
|
||||||
|
|
||||||
|
|
|
@ -6,7 +6,7 @@ image: https://antergos.com/wp-content/uploads/2014/09/antergos-wallpaper.png
|
||||||
tags: [arch]
|
tags: [arch]
|
||||||
---
|
---
|
||||||
|
|
||||||
I've been an [Antergos](https://antergos.com/) user for almost three years, and I love it! It's like Arch, but with a simple installation process, and yields a near-pure Arch install, unlike Arch derivatives like [Manjaro](https://manjaro.org/). Unfortunately, on 21st May 2019, the [Antergos project ended](https://antergos.com/blog/antergos-linux-project-ends/). Those behind the project were unable to commit the time the project needed and deserved. I for one want to thank them for the effort they have put in!
|
I've been an [Antergos](https://web.archive.org/web/20190903082315/https://antergos.com/) user for almost three years, and I love it! It's like Arch, but with a simple installation process, and yields a near-pure Arch install, unlike Arch derivatives like [Manjaro](https://manjaro.org/). Unfortunately, on 21st May 2019, the [Antergos project ended](https://web.archive.org/web/20190816093432/https://antergos.com/blog/antergos-linux-project-ends/). Those behind the project were unable to commit the time the project needed and deserved. I for one want to thank them for the effort they have put in!
|
||||||
|
|
||||||
The issue now is what to do with my machines which run Antergos (of which there are currently 5). Technically, I don't need to do anything, the Antergos team state that because existing installations are _basically_ vanilla arch, there's no need to panic and wipe:
|
The issue now is what to do with my machines which run Antergos (of which there are currently 5). Technically, I don't need to do anything, the Antergos team state that because existing installations are _basically_ vanilla arch, there's no need to panic and wipe:
|
||||||
|
|
||||||
|
|
|
@ -22,7 +22,7 @@ Stage two uses a completely different container as the base, `nginx:latest-alpin
|
||||||
|
|
||||||
## Deployment
|
## Deployment
|
||||||
|
|
||||||
This container is built using GitHub actions, automatically on push, and then uploaded to GitHubs package registry. A [docker-compose configuration](https://github.com/RealOrangeOne/infrastructure/blob/master/ansible/roles/docker/files/theorangeone.net/docker-compose.yml) is pre-installed on my server, pointed at this container, and with the necessary Traefik rules to route traffic correctly.
|
This container is built using GitHub actions, automatically on push, and then uploaded to GitHubs package registry. A [docker-compose configuration](https://github.com/RealOrangeOne/infrastructure/blob/master/ansible/roles/website/files/docker-compose.yml) is pre-installed on my server, pointed at this container, and with the necessary Traefik rules to route traffic correctly.
|
||||||
|
|
||||||
To maintain auto-deployment functionality, something I find really important, I run [watchtower](https://containrrr.github.io/watchtower/). Watchtower polls the repositories of all the containers I depend on, and when there are changes, automatically pulls and restarts them. The poll interval is five minutes, so it's a slower update than Netlify, but for my needs it's fine. Generally this is ill-advised as it can cause containers to update unexpectedly, but I pin containers properly, so I'm not worried.
|
To maintain auto-deployment functionality, something I find really important, I run [watchtower](https://containrrr.github.io/watchtower/). Watchtower polls the repositories of all the containers I depend on, and when there are changes, automatically pulls and restarts them. The poll interval is five minutes, so it's a slower update than Netlify, but for my needs it's fine. Generally this is ill-advised as it can cause containers to update unexpectedly, but I pin containers properly, so I'm not worried.
|
||||||
|
|
||||||
|
|
|
@ -22,7 +22,7 @@ If we combine revealjs and a static site generator, we get many benefits. Beside
|
||||||
## `hugo-theme-revealjs`
|
## `hugo-theme-revealjs`
|
||||||
`hugo-theme-revealjs` is a theme for Hugo which combines the two: a powerful static site generator, with a powerful presentation framework. The theme makes writing content east, especially for those who like content organized. Each slide is a separate markdown file, which can be grouped into sections to form the vertical slide groups Reveal is famous for. All settings and configuration options for Reveal are accessible through this theme, in an attempt to make it versatile and usable by all people.
|
`hugo-theme-revealjs` is a theme for Hugo which combines the two: a powerful static site generator, with a powerful presentation framework. The theme makes writing content east, especially for those who like content organized. Each slide is a separate markdown file, which can be grouped into sections to form the vertical slide groups Reveal is famous for. All settings and configuration options for Reveal are accessible through this theme, in an attempt to make it versatile and usable by all people.
|
||||||
|
|
||||||
The source for the theme is on [GitHub](https://github.com/RealOrangeOne/hugo-theme-revealjs), and can be [installed](https://gohugo.io/themes/installing-and-using-themes/) as if it were any other theme.
|
The source for the theme is on [GitHub](https://github.com/RealOrangeOne/hugo-theme-revealjs), and can be [installed](https://gohugo.io/hugo-modules/theme-components/) as if it were any other theme.
|
||||||
|
|
||||||
{{< iframe src="https://hugo-theme-revealjs.netlify.com/" >}}
|
{{< iframe src="https://hugo-theme-revealjs.netlify.com/" >}}
|
||||||
Example presentation, which shows off some features of the theme.
|
Example presentation, which shows off some features of the theme.
|
||||||
|
|
Loading…
Reference in a new issue