Howdy, hakkers!

Since Friday I've been getting caught up on website maintenence. Here's whats 
been done so far:

* Turns out I never actually added the second webserver (www-1) to our load 
balancer, so the site still went down. That is fixed and the load is actually 
getting balanced now.

* The new SYNHAK theme that Persa's freelancer did for us is available. It 
isn't the default yet since I think we should discuss that. Here's how you can 
see it: http://synhak.org/w/index.php?title=Main_Page&useskin=gumaxdd

You can set it as your default in your preferences: 
http://synhak.org/wiki/Special:Preferences#mw-prefsection-rendering. Use the 
"GuMaxDD" theme.

* HTTPS on synhak.org is broken until a proper SSL certificate is generated 
and uploaded into our AWS load balancer. HTTPS still works on www-0.synhak.org 
and www-1.synhak.org. I heard rumors that someone was interested in chipping 
in some cash to get us a SSL certificate that isn't self-signed.

* Since the wiki is hosted across two machines, image uploading and 
thumbnailing is completely broken on www-1. If you need to upload something or 
see an image, use www-0. I'm waiting on a reply to this forum topic to figure 
out how to properly use this AWS extension to have S3 host uploads: 
http://bit.ly/13CZCwk. Once that is resolved, you'll all hear about it.

* I'm in the process of rewriting bits of Phong to support a more modular 
design, which will allow his functionality to be easily used by other spaces 
and allow for much faster iterations when adding new functionality.

* Documentation! http://synhak.org/wiki/Sysadmin and 
https://github.com/SYNHAK/infrastructure/blob/master/README.md

And of course, all of this is available in our infrastructure repository:

https://github.com/SYNHAK/infrastructure

Things I am working on next but won't put a deadline on because that idea 
hasn't worked out for me in the last two years:

* Fixing the [email protected] system by writing a setuid executable so it 
has proper permissions to check for [email protected] list membership instead 
of assuming nobody is a member
* Refactoring a bunch of spiff's UI so the treasurer can easily note payments 
in spiff
* Adding various email notifications to spiff so the treasurer knows when 
someone pays dues and letting members know when their non-electronic payments 
have been recorded
* Fixing spiff monthly invoice generation
* Adding faceted search to spiff so the mail server doesn't ever need access 
to the mysql database
* Writing some kind of secretary/treasurer dashboard into spiff to easily 
check and see if people's memberships are up to date
* Looking at where we can move the mailing lists since mailman still can bring 
us to our knees
* Nagios and AWS CloudWatch monitoring
* Writing live.synhak.org so you can view the webcam from the same address 
whether you are in the space or out, along with finally showing if the kiosk's 
open/closed button has been toggled.
* Finding more people to moderate the discuss mailing list
* Adding a keepassx database to our private security repo
* Putting this list into some kind of tracker or wiki page or something

If someone wants to step up and chip away at that list or they've got other 
ideas, please let me know!

Stay Excellent, my friends.
_______________________________________________
Discuss mailing list
[email protected]
http://synhak.org/mailman/listinfo/discuss

Reply via email to