Replace all post_url with Hugo ref blocks
This commit is contained in:
@ -12,7 +12,7 @@ a bit different back in 2016. There was a switch provided by Litecom in which
|
||||
ports were resold OEM to upstream ISPs, and Litecom would provide the L2
|
||||
backhaul to a central place to hand off the customers to the ISPs, in my case
|
||||
Easyzone. In Oct'16, Fredy asked me if I could do a test of
|
||||
Fiber7-on-Litecom, which I did and reported on in a [blog post]({% post_url 2016-10-07-fiber7-litexchange %}).
|
||||
Fiber7-on-Litecom, which I did and reported on in a [blog post]({{< ref "2016-10-07-fiber7-litexchange" >}}).
|
||||
|
||||
Some time early 2017, Init7 deployed a POP in Dietlikon (790BRE) and then
|
||||
magically another one in Brüttisellen (1790BRE). It's a funny story
|
||||
@ -78,7 +78,7 @@ and aggregation switches are C9500-32C which take 32x QSFP+ (40/100Gbit).
|
||||
As a subscriber, we all got a courtesy headsup on the date of 1790BRE's upgrade.
|
||||
It was [scheduled](https://as13030.net/status/?ticket=4238550) for Thursday Aug 26th
|
||||
starting at midnight. As I've written about before (for example at the bottom of my
|
||||
[Bucketlist post]({% post_url 2021-07-26-bucketlist %})), I really enjoy the immediate
|
||||
[Bucketlist post]({{< ref "2021-07-26-bucketlist" >}})), I really enjoy the immediate
|
||||
gratification of physical labor in a datacenter. Most of my projects at work are on the
|
||||
quarters-to-years timeframe, and being able to do a thing and see the result of that
|
||||
thing ~immmediately, is a huge boost for me.
|
||||
|
Reference in New Issue
Block a user