BlingNode's Principles
Here at Bixly, we have several overarching principles regarding adding new features to BlingNode.
Mission: To help a Django programmer finish their project sooner
The calculation is easy. If you are spending less time setting up tools, you finish sooner. Also, if you have tools that increase your programming power, you can write better code. If new ideas/features don't fit into this mission, we won't add it in.
Deeper. Not Wider.
This means that we have more tools for a better development experience on just a few platforms; rather than just a couple of simple tools on a whole bunch of platforms. With the natural limits on our resources, we had to choose: We could either be more effective on just two platform, or less effective (less configurations and tools) on many platforms
Must be useful for Bixly
BlingNode arose out of a need for our development at Bixly. Thus, all of the features in BlingNode are actually useful for our daily development for all of our projects. It works out better for everyone this way. If it's a tool we use, we will be happy to keep it up and release it to the community.
Must not require learning besides that found on package docs
The last thing we want to do is add any more complexity to Linux, or the tools that BlingNode installs. If you want to learn how to tweak the crap out of a tool installed by BlingNode, just go research that tool. There are no BlingNode docs that are required to successfully setup a new system.
Must be installed in the way the package maintainer describes or at least consistent with the Linux system
Many popular tools (ISPconfig, Cpanel, Plesk) adjust the programs they install to better suite the tool than the system. This sometimes locks you out of tweaking the tools since the configs are hidden or packages are compiled in a special way. BLingNode just installs the tools the way they are supposed to. No new "BlingNode" systems to learn. If you know how to use the package in questions, no other study is necessary.