I changed the subject, felt like it was time :-)

On Wed, 4 Mar 2009, Bo Peng wrote:

sf.net provides ssh access, something even my web hosting company is
unwilling to provide. I just checked and it has doxygen pre-installed.

But the shells are time limited, so I doubt we'd be able to set up a cron job to regenerate things for instance. Even so, I'm working on setting up something that'll do that elsewhere and then upload the results, so it's strictly speaking not necessary.

i like all the stuff Christian is providing with wiki which i doubt would be possible under sf,

As long as Christian is using pmwiki (php), I believe migration should be easy. It can be as simple as 'scp -r' and some modifications to local/config.php because no database is involved.

It is driven by PmWiki, which can be used on SF. However, I believe it'll require quite a bit of work to migrate to a different host(name). It was never designed to be portable like the web pages (which are also generated by PmWiki).

Personally I like working with a "regular" server, guess I'm more at home with that kind of setup.

A more important drawback might be how to allow users' to upload files to the wiki. This is _not_ being done via PmWiki, but through some other file manager. I have no idea if we can get that working on SF. Or indeed if this is even something that's allowed...



On a more practical note, I'm currently checking out the web files to SF using SVN. It's incredibly slow, I'm talking about a few seconds per file... Here's the setup, if anyono knows what the problem is, please tell me:

* Mounted the file area on SF using sshfs using a local directory
* CD'd to that directory and did 'svn co ...'

So the whole thing is done on top of sftp, which could be the reason in combination with slow servers at SF or a slow aussie.

/Christian

--
Christian Ridderström                           Mobile: +46-70 687 39 44

Reply via email to