| # ~/.bashrc: executed by bash(1) for non-login shells. | |
| # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) | |
| # for examples | |
| # If not running interactively, don't do anything | |
| [ -z "$PS1" ] && return | |
| # don't put duplicate lines in the history. See bash(1) for more options | |
| # ... or force ignoredups and ignorespace | |
| HISTCONTROL=ignoredups:ignorespace |
| cmdStr := "thumbnail.sh " + url | |
| cmd := exec.Command("/bin/sh", "-c", cmdStr) | |
| _, err := cmd.Output() | |
| if err != nil { | |
| println(err.Error()) | |
| return | |
| } |
Our goal here is to have one USB stick to rule them all. Objectives:
The last bullet is subject to interpretation, but I'm defining functional as:
Navigate to http://nodejs.org/download/ and on the Linux Binaries (.tar.gz) row click to download the 64-bit version of the current latest release.
Say you've downloaded node-v0.10.7-linux-x64.tar.gz into the Downloads directory. Then, open the terminal and type the following:
$ cd ~/Downloads
$ mkdir -p ~/local/node
$ tar xzf node-v0.10.7-linux-x64.tar.gz -C ~/local/node --strip-components=1
$ echo '# Node Enviroment Setup' >> ~/.bashrc
$ echo 'export PATH=$HOME/local/node/bin:$PATH' >> ~/.bashrc
| Framework | Average | Get (/) | Params, query & header | Post JSON |
|---|---|---|---|---|
| uws (node) | 98,742.06 | 117,931.1 | 106,347.08 | 71,948 |
| hyper-express (node) | 82,449.5 | 118,198.57 | 88,546.88 | 40,603.05 |
| bun (bun) | 81,971.373 | 99,946.51 | 78,488.13 | 67,479.48 |
| elysia (bun) | 79,643.103 | 98,266.18 | 76,637.37 | 64,025.76 |
| vixeny (bun) | 79,508.623 | 96,996.36 | 79,585.35 | 61,944.16 |
| stricjs (bun) | 79,120.123 | 97,804.01 | 78,028.85 | 61,527.51 |
| hono (bun) | 75,293.96 | 95,430.31 | 70,915.01 | 59,536.56 |
| bun-web-standard (bun) | 73,925.933 | 88,856.78 | 70,520.02 | 62,401 |
Simple way to setup an arm chroot for building packages for your arm devices. This is an alternative to cross-compiling where you are limited to only linking against the libs in your toolchain.
You can store the chroot wherever you like. I choose to store it in a disk-image which I mount to my filesystem.
This example is specifically for my Osmosis seed node, that I run in the cloud, all my other nodes are on hardware, and I use a very different setup on those.
These instructions should work on just about any cloud provider, by striping block devices it's possible to get much higher IOPS and throughput. On Omosis in particular this is important. It doesn't cost any more to use striped volumes, so for example 3 40GB volumes cost the same as a single 120GB, but give (almost) 3x the performance.
After provisioning new block devices (do not format automatically) in the DO console and attaching them, ssh into the droplet and as root follow the directions below. I try to shoot for < 50% usage, so right now with about 120GiB needed, three 90GB volumes will do nicely.
_Note that extending the volume group in the future will require adding exactly the same number and size of volumes. Alternatively you can just use the same procedure here to move the files into a new vol
This table was created in 2015 so may be quite outdated today.
| Feature | Meteor Solution | Alternative Solutions | Description |
|---|---|---|---|
| Live DB Sync | [livequery][lq] ([mongo-oplog]), [ddp] | RethinkDB, Redis, ShareDB, [npm:mongo-oplog], [firebase], etc. | Push DB updates to client/server. |
| Latency Compensation, Optimistic UI | [minimongo][mm] | [RethinkDB][lcr], [mWater/minimongo] (fork, not ws but http, browserify) | Imitate successful db query on client before it is done. |
| Isomorphic Code | [isobuild] & isopacks | browserify | Write one code for server/client/mobile. |
| Isomorphic Packaging | [isobuild], atmosphere | No more separate packages for server & client. Get bower + npm + mobile. |
| Variables | |
| ========== | |
| predefined variables : | |
| - inventory_hostname (fqdn) (normally the same as ansible.fqdn) | |
| - inventory_hostname_short | |
| To know the return codes returned by ansible modules, just use plain ansible -vvv to see them : | |
| ansible -i ~/ansible/arrfab.net/hosts/hosts.cfg -vvv -m copy -a 'src=files/sysinfo dest=/etc/sysinfo' tungstene.arrfab.net | |
| tungstene.arrfab.net | success >> { | |
| "changed": true, |
| #!/dev/null | |
| # This 'script' is a set of instructions for preparing and bundling an Arch | |
| # Linux AMI for Amazon's EC2. Bits are to be run on three different | |
| # computers, and there is interaction required, so please follow along and | |
| # run commands individually. | |
| # PROTIP: THESE DON'T ACTUALLY WORK. That's why I'm pasting them here, | |
| # attemping to get some input on what I'm doing wrong. When the instructions | |
| # are ready for prime-time, I'll clean them up and post them to my blog. If | |
| # you're really interested, watch for it there: |