Magic words:
psql -U postgresSome interesting flags (to see all, use -h or --help depending on your psql version):
-E: will describe the underlaying queries of the \ commands (cool for learning!)-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)
| ab \ | |
| -n 1000 \ | |
| -c 20 \ | |
| -s 30 \ | |
| -p post-data.txt \ | |
| -T 'application/x-www-form-urlencoded; charset=UTF-8' \ | |
| -v 3 \ | |
| -H "X-Requested-With: XMLHttpRequest" \ | |
| -H "X-Ajax-Referer: http://example.com" \ | |
| -H "Accept-Encoding: gzip, deflate" \ |
| rvm --create 1.9.3@benchmarks |
| -- when you have a record which looks like this | |
| -- | |
| -- id: 5, | |
| -- properties: { | |
| -- ages: [20, 30] | |
| -- } | |
| -- | |
| -- it is a bit of a pain if you need to query based on the contents of the "ages" array inside the JSON object "properties" | |
| -- because PG currently lacks easy to use operators to work with JSON arrays |
| require 'active_record' | |
| require 'activerecord-import' | |
| require 'benchmark' | |
| require 'pg' | |
| include ActiveRecord | |
| Base.establish_connection adapter: 'postgresql', | |
| encoding: 'unicode', | |
| pool: 5, |
FWIW: I didn't produce the content present here. I've just copy-pasted it from somewhere over the Internet, but I cannot remember exactly the original source. I was also not able to find the author's name, so I cannot give him/her the proper credit.
| ## On Windows: | |
| ``http://www.graphicsmagick.org/INSTALL-windows.html`` | |
| ## On the Mac: | |
| ``brew install graphicsmagick`` | |
| ## On the Joyent box: | |
| ``` |
They say that one of the pros of NodeJS is that you use the same language on the back-end and the front-end, so it's easy to share code between them. This sounds great in theory, but in practice the synchronous dependency handling in NodeJS works completely different than any client-side frameworks (which are asynchronous).
Usually that means that you end up copy-pasting your code between your NodeJS sources and your client-side sources, or you use some tool like Browserify, which is brilliant, but they add an extra step in the build process and most likely will conflict with the dependency handling of the framework of your choice (like AnularJS DI). I couldn't look in the mirror if I would call that code sharing.
Fortunately, with a couple of lines of boilerplate code, you can write a module which works in NodeJS and AngularJS as well without any modification.
No globals in the front-end, and dependencies will work. The isNode and isAngular va
| # This deploy script takes a parameter to define the number of instances to deploy (default is 1) | |
| # ex: cap deploy -s instances=3 | |
| set :application, "YOUR_APP_NAME" | |
| set :repository, "git@YOUR_GIT_REPOT.git" | |
| set :scm, :git | |
| set :deploy_via, :remote_cache | |
| set :user, "deploy" | |
| set :deploy_to, "/home/deploy/www/#{application}" |
| This assumes you've already set up your instance with node, npm, forever, mongodb, configured ports, and have optionally added a web server like nginx to proxy access to meteor. | |
| Local | |
| 1. Install Ruby | |
| 2. gem install capistrano | |
| 3. cd /your/meteor/project | |
| 4. capify . | |
| 5. edit config/deploy.rb as needed with below | |
| AWS |