You don't ever need compass on your production servers, but you do need it
on any development or build servers (anywhere you're going to compile the
css).
This compass command:
compass compile --force -e production path/to/project
can be called from any shell script or the executed from another program as
long as compass is on the PATH.
You might need to patch django-css to teach it about compass if it doesn't
know about it yet.
Another approach is to pass the following options to the sass CLI. this
still requires compass to be installed but might be able to work with
django-css out of the box:
-r compass `compass imports`
Chris
On Mon, Jul 26, 2010 at 11:41 AM, step <ste
...@gmail.com> wrote:
> I'm working a blueprint/semantic project with django. I plan on using
> django-css to compile the scss files (as opposed to compass -w). Is
> there a way to create a self-contained project (that includes all of
> the compass dependencies) so we don't have to use COMPASS on our
> production servers and avoid potential project with team members
> having different versions of COMPASS installed locally (IE over the
> next few years).
> --
> You received this message because you are subscribed to the Google Groups
> "Compass" group.
> To post to this group, send email to compass-users@googlegroups.com.
> To unsubscribe from this group, send email to
> compass-users+unsubscribe@googlegroups.com<compass-users%2Bunsubscribe@goog legroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/compass-users?hl=en.