modx Lite anyone?

I’m a fan of modx, really.
Nut sometimes I wish I could have lite version that doesn’t require a database.

I really like the way the chunks, snippets, and templates work in modx, but for smaller sites a database can be overkill. How about a modX lite?

does anyone know of any alternatives that do this?
lightneasy seems ok, but I gots myself hooked on the good stuff.

In theory, everything in the DB could go in files and it’s an interesting idea. I think there’s too much legacy code in Evolution to do it there, but it would be much more feasible in Revolution (though not trivial, by any means).

Actually, I am working through converting MODx to use sqlite. It’s just an idle pastime for the fun of it (and learning PDO), though, so no saying when it will be done.

Quote from: BobRay at Aug 22, 2009, 07:48 AM

In theory, everything in the DB could go in files and it’s an interesting idea. I think there’s too much legacy code in Evolution to do it there, but it would be much more feasible in Revolution (though not trivial, by any means).

All that needs be done for Revolution is developing the SQLite xPDO implementation; it actually is almost trivial. With that and very little other work, we will be able to deploy Revolution on SQLite. Same for other database drivers available for PDO.

I do believe that once there are a few other database options, MODx usage will explode.

Could we expect a Revolution release with support for MYSql, PGSql and sqlite?

Quote from: lossendae at Aug 22, 2009, 06:10 PM

Could we expect a Revolution release with support for MYSql, PGSql and sqlite?

Definitely the goal; but this will likely be after 2.0.0 is released only for MySQL.

Actually, I am working through converting MODx to use sqlite.

Susan, could you progress in this project?

Instead of porting all MODx Evolution to sqlite, I dream of the possibility attaching sqlite database files through links in the MODx tree. Anyone else interested?

The sqlite files would contain subtrees and the MODx tree as well as snippets like Wayfinder / Ditto would treat the ressources stored in the sqlite databases exactly like regular ressources in the MySQL database.

This way, you would only have to drag & drop an updated sqlite database to update all the content of a subtree. Some special icon would show which ressource links an sqlite database.

I have no idea about how difficult it would to adapt the document tree, Wayfinder, Ditto and DocManager for this. I assume that at the beginning it would be easier to disable some features, making for instance the sqlite subnodes read-only.
Another question is if the sqlite documents should have all columns of modx_site_content or if MODx could adapt to minimalist mandatory columns (id & title) and how it would treat optional non-MODx columns.
Also, for many projects, fields like "introtext", "longtitle" and even "content" are useless and sometimes boring.

For me,all these questions leads in the direction of a "MODx Evo Lite", which would become even more a generic "node management system" than a "document management system".