Pipedot Status Week 1
Just a quick update on the progress after its first week of life:
The code base is all new (not based on Slashcode) and using modern web technologies (nginx instead of Apache, no Perl CGI, etc...). There are currently six servers plus a load balancer with more webservers available to spin up as needed. Sections of code that are either CPU heavy or database intensive (threaded comments) are able to be memcached to maintain performance.
Stay tuned for the next week of updates!
- Thursday : registered the pipedot.org domain!
- Friday : setup the DNS and mail servers.
- Saturday : Web, database, and memcache servers built up.
- Sunday : Load balancer added to balance between the two webservers. Also finished setting up the HTTPS certificate and IPv6 support.
- Monday : Initial look, logos, icons and CSS design.
- Tuesday : Database-backed stories (no more static placeholders).
- Wednesday : Login system was enabled.
- Thursday : The first poll was posted late Thursday in time for Valentines Day on Friday.
- Saturday : Topics and the Pipe activated.
- Sunday : Threaded comments and user-submitted stories enabled.
The code base is all new (not based on Slashcode) and using modern web technologies (nginx instead of Apache, no Perl CGI, etc...). There are currently six servers plus a load balancer with more webservers available to spin up as needed. Sections of code that are either CPU heavy or database intensive (threaded comments) are able to be memcached to maintain performance.
Stay tuned for the next week of updates!
We still haven't discussed the language. Though we've had people request everything from perl to python to ruby, most say avoid PHP, which again is odd since PHP seems to be the go-to web programming language. Personally I think perl should be avoided, it's a relic that was never intended for web programming, but was forced into that role and was abused severely by people writing CGI scripts that lead to huge gaping security holes.