Commit 5eb295cf authored by Thomas Lake's avatar Thomas Lake 🔧
Browse files

Introduce myself, and add a post

parent 847d707b
Pipeline #763 passed with stages
in 1 minute and 14 seconds
---
name: "Thomas Lake"
# Delete the following if unused
twitter: "@DrTomLake"
github: "tswsl1989"
website: "https://sucs.org/~tswsl1989/"
---
Marine Energy researcher in the [ZCCE Energy and Environment Research Group](https://www.swansea.ac.uk/engineering/zcce/energy-environment/). One of the SUCS admin team, trying to be as useful as possible when time permits.
---
title: "Attempting to deploy Hugo with GitLab CI/CD"
date: 2020-09-24T20:21:00+01:00
draft: false
toc: false
authors:
- Thomas Lake
tags:
- sucs
- gitlab
---
How do you arrange to deploy a new project on to an old server, without opening up a raft of vulnerabilities?
The answer to that is, unsurprisingly, "with difficulty"
<!--more-->
SUCS has a single main server, called silver, that provides pretty much all of our public facing services. There are a few things, such as gitlab, that live as virtual machines on a second server (called iridium).
The current deployment method uses a PHP script hosted on the blogs site that, when called from an authorised IP, will download the latest blog build from GitLab and extract it on the server for the world to see.
This appeared to be a more tightly constrained solution than allowing SSH access for the user that the site runs as, but still feels like a bit of a bodge. At least it fits in with the rest of the bodges, patches and decade old "temporary" solutions that make up most of the SUCS infrastructure!
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment