Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/infrastructure/access_System.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ The keycode access system runs in parallel with the fob access system.
### Hardware

It consists of:

- A keypad outside
- A pi Inside
- A relay board inside
Expand All @@ -26,4 +27,4 @@ Common numbers like `12345678` etc have already been blacklisted so can't accien
The current system has been in service for many years now and has proven mostly reliable.
However, it requires a Pi 1, due to a custom had that was made for it.

It's therefore a candidate for modernising using a Pi 4.
It's therefore a candidate for modernising using a Pi 4.
6 changes: 3 additions & 3 deletions docs/infrastructure/nginx.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# NGINX Setup

Original article - https://francoisromain.medium.com/host-multiple-websites-with-https-inside-docker-containers-on-a-single-server-18467484ab95
Original article - <https://francoisromain.medium.com/host-multiple-websites-with-https-inside-docker-containers-on-a-single-server-18467484ab95>

## Hosting multiple websites on a single Virtual Private Server is simple and efficient. Nowadays, HTTPS is a required feature for any website.

Expand Down Expand Up @@ -127,7 +127,7 @@ First create the network:

Then create the reverse proxy with the `nginx`, `nginx-gen` and `nginx-letsencrypt` containers from the `docker-compose.yml` file:

`$ cd /srv/www/nginx-proxy/`
`$ cd /srv/www/nginx-proxy/`
`$ docker-compose up -d`

Now the reverse-proxy is running.
Expand Down Expand Up @@ -177,7 +177,7 @@ networks:

**Now lets start the website with:**

`$ cd /srv/www/your-website.tld`
`$ cd /srv/www/your-website.tld`
`$ docker-compose up -d`

**The website is automatically detected by the reverse proxy, has a HTTPS certificate and is visible at https://your-website.tld .**
Expand Down
17 changes: 8 additions & 9 deletions docs/infrastructure/overview.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# ZeroCool

### Overview
### Overview
ZeroCool is the external server hosted at Hetzner and houses the majority of the tech infrastructure for the hackspace including

1. Main Website - https://www.hacman.org.uk
Expand All @@ -10,7 +10,7 @@ ZeroCool is the external server hosted at Hetzner and houses the majority of the

Setup by Rossy in November 2018 this contains the heart of our infrastructure

### Reverse Proxy
### Reverse Proxy

The server is setup with a reverse proxy that uses automatic configuration to set the forwarding of the sub domain to the correct docker instance rathr than manually needing configured. This is based on the following docker file https://github.com/nginx-proxy/nginx-proxy.git and the setup process is detailed [here](https://docs.hacman.org.uk/infrastructure/nginx)

Expand Down Expand Up @@ -136,7 +136,7 @@ Buddy.works is used to run the member system billing script that requires to be

Standard Discourse install operates on a seperate ip to the rest of the server

### SMTP Server
### SMTP Server

Until recently this was hosted with mailgun for free however due to the introduction of charges for that it we now currently use a mixture of Amazon Simple Email Service and smtp2go and is used for sending transactional email from each of the systems above

Expand All @@ -148,14 +148,13 @@ The Zerocool server is resticted to ssh access for security and GDPR reasons thi

We use uptimerobot to monitor each server application including the space internet itself, the systems can be checked using the status page at https://status.hacman.org.uk

### DNS Managmeent
### DNS Managmeent and Domain registration

All DNS management is done via cloudflare
All DNS management is done via Cloudflare, which is also the domain registrar

### Backups

The Database server is backup on a daily basis using sqlbak to a dedicated google drive
Backups are stored for 30 days

Daily File Backups are done and stored on google drive, these are kept for 2 days (space limitations)
The Database server is backup on a daily basis using sqlbak to a dedicated Google Drive
Backups are stored for 30 days

Daily File Backups are done and stored on Google Drive, these are kept for 2 days (space limitations)