Jeffrey Paul

Web Project

sneak plans

  1. Chat Project / Realtime Communication System
    • chat.example.com
    • adjunct to Discord, not a replacement, users can use whichever they prefer
    • likely IRC-based for v1, perhaps Riot protocol later
    • On-prem, in the shop
    • TLS for all connections
    • Available via direct TLS connection to service
    • Available via Tor hidden service endpoint
    • Optional: bridged to existing Discord chat
    • Document all configuration/admin in markdown, pending wiki overhaul for RTFM
  2. Self-hosted Discourse Forum
    • bbs.example.com
    • Discourse supports emailing people their notifications
    • Document all configuration/admin in markdown, pending wiki overhaul for RTFM
  3. Self-hosted Mailing Lists
    • lists.example.com
    • Move from Google Groups (which currently requires a Google Account)
    • Document all configuration/admin in markdown, pending wiki overhaul for RTFM
  4. Migrate RTFM to actual wiki instead of mkdocs for online editing
    • phase one: manual account creation for editors
    • later: ldap/sso integration?
    • update information in the site, make sure stuff is current/valid
    • write new homepage for www as an article on the wiki
  5. Overhaul of public main www site
    • Stage one: set up staging site on different domain for review/dev
    • Replace Drupal with static site generation such as Hugo or Jekyll
    • Move member services Drupal site to subdomain
    • Pull homepage from a defined wiki page at static site generation time
    • Authoritative and all-inclusive list of web resources on homepage:
      • Forums and Mailing Lists, with easy embedded signup form
      • Realtime Chat system (riot/irc)
      • Discord
      • Wiki
      • Future: Gitea?
    • Clarify that opening hours are open to the public/nonmembers

Result:

Web presence is the following:

Things Needed from Infrastructure Admin for Chat Project

  1. PoE in cabinet
    • I can donate a PoE switch if we don’t have one already
  2. Dangle the chat system RPI4 off the PoE
  3. Assign a static IP (either in the DHCP server for the MAC address, or statically configured on the device itself, following whatever the existing convention is)
  4. Forward port 6697 from the external IP to the RPI4 chat system

sneak SSH keys

https://sneak.cloud/authorized_keys

sneak contact info