Unicorn

From Noisebridge
Revision as of 02:25, 18 November 2018 by James (talk | contribs) (SSH Config)
Jump to: navigation, search

Unicorn is a homage to our long dead server, formerly known as Stallion. It has no guaranteed uptime or functionality; it is up to you to keep the services you want running, running. Like a stallion.
Pissingponynb.png

This utility server is 4 cores, 24gb ram, 120gb ssd storage and 12tb bandwidth.
Volunteers warmly encouraged to setup and maintain it! Please contact us via the main Noisebridge Discussion Mailing List


System Info

  • IP: 172.93.55.252
  • OS: Debian 9 x86_64
  • Web server: Nginx is running on ports 80 and 443
  • Domains: Current domains and subdomains hosted on this server: (see /etc/nginx/sites-enabled/*)
  • DNS: all *.noisebridge.info subdomains point to this server, as does the naked domain (noisebridge.info)
  • SSL: certbot runs every day to renew certs for all (sub)domains it knows about
  • To add a new service at, say, somethingcool.noisebridge.info...
    • Create a file similar to /etc/nginx/sites-available/noisebridge.info called /etc/nginx/sites-available/somethingcool.noisebridge.info
    • Run sudo ln -s /etc/nginx/sites-available/somethingcool.noisebridge.info /etc/nginx/sites-enabled/somethingcool.noisebridge.info; sudo nginx -t
    • If you don't get any errors, now run sudo service nginx restart

Rules and Guidelines

  • Be excellent to each other
    • Don't fuck up other people's shit
  • Usage of containers is encouraged where practical, but not required
    • Databases sometimes have issues running in Docker, for example
  • If you need a different version of some database that is already running on the default port, run the version you need in a Docker container, or on a different port (and that stores its data in a different directory!)


Access

For SSH access, ask @jslack, @elimisteve, or @Rando in Slack, or visit the Unicorn Slack channel and ask.


SSH Config

I can haz access?

Consider generating a new SSH key pair with

$ ssh-keygen -b 4096

then calling it, say, unicorn-nb, then add this to your ~/.ssh/config file:

Host unicorn-nb User noisebridge Hostname 172.93.55.252 PreferredAuthentications publickey IdentityFile ~/.ssh/unicorn-nb

If your SSH pub key (~/.ssh/unicorn-nb.pub) has been added to unicorn-nb:~/.ssh/authorized_keys, you should now be able to shell in by typing

$ ssh unicorn-nb

...and thanks to the ~/.ssh/config entry, the name of the server you're trying to SSH into -- namely unicorn-nb in this case -- should autocomplete!