Hi,

 

in the last weeks there was no activity in the project. If we want to start a server we must do something!

 

Best regards,

Jan

 

Von: wikiversity-l-bounces@lists.wikimedia.org [mailto:wikiversity-l-bounces@lists.wikimedia.org] Im Auftrag von Jan Luca
Gesendet: Dienstag, 1. Juni 2010 20:35
An: 'Mailing list for Wikiversity'
Betreff: Re: [Wikiversity-l] Sandbox Server

 

Hi,

 

I would use a Linux like Debian because I have no experience in BSD and I think some others, too. Debian has a good packet system, too, which is easy to administer the software (apt/aptitude + deb).

 

With the projects: I have started some but until now only one person adds himself to the list.

 

Best regards,

Jan

 

Von: wikiversity-l-bounces@lists.wikimedia.org [mailto:wikiversity-l-bounces@lists.wikimedia.org] Im Auftrag von Gerald A
Gesendet: Dienstag, 1. Juni 2010 02:57
An: Mailing list for Wikiversity
Betreff: Re: [Wikiversity-l] Sandbox Server

 

Hi Jan,

2010/5/18 Jan Luca <jan@jans-seite.de>

here two of my ideaa: 

1.      Website: The main website (e.g. www.sandbox-server.org ) contain general information, the information how to get an account/project, a link to a list of the projects/users and a “Thank you” for WMDE. The projects are under the project.<server name> and accessible per /~<project name> (userdir in Apache). The user pages (for own files and so on) are similar to the project page accessible per user.<server name>/~<user name>.

There should be a config interface, too. I think the address should be https://config.<server name>.

Sounds interesting. I like the idea of making it clear who the project sponsor is, and being up front about thanking them. I also like the idea that a "project" should have a project page. While user pages and "public_html" directories are easy for us techs, Leigh and Cormac are going to have an easier time with an easier interface. A wiki? Some other software? I'm open to suggestions here.

 2.      Software: The basic software should be Apache, PHP (maybe PHP 6.0 too for testing), MySQL and Perl. I think for security should PHP use fastcgi with suexec to run in Apache so the scripts are run as the owner. Fastcgi should give some performance.

I think Apache, PHP, MySQL and Perl are all doable. Since I'm going to be the lead guy on this (it seems), I'm going to pull a little weight and suggest we use FreeBSD as the base OS. It's Unix, and it has some good features I'd like to leverage. I'm open to suggestions, but they have to be (a) easy to use and (b) easy to administer.

 

I've been doing some digging and I haven't been able to find a local provider who can do what we need at the price point we are looking at. I'd prefer a box that I can visit, as it would allow a bit more flexibility, but we can work around that.

 

I was hoping to elicit another project or two from wv-en, but I haven't heard anything on that front. I'll check out the new central sandbox page, maybe we can harvest a few projects from there.

 

Thanks,

Gerald