My path through nerd matter
As I was doing a routine migration of a WordPress site this morning I was looking at the fabric menu ( fab -l ) that had grown painfully long. And I wondered: “Would’nt it be nice if I counld just be typing the first letter in he fabric task and then hit tab to get the rest of it?”
Google next, and there on GitHub, just the thing I needed: Fabric-completion.
Enter Salt master, edit my user state, state.highstate, and voila: Fabric bash completion 🙂
It works for task aliases as well 😉
Suddenly, probaly after an upgrade, my network connection started being slow.
Seams like IPv6 is the one to blame so I followed this suggestion and my network connection was brought back to normal again:
disable-ipv6-if-your-internet-is
How often do you copy and paste the contents of ~/.ssh/id_rsa.pub to remote ~/.ssh/authorized_keys?
With ssh-copy-id its easy!
Say you need to copy your public key to example.com, this would do the trick:
|
1 |
ssh-copy-id myusername@example.com |
Thanks to Johan Westin that tipped me about this page 🙂
See vimninjas.com for the whole article.
Create a file called “vimrc-local.vim” in the ~/.vim/plugin/ directory. After that, put the following 5 lines of code in it:
|
1 2 3 4 5 |
" Do we have local vimrc? if filereadable('.vimrc.local') " If so, go ahead and load it. source .vimrc.local endif |
Reacently I shared a development environment with a colleague. When he started up the vm he got an error message stating that some settings where incorrect from vagrant (sorry, I don’t have the message to paste in here). When he ran the vm from the VirtualBox gui he got this error message:
It turned out my colleatues pc did not support hardware virtualization and thus could not use 64 bit vms. No big deal, he switched to use lucid32.box instad and everything was fine 🙂
Developing web applications using CMS like Drupal may be chalanging when there are more than one developer working on the same project. Source code is managed easily with Git (or other VCS), but the database content must be treated with care. Either you go for a relay baton method: One developer updating the database at the time and all other must get new dumps after the update, or you can export / import features stored in the database.
I wanted to try the latter with Drupal Views, and could not find any documentation that worked out-of-the-box with my project so here is what I ended up with:
Create a new module
See Creating modules – a tutorial: Drupal 7.x
|
1 2 3 4 5 6 |
viewsimport/ ├── views │ └── view.my_exported_view.inc ├── viewsimport.info ├── viewsimport.module └── viewsimport.views_default.inc |
Export view(s)
Export whatever views you want to be able to import (revert). From the views list (admin/structure/views) you should be able to select “Export” on the views you want to export.
This will display PHP code in a textarea. You should copy the contents and paste it in a file, say named view.my_exported_view.inc.
Remember to add “<?php” on the first line.
My example files
Here is my modules/viewsimport/viewsimport.info file:
|
1 2 3 4 |
name = "Views Import" description = "A module that allows views to be imported" core = "7.x" dependencies[] = "views" |
Here is my modules/viewsimport/viewsimport.module file:
|
1 2 3 4 5 6 7 8 |
/** * Implementation of hook_views_api(). */ function viewsimport_views_api() { return array( 'api' => 3.0, ); } |
Here is my modules/viewsimport/viewsimport.views_default.inc:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
/** * @file * Load default views for this module */ /** * iframe_views_default_views * * Load the default views * * @access public * @return void */ function viewsimport_views_default_views() { $views = array(); include(dirname(__FILE__) .'/views/view.my_exported_view.inc'); $views[$views->name] = $view; return $views; } |
Some of the articles I stumbled over:
Some time it is necessary to fool your PHP application to test functionality related to a “current date”.
Fooling php cli is simple using faketime:
Say you have this PHP script:
|
1 2 |
#!/usr/bin/env php print date( 'F j. Y [H:i]' )."\n"; |
Rendering this script with php through faketime will give you results like this:
|
1 2 |
$ faketime 'last Friday 5 pm' ./time.php December 9. 2011 [17:00] |
The same can be achieved using the datefudge command:
|
1 2 |
$ datefudge "2007-04-01 10:23" ./time.php April 1. 2007 [10:23] |
Faking time for a webapplication
Faking time for a web application is not that simple since apache will fork a process for each request and thus create a new php processes.
In this post I will show you how to use FakeTime Preload Library to fake time system wide while running tests on a web application.
First I need to install faketimelib as described on the librarys homepage.
In short:
|
1 2 3 4 5 6 7 |
wget http://www.code-wizards.com/projects/libfaketime/libfaketime-0.8.1.tar.gz tar -xvzf libfaketime-0.8.1.tar.gz cd libfaketime-0.8.1 vim README make sudo make install export LD_PRELOAD=/usr/local/lib/faketime/libfaketime.so.1 |
For the demonstration I will use a php script like this:
|
1 |
printf( "The current time of the server is: %s\n", date('l F j. Y [H:i:s]') ); |
Running this script should yield something like:
|
1 2 |
$ php time.php The current time of the server is: Friday December 16. 2011 [08:02:43] |
Now I create a file in my home folder, faketimerc, with a new future time. I will use this file in different ways to show how I can manipulate the time.
|
1 |
echo "@2012-12-21 12:12:12" > faketimerc |
If you now create an environment variable, FAKETIME, give it a future time, and running the same script would yield something like this:
|
1 2 3 4 5 6 7 8 |
$ php time.php The current time of the server is: Friday December 16. 2011 [08:19:39] $ export FAKETIME=$(cat faketimerc) $ php time.php The current time of the server is: Friday December 21. 2012 [12:12:12] $ unset FAKETIME $ php time.php The current time of the server is: Friday December 16. 2011 [08:19:56] |
As you can see, the processes you run while the environment variable is set to a future time will get a fake time. Once the variable is unset new processes will get normal time.
This can be achieved also by creating a file. “.faketimerc” in your home folder:
|
1 2 3 4 5 6 7 8 |
$ php time.php The current time of the server is: Friday December 16. 2011 [08:23:12] $ cp faketimerc .faketimerc $ php time.php The current time of the server is: Friday December 21. 2012 [12:12:12] $ rm -f .faketimerc $ php time.php The current time of the server is: Friday December 16. 2011 [08:23:36] |
If you want to change time for a php application that runs though apache you may want to set the fake time system wide so that the php processes spowned use the faked time. To do this you need to create a file, /etc/.faketimerc, just the same as the one I created in my home folder.
I will use w3m for this demonstration. I assume a normal ubuntu server with apache2 installed.
|
1 2 3 4 5 6 7 8 9 10 |
sudo cp time.php /var/www sudo cp faketimerc /etc/ $ sudo /etc/init.d/apache2 restart * Restarting web server apache2 ... waiting $ php /var/www/time.php The current time of the server is: Friday December 21. 2012 [12:12:12] $ date fr. 21. des. 12:12:12 +0100 2012 $ w3m -dump localhost/time.php The current time of the server is: Friday December 16. 2011 [11:16:24] |
As you can see, the date command and when rendering the script with php, gives me the fake time, but when rendering the script through apache I loose the fake time. This is because the environment variable LD_PRELOAD is not set for the apache process.
To fix this I need to set LD_PRELOAD for apache by editing /etc/apache/envvars. Lets test it again:
|
1 2 3 4 5 |
$ sudo bash -c "echo \"export LD_PRELOAD='/usr/local/lib/faketime/libfaketime.so.1'\" >> /etc/apache2/envvars" $ sudo /etc/init.d/apache2 restart * Restarting web server apache2 ... waiting $ w3m -dump localhost/time.php The current time of the server is: Friday December 21. 2012 [12:12:16] |
Fake time! 🙂
PS! If you also want your PostgreSQL server to use fake time:
|
1 2 |
$ sudo bash -c "echo \"LD_PRELOAD='/usr/local/lib/faketime/libfaketime.so.1'\" >> /etc/postgresql/8.4/main/environment" $ sudo /etc/init.d/postgresql-8.4 restart |
In case you should wonder what is the difference between the /usr/bin/ubuntu-vm-builder and /ur/bin/vmbuilder, there is no difference.
Both scripts use the same python VMBuilder library, and contain accactly the same code…
You want to create a VirtualBox with Ubuntu 10.04.3 using Veewee, but there is no ubuntu-10.04.3 template?
Here is what you can do:
Download (git clone) a copy of veewee from GitHub and copy the templates.
|
1 2 3 |
git clone https://github.com/jedi4ever/veewee.git cd veewee sudo cp -r templates/ubuntu-10.04.3-server-* /usr/lib/ruby/gems/1.8/gems/veewee-0.2.0/templates/ |
To verify that you have the new templates:
|
1 |
vagrant basebox templates |
Recently I discovered that the virtual server I was working on did not give me the usual bash completion I’m so used to on my Kubuntu workstations. Working on git repositories and upgrading web applications made this to an itch I just had to scratch.
After a bit of searching it appeared that I was missing a file: /etc/bash_completion. Next I discovered that there is a /etc/bash_completion.d/ directory and under this a file named ‘git’. I copied the bash_completion file from my workstation and followed the instruction in /etc/bash_completion.d/git and suddenly I had bash completion and a prompt that gave me branch name and the status of the git repository I was currently in.
Just to give you a hint, here is the comment from the /etc/bash_completion.d/git file:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 |
#!bash # # bash completion support for core Git. # # Copyright (C) 2006,2007 Shawn O. Pearce # Conceptually based on gitcompletion (http://gitweb.hawaga.org.uk/). # Distributed under the GNU General Public License, version 2.0. # # The contained completion routines provide support for completing: # # *) local and remote branch names # *) local and remote tag names # *) .git/remotes file names # *) git 'subcommands' # *) tree paths within 'ref:path/to/file' expressions # *) common --long-options # # To use these routines: # # 1) Copy this file to somewhere (e.g. ~/.git-completion.sh). # 2) Added the following line to your .bashrc: # source ~/.git-completion.sh # # Or, add the following lines to your .zshrc: # autoload bashcompinit # bashcompinit # source ~/.git-completion.sh # # 3) Consider changing your PS1 to also show the current branch: # PS1='[\u@\h \W$(__git_ps1 " (%s)")]\$ ' # # The argument to __git_ps1 will be displayed only if you # are currently in a git repository. The %s token will be # the name of the current branch. # # In addition, if you set GIT_PS1_SHOWDIRTYSTATE to a nonempty # value, unstaged (*) and staged (+) changes will be shown next # to the branch name. You can configure this per-repository # with the bash.showDirtyState variable, which defaults to true # once GIT_PS1_SHOWDIRTYSTATE is enabled. # # You can also see if currently something is stashed, by setting # GIT_PS1_SHOWSTASHSTATE to a nonempty value. If something is stashed, # then a '$' will be shown next to the branch name. # # If you would like to see if there're untracked files, then you can # set GIT_PS1_SHOWUNTRACKEDFILES to a nonempty value. If there're # untracked files, then a '%' will be shown next to the branch name. # # If you would like to see the difference between HEAD and its # upstream, set GIT_PS1_SHOWUPSTREAM="auto". A "<" indicates # you are behind, ">" indicates you are ahead, and "<>" # indicates you have diverged. You can further control # behaviour by setting GIT_PS1_SHOWUPSTREAM to a space-separated # list of values: # verbose show number of commits ahead/behind (+/-) upstream # legacy don't use the '--count' option available in recent # versions of git-rev-list # git always compare HEAD to @{upstream} # svn always compare HEAD to your SVN upstream # By default, __git_ps1 will compare HEAD to your SVN upstream # if it can find one, or @{upstream} otherwise. Once you have # set GIT_PS1_SHOWUPSTREAM, you can override it on a # per-repository basis by setting the bash.showUpstream config # variable. # # # To submit patches: # # *) Read Documentation/SubmittingPatches # *) Send all patches to the current maintainer: # # "Shawn O. Pearce" # # *) Always CC the Git mailing list: # # git@vger.kernel.org # |
