zola: build
This commit is contained in:
parent
b4dbfaff3b
commit
e5fb61b16e
|
@ -100,7 +100,7 @@ headscale in a little more detail, which might be worth checking out.</p
|
|||
post, and the inspiration for this one came seemingly randomly - I hope
|
||||
someone finds this useful.</p>
|
||||
<div class="footnote-definition" id="1"><sup class="footnote-definition-label">1</sup>
|
||||
<p>Naturally, you shouldn't just copy and paste the snippets into</p>
|
||||
<p>Naturally, you shouldn't just copy and paste the snippets into your own config. Do your research first!</p>
|
||||
</div>
|
||||
</content>
|
||||
</entry>
|
||||
|
|
|
@ -19,4 +19,4 @@
|
|||
</span><span> };
|
||||
</span><span> };
|
||||
</span><span>};
|
||||
</span></code></pre><li><p>This probably doesn't need to be said, but <strong>use strong passwords</strong>!</p><li><p>Host a <a rel="nofollow noreferrer" href=https://fail2ban.org>fail2ban</a> instance to ban hosts making bruteforce attempts.</p></ul><p>I think that's all there is for almost everyone, and is basically the minimal amount of effort a home server administrator should do. Personally, I would prefer to enforce a VPN connection in order to access my <em>personal</em> services for that extra layer of security (because why'd they need to be exposed to the internet?). This can be done faily easily with tailscale, and for the slightly more paranoid - <a rel="nofollow noreferrer" href=https://headscale.net/>headscale</a> is a viable...alternative? Anyways, I've got a blog post that explores headscale in a little more detail, which might be worth checking out.<p>Well, that's all I wanted to say. It's been a while since my last blog post, and the inspiration for this one came seemingly randomly - I hope someone finds this useful.<div class=footnote-definition id=1><sup class=footnote-definition-label>1</sup><p>Naturally, you shouldn't just copy and paste the snippets into</div></article><div class=giscus></div></div><footer><div class=copyright><p>© 2024 Muhammad Nauman Raza</div><div class=credits>powered by <a rel="noreferrer noopener" href=https://www.getzola.org target=_blank>zola</a> and <a rel="noreferrer noopener" href=https://github.com/isunjn/serene target=_blank>serene</a></div></footer></main></div><script src=/js/lightense.min.js></script><script src=/js/main.js></script>
|
||||
</span></code></pre><li><p>This probably doesn't need to be said, but <strong>use strong passwords</strong>!</p><li><p>Host a <a rel="nofollow noreferrer" href=https://fail2ban.org>fail2ban</a> instance to ban hosts making bruteforce attempts.</p></ul><p>I think that's all there is for almost everyone, and is basically the minimal amount of effort a home server administrator should do. Personally, I would prefer to enforce a VPN connection in order to access my <em>personal</em> services for that extra layer of security (because why'd they need to be exposed to the internet?). This can be done faily easily with tailscale, and for the slightly more paranoid - <a rel="nofollow noreferrer" href=https://headscale.net/>headscale</a> is a viable...alternative? Anyways, I've got a blog post that explores headscale in a little more detail, which might be worth checking out.<p>Well, that's all I wanted to say. It's been a while since my last blog post, and the inspiration for this one came seemingly randomly - I hope someone finds this useful.<div class=footnote-definition id=1><sup class=footnote-definition-label>1</sup><p>Naturally, you shouldn't just copy and paste the snippets into your own config. Do your research first!</div></article><div class=giscus></div></div><footer><div class=copyright><p>© 2024 Muhammad Nauman Raza</div><div class=credits>powered by <a rel="noreferrer noopener" href=https://www.getzola.org target=_blank>zola</a> and <a rel="noreferrer noopener" href=https://github.com/isunjn/serene target=_blank>serene</a></div></footer></main></div><script src=/js/lightense.min.js></script><script src=/js/main.js></script>
|
Loading…
Reference in a new issue