I got carbon to work from source by simply editing setup.cfg and commenting out the lines referring to the install prefix. It then installed in the virtualenv just fine. Without those lines there, it should be possible to even install it directly from PyPI via pip which I think would be a huge win :)
After that I just had to go to $VIRTUAL_ENV/conf and run:
for f in *.example; do cp $f ${f/.example/}; done
carbon-aggregator.py start
and I was up and running. No need for root access or a system-wide install.
The --prefix and --install-lib switches could be used when building RPMs or DEBs to preserve the existing behaviour there, but I don't think they should be the default in order to facilitate virtualenv installation.
I got carbon to work from source by simply editing setup.cfg and commenting out the lines referring to the install prefix. It then installed in the virtualenv just fine. Without those lines there, it should be possible to even install it directly from PyPI via pip which I think would be a huge win :)
After that I just had to go to $VIRTUAL_ENV/conf and run:
for f in *.example; do cp $f ${f/.example/}; done aggregator. py start
carbon-
and I was up and running. No need for root access or a system-wide install.
The --prefix and --install-lib switches could be used when building RPMs or DEBs to preserve the existing behaviour there, but I don't think they should be the default in order to facilitate virtualenv installation.
I haven't tried anything with graphite-web yet.