Stories
Slash Boxes
Comments

SoylentNews is people

posted by NCommander on Friday March 21 2014, @09:45PM   Printer-friendly
from the 40-minutes-by-the-clock dept.
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.
 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by ls671 on Saturday March 22 2014, @05:01AM

    by ls671 (891) Subscriber Badge on Saturday March 22 2014, @05:01AM (#19618) Homepage

    Damn, I meant:
    In these cases, it is common to call pre-prod "dev" ;-)

    --
    Everything I write is lies, including this sentence.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Saturday March 22 2014, @05:27PM

    by Anonymous Coward on Saturday March 22 2014, @05:27PM (#19751)

    Depends on where you come from. Our shop was mainframe-centric for around 20 years before moving into Unix/Linux and Windows servers, and we traditionally divided things up into dev, qual and prod. But keeping 3 environment in sync takes a lot of hard work. The mainframe guys were incredibly disciplined, the Unix admins and mostly Java developers... not so much. As a result in most places qual doesn't look like prod and dev is even further away. Lately I've been only ordering up dev and prod environments, forcing the programmers to trim up dev so they can preview the changes they want to make in prod (of course that often doesn't happen because people are in too much of a rush and the exceptions outnumber the rules when it comes to change control). On some infrastructure projects I've set up a separate "test" environment to mirror prod exactly so that the sysadmins can have someplace to try out *their* changes (like O/S and other platform updates) without having to worry about where things are in the application development cycle.