diff options
| author | Franck Cuny <franck.cuny@gmail.com> | 2013-12-09 22:08:44 -0800 |
|---|---|---|
| committer | Franck Cuny <franck.cuny@gmail.com> | 2013-12-09 22:08:44 -0800 |
| commit | 7286cd50a139faef33da5eb50ad76b605e5886aa (patch) | |
| tree | d8a0dbc50249fd17dc33c1e654e011ba576eccd2 | |
| parent | Remove a bunch of unused files. (diff) | |
| download | lumberjaph-7286cd50a139faef33da5eb50ad76b605e5886aa.tar.gz | |
Mostly, fix broken links.
35 files changed, 131 insertions, 149 deletions
diff --git a/_posts/2008-06-14-how-to-use-vim-as-a-personal-wiki.md b/_posts/2008-06-14-how-to-use-vim-as-a-personal-wiki.md index c5efedb..759b506 100644 --- a/_posts/2008-06-14-how-to-use-vim-as-a-personal-wiki.md +++ b/_posts/2008-06-14-how-to-use-vim-as-a-personal-wiki.md @@ -9,7 +9,7 @@ There is different reasons to want a personal wiki on your machine: * privacy * having it everywhere -I've tested a few wikis engines, like tiddlywiki, but I've found nothing that was really what I wanted. The main inconveniance is the need to use a webbrowser. A browser is not a text processor, so it's really painfull to use them for writing. +I've tested a few wikis engines, like [tiddlywiki](http://tiddlywiki.com/), but I've found nothing that was really what I wanted. The main inconveniance is the need to use a webbrowser. A browser is not a text processor, so it's really painfull to use them for writing. I've started to try to use vim as wiki. Why would I want to use something like vim for this ? well, it's plain text (easy to grep, or to write script for manipulating data), application independent, it's a real text processor, you can customize it, and most importantly, I know how to use it, ... @@ -34,14 +34,12 @@ set softtabstop=2 " Unify I organize my files in directory. I've got a **work**, **lists**, **recipes**, **misc**, ... and I put my files in this directory. -I've got an index page, with links to main section. I don't have wikiword in camelcase or things like that, so if i want to put a link to a page, I just wrote the link this way **dir_name/page_name**, then, i juste have to hit `gf` on this link to open the page. I also use this place as a todo list manager. I've got one paragrah per day, like this : +I've got an index page, with links to main section. I don't have wikiword in camelcase or things like that, so if i want to put a link to a page, I just wrote the link this way **dir_name/page_name**, then, i juste have to hit `gf` on this link to open the page. I also use this place as a todo list manager. I've got one paragrah per day, like this : -``` -2008-06-14 - - [@context] task 1 - - [@context] task 2 - ... -``` + 2008-06-14 + - [@context] task 1 + - [@context] task 2 + ... and a bunch of vim mapping for marking complete (`,c`), work in progress (`,w`) or canceled (`,x`). diff --git a/_posts/2008-06-18-keep-your-zshrc-simple.md b/_posts/2008-06-18-keep-your-zshrc-simple.md index 65332bd..8a632b6 100644 --- a/_posts/2008-06-18-keep-your-zshrc-simple.md +++ b/_posts/2008-06-18-keep-your-zshrc-simple.md @@ -12,7 +12,7 @@ zsh_cache=${HOME}/.zsh_cache mkdir -p $zsh_cache compinit -d $zsh_cache/zcomp-$HOST for f in ~/.zshrc $zsh_cache/zcomp-$HOST; do - zrecompile -p $f && rm -f $f.zwc.old + zrecompile -p $f && rm -f $f.zwc.old done setopt extended_glob for zshrc_snipplet in ~/.zsh.d/S[0-9][0-9]*[^~] ; do @@ -23,15 +23,13 @@ function history-all { history -E 1 } and then, in my **.zsh.d** directory, I've got: -{% highlight sh %} -S10_zshopts -S20_environment -S30_binds -S40_completion -S50_aliases -S60_prompt -S71_ssh -S72_git -{% endhighlight %} + S10_zshopts + S20_environment + S30_binds + S40_completion + S50_aliases + S60_prompt + S71_ssh + S72_git All my aliases are in the same file, it's much easier to search/find/add. diff --git a/_posts/2008-06-24-ack.md b/_posts/2008-06-24-ack.md index c791e83..6520ee2 100644 --- a/_posts/2008-06-24-ack.md +++ b/_posts/2008-06-24-ack.md @@ -8,7 +8,7 @@ summary: In which I share my settings for ack.. [Ack](https://metacpan.org/module/App::Ack) is a really nice tool for searching your source code. It's faster than grep because he already knows what you want : searching your sources files :) -By default it will not search in SCM files (**.svn**, **.cvs**, ...), backups files (**source.pl~**, **source.pl.bak**, ...). You can specify what kind of files you want (`--perl`, `--cc`, ...), make it match some regex with `--match`, ... +By default it will not search in SCM files (.git, .svn, ...), backups files (source.pl~, source.pl.bak, ...). You can specify what kind of files you want (`--perl`, `--cc`, ...), make it match some regex with `--match`, ... And you can set some defaults configuration in a .ackrc file ! Mine looks like this: @@ -19,6 +19,6 @@ And you can set some defaults configuration in a .ackrc file ! Mine looks like t --follow {% endhighlight %} -Check also: [vim with ack integration](http://use.perl.org/~Ovid/journal/36430?from=rss). +Check also: [vim with ack integration](http://use.perl.org/use.perl.org/_Ovid/journal/36430.html). Oh, and it's the only program with `--thpppt` option! diff --git a/_posts/2008-06-26-git-branch-everywhere.md b/_posts/2008-06-26-git-branch-everywhere.md index bde1ffa..ed93df2 100644 --- a/_posts/2008-06-26-git-branch-everywhere.md +++ b/_posts/2008-06-26-git-branch-everywhere.md @@ -9,7 +9,7 @@ The current trend is to have the name of the current git branch everywhere. Pers Here is my vimrc configuration for this (I'm not the author of this function, and can't remember where I saw it first): {% highlight vim %} -set statusline=%<[%n]%m%r%h%w%{'['.(&fenc!=''?&fenc:&enc).':'.&ff}%{g:gitCurrentBranch}%{']'}%y\ %F%=%l,%c%V%8P +set statusline=%<[%n]%m%r%h%w%{'['.(&fenc!=''?&fenc:&enc).':'.&ff}%{g:gitCurrentBranch}%{']'}%y\ %F%=%l,%c%V%8P autocmd BufEnter * :call CurrentGitBranch() let g:gitCurrentBranch = '' @@ -32,7 +32,7 @@ and my zshrc: {% highlight vim %} local git_b git_b='$(get_git_prompt_info '%b')' -PROMPT="%(?..%U%?%u:) $git_b %40<...<%/%(#.%U>%u.%B>%b) " +PROMPT="%(?..%U%?%u:) $git_b %40>...<%/%(#.%U>%u.%B>%b) " {% endhighlight %} with the following script [S55_git](http://www.jukie.net/~bart/conf/zsh.d/S55_git). diff --git a/_posts/2008-06-27-dotfiles-and-scm.md b/_posts/2008-06-27-dotfiles-and-scm.md index 5e1888b..6769efd 100644 --- a/_posts/2008-06-27-dotfiles-and-scm.md +++ b/_posts/2008-06-27-dotfiles-and-scm.md @@ -1,6 +1,6 @@ --- layout: post -summary: In which I share how I manage my dotfiles +summary: In which I share how I manage my dotfiles. title: Dotfiles and SCM --- @@ -10,36 +10,36 @@ So, instead of copying my files over different computers, I put everything in a I've got a $HOME/dotfiles directory, which is versionned (with git in my case). All my configurations file are stored here. -In this directory, as I'm avery lazy person, I've created a Makefile. Each time I create a new file, I add it to the makefile at the same time. The content of the Makefile is the following: +In this directory, as I'm avery lazy person, I've created a Makefile. Each time I create a new file, I add it to the makefile at the same time. The content of the Makefile is the following: -{% highlight sh %} +{% highlight make %} DOTFILES := $(shell pwd) all: shell code perl plagger web shell: -ln -fs $(DOTFILES)/zshrc ${HOME}/.zshrc -ln -fns $(DOTFILES)/zsh.d ${HOME}/.zsh.d -ln -fs $(DOTFILES)/inputrc ${HOME}/.inputrc -ln -fs $(DOTFILES)/screenrc ${HOME}/.screenrc -ln -fns $(DOTFILES)/screen ${HOME}/.screen -ln -fs $(DOTFILES)/profile ${HOME}/.profile -ln -fs $(DOTFILES)/gnupg ${HOME}/.gnupg code: -ln -fs $(DOTFILES)/vimrc ${HOME}/.vimrc -ln -fs $(DOTFILES)/gvimrc ${HOME}/.gvimrc -ln -fns $(DOTFILES)/vim ${HOME}/.vim -ln -fs $(DOTFILES)/ackrc ${HOME}/.ackrc -ln -fs $(DOTFILES)/gitignore ${HOME}/.gitignore -ln -fs $(DOTFILES)/gitconfig ${HOME}/.gitconfig -ln -fs $(DOTFILES)/psqlrc ${HOME}/.psqlrc perl: -ln -fs $(DOTFILES)/proverc ${HOME}/.proverc -ln -fs $(DOTFILES)/pause ${HOME}/.pause -ln -fs $(DOTFILES)/perltidyrc ${HOME}/.perltidyrc -ln -fns $(DOTFILES)/module-starter ${HOME}/.module-starter plagger: -ln -fns $(DOTFILES)/plagger ${HOME}/.plagger web: -ln -fns $(DOTFILES)/irssi ${HOME}/.irssi -ln -fns $(DOTFILES)/vimperator ${HOME}/.vimperator -ln -fs $(DOTFILES)/vimperatorrc ${HOME}/.vimperatorrc -ln -fs $(DOTFILES)/flickrrc ${HOME}/.flickrrc -ln -fs $(DOTFILES)/rtorrent.rc ${HOME}/.rtorrent.rc + ln -fs $(DOTFILES)/zshrc ${HOME}/.zshrc + ln -fns $(DOTFILES)/zsh.d ${HOME}/.zsh.d + ln -fs $(DOTFILES)/inputrc ${HOME}/.inputrc + ln -fs $(DOTFILES)/screenrc ${HOME}/.screenrc + ln -fns $(DOTFILES)/screen ${HOME}/.screen + ln -fs $(DOTFILES)/profile ${HOME}/.profile + ln -fs $(DOTFILES)/gnupg ${HOME}/.gnupg code: + ln -fs $(DOTFILES)/vimrc ${HOME}/.vimrc + ln -fs $(DOTFILES)/gvimrc ${HOME}/.gvimrc + ln -fns $(DOTFILES)/vim ${HOME}/.vim + ln -fs $(DOTFILES)/ackrc ${HOME}/.ackrc + ln -fs $(DOTFILES)/gitignore ${HOME}/.gitignore + ln -fs $(DOTFILES)/gitconfig ${HOME}/.gitconfig + ln -fs $(DOTFILES)/psqlrc ${HOME}/.psqlrc perl: + ln -fs $(DOTFILES)/proverc ${HOME}/.proverc + ln -fs $(DOTFILES)/pause ${HOME}/.pause + ln -fs $(DOTFILES)/perltidyrc ${HOME}/.perltidyrc + ln -fns $(DOTFILES)/module-starter ${HOME}/.module-starter plagger: + ln -fns $(DOTFILES)/plagger ${HOME}/.plagger web: + ln -fns $(DOTFILES)/irssi ${HOME}/.irssi + ln -fns $(DOTFILES)/vimperator ${HOME}/.vimperator + ln -fs $(DOTFILES)/vimperatorrc ${HOME}/.vimperatorrc + ln -fs $(DOTFILES)/flickrrc ${HOME}/.flickrrc + ln -fs $(DOTFILES)/rtorrent.rc ${HOME}/.rtorrent.rc {% endhighlight %} So next time I want to deploy my dotfiles on a new computer, I can run `make all` or `make perl code vim` and I can start coding some perl with vim. diff --git a/_posts/2008-06-30-upgrading-to-perl-5.10.md b/_posts/2008-06-30-upgrading-to-perl-5.10.md index 9746ac4..057c294 100644 --- a/_posts/2008-06-30-upgrading-to-perl-5.10.md +++ b/_posts/2008-06-30-upgrading-to-perl-5.10.md @@ -22,4 +22,4 @@ then install Perl 5.10: % /opt/perl/bin/perl -e 'use feature qw(say); say "hi"' {% endhighlight %} -and then re-install your modules with `cpan \`cat module.list\``. +and then re-install your modules with <code>cpan \`cat module.list\`</code>. diff --git a/_posts/2008-12-05-vim-and-git.md b/_posts/2008-12-05-vim-and-git.md index 00f8ff1..39f8024 100644 --- a/_posts/2008-12-05-vim-and-git.md +++ b/_posts/2008-12-05-vim-and-git.md @@ -4,7 +4,7 @@ summary: In which I share another snippet of code for vim. title: vim and git --- -idea from "Ovid's journal":http://use.perl.org/~Ovid/journal/37966 (ovid is full of really good ideas for vim): +idea from [Ovid's journal](http://use.perl.org/use.perl.org/_Ovid/journal/37966.html) (ovid is full of really good ideas for vim): to get a quick git diff in my vim session, put this in your .vimrc @@ -33,15 +33,11 @@ endfunction the output looks like this: -{% highlight sh %} -Choose a revision: -1: ea0bb4d - (3 days ago) franck cuny - fix new_freq -2: a896ac7 - (5 weeks ago) franck cuny - fix typo -3: c9bc5fd - (5 weeks ago) franck cuny - update test -4: e9de4be - (5 weeks ago) franck cuny - change the way we rewrite and check an existing url -5: 3df1fd6 - (7 weeks ago) franck cuny - put id category -{% endhighlight %} + Choose a revision: + 1: ea0bb4d - (3 days ago) franck cuny - fix new_freq + 2: a896ac7 - (5 weeks ago) franck cuny - fix typo + 3: c9bc5fd - (5 weeks ago) franck cuny - update test + 4: e9de4be - (5 weeks ago) franck cuny - change the way we rewrite and check an existing url + 5: 3df1fd6 - (7 weeks ago) franck cuny - put id category You choose the revision you want to check the diff against, and you got a (colorless) diff in your vim buffer. - - diff --git a/_posts/2009-03-08-belgian-perl-workshop-09.md b/_posts/2009-03-08-belgian-perl-workshop-09.md index 19ef01f..d4d047e 100644 --- a/_posts/2009-03-08-belgian-perl-workshop-09.md +++ b/_posts/2009-03-08-belgian-perl-workshop-09.md @@ -1,7 +1,7 @@ --- layout: post summary: In which I went to the Belgian Perl Workshop. -title: belgian perl workshop 09 +title: Belgian Perl Workshop 09 --- last weekend my co-workers and I went to the [Belgian Perl Workshop 09](http://conferences.mongueurs.net/bpw2009/). I attended the following presentations: diff --git a/_posts/2009-04-27-a-simple-feed-aggregator-with-modern-perl-part-1.md b/_posts/2009-04-27-a-simple-feed-aggregator-with-modern-perl-part-1.md index 4acb0e7..9cda369 100644 --- a/_posts/2009-04-27-a-simple-feed-aggregator-with-modern-perl-part-1.md +++ b/_posts/2009-04-27-a-simple-feed-aggregator-with-modern-perl-part-1.md @@ -4,14 +4,14 @@ summary: In which I write a feed aggregator in Perl. layout: post --- -Following [Matt's post](http://www.shadowcat.co.uk/blog/matt-s-trout/iron-man/) about people not blogging enough about Perl, I've decided to try to post once a week about Perl. So I will start by a series of articles about what we call **modern Perl**. For this, I will write a simple feed agregator (using [Moose](http://search.cpan.org/~drolsky/Moose-0.75/lib/Moose.pm), [DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class), [KiokuDB](http://search.cpan.org/perldoc?KiokuDB), some tests, and a basic frontend (with [Catalyst](http://search.cpan.org/perldoc?Catalyst)). This article will be split in four parts: +Following [Matt's post](http://www.shadowcat.co.uk/blog/matt-s-trout/iron-man/) about people not blogging enough about Perl, I've decided to try to post once a week about Perl. So I will start by a series of articles about what we call **modern Perl**. For this, I will write a simple feed agregator (using [Moose](https://metacpan.org/pod/Moose), [DBIx::Class](http://search.cpan.org/perldoc?DBIx::Class), [KiokuDB](http://search.cpan.org/perldoc?KiokuDB), some tests, and a basic frontend (with [Catalyst](http://search.cpan.org/perldoc?Catalyst)). This article will be split in four parts: * the first one will explain how to create a schema using **DBIx::Class** * the second will be about the aggregator. I will use **Moose*** and **KiokuDB** * the third one will be about writing tests with **Test::Class** * the last one will focus on **Catalyst** -The code of these modules will be available on my github account at the same time each article is published. +The code of these modules will be available on [my Bitbucket account](https://bitbucket.org/franckcuny/) at the same time each article is published. > I'm not showing you how to write the perfect feed aggregator. The purpose of this series of articles is only to show you how to write a simple aggregator using modern Perl. @@ -130,14 +130,8 @@ sub usage { This script will deploy for you the schema (you need to create the database first if using with mysql). -Executing the following command: +Executing the following command `perl bin/deploy_mymodel.pl --dsn dbi:SQLite:model.db` will generate a **model.db** database so we can work and test it. Now that we got our (really) simple **MyModel** schema, we can start to hack on our aggregator. -{% highlight bash %} -% perl bin/deploy_mymodel.pl --dsn dbi:SQLite:model.db -{% endhighlight %} - -generate a **model.db** database so we can work and test it. Now that we got our (really) simple **MyModel** schema, we can start to hack on our aggregator. - -[link to the code](http://github.com/franckcuny/ironman-mymodel/tree/master) +[The code is available on Bitbucket](https://bitbucket.org/franckcuny/ironman-mymodel/overview). > while using **DBIx::Class**, you may want to take a look at the generated queries. For this, export `DBIC_TRACE=1` in your environment, and the queries will be printed on STDERR. diff --git a/_posts/2009-04-28-a-simple-feed-aggregator-with-modern-perl-part-2.md b/_posts/2009-04-28-a-simple-feed-aggregator-with-modern-perl-part-2.md index c90d31d..b63e27e 100644 --- a/_posts/2009-04-28-a-simple-feed-aggregator-with-modern-perl-part-2.md +++ b/_posts/2009-04-28-a-simple-feed-aggregator-with-modern-perl-part-2.md @@ -8,7 +8,7 @@ summary: In which we continue to write a feed aggregator in Perl. For the feed aggregator, I will use **Moose**, **KiokuDB** and our **DBIx::Class** schema. Before we get started, I'd would like to give a short introduction to Moose and KiokuDB. -Moose is a "A postmodern object system for Perl 5". Moose brings to OO Perl some really nice concepts like roles, a better syntax, "free" constructor and destructor, ... If you don't already know Moose, check "http://www.iinteractive.com/moose/":http://www.iinteractive.com/moose/ for more informations. +Moose is a "A postmodern object system for Perl 5". Moose brings to OO Perl some really nice concepts like roles, a better syntax, "free" constructor and destructor, ... If you don't already know Moose, check [it here](http://www.iinteractive.com/moose/) for more information. KiokuDB is a Moose based frontend to various data stores [...] Its purpose is to provide persistence for "regular" objects with as little effort as possible, without sacrificing control over how persistence is actually done, especially for harder to serialize objects. [...] KiokuDB is meant to solve two related persistence problems: diff --git a/_posts/2009-05-04-rtgi-and-perl-conferences.md b/_posts/2009-05-04-rtgi-and-perl-conferences.md index 0f3d754..75711e2 100644 --- a/_posts/2009-05-04-rtgi-and-perl-conferences.md +++ b/_posts/2009-05-04-rtgi-and-perl-conferences.md @@ -4,4 +4,4 @@ summary: In which I go to a few conferences. title: RTGI and Perl conferences --- -<a href="http://rtgi.fr">RTGI</a> will be one of the sponsors of the <a href="http://conferences.mongueurs.net/fpw2009/">French Perl Workshop 2009</a>. I (or Camille, not sure yet) will also give a <a href="http://conferences.mongueurs.net/fpw2009/talk/1934">talk</a> about the Perl and CPAN community on the web. Camille (for sure this time) will also give do this talk at the <a href="Yhttp://yapceurope2009.org/ye2009/">YAPC::EU</a> at Lisbon this summer <a href="http://yapceurope2009.org/ye2009/talk/2061">(and in english this time)</a>. +<a href="http://rtgi.fr">RTGI</a> will be one of the sponsors of the <a href="http://conferences.mongueurs.net/fpw2009/">French Perl Workshop 2009</a>. I (or Camille, not sure yet) will also give a <a href="http://conferences.mongueurs.net/fpw2009/talk/1934">talk</a> about the Perl and CPAN community on the web. Camille (for sure this time) will also give do this talk at the <a href="http://yapceurope2009.org/ye2009/">YAPC::EU</a> at Lisbon this summer <a href="http://yapceurope2009.org/ye2009/talk/2061">(and in english this time)</a>. diff --git a/_posts/2009-05-13-a-simple-feed-aggregator-with-modern-perl-part-4.md b/_posts/2009-05-13-a-simple-feed-aggregator-with-modern-perl-part-4.md index aace6ea..2d3cca7 100644 --- a/_posts/2009-05-13-a-simple-feed-aggregator-with-modern-perl-part-4.md +++ b/_posts/2009-05-13-a-simple-feed-aggregator-with-modern-perl-part-4.md @@ -141,13 +141,9 @@ We create our 2 templates (for index and view): </ul> {% endhighlight %} -If you point your browser to +If you point your browser to http://localhost:3000/feed/ you will see this: -bc. http://localhost:3000/feed/ - -you will see this: - -!/static/imgs/list_feed.png(list feeds)! +<img src='/static/imgs/list_feed.png' alt='list feeds'> Now the controller for displaying the entries: @@ -182,7 +178,7 @@ The function **view** fetch an entry from the kiokudb backend, and store it in t If you point your browser to an entry (something like **http://localhost:3000/entry/somesha256value**), you will see an entry: -!/static/imgs/show_entry.png(show entry)! +<img src='/static/imgs/show_entry.png' alt='show entry'> Et voila, we are done with a really basic feed reader. You can add methods to add or delete feed, mark an entry as read, ... diff --git a/_posts/2009-05-18-a-simple-feed-aggregator-with-modern-perl-part-4.1.md b/_posts/2009-05-18-a-simple-feed-aggregator-with-modern-perl-part-4.1.md index 8f0e033..0c3af16 100644 --- a/_posts/2009-05-18-a-simple-feed-aggregator-with-modern-perl-part-4.1.md +++ b/_posts/2009-05-18-a-simple-feed-aggregator-with-modern-perl-part-4.1.md @@ -138,19 +138,19 @@ We got `feed` which is chained to root. `index` is chained to feed, and take no If you start the application, you will see the following routes: -> .-------------------------------------+--------------------------------------. -> | Path Spec | Private | -> +-------------------------------------+--------------------------------------+ -> | /root/entry/* | /root (0) | -> | | => /entry/view | -> | /root/feed | /root (0) | -> | | -> /feed/feed (0) | -> | | => /feed/index | -> | /root/feed/view/* | /root (0) | -> | | -> /feed/feed (0) | -> | | => /feed/view | -> | /root | /root (0) | -> | | => /index | -> '-------------------------------------+--------------------------------------' + .-------------------------------------+--------------------------------------. + | Path Spec | Private | + +-------------------------------------+--------------------------------------+ + | /root/entry/* | /root (0) | + | | => /entry/view | + | /root/feed | /root (0) | + | | -> /feed/feed (0) | + | | => /feed/index | + | /root/feed/view/* | /root (0) | + | | -> /feed/feed (0) | + | | => /feed/view | + | /root | /root (0) | + | | => /index | + '-------------------------------------+--------------------------------------' I hope you got a better idea about chained action in catalyst now. And again, thanks to bobtfish for the code. diff --git a/_posts/2009-05-30-catalystx-dispatcher-asgraph.md b/_posts/2009-05-30-catalystx-dispatcher-asgraph.md index 735cb52..89591e1 100644 --- a/_posts/2009-05-30-catalystx-dispatcher-asgraph.md +++ b/_posts/2009-05-30-catalystx-dispatcher-asgraph.md @@ -4,9 +4,9 @@ title: CatalystX::Dispatcher::AsGraph summary: In which I wrote a module to visualize routes in Catalyst. --- -This morning I saw [this post](http://marcus.nordaaker.com/2009/05/awesome-route-graph-with-mojoxroutesasgraph/) from Marcus Ramberg about [MojoX::Routes::AsGraph](http://search.cpan.org/perldoc?MojoX::Routes::AsGraph). I liked the idea. But as I Catalyst instead of Mojo, I thought I could give a try and do the same thing for Catalyst dispatcher, and I've coded CatalystX::Dispatcher::AsGraph. For the moment only private actions are graphed. +This morning I saw [this post](http://marcus.nordaaker.com/awesome-route-graph-with-mojoxroutesasgraph/) from Marcus Ramberg about [MojoX::Routes::AsGraph](http://search.cpan.org/perldoc?MojoX::Routes::AsGraph). I liked the idea. But as I Catalyst instead of Mojo, I thought I could give a try and do the same thing for Catalyst dispatcher, and I've coded CatalystX::Dispatcher::AsGraph. For the moment only private actions are graphed. -!/static/imgs/routes-300x249.png(routes)! +<img src='/static/imgs/routes-300x249.png' alt='routes'> You use it like this: `perl bin/catalyst_graph_dispatcher.pl --appname Arkham --output routes.png` @@ -22,6 +22,6 @@ $graph->run; print $graph->graph->as_txt; {% endhighlight %} -The code is on [GitHub](http://github.com/franckcuny/CatalystX--Dispatcher--AsGraph/tree/master) for the moment. +The code is on [Bitbucket](https://bitbucket.org/franckcuny/catalystx-dispatcher-asgraph) for the moment. For thoses who are interested by visualization, I'll publish soon some (at least I think) really nice visualisations about CPAN, Perl, and his community, that we have created at [$work](http://rtgi.fr). diff --git a/_posts/2009-06-06-modules-i-like-web-scraper.md b/_posts/2009-06-06-modules-i-like-web-scraper.md index e2808cc..0f53338 100644 --- a/_posts/2009-06-06-modules-i-like-web-scraper.md +++ b/_posts/2009-06-06-modules-i-like-web-scraper.md @@ -1,7 +1,7 @@ --- layout: post -summary: In which I talk about Web::Scraper -title: modules I like Web::Scraper +summary: In which I talk about Web::Scraper. +title: Modules I like Web::Scraper --- For [$work](http://rtgi.fr) I need to write scrapers. It used to be boring and painful. But thanks to [miyagawa](http://search.cpan.org/~miyagawa/), this is not true anymore. [Web::Scraper](http://search.cpan.org/perldoc?Web::Scraper) offer a nice API: you can write your rules using XPath, you can chaine rules, a nice and simple syntax, etc. diff --git a/_posts/2009-06-12-shape-of-cpan.md b/_posts/2009-06-12-shape-of-cpan.md index 0e4ef86..12ef04f 100644 --- a/_posts/2009-06-12-shape-of-cpan.md +++ b/_posts/2009-06-12-shape-of-cpan.md @@ -6,7 +6,7 @@ title: The shape of the CPAN My talk at the [FPW](http://conferences.mongueurs.net/fpw2009/) this year is about the shape of the Perl and CPAN community. This talk was prepared by some [$coworkers](http://labs.rtgi.eu/) and me. -!/static/imgs/draft_cpan_prelimsmall.png(map of the Perl community on the web)! +<img src='/static/imgs/draft_cpan_prelimsmall.png' alt='map of the Perl community on the web' align='right'> We generated two maps (authors and modules) using the CPANTS' data. For the websites, we crawled a seed generated from the CPAN pages of the previous authors. diff --git a/_posts/2009-07-16-cpanhq-and-dependencies-graph.md b/_posts/2009-07-16-cpanhq-and-dependencies-graph.md index c21f9cb..b5263e6 100644 --- a/_posts/2009-07-16-cpanhq-and-dependencies-graph.md +++ b/_posts/2009-07-16-cpanhq-and-dependencies-graph.md @@ -8,7 +8,7 @@ CPANHQ is a new project that "aims to be a community-driven, meta-data-enhanced I believe that a good vizualisation can help to have a better understanding of datas. One of the missing thing on the actual search.cpan.org is the lack of informations about a distribution's dependencies. So my first contribution to the CPANHQ project was to add such informations. -!/static/imgs/cpanhq-dep.png(cpanhq deps)! +<img src='/static/imgs/cpanhq-dep.png' alt='cpanhq deps' align=left'> For each distributions, a graph is generated for the this distribution. For this, I use [Graph::Easy](http://search.cpan.org/perldoc?Graph::Easy) and data available from the CPANHQ database. I alsa include a simple list of the dependencies after the graph. diff --git a/_posts/2009-07-26-cpan-explorer.md b/_posts/2009-07-26-cpan-explorer.md index 10e6f7e..8fb5ab2 100644 --- a/_posts/2009-07-26-cpan-explorer.md +++ b/_posts/2009-07-26-cpan-explorer.md @@ -1,9 +1,9 @@ --- layout: post summary: In which I share an update to CPAN Explorer. -title: cpan-explorer +title: CPAN Explorer --- -We ([RTGI]"http://rtgi.fr") have been working to update the [cpan-explorer](http://cpan-explorer.org). A new version will be available this week, before YAPC::EU. Three new maps have been created, using different informations than the previous one, and you will be able to search and pinpoint the browsable maps. +We ([RTGI](http://rtgi.fr)) have been working to update the [cpan-explorer](http://cpan-explorer.org). A new version will be available this week, before YAPC::EU. Three new maps have been created, using different informations than the previous one, and you will be able to search and pinpoint the browsable maps. -!/static/imgs/authorsmap.png(authors map)! +<img src='/static/imgs/authorsmap.png' alt='authors map'> diff --git a/_posts/2009-07-28-cpan-explorer-update-and-three-new-maps.md b/_posts/2009-07-28-cpan-explorer-update-and-three-new-maps.md index c535efc..d26353c 100644 --- a/_posts/2009-07-28-cpan-explorer-update-and-three-new-maps.md +++ b/_posts/2009-07-28-cpan-explorer-update-and-three-new-maps.md @@ -1,20 +1,20 @@ --- layout: post -summary: In which -title: cpan-explorer update and three new maps +summary: In which CPAN explorer got updated. +title: CPAN Explorer update and three new maps --- The site [cpan-explorer](http://cpan-explorer.org/) have been update with three new maps for the [YAPC::EU](http://yapceurope2009.org/ye2009/). This three maps are different from the previous one. This time, instead of having a big photography of the distributions and authors on the CPAN, Task::Kensho have been used to obtain a representation of what we call the **modern Perl**. ## distributions map -!/static/imgs/moosedist.png(moose)! +<img src='/static/imgs/moosedist.png' alt='moose'> Task::Kensho acted as the seed for this map. Task::Kensho contains a list of modules recommended to do modern Perl development. So we extracted the modules that have a dependancie toward one of these modules, and create the graph with this data. ## authors map -The authors listed on this map are the one from the previous map. There is a far less authors thant the previous authors map, but it's more readable. A lot of informations are on the map : label size, node size, edge size, color of the node. +The authors listed on this map are the one from the previous map. There is a far less authors thant the previous authors map, but it's more readable. A lot of informations are on the map : label size, node size, edge size, color of the node. ## web communities map @@ -22,8 +22,8 @@ This map look a lot like the previous one, as we used nearly the same data. The ## cpan-explorer -cpan-explorer is now hosted on a wordpress, so you can leave comments or suggestions for new maps you would like to see (a focus on web development modules, tests::* module, etc ...). All the new maps are also searchable, and give you a permalink for you search ([I'm here](http://cpan-explorer.org/2009/07/28/new-web-communities-map-for-yapceu/#dist%3Dlumberjaph.net) and [here](http://cpan-explorer.org/2009/07/28/version-of-the-authors-graph-for-yapceu/#author%3Dfranck)) +CPAN Explorer is now hosted on a wordpress, so you can leave comments or suggestions for new maps you would like to see (a focus on web development modules, tests::* module, etc ...). All the new maps are also searchable, and give you a permalink for you search ([I'm here](http://cpan-explorer.org/2009/07/28/new-web-communities-map-for-yapceu/#dist%3Dlumberjaph.net) and [here](http://cpan-explorer.org/2009/07/28/version-of-the-authors-graph-for-yapceu/#author%3Dfranck)) -I will give a talk at the "YAPC::EU":http://yapceurope2009.org/ye2009/talk/2061 about this work. Also, each map have been printed, and will be given for the auction. +I will give a talk at the [YAPC::EU](http://yapceurope2009.org/ye2009/talk/2061) about this work. Also, each map have been printed, and will be given for the auction. -This work is a collective effort from all the guys at "RTGI":http://rtgi.fr/ (antonin created the template for wordpress, niko the js and the tools to extract information from the SVG for the searchable map, julian helped me to create the graphs and extract valuable informations, and I got a lot of feedback from others coworkers), thanks guys!. +This work is a collective effort from all the guys at [RTGI](http://rtgi.fr/) (antonin created the template for wordpress, niko the js and the tools to extract information from the SVG for the searchable map, julian helped me to create the graphs and extract valuable informations, and I got a lot of feedback from others coworkers), thanks guys!. diff --git a/_posts/2009-10-03-teh-batmoose-at-osdc.fr.md b/_posts/2009-10-03-teh-batmoose-at-osdc.fr.md index 0ee6434..dbaceab 100644 --- a/_posts/2009-10-03-teh-batmoose-at-osdc.fr.md +++ b/_posts/2009-10-03-teh-batmoose-at-osdc.fr.md @@ -6,6 +6,8 @@ summary: In which I share the batmoose Today I presented a talk about Moose at [OSDC.fr](http://osdc.fr). The slides are available [here](http://franck.lumberjaph.net/blog/slides/Introduction_a_Moose.pdf) +<img src='/static/imgs/batmoose_1024cut-300x225.png' alt='teh batmoose'> + And big thanks to my friend [Morgan](http://www.bwoup.com) for his illustration of the batmoose :) - + diff --git a/_posts/2010-03-07-github-explorer-a-preview.md b/_posts/2010-03-07-github-explorer-a-preview.md index 1cfc3e1..69517bb 100644 --- a/_posts/2010-03-07-github-explorer-a-preview.md +++ b/_posts/2010-03-07-github-explorer-a-preview.md @@ -1,21 +1,19 @@ --- layout: post -summary: In which I share a preview of GitHub Explorer +summary: In which I share a preview of GitHub Explorer. title: GitHub Explorer - a preview --- > You may want to see the final version here: [GitHub Explorer](/github-explorer/). -For the last weeks, I've been working on the successor of [CPAN Explorer](http://cpan-explorer.org/). This time, I've decided to create some visualizations (probably 8) of the various communities using [GitHub](http://github.com/). I'm happy with the result, and will soon start to publish the maps (statics and interactives) with some analyses. I'm publishing two previews: the Perl community and the european developers. These are not final results. The colors, fonts, and layout may change. But the structure of the graphs will be the same. All the data was collected using the [GitHub API](http://develop.github.com/). +For the last weeks, I've been working on the successor of [CPAN Explorer](http://cpan-explorer.org/). This time, I've decided to create some visualizations (probably 8) of the various communities using [GitHub](http://github.com/). I'm happy with the result, and will soon start to publish the maps (statics and interactives) with some analyses. I'm publishing two previews: the Perl community and the european developers. These are not final results. The colors, fonts, and layout may change. But the structure of the graphs will be the same. All the data was collected using the [GitHub API](http://developer.github.com/). -<a href="http://www.flickr.com/photos/franck_/4413528529/sizes/l/">!/static/imgs/github-perl-preview.png(the Perl community on github)!</a> +<a href='/static/imgs/4413528529_8d6b8dca1c_o.jpg'><img src='/static/imgs/github-perl-preview.png' alt='the Perl community on GitHub' /></a> -Each node on the graph represents a developer. When a developer "follows" another developer on github, a link between them is created. The color on the Perl community map represent the countries of the developer. One of the most visible things on this graph is that the japanese community is tighly connected and shares very little contact with the foreign developers. miyagawa obviously acts as a glue between japanese and worldwide Perl hackers. +Each node on the graph represents a developer. When a developer "follows" another developer on GitHub, a link between them is created. The color on the Perl community map represent the countries of the developer. One of the most visible things on this graph is that the japanese community is tighly connected and shares very little contact with the foreign developers. miyagawa obviously acts as a glue between japanese and worldwide Perl hackers. -<a href="http://www.flickr.com/photos/franck_/4414287310/sizes/o/in/photostream/">!static/imgs/github-europe-preview.png(European developers on github)!</a> +<a href='/static/imgs/4414287310_20094fe6bc_o.jpg'><img src='/static/imgs/github-europe-preview.png' alt='European developers on GitHub' /></a> -The second graph is a little bit more complex. It represents the European developers on github. Here the colors represent the languages used by the developers. It appears that ruby is by far the most represented language on github, as it dominates the whole map. Perl is the blue cluster at the bottom of the map, and the green snake is... Python. +The second graph is a little bit more complex. It represents the European developers on GitHub. Here the colors represent the languages used by the developers. It appears that ruby is by far the most represented language on GitHub, as it dominates the whole map. Perl is the blue cluster at the bottom of the map, and the green snake is... Python. Thanks to [bl0b](http://code.google.com/p/tinyaml/) for his suggestions :) - - diff --git a/_posts/2010-03-19-easily-create-rest-interface-with-the-dancer-1.170.md b/_posts/2010-03-19-easily-create-rest-interface-with-the-dancer-1.170.md index e5f04f7..b37f9af 100644 --- a/_posts/2010-03-19-easily-create-rest-interface-with-the-dancer-1.170.md +++ b/_posts/2010-03-19-easily-create-rest-interface-with-the-dancer-1.170.md @@ -4,9 +4,9 @@ summary: In which we see that it's easy to create REST interface with Dancer. title: Easily create REST interface with the Dancer 1.170 --- -This week, with [Alexi](http://www.sukria.net/fr/)'s help, [I've been working on](http://github.com/sukria/Dancer) to add auto-(de)serialization to Dancer's request. This features will be available in the next [Dancer](http://perldancer.org/) version, the 1.170 (which will be out before April). +This week, with [Alexi](http://www.sukria.net/fr/)'s help, [I've been working on](http://github.com/perldancer/Dancer) to add auto-(de)serialization to Dancer's request. This features will be available in the next [Dancer](http://perldancer.org/) version, the 1.170 (which will be out before April). -The basic idea was to provides to developer a simple way to access data that have been send in a serialized format, and to properly serialize the response. +The basic idea was to provides to developer a simple way to access data that have been send in a serialized format, and to properly serialize the response. At the moment, the supported serializers are : diff --git a/_posts/2010-04-19-the-dancer-ecosystem.md b/_posts/2010-04-19-the-dancer-ecosystem.md index d10d394..d201a72 100644 --- a/_posts/2010-04-19-the-dancer-ecosystem.md +++ b/_posts/2010-04-19-the-dancer-ecosystem.md @@ -34,7 +34,7 @@ The last one is for writing directly your log message via <ah href="http://searc To debug your application with Plack, you can use the awesome <a href="http://search.cpan.org/perldoc?Plack::Middleware::Debug">Plack::Middleware::Debug</a>. I've writen <a href="http://github.com/franckcuny/dancer-debug">Dancer::Debug</a> (which requires my fork of <a href="http://github.com/franckcuny/Plack-Middleware-Debug">P::M::Debug</a>), a middleware that add panels, with specific informations for Dancer applications. -<a href="http://www.flickr.com/photos/franck_/4535496880/" title="Dancer::Debug middleware by franck.cuny, on Flickr"><img src="http://farm3.static.flickr.com/2750/4535496880_37e5e68a57.jpg" width="500" height="313" alt="Dancer::Debug middleware" /></a> +<img src="/static/imgs/4535496880_37e5e68a57_z.jpg"alt="Dancer::Debug middleware" /> To activate this middleware, update your app.psgi to make it look like this: diff --git a/_posts/2010-06-13-fpw2010-summary.md b/_posts/2010-06-13-fpw2010-summary.md index 2883242..c0cedba 100644 --- a/_posts/2010-06-13-fpw2010-summary.md +++ b/_posts/2010-06-13-fpw2010-summary.md @@ -10,7 +10,7 @@ Even if Calais was not the easiest destination for every one, it was a really fu For those who missed this workshop, a short summary for you: - * had excellent discussions with [sukria](http://www.sukria.net/fr/) about the future of [Dancer](http://github.com/sukria/dancer) + * had excellent discussions with [sukria](http://www.sukria.net/fr/) about the future of [Dancer](http://github.com/perldancer/dancer) * fun facts about time zone and unicode with [maddingue](http://twitter.com/maddingue), [rgs](http://twitter.com/octoberequus) and [fperrad](http://github.com/fperrad) * interesting chat with fperrad about lua and parrot * convinced more people that Plack *is* the future for Perl Web development diff --git a/_posts/2010-06-25-presque-new_features.md b/_posts/2010-06-25-presque-new_features.md index de94d65..4d2923c 100644 --- a/_posts/2010-06-25-presque-new_features.md +++ b/_posts/2010-06-25-presque-new_features.md @@ -6,7 +6,7 @@ title: presque I've added a few new features to [presque](http://github.com/franckcuny/presque). -[presque](http://lumberjaph.net/presque-a-redis---tatsumaki-based-message-queue.html) is a persistant job queue based on [Redis](http://github.com/antirez/redis) and [Tatsumaki](http://github.com/miyagawa/Tatsumaki). +[presque](/presque-a-redis-tatsumaki-based-message-queue/) is a persistant job queue based on [Redis](http://github.com/antirez/redis) and [Tatsumaki](http://github.com/miyagawa/Tatsumaki). A short list of current features implemented: diff --git a/_posts/2010-09-17-spore.md b/_posts/2010-09-17-spore.md index 8725c98..6c60f9d 100644 --- a/_posts/2010-09-17-spore.md +++ b/_posts/2010-09-17-spore.md @@ -95,7 +95,7 @@ Middlewares are the nice part of it. By default, the core only creates a request * proxying * ... -<center>!/static/imgs/chart.png(schema)!</center> +<img src='/static/imgs/chart.png' alt='schema'> The most obvious middleware is the one that handles the format. When you load the middleware Format::JSON, it will set various headers on your request. In case of a GET method, the **Accept** header will be set to **application/json**. For a POST, the **Content-Type** will be also set. Before returning the result to the client, the content will be transformed from JSON to a Perl structure. diff --git a/_posts/2010-10-04-how-to-contribute-to-dancer.md b/_posts/2010-10-04-how-to-contribute-to-dancer.md index b35ee30..65c4262 100644 --- a/_posts/2010-10-04-how-to-contribute-to-dancer.md +++ b/_posts/2010-10-04-how-to-contribute-to-dancer.md @@ -8,7 +8,7 @@ For our development projects, we rely a lot on Github. Lately, more and more peo ## the code -The main repository is hosted [here](http://github.com/sukria/dancer). There are two main branches: +The main repository is hosted [here](http://github.com/perldancer/dancer). There are two main branches: * master * devel @@ -19,7 +19,7 @@ The devel branch is where we add new features, or improve existing features. ## contributing -First, go to [github.com/sukria/dancer](http://github.com/sukria/dancer) and click on the "fork" button. Now, here is a little tutorial on how to fetch the repository, list the local and remote branches, and track the remote devel branch. +First, go to [github.com/perldancer/dancer](http://github.com/perldancer/dancer) and click on the "fork" button. Now, here is a little tutorial on how to fetch the repository, list the local and remote branches, and track the remote devel branch. Now that you know what the purpose of each branch is, you can decide to work on master or devel (`git checkout devel` to switch branch). @@ -27,11 +27,11 @@ Now that you know what the purpose of each branch is, you can decide to work on As I've previously stated, we rely a lot on the github features and interface. So now you've written your patch. First, be sure to provide one or more tests, and to run the test suite (with `make test` or `prove -r t/`). If all the tests pass, you can send a pull request. For this, you go on your own fork on github (http://github.com/$user/dancer), and you click on the "Pull Request" button. -You can at any time see all the commits done by others that have not yet been merged into one of our branches at [this url](http://github.com/sukria/Dancer/forkqueue). +You can at any time see all the commits done by others that have not yet been merged into one of our branches at [this url](http://github.com/perldancer/Dancer/forkqueue). ## reporting and/or fixing bugs -We prefer to use the github issue tracker instead of RT. So if you want to report a bug, go [there](http://github.com/sukria/dancer/issues). +We prefer to use the github issue tracker instead of RT. So if you want to report a bug, go [there](http://github.com/perldancer/dancer/issues). If your commit fixes a bug reported there, please add in your commit message something like 'fixing GH #xxx" where xxx is the bug id. diff --git a/_posts/2010-10-12-osdcfr.md b/_posts/2010-10-12-osdcfr.md index f91336e..af36656 100644 --- a/_posts/2010-10-12-osdcfr.md +++ b/_posts/2010-10-12-osdcfr.md @@ -8,7 +8,7 @@ This weekend I went to the second edition of the OSDC.fr conference. This confer The first day of the conference, we had two excellents talk about Git. The first one by [mojombo](http://github.com/mojombo), about [advanced git usages](http://git-tips.heroku.com/#1). I've managed to get him to sign my copy of the [GitHub poster](http://lumberjaph.net/graph/2010/03/25/github-explorer.html). The second one by BooK was about his module [Git::Repository](http://search.cpan.org/perldoc?Git::Repository) (which I use for [jitterbug](http://github.com/franckcuny/jitterbug)). He show us how he used git to graph his familly tree. -<center><img width="600" height="500" class="img_center" src="http://farm5.static.flickr.com/4070/5074738888_a6c2481b03_b.jpg" alt="github poster" /></center> +<img src="/static/imgs/github-sig-small.jpg" alt="github poster" /> Germain did an [introduction to Riak](http://www.slideshare.net/franckcuny/riak-a-file-system-for-internet), and [Julian](http://twitter.com/flngr) did a talk about [Gephi](http://gephi.org/), about how it relies on the netbeans platform, and why a tool to visualize graphs is useful. diff --git a/_posts/2010-10-25-perl-moderne.md b/_posts/2010-10-25-perl-moderne.md index a9f5ef1..36343f9 100644 --- a/_posts/2010-10-25-perl-moderne.md +++ b/_posts/2010-10-25-perl-moderne.md @@ -19,7 +19,7 @@ Enfin, la dernière partie est celle consacrée au web, avec la présentation de Par ailleurs, si après la lecture de cet ouvrage il vous vient à l’idée de vouloir récupérer du contenu sur des pages web à l’aide d’expression régulières, il est fort probable que vous ayez lu ce livre à l’envers, ou c’est par pur goût de la provocation envers les auteurs. -A, et un point négatif, me diriez vous ? Bien sûr que j’en ai un. A mon grand regret, nulle part dans l’ouvrage il n’est fait référence à [Dancer](http://github.com/sukria/dancer). Tant pis ! +A, et un point négatif, me diriez vous ? Bien sûr que j’en ai un. A mon grand regret, nulle part dans l’ouvrage il n’est fait référence à [Dancer](http://github.com/perldancer/dancer). Tant pis ! Dans l’ensemble c’est un bon livre pour qui veut découvrir Perl en 2010. Tous les outils que l’on s’attend à utiliser au quotidien sont présentés. L’organisation du livre, et le fait d’avoir de nombreux exemples, seront pratiques pour les débutants. Je pense en commander quelques exemplaires pour le travail, afin de le mettre à disposition de nos (futurs) stagiaires. diff --git a/_posts/2010-11-22-vagrant-rocks.md b/_posts/2010-11-22-vagrant-rocks.md index 9e66603..3d9da05 100644 --- a/_posts/2010-11-22-vagrant-rocks.md +++ b/_posts/2010-11-22-vagrant-rocks.md @@ -8,7 +8,7 @@ summary: In which I share my enthusiasm for Vagrant I've been toying with [vagrant](http://vagrantup.com/) lately, and it **really rocks**. You should definitly give it a try. If you're only looking for some resources to get started with it, go there: - * [introduction](http://vagrantup.com/docs/index.html) + * [introduction](http://docs.vagrantup.com/v2/why-vagrant/index.html) * [google group](http://groups.google.com/group/vagrant-up) ## What is Vagrant @@ -23,7 +23,7 @@ I won't go into the details to describe Chef and VirtualBox, but here is a quick ## The basic -To install vagrant, you'll need ruby and virtualbox. You have the basic instructions detailed [here](http://vagrantup.com/docs/getting-started/index.html). This will explain how to install vagrant and how to fetch a **base** image. +To install vagrant, you'll need ruby and virtualbox. You have the basic instructions detailed [here](http://docs.vagrantup.com/v2/getting-started/index.html). This will explain how to install vagrant and how to fetch a **base** image. ### Creating a first project @@ -49,12 +49,12 @@ end These instructions will: * tell vagrant to use the image named **base** (a lucid32 image by default) - * use chef in **solo** mode + * use chef in **solo** mode * the recipes will be in a directory named **cookbooks** * the main recipe will be named **vagrant_main** * forward local HTTP port 4000 to 5000 on the VM -### My recipes +### My recipes Now we need to create or use some recipes. First we create our **cookbooks** directory: diff --git a/_posts/2011-02-20-psgichrome.md b/_posts/2011-02-20-psgichrome.md index bf8338a..708839a 100644 --- a/_posts/2011-02-20-psgichrome.md +++ b/_posts/2011-02-20-psgichrome.md @@ -44,7 +44,7 @@ my $app = sub { }); return [ 200, [ 'Content-Type' => 'text/html' ], [$content] ]; }; - + builder { enable "ConsoleLogger"; $app; @@ -57,7 +57,7 @@ point your browser to http://localhost:5000, activate the javascript console. If this works correctly, you should have a smiliar output in your console: -<a href="http://f.lumberjaph.net/blog/misc/plack_chrome.png"><img class="img_center" src="http://f.lumberjaph.net/blog/misc/plack_chrome.png" /></a> +<img src="/static/imgs/plack_chrome.png" /> ## Dancer @@ -68,7 +68,7 @@ First, you need to install [Dancer::Logger::PSGI](http://search.cpan.org/perldoc {% highlight yaml %} logger: "PSGI" plack_middlewares: - - + - - ConsoleLogger {% endhighlight %} diff --git a/_posts/2011-03-06-how_to_use_github_effectively_for_your_project.md b/_posts/2011-03-06-how_to_use_github_effectively_for_your_project.md index 53547b6..08872e5 100644 --- a/_posts/2011-03-06-how_to_use_github_effectively_for_your_project.md +++ b/_posts/2011-03-06-how_to_use_github_effectively_for_your_project.md @@ -10,7 +10,7 @@ summary: In which we look at how we can use GitHub effectively for your project. ## code review -<a href="https://github.com/sukria/dancer">Dancer</a>'s development goes fast. We do our best to ship often, we do a lot of refactoring, and we listen our users. This means processing pull request and issues as fast as possible. +<a href="https://github.com/perldancer/dancer">Dancer</a>'s development goes fast. We do our best to ship often, we do a lot of refactoring, and we listen our users. This means processing pull request and issues as fast as possible. ## pull request @@ -26,7 +26,7 @@ As the work consists to read the code and comment, it's quiete easy to handle tw We don't use "RT":http://bestpractical.com/rt/ to manage our issues. It's not that RT is bad or that we don't like it, it's just that GitHub's issues are more integrated with our workflow. GitHub's issues are really simple (one can even say naive), but most of the time it's ok for our usage. We don't need advanced features like "track how much time you've spend on this ticket" (even if I do track my time spent on Dancer, using [orgmode](http://orgmode.org/manual/Clocking-commands.html#Clocking-commands)). -One of the nice feature of GitHub's issues, is that you can close them with a commit. If the commit's message looks like 'closes GH-123', the issue 123 will be closed, with a link to the commit in the comment ([take a look](https://github.com/sukria/Dancer/issues/249)). I find this feature really useful, since when refering to a closed issue, you can find the commit inside the ticket. +One of the nice feature of GitHub's issues, is that you can close them with a commit. If the commit's message looks like 'closes GH-123', the issue 123 will be closed, with a link to the commit in the comment ([take a look](https://github.com/perldancer/Dancer/issues/249)). I find this feature really useful, since when refering to a closed issue, you can find the commit inside the ticket. Once or twice a week, we try to proceed a **triage**, where we go through the issues, and tag them. @@ -42,11 +42,11 @@ An issue doesn't need to be about a bug, it could be: Another nice feature is the possibility to comment the code. Most of the time you'll do it while reviewing a pull request. But a user can also comment on something. -Sometimes we push a branch that need some feedback, and "a discussion will be started":https://github.com/sukria/Dancer/commit/d8e79e0d63d0e1b0e05fd36f9e31c378678fccc3. +Sometimes we push a branch that need some feedback, and "a discussion will be started":https://github.com/perldancer/Dancer/commit/d8e79e0d63d0e1b0e05fd36f9e31c378678fccc3. ## comparing branches -You can easily diff two branches. With [this url](https://github.com/sukria/Dancer/compare/master...devel) you can do a quick diff of the changes between master and devel, see the list of commits, and which files have changed. +You can easily diff two branches. With [this url](https://github.com/perldancer/Dancer/compare/master...devel) you can do a quick diff of the changes between master and devel, see the list of commits, and which files have changed. This is usefull when you want to have an overview of the work. diff --git a/_posts/2011-05-08-french_perl_workshop.md b/_posts/2011-05-08-french_perl_workshop.md index 2d27494..bafe2be 100644 --- a/_posts/2011-05-08-french_perl_workshop.md +++ b/_posts/2011-05-08-french_perl_workshop.md @@ -6,7 +6,7 @@ summary: In which I remind you of the French Perl Worksphop. The call for paper for the [French Perl Workshop](http://journeesperl.fr/fpw2011/) is open. This event will be held the 24th and 25th of June in Paris. As always, this is a free conference. -<img align="left" src="/images/affiche_fpw11.jpg" /> +<img align="left" src="/static/imgs/affiche_fpw11.jpg" /> ## Where diff --git a/_posts/2013-01-28-let-s-talk-about-graphite.md b/_posts/2013-01-28-let-s-talk-about-graphite.md index 2722123..f15e65f 100644 --- a/_posts/2013-01-28-let-s-talk-about-graphite.md +++ b/_posts/2013-01-28-let-s-talk-about-graphite.md @@ -4,7 +4,7 @@ summary: In which I share my experience with Graphite title: Let's talk about Graphite --- -As I've already mentionned in a [previous post](http://lumberjaph.net/devops/2013/01/10/carbons-manhole.html), at [$work](http://saymedia.com) we are currently deploying Graphite and the usual suspects. +As I've already mentionned in a [previous post](/carbons-manhole/), at [$work](http://saymedia.com) we are currently deploying Graphite and the usual suspects. Finding articles on how to install all these tools is easy, there's plenty of them. But what's *really* hard to find, are stories on *how to use them*: what's collected, how, why, how do you organize your metrics, do you rewrite them, etc. @@ -97,6 +97,6 @@ We have some other complains about Graphite. Even after reading the [rationals] ## Meetup -We've a huge basement at work that can be used to host meetup. There's already a few meetup in the San Francisco about "devops" stuff ([Metrics Meetup](http://www.meetup.com/San-Francisco-Metrics-Meetup/events/98875712/), [SF DevOps](http://www.meetup.com/San-Francisco-DevOps/), etc), but maybe there's room for another one with a different format. +We've a huge basement at work that can be used to host meetup. There's already a few meetup in the San Francisco about "devops" stuff ([Metrics Meetup](http://www.meetup.com/San-Francisco-Metrics-Meetup/events/98875712/), [SF DevOps](http://www.meetup.com/San-Francisco-DevOps/), etc), but maybe there's room for another one with a different format. What I would like, is a kind of forum, where a topic is picked, and people share their *experiences* (the bad, the good and the ugly), not how to configure or deploy something. And there's a lot of topics where I've questions: deployment (this will be the topic of my next entry I think), monitoring, alerting, post-mortem, etc. If you're interested, send me an email, or drop a comment on this post. diff --git a/_posts/2013-07-28-patch.pm-report.md b/_posts/2013-07-28-patch.pm-report.md index f29503a..216ceef 100644 --- a/_posts/2013-07-28-patch.pm-report.md +++ b/_posts/2013-07-28-patch.pm-report.md @@ -4,7 +4,7 @@ title: Patch.pm - report summary: In which I summarize my activity during the first patch.pm --- -This week-end I participated to [patch.pm](http://patch.pm/p0), the first version of a new hackathon organized by the Mongueurs. Sadly (or maybe not) I was not physically with my fellow mongueurs to work on code, and did it remotely. +This week-end I participated to [patch.pm](http://patch.pm/p0/), the first version of a new hackathon organized by the Mongueurs. Sadly (or maybe not) I was not physically with my fellow mongueurs to work on code, and did it remotely. My goal for this two days was to get some work done on [Dancer2](https://github.com/PerlDancer/Dancer2): code review, fixes, submit bugs, and get some work done on the core. |