Sometimes the simplest, easiest things are not documented anywhere, or at least, not documented very clearly, so I just thought I would document what I did here in order to get started running the examples provided in the full Express codebase.
Let's suppose that node and npm are already installed and I am in the home directory of a Linux user. I do:
$ git clone https://github.com/visionmedia/express.git express_examples
and Express is cloned to the express_examples subdirectory. I then change into that directory:
$ cd express_examples
and tell the npm package manager to check for all dependencies (if you are on the Express mailing list see discussion at http://groups.google.com/group/express-js/browse_thread/thread/166a75fdb...):
$ git submodule update --init
$ npm install
The package manager npm will now do a lot of work and pages will scroll by. After a short while the trundling will stop and a ./node_modules directory will be filled with dependencies.
Then you can run any example you like:
In this series of articles we'll see how to set up a Cloud App Server with CouchDB and Node.js on Ubuntu 10.04 LTS, and why.
After following these clear instructions for upgrading to Firefox 4.0 on Ubuntu 10.04/10.10, after delighting in the speed and reveling in the speed and other good stuff, I wanted to get firebug back so I could do some socially useful work!
So I went to Tools / Add Ons from the browser menu, and a pop-up window showed me all my disabled stuff that was incompatible with Firefox 4.0
Then, I returned to Add-ons Manager at Tools / Add-ons and from the little drop down list icon to the left of the search box in the top-right corner, I selected Install Add-on from File...
So dusted off my Safari books online subscription, and started searching around for stuff to get me up to speed on Python. Want to use it bad for general utilities, and for migrating to OOP based frameworks, to be treated in the manner in which I am accustomed.
Obviously the front line winners are:
Project Flow & Tracker Status update for early January, 2011
As tweeted four days ago, Project Flow & Tracker is now an installation profile http://drupal.org/project/pft on d.o. Please read the project page for download and install instructions and road-map. The most important aspect is that since this is an "everything in code" install profile, there will be no more getting locked into an outdated version. Just by running update.php you will get access to all updates available as the pft modules evolve. Also, even though I am creating a SaaS platform, the "everything in code" paradigm will prevent a "commercial" vs "free" version since every advance made on the SaaS platform will be present in the installation profile base modules as updates right on http://drupal.org. As long as its there.
I have already written several articles on how this can be done, and I will be thoroughly documenting the workflow I have finally chosen in great detail.
I hope many will download and start using the install profile! Meet you on the issue queue!
A word on the Free software pledge
This gives me a material base upon which to make the free software pledge as a way of clearly showing where I stand on the "Drupal App store" debate. It is my way of struggling against such an App Store, and I hope others will make similar pledges.
I take this position for reasons I will elaborate upon in a future article (among many other things, greater and smaller, I would like to know who decides what goes in and what is excluded (no-one is addressing this question); and I would like to know how I can charge for stuff based on modules other people have developed, not to mention core...).