I'm thinking of starting up an OSQA site for an academic department, but I won't be around to maintain the site forever. For all of you who've started up OSQA sites, what's the workload like for an administrator? How hard is the site to maintain?

And if/when I hand off administration to the next guy, how steep will the learning curve be for him?

asked 22 Mar '11, 21:04

agong's gravatar image

agong
71136
accept rate: 0%


It's still not trivial, but as for standard maintenance - "If you don't change anything, it doesn't break". I'm still learning the ropes, the tougher parts for me were first installation and then sometimes upgrades.

Now, installation is easier with the Amazon EC2 AMI. Normal upgrades should be taken care of by the instructions here, although they always have the potential to break the site. Right now, I'm setting up a separate "beta" version of my site to try the upgrades on. What I did until now is used Amazon EC2 to clone the running image and do the upgrade experiments on the clone, in order not to break the production site.

The nice thing about OSQA is that it supports itself - if you have a question, ask here and there's a fairly good chance you'll get an answer.

link

answered 23 Mar '11, 02:39

ripper234's gravatar image

ripper234 ♦
3.2k60116123
accept rate: 19%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×10

Asked: 22 Mar '11, 21:04

Seen: 418 times

Last updated: 23 Mar '11, 02:39

powered by OSQA