Hi there

I’m trying out Cruise. I have a habit of installing tools into source-control so I can play around with their configs in a whimsical ad-hoc fashion (some would say I approach development in the same way, and that’s why I need SCM and CI… ;-) ).

With that in mind, is there anything in the server install that I wouldn’t want to check in? Logs, automatically-generated things, databases? So far only the {server}/logs directory looks like a likely culprit (I’ve configured my artifacts to be outside the server-installation directory).

Cheers
Pete

Apart from the artifacts repository, there’s a hypersonic database kicking around that you won’t want to check in (where it lives depends on your platform). All the configuration that’s important is in cruise-config.xml—we have taken care to avoid scattering config around the filesystem. In future, Cruise will version control its configuration for you.

I’m on a windows 2008×64 box. I’ve not heard of hypersonic (coming, as I do, from the .NET world) – is it similar to SQLite?

Hypersonic, aka HSQLDB, is used in similar circumstances as SQLite. It is a small, fast, standalone RDBMS that is easy to embed in an application. HSQLDB is an RDBMS written in Java, however, which is why it’s not used as often on .NET projects. In Cruise, though, you’ll never need to know it’s there.