BibSonomy ::  tag ::

order by ( date | folkrank )

Save. Refresh. Enjoy. And stop redeploying in Java! JRebel is a small JVM-plugin that makes it possible for Java developers to instantly see any code change

Buildr is a build system for Java applications in Ruby Maven compatible * A simple way to specify projects, and build large projects out of smaller sub-projects. * Pre-canned tasks that require the least amount of configuration, keeping the build script DRY and simple. * Compiling, copying and filtering resources, JUnit/TestNG test cases, APT source code generation, Javadoc etc * A dependency mechanism that only builds what has changed since the last release. * A drop-in replacement for Maven 2.0, Buildr uses the same file layout, artifact specifications, local and remote repositories. * All your Ant tasks belong to us! Anything you can do with Ant, you can do with Buildr. * No overhead for building “plugins” or configuration. Just write new tasks or functions. * Buildr is Ruby all the way down. No one-off task is too demanding when you write code using variables, functions and objects. * Simple to upgrade to new versions. * fast

Free, easy to setup wikis, blogs, forums and many other web applications that you can run locally or in the cloud. BitNami makes deploying server software a simple and enjoyable process.

virtualenv is a tool to create isolated Python environments. The basic problem being addressed is one of dependencies and versions, and indirectly permissions. Imagine you have an application that needs version 1 of LibFoo, but another application requires version 2. How can you use both these applications? If you install everything into /usr/lib/python2.4/site-packages (or whatever your platform's standard location is), it's easy to end up in a situation where you unintentionally upgrade an application that shouldn't be upgraded. Or more generally, what if you want to install an application and leave it be? If an application works, any change in its libraries or the versions of those libraries can break the application. Also, what if you can't install packages into the global site-packages directory? For instance, on a shared host.

virtualenv is a tool to create isolated Python environments. The basic problem being addressed is one of dependencies and versions, and indirectly permissions. Imagine you have an application that needs version 1 of LibFoo, but another application requires version 2. How can you use both these applications? If you install everything into /usr/lib/python2.4/site-packages (or whatever your platform's standard location is), it's easy to end up in a situation where you unintentionally upgrade an application that shouldn't be upgraded. Or more generally, what if you want to install an application and leave it be? If an application works, any change in its libraries or the versions of those libraries can break the application. Also, what if you can't install packages into the global site-packages directory? For instance, on a shared host.

Use virtualenv with django and mod_wsgi Added 2009-09-27: To use the the packages in my virtualenv, I used site.addsitedir at the top of my .wsgi application file. You may also want to set the WSGIPythonHome variable in your httpd.conf file (outside of any VirtualHost sections). For detailed information on using mod_wsgi with virtualenv, see the Virtual Environments section of the modwsgi project documentation.

Use virtualenv with django and mod_wsgi Added 2009-09-27: To use the the packages in my virtualenv, I used site.addsitedir at the top of my .wsgi application file. You may also want to set the WSGIPythonHome variable in your httpd.conf file (outside of any VirtualHost sections). For detailed information on using mod_wsgi with virtualenv, see the Virtual Environments section of the modwsgi project documentation.

simple “pip install superlance” should do the trick. It will install both Supervisor and the Superlance plugin. I’m including my init script for supervisor in my example supervisor.tgz archive. It is Debian specific, modify to your needs on a RedHat system. Configuring Supervisor to start and monitor your sites is remarkably simple and short. Here are the key lines from my supervisord.conf file: [program:invisible]

simple “pip install superlance” should do the trick. It will install both Supervisor and the Superlance plugin. I’m including my init script for supervisor in my example supervisor.tgz archive. It is Debian specific, modify to your needs on a RedHat system. Configuring Supervisor to start and monitor your sites is remarkably simple and short. Here are the key lines from my supervisord.conf file: [program:invisible]

In a previous post I talked about a neat middleware to debug production environments in Django. It basically checked to see if you were a superuser, or if you were in settings.INTERNAL_IPS, and if so, then it displayed a technical 500 page for you (The yellow one you know and love). Anyway, at that point it was more of a simple idea, and not really used in production.