SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
SoylentNews
We're back up and running, with a slightly longer than expected downtime. As part of this maintenance cycle, we've installed new varnish configuration files which *should* hopefully fix the long standing issues with logging in, as well as articles not showing up on the main page.
Furthermore, we've dumped the static page generation used by slash in favor of simply varnishing everything. Now anonymous users are on a 5 minute page cache (so new comments and such will take a bit of time to show up, consistent with the other site), which logged in users can bypass the cache and get live access to articles. A couple of things such as comment count are still dependent on slashd's freshen.pl task, so those don't update in real time (yet).
In other news, we've (finally) got a proper development server up at http://dev.soylentnews.org/, running a copy of the production database where we can stage changes and other various things before deploying here. If you want to see what we're up to before we push it live, check it out. As usual, if we make any large scale changes, we'll announce it BEFORE pushing it here.
Furthermore, we've dumped the static page generation used by slash in favor of simply varnishing everything. Now anonymous users are on a 5 minute page cache (so new comments and such will take a bit of time to show up, consistent with the other site), which logged in users can bypass the cache and get live access to articles. A couple of things such as comment count are still dependent on slashd's freshen.pl task, so those don't update in real time (yet).
In other news, we've (finally) got a proper development server up at http://dev.soylentnews.org/, running a copy of the production database where we can stage changes and other various things before deploying here. If you want to see what we're up to before we push it live, check it out. As usual, if we make any large scale changes, we'll announce it BEFORE pushing it here.
This discussion has been archived.
No new comments can be posted.
Site Maintence Complete: 21-03-2014
|
Log In/Create an Account
| Top
| 33 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
The last time I saw him he was walking down Lover's Lane holding his own hand.
-- Fred Allen
(Score: 2) by NCommander on Monday March 24 2014, @07:23AM
slashd hung when we updated the backend authetication. Its done this before, but it tends to self-resolve if left alone long enough. I didn't notice, and it wasn't until several hours later when the comment counts were still at zero that anyone else did. Due to the authetication changeover, no one with access to the boxes could kick it. This was a combination of bad design in slash and bad timing.
We're setting up a crontab to auto restart slashd as a stopgap, and we've got everyone in LDAP now with boot kicking permissions to restart slashd should it do this agian.
Still always moving