I'm looking for something for the short term - a big conversion project is not possible at this time - to provide a web-based file management system. We've been using Mason-CM for years; it's ugly as sin, but it can work with plain HTML files as well as javascript, CSS, text files, images, and anything else we want to throw at it. However, the product is dead, dead, dead - it hasn't been updated in years, and was never made to run under Apache 2. Another project is now forcing the issue.

Mason-CM is a simple manager for a web site. While it is Mason (Perl) based, it doesn't enforce the use of Mason in the files it manages; we can - and do - feed it plain old everyday HTML, as well as other file types. There's an automatic built-in version control system that lets you recover older files or look at differences between versions, and provides file locking so that two users can't
edit the same file at the same time. It also provides deployment to the production server.

Ideally, I'd like to find something that can work with the HTML (and assorted other files) as-is, and just provide a simple interface for checking stuff in and out, editing files, and, of course, deploying the files. What I am not looking for is anything that requires modifying the existing files to fit into its scheme - we need to keep the Mason code in our system as is, and don't want to have to adapt things to fit into some sort of templating system.

Any suggestions? Something we can run on our own servers without a great deal of effort, or an inexpensive SaaS solution, are acceptable. Thanks in advance for any help you can provide.

I am unclear on your requirments.

This is a demo you can try:

http://kottidemo.danielnouri.org/


Here are more that use python:

https://wiki.python.org/moin/ContentManagementSystems

i am unclear, too.

so your cureent cms (content management system) is outdated and you need to switch to a new one and are asking for suggestion?

i don't think it will be possible to move the file structure "as is".
a painful migration process will most probably be necessary.

but, what is this mason-cm, a link, forums, wiki? maybe they themselves provide pointers on how to continue.

Thanks for the feedback, folks, and sorry for my late reply.

At this point, we've decided to use Dropbox for the short term. It's not perfect, but it will do enough of what we need it to do until we can get the migration done.

FWIW, the project itself lives at https://sourceforge.net/projects/mas...?source=navbar