Merge branch 'master' of code.ungleich.ch:ungleich-public/ungleich-staticcms
This commit is contained in:
sanghee
commit
d06a05eb8b
6 changed files with 313 additions and 16 deletions
107
content/u/products/dns-server-as-a-service/contents.lr
Normal file
107
content/u/products/dns-server-as-a-service/contents.lr
Normal file
|
|
@ -0,0 +1,107 @@
|
||||||
|
_discoverable: no
|
||||||
|
---
|
||||||
|
_hidden: no
|
||||||
|
---
|
||||||
|
title: DNS Server (as a service)
|
||||||
|
---
|
||||||
|
subtitle: Manage your own DNS records
|
||||||
|
---
|
||||||
|
headline1: Unlimited domains
|
||||||
|
---
|
||||||
|
headline2: GitOps flow
|
||||||
|
---
|
||||||
|
headline3: Worry free DNS
|
||||||
|
---
|
||||||
|
header_background_color: #1393B4
|
||||||
|
---
|
||||||
|
header_text_color: text-light
|
||||||
|
---
|
||||||
|
nav_classes: navbar-dark
|
||||||
|
---
|
||||||
|
FIXMEimage: /u/image/cards/supportsystem.jpg
|
||||||
|
---
|
||||||
|
feature1_title: Scalable
|
||||||
|
---
|
||||||
|
feature1_text:
|
||||||
|
Need just a single DNS server? Easy, we got you covered.
|
||||||
|
Need 2, 3 or many more DNS servers? No problem, deploy and manage them
|
||||||
|
exactly the same.
|
||||||
|
---
|
||||||
|
feature2_title: Made for developers with GitOps
|
||||||
|
---
|
||||||
|
feature2_text:
|
||||||
|
How should one manage DNS zones? What kind of configuration utility
|
||||||
|
should one use? There is a simple answer to this: none at all. Simply
|
||||||
|
commit your DNS zones to a git repository, push it - done. Everything
|
||||||
|
else is taken care of by the our infrastructure.
|
||||||
|
---
|
||||||
|
feature3_title: Concentrate your core business
|
||||||
|
---
|
||||||
|
feature3_text: Don't worry - be happy
|
||||||
|
With the hosted DNS server you can focus on your
|
||||||
|
core business. The system upgrade and maintaenance is taken cared by us.
|
||||||
|
---
|
||||||
|
content1_text:
|
||||||
|
|
||||||
|
## DNS Server as a Service (DNSSaaS)
|
||||||
|
|
||||||
|
This service allows you to manage DNS entries on your own DNS
|
||||||
|
servers. You manage zone files and zone records in the standard BIND
|
||||||
|
format.
|
||||||
|
|
||||||
|
### Not included
|
||||||
|
|
||||||
|
This service does not register a domain or manage your SSL
|
||||||
|
certificates. It is purely allowing you to manage your DNS zones files
|
||||||
|
without having to run your own DNS server.
|
||||||
|
|
||||||
|
The DNS server does not support IXFR or AXFR request. The
|
||||||
|
distribution of DNS information is assumed to be done by other means
|
||||||
|
such as git.
|
||||||
|
|
||||||
|
## Features
|
||||||
|
|
||||||
|
The provided DNS servers are reachable via IPv6 and IPv4.
|
||||||
|
The DNS servers are configured to pull from the configured repository
|
||||||
|
every 5 minutes.
|
||||||
|
|
||||||
|
If you order more than one DNS server, we offer to place them into
|
||||||
|
different data centers and IP ranges.
|
||||||
|
|
||||||
|
## How to use the DNS servers
|
||||||
|
|
||||||
|
There are a few simple steps required:
|
||||||
|
|
||||||
|
* Create a git repository anywhere you want - for instance on
|
||||||
|
[code.ungleich.ch](https://code.ungleich.ch) with an [ungleich
|
||||||
|
account](https://account.ungleich.ch).
|
||||||
|
* Create the zone files in the directory "zones/"
|
||||||
|
* Every file in the zones/ directory becomes a zone served by the DNS
|
||||||
|
server
|
||||||
|
* The zone ("domain") is infered from the filename
|
||||||
|
* Symbolic links are supported, so you can have different zones with
|
||||||
|
the same content
|
||||||
|
|
||||||
|
|
||||||
|
## Fully Open Source and IPv6 enabled
|
||||||
|
|
||||||
|
The DNS is completely based on Open
|
||||||
|
Source Software components. From the operating system to the software
|
||||||
|
stack, nothing is closed. This service is based
|
||||||
|
on [Knot-DNS](https://www.knot-dns.cz/).
|
||||||
|
|
||||||
|
## Zero Carbon
|
||||||
|
|
||||||
|
The DNS servers are running in our [Zero Carbon
|
||||||
|
Data Center.](httsp://datacenterlight.ch)
|
||||||
|
|
||||||
|
## Pricing
|
||||||
|
|
||||||
|
The hosted DNS server including IPv6 and IPv4 reachability is 17
|
||||||
|
CHF/month with a 25 CHF setup fee.
|
||||||
|
|
||||||
|
## How to order
|
||||||
|
|
||||||
|
As the support system can be setup for very different use cases, we
|
||||||
|
recommend to contact us at **support -at- ungleich.ch** to discuss how
|
||||||
|
you would like to have your system setup.
|
||||||
123
content/u/products/vpn-server-as-a-service/contents.lr
Normal file
123
content/u/products/vpn-server-as-a-service/contents.lr
Normal file
|
|
@ -0,0 +1,123 @@
|
||||||
|
_discoverable: no
|
||||||
|
---
|
||||||
|
_hidden: no
|
||||||
|
---
|
||||||
|
title: VPN Server (as a service)
|
||||||
|
---
|
||||||
|
subtitle: Manage your own VPN connections
|
||||||
|
---
|
||||||
|
headline1: Your own VPN server
|
||||||
|
---
|
||||||
|
headline2: GitOps flow
|
||||||
|
---
|
||||||
|
headline3: Worry free VPN
|
||||||
|
---
|
||||||
|
header_background_color: #1393B4
|
||||||
|
---
|
||||||
|
header_text_color: text-light
|
||||||
|
---
|
||||||
|
nav_classes: navbar-dark
|
||||||
|
---
|
||||||
|
FIXMEimage: /u/image/cards/supportsystem.jpg
|
||||||
|
---
|
||||||
|
feature1_title: Ready for teams
|
||||||
|
---
|
||||||
|
feature1_text:
|
||||||
|
|
||||||
|
|
||||||
|
---
|
||||||
|
feature2_title: Made for developers with GitOps
|
||||||
|
---
|
||||||
|
feature2_text:
|
||||||
|
How should one manage VPN zones? What kind of configuration utility
|
||||||
|
should one use? There is a simple answer to this: none at all. Simply
|
||||||
|
commit your VPN zones to a git repository, push it - done. Everything
|
||||||
|
else is taken care of by the our infrastructure.
|
||||||
|
---
|
||||||
|
feature3_title: Concentrate your core business
|
||||||
|
---
|
||||||
|
feature3_text: Don't worry - be happy
|
||||||
|
With the hosted VPN server you can focus on your
|
||||||
|
core business. The system upgrade and maintaenance is taken cared by us.
|
||||||
|
---
|
||||||
|
content1_text:
|
||||||
|
|
||||||
|
## VPN Server as a Service (VPNSaaS)
|
||||||
|
|
||||||
|
This service allows you to manage VPN connections on your own VPN
|
||||||
|
servers. You manage client configurations using the standard
|
||||||
|
Wireguard configuration format.
|
||||||
|
|
||||||
|
## Features
|
||||||
|
|
||||||
|
The provided VPN servers are reachable via IPv6 and IPv4.
|
||||||
|
|
||||||
|
They are available in IPv6 only and dual stack (IPv6 + IPv4) versions.
|
||||||
|
|
||||||
|
The VPN servers are configured to pull from the configured repository
|
||||||
|
every 5 minutes.
|
||||||
|
|
||||||
|
If you order more than one VPN server, we offer to place them into
|
||||||
|
different data centers and IP ranges.
|
||||||
|
|
||||||
|
## How to use the VPN servers
|
||||||
|
|
||||||
|
There are a few simple steps required:
|
||||||
|
|
||||||
|
* Create a git repository anywhere you want - for instance on
|
||||||
|
[code.ungleich.ch](https://code.ungleich.ch) with an [ungleich
|
||||||
|
account](https://account.ungleich.ch).
|
||||||
|
* Create a wireguard configuration file named wg0.conf
|
||||||
|
|
||||||
|
## VPN Server modes
|
||||||
|
|
||||||
|
The needs for VPN protection are different depending on your situation
|
||||||
|
and we show some common modes on how to use the VPN server.
|
||||||
|
|
||||||
|
### IPv6 only
|
||||||
|
|
||||||
|
If you want to enable your clients with IPv6, you can assign
|
||||||
|
IPv6 addresses or IPv6 subnetworks to the clients.
|
||||||
|
|
||||||
|
### Dedicated Public IPv4
|
||||||
|
|
||||||
|
If you want your client to be reachable via IPv4 from the outside, you
|
||||||
|
can make them reachable by assigning the client a dedicated public
|
||||||
|
IPv4 address.
|
||||||
|
|
||||||
|
This mode can be combined with the IPv6 mode above.
|
||||||
|
|
||||||
|
### Shared Public IPv4
|
||||||
|
|
||||||
|
If you want your your clients to reach the IPv4 Internet via a shared
|
||||||
|
public IPv4 address. This is the "typical VPN mode".
|
||||||
|
|
||||||
|
This mode can be combined with the IPv6 mode above.
|
||||||
|
|
||||||
|
## Fully Open Source and IPv6 enabled
|
||||||
|
|
||||||
|
The VPN is completely based on Open
|
||||||
|
Source Software components. From the operating system to the software
|
||||||
|
stack, nothing is closed. This service is based
|
||||||
|
on [Wireguard](https://www.wireguard.com/).
|
||||||
|
|
||||||
|
## Zero Carbon Hosting
|
||||||
|
|
||||||
|
The VPN servers are running in our [Zero Carbon
|
||||||
|
Data Center.](https://datacenterlight.ch)
|
||||||
|
|
||||||
|
## Pricing
|
||||||
|
|
||||||
|
Your own VPN server is available in 2 versions:
|
||||||
|
|
||||||
|
* IPv6 only VPN server with a /48 network: 37 CHF/month
|
||||||
|
* Dual stack (IPv6+IPv4) VPN server with a /48 network: 46.5 CHF/month
|
||||||
|
|
||||||
|
Every additional public IPv6 /48 network is 5 CHF/month.
|
||||||
|
Every additional public IPv4 address is 9.5 CHF/month.
|
||||||
|
|
||||||
|
The one time setup fee is 25 CHF.
|
||||||
|
|
||||||
|
## How to order
|
||||||
|
|
||||||
|
You can order via **support -at- ungleich.ch**.
|
||||||
|
|
@ -6,7 +6,7 @@ image: /u/image/cards/hack4glarus.png
|
||||||
---
|
---
|
||||||
description1:
|
description1:
|
||||||
|
|
||||||
##The Hackathon of Glarus
|
## The Hackathon of Glarus
|
||||||
|
|
||||||
Hack4Glarus is the first hackathon of Glarus. It is your chance to
|
Hack4Glarus is the first hackathon of Glarus. It is your chance to
|
||||||
meet & hack with geniuses of Switzerland and the world. To our
|
meet & hack with geniuses of Switzerland and the world. To our
|
||||||
|
|
|
||||||
|
|
@ -0,0 +1,51 @@
|
||||||
|
title: Mini Hack4Glarus 2022-03
|
||||||
|
---
|
||||||
|
subtitle: The first Hack4Glarus since Corona started
|
||||||
|
---
|
||||||
|
description1:
|
||||||
|
|
||||||
|
## Hack4Glarus in the Corona times
|
||||||
|
|
||||||
|
As many of you know, before Corona we had the bi-yearly
|
||||||
|
[Hack4Glarus](https://hack4glarus.ch) in Digital Glarus.
|
||||||
|
For everyone's protection, we cancelled all events. While the health
|
||||||
|
aspect was the main reason to cancel the event, the logistic aspects
|
||||||
|
(potentially quarantine 14 days on arrival, potentially quarantine 14
|
||||||
|
days after departure) also played a big role for us to cancel the
|
||||||
|
event.
|
||||||
|
|
||||||
|
## Introducting the Mini-Hack4Glarus
|
||||||
|
|
||||||
|
The measures are slowly being removed in many countries, including
|
||||||
|
Switzerland. While we are taking it a bit slower at ungleich in
|
||||||
|
regards to opening up, we also want to try to slowly normalise our
|
||||||
|
lives.
|
||||||
|
|
||||||
|
For this reason we are launching a series of Mini-Hack4Glarus at the
|
||||||
|
[Hacking Villa Diesbach](/u/projects/hacking-villa). Each of the
|
||||||
|
Mini-Hack4Glarus will be limited in terms of participants to keep it
|
||||||
|
comfortable for everyone attending.
|
||||||
|
|
||||||
|
|
||||||
|
## 2022-03: Mini-Hack4Glarus No. 1
|
||||||
|
|
||||||
|
The first Mini-Hack4Glarus will take place from the 18th of March to
|
||||||
|
20th of March. It is limited to 5 participants, so that we can ensure
|
||||||
|
that everyone can sleep in their own room and that we have enough
|
||||||
|
space.
|
||||||
|
|
||||||
|
The topic of the Mini-Hack4Glarus No. 1 is:
|
||||||
|
"**Corona: been there, done that**". The objective is to discuss the
|
||||||
|
learning of the Corona pandemic, which learnings there are
|
||||||
|
from it and which role Open Source and offsite places like Digital
|
||||||
|
Glarus can play in our future lives.
|
||||||
|
|
||||||
|
If you are interested in participating, submit a proposal
|
||||||
|
in the [Mini
|
||||||
|
Hack4Glarus
|
||||||
|
2022-03 Redmine
|
||||||
|
project](https://redmine.ungleich.ch/projects/mini-hack4glarus-2022-03/issues/new)
|
||||||
|
until 2022-03-11.
|
||||||
|
|
||||||
|
If you do not yet have an ungleich account, you can create one
|
||||||
|
on [account.ungleich.ch](https://account.ungleich.ch).
|
||||||
|
|
@ -77,7 +77,12 @@ Create a django project that provides the following features:
|
||||||
|
|
||||||
## Jobs
|
## Jobs
|
||||||
|
|
||||||
Currently there are no permanent job openings.
|
We are currently looking for three new engineers to join us:
|
||||||
|
|
||||||
|
* Senior DevOps (K8S, cdist, Alpine Linux) Engineer (20-100% role)
|
||||||
|
* Senior Developer (Python, Django) (20-100% role)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Bounties
|
## Bounties
|
||||||
|
|
||||||
|
|
@ -106,20 +111,6 @@ updates for some time, so we offer the following bounties:
|
||||||
* Eboard does not work in NAT64 scenarios, because it does not have IPv6 support
|
* Eboard does not work in NAT64 scenarios, because it does not have IPv6 support
|
||||||
** Bounty successful when a new eboard release was made with it
|
** Bounty successful when a new eboard release was made with it
|
||||||
|
|
||||||
### Bounty 2: Alpine Linux installable in IPv6 only networks
|
|
||||||
|
|
||||||
Alpine Linux currently does not start rdnssd in the installer nor does
|
|
||||||
it have the ndisc package installed.
|
|
||||||
|
|
||||||
The installer in particular needs to assign itself IPv6 addresses
|
|
||||||
(SLAAC should already work), needs to accept DNS servers and search
|
|
||||||
suffix from router advertisements (requires rdnssd running) and
|
|
||||||
wget/curl need to have IPv6 support to retrieve files via IPv6.
|
|
||||||
|
|
||||||
Present a short video that successfully shows the updated upstream
|
|
||||||
installer working in an IPv6 only network to install Alpine
|
|
||||||
Linux. Bounty is __100 CHF__.
|
|
||||||
|
|
||||||
### Bounty 3: Enable IPv6 only in the Linux kernel
|
### Bounty 3: Enable IPv6 only in the Linux kernel
|
||||||
|
|
||||||
As you might remember, we created
|
As you might remember, we created
|
||||||
|
|
@ -176,3 +167,24 @@ On the wireguard mailing list it was discussed whether a peer can have
|
||||||
multiple IP addresses. This could be a proper solution, as it also
|
multiple IP addresses. This could be a proper solution, as it also
|
||||||
addresses the case when a VPN server has multiple IPv6 or IPv4
|
addresses the case when a VPN server has multiple IPv6 or IPv4
|
||||||
addresses.
|
addresses.
|
||||||
|
|
||||||
|
## Historic Bounties
|
||||||
|
|
||||||
|
### Bounty 2: Alpine Linux installable in IPv6 only networks
|
||||||
|
|
||||||
|
Alpine Linux currently does not start rdnssd in the installer nor does
|
||||||
|
it have the ndisc package installed.
|
||||||
|
|
||||||
|
The installer in particular needs to assign itself IPv6 addresses
|
||||||
|
(SLAAC should already work), needs to accept DNS servers and search
|
||||||
|
suffix from router advertisements (requires rdnssd running) and
|
||||||
|
wget/curl need to have IPv6 support to retrieve files via IPv6.
|
||||||
|
|
||||||
|
Present a short video that successfully shows the updated upstream
|
||||||
|
installer working in an IPv6 only network to install Alpine
|
||||||
|
Linux. Bounty is __100 CHF__.
|
||||||
|
|
||||||
|
```
|
||||||
|
Solution: Alpine Linux now ships with dhcpcd enabling IPv6 address
|
||||||
|
acquisition as well as name resolution.
|
||||||
|
```
|
||||||
|
|
|
||||||
|
|
@ -198,3 +198,7 @@ type = url
|
||||||
[fields.image]
|
[fields.image]
|
||||||
label = Index Image
|
label = Index Image
|
||||||
type = url
|
type = url
|
||||||
|
|
||||||
|
[children]
|
||||||
|
model = product
|
||||||
|
order_by = title
|
||||||
Loading…
Reference in a new issue