fix: remaining console errors
This commit is contained in:
parent
43b1183e9a
commit
cb2c5ae8c9
4 changed files with 4 additions and 8 deletions
|
|
@ -17,7 +17,7 @@
|
|||
// svelte-ignore unused-export-let
|
||||
export let data;
|
||||
// svelte-ignore unused-export-let
|
||||
export let errors;
|
||||
export let form;
|
||||
|
||||
export let title;
|
||||
// svelte-ignore unused-export-let
|
||||
|
|
|
|||
|
|
@ -3,10 +3,6 @@
|
|||
import ListItem from '$components/ListItem.svelte';
|
||||
import Link from '$components/Link.svelte';
|
||||
import type { Skill } from '$lib/utils/types';
|
||||
// svelte-ignore unused-export-let
|
||||
export let data;
|
||||
// svelte-ignore unused-export-let
|
||||
export let errors;
|
||||
|
||||
let _SKILLS = [
|
||||
{ name: 'Web development (React/Svelte)', started: 2019 },
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ bridge for networking so that I can resolve my other services with DNS. After th
|
|||
navigate to http://IP:17170 and are presented with the administration panel, where we can
|
||||
create users and groups.
|
||||
|
||||
<Image meta={overview} />
|
||||
<Image meta={overview} alt="LLDAP Userinterface"/>
|
||||
|
||||
## Integration with Caddy
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ cloud provider probably organizes good routing to both sides. Since I meant to t
|
|||
Oracles free tier anyway, it seemed like a good opportunity to learn ansible properly and
|
||||
develop with IaC scripts to set up a reverse proxy in the cloud.
|
||||
|
||||
<Image meta={architecture} />
|
||||
<Image meta={architecture} alt="Architecture of the site two site wireguard setup"/>
|
||||
|
||||
1. Create Wireguard keys. If the CLI is not an option [this
|
||||
website](https://www.wireguardconfig.com/) is cool too (keys are client-sided generated)
|
||||
|
|
@ -34,7 +34,7 @@ develop with IaC scripts to set up a reverse proxy in the cloud.
|
|||
3. Create a new peer as follows. Important is the entry to allow the IP address of the
|
||||
cloud wg endpoint, otherwise the cloud cant ping back home.
|
||||
<div style="max-width:600px">
|
||||
<Image meta={peer} />
|
||||
<Image meta={peer} alt="Mikrotik router peer setup"/>
|
||||
</div>
|
||||
4. I had to adjust the firewall rules to allow communication with the tunnel network.
|
||||
5. On the proxy server we use similar settings. Interestingly enough, the Mikrotik wg
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue