Technical infrastructure: Difference between revisions
(→TODO) |
|||
| Line 25: | Line 25: | ||
#[[Install Server]] <- planning done, but not yet installed and running. See https://github.com/freegeek-seattle/install_pxeserver | #[[Install Server]] <- planning done, but not yet installed and running. See https://github.com/freegeek-seattle/install_pxeserver | ||
#[[APT Proxy] | #[[APT Proxy]] | ||
#[[Router]] | #[[Router]] | ||
#[[FCS Network]] | #[[FCS Network]] | ||
Revision as of 20:51, 15 June 2014
Internet
Email list
We have Google Groups mailing list:
freegeekseattle@google-groups.com
IMO it would be better for us to host our own email and listserv. Unfortunately email administration takes an ongoing time commitment. If you are interested in babysitting our maillist, please contact the Technical Infrastructure Coordinator.
Web
We have a web site, hosted on Mark's server dynamo. It is a Mediawiki instance. You are reading it now.
Road Map
This is the approximate plan for the next few projects.
- Install Server <- planning done, but not yet installed and running. See https://github.com/freegeek-seattle/install_pxeserver
- APT Proxy
- Router
- FCS Network
- Volunteer database <- Currently in progress
- SSL <- This is only part of the security picture; see below
- Inventory tracking database
Install server, APT proxy and router will likely all be the same machine, which is already set up thanks to User:Mousey.
Lucas and koanhead are currently working on the volunteer database. Before the new extension is installed to the production server, we will need to secure that server. SSL is a necessary but not sufficient step, koanhead is also looking at Kerberizing dynamo's FGSEA-related services and possibly providing SSO.
User:boxcutter is currently planning on changes to the FCS network, which may actually be in progress as of --Koanhead (talk) 17:57, 27 May 2014 (PDT)
In progress
Local
This section refers to our setup in the working area at FCS.