The members of 57North Hacklab maintain infrastructure projects that help with the day-to-day running of the space, such as providing network access, telephony and web services.
Some of the things we run are considered to be required for the space to function and are listed under the Core Infrastructure section, others are provided on a best effort basis and we're not going to panic if they break.
“There is only one service provider whose interests are directly aligned with your own, yourself!”
Some things are required for the space to function properly. The things in this section are on that list.
If anything on this list isn't working please let us know (loudly).
The public facing site for the space: https://57north.org.uk/
The site is on github: https://github.com/hackerdeen/website
Hosted on garioch, from /srv/vhosts/57north/
SSL cert from letsencrypt - needs renewed (at least) every 90 days. letsencrypt_update
See also website
A temporary backup internet connection using hotspots can rigged by following the guide at lechacal.com
HackHub records details of members, payments, allows opening the door and setting the space status.
Hosted on finzean under the hackhub user. Running in a virtualenv in ~hackhub/.hackhub/. Code is in ~hackhub/hackhub/. Apache config /etc/apache2/sites-available/hub.57north.org.uk-le-ssl.conf.
57North ID Our login/signon system. Used by the membership system and anything else that wants to use space accounts.
Hosted on finzean. Under 57n-id user. Apache config /etc/apache2/site-available/id.57north.org.uk-le-ssl.conf.
On Finzean. Config in /etc/bind/
Accept mail for 57North domains and the mailing lists.
Runs on garioch
/etc/aliases has things to point contact addresses at addresses for the people handling them. Run newaliases after editing this.
Mailing lists can be managed with the commands in /usr/lib/mailman/bin
Stuff in the space that allows members to unlock the door with commands in hackhub. Currently a Pi Zero W controlling a relay that unlocks strike release plates on the downstairs and street doors.
See also Doorbot.
Main domain is 57north.org.uk We have previously used 57north.co and hackerdeen.org and still have some things using them (mailing lists on 57north.co, possibly some other stuff). At Some Point™ everything should be moved onto 57north.org.uk
Currently all owned by the space account at GANDI (details in the password store).
Actively Maintained Infrastructure:
|Digital Infrastructure||Digital Infrastructure The members of 57North Hacklab maintain infrastructure projects that help with the day-to-day running of the space, such as providing network access, telephony and web services. Some of the things we run are considered to be required for the space to function and are listed under the|
|Finzean||Finzean Finzean is one of our core servers. Services Port Service Purpose 22 sshd SSH 25 exim4 mail 80,443 apache2 web 53, 953 named DNS 389 slapd LDAP 12000 nodejs ? Websites Website Purpose hub hackhub ID SSO Service Services Hosted on Finzean|
|Garioch||Garioch Garioch is one of our core servers. Services Port Service Purpose 22 sshd SSH 25 master mail 53, 953 named DNS 3306 mysqld MySQL for ? Websites Website Purpose www Main Website git cgit for git lists Mailing Lists Let’s Encrypt is on this machine, it has been set to auto renew certs.|
|Hackhub||Hackhub Hackhub is our member database and lives on Finzean. It is very closely integrated with 57North ID and both need to be running. Hackhub code is hosted at Github. Hibby's work in progress attempt to set up hackhub on a server Requirements Some form of OS (Debian stable):|
|The Wiki||The Wiki The 57North Hacklab wiki runs somewhere. This wiki is available for all members of 57North Hacklab to share whatever content they wish to share with the wider community. The wiki is based on dokuwiki and has been configured with features that are useful to the hackerspace, e.g. documentation of member|
Infrastructure in need of a Maintainer:
|57North ID||57North ID 57North ID combines an LDAP server with a user management portal and a CAS IdP to become a single, centralised point for user identity within 57North. All 57North services should authenticate against it, which they can do in a handful of ways:|