This iteration I’ve been working using the HTTPDUserAdminContrib – as having the users and groups in the database makes it hard to work on.
Hopefully there’ll be time to use and extend it for foswiki 1.1
Stuff I've been working on
This iteration I’ve been working using the HTTPDUserAdminContrib – as having the users and groups in the database makes it hard to work on.
Hopefully there’ll be time to use and extend it for foswiki 1.1
I’ve updated the USB Foswiki to include foswiki 1.0.7, and updated the systray controller to be a little more slick 🙂
I’m still looking for feedback from users – Its a nice fast way to try out foswiki without needing to install anything – just unzip the archive into the root of a disk, and click start_foswiki.bat
(on Windows XP the autorun should start that automatically for you)
Continuing our commitment to bug fixing and solving difficult security issues, we’re proud to announce that the Foswiki project has released 1.0.7.
This release contains:
see http://foswiki.org/Download/WebHome for more details, and to download the update.
I’m updating the Foswiki On a USB Stick at the moment, and will then work on Windows and Debian.
Ohloh shows a very comforting graph for me – over the year, we’ve been maintaining our momentum, and regularly have over 10 different contributors every month.
FoswikiOnAStick v0.1 (running foswiki 1.0.6)
I was asked on Friday night if I could make a demo foswiki USB system, and given that its high time we did one, I started to look into it. Initially I thought this would be a great oportunity to try out the HTTPEngine work Gilmar has been doing, but we’re not quite there yet. And so, I started a quick perusal of the existing WebServer on a Stick systems. Ideally, I want to use Strawberry perl, apache, and have the server and a browser start up automatically when the USB stick is inserted into the computer.
MicroApache was the first thing i looked at, as the contact pointed out DokuWikiOnAStick, but that server doesn’t seem to have source, nor is the upstream web site there (last release seems to be 2007, so too old for Strawberry perl too) Server2Go looks nice, but as its not really free in the debian sense, I’ll pass on that unless nothing else works. XAMPP – unzipped it, foswiki and did some minor configurations. unziped, removed everything except apache, added strawberry perl, and wrote a systray icon and menu system for you to control it with. TADA! FoswikiOnAStick v0.1v0.3 (running foswiki 1.0.6). please try it out.
before ejecting the usb key, you need to stop the webserver by running stop_foswiki.bat yes, thats all. Please report any issues or observations to me – SvenDowideit@fosiki.com
I have made no attempt (yet) to reduce the accesses to the disk – so it may use up all the blue smoke in your usbkey, cause your bits to turn green, or one of many other unforseen side effects which may or may not appear amusing if they happen to someone else. I’ve tested this on Windows7rc, Windows Vista, Windows2003server, and Windows XP – if it works for you, excellent :).
see http://foswiki.org/downloads and http://fosiki.com/Foswiki_debian/ for more information.
I’ve just (finally) set up the auto unit test run, PerlCritic and release build for the Release01x00 branch, and fixed the trunk builder.
Foswiki trunk gets built every 6 hours, and Release01x00 every 12 (based on my Sydney TZ).
If the unit tests fail, and email will be sent to the foswiki-discuss mailing list – no news is good news. See the build output areas:
where you will find the output log files, the built tar.gz and zip files and each of the component packages that make up a release.
I was just asked on IRC how to protect some attachments without forcing all requested attachments to go through the viewfile cgi script (as that causes your foswiki images and css to load incredibly slowly), and here’s the howto I answered with:
I was just asked on IRC how to protect some attachments without forcing all requested attachments to go through the viewfile cgi script (as that causes your foswiki images and css to load incredibly slowly), and here’s the howto I answered with:
I coded foswiki 1.0’s viewfile script to work as an apache ErrorDocument, so If you can find a way to trigger a 404 or 401 error, you can get apache to run viewfile –
ErrorDocument 404 /foswiki/bin/viewfile ErrorDocument 401 /foswiki/bin/viewfile
If you place your pub dir somewhere outside where apache serves files and then softlink the non-protected webs into apache’s path (so it serves them full speed), then the secured webs will generate a 404, triggering the viewfile ErrorDocument – which will thus serve the file only to authenticated users
This will work irrespective of the authentication choices in your foswiki setup – and as the files that require securing are outside apache’s file serving areas, can be considered as secure as possible.
As an added bonus, any request to a file that does not exist will show a foswiki error page, rather than a static html.
I’ve been working on expanding the use of Foswiki Applications and in the process began to build (using TML) a much more usable user interface for configuring and managing your Foswiki.
So – to the picture show 🙂
Many of these features already do work in Foswiki 1.0.4 – by installing FoswikiApplications Contrib, but they are a work in progress – and getting more advanced every week.
Foswiki 1.0.4 has been released with more than 100 bug fixes and some small enhancements. Upgrading is highly recommended. If you did not upgrade from TWiki yet, now is a good time as Foswiki 1.0.4 fixes more around 300 bugs relative to TWiki 4.2.4.
Grab it now from : http://foswiki.org/Download/WebHome – the straight and upgrade archives, OSX installer and my Windows Installers are here.
My debian package repository now spans Foswiki 1.0.4 and 168 Foswiki extensions – its never been easier to install 🙂
see http://fosiki.com/Foswiki_debian
Over the 4 months of our project’s existence, 33 developers have been involved in making ~3000 commits – next up, the future !