summaryrefslogtreecommitdiff
path: root/posts/2009-04-27-a-simple-feed-aggregator-with-modern-perl-part-1.md
diff options
context:
space:
mode:
authorFranck Cuny <franck.cuny@gmail.com>2016-08-13 09:17:02 -0700
committerFranck Cuny <franck.cuny@gmail.com>2016-08-13 09:17:02 -0700
commit68fe46bcaa439f607a11db1a20c7ab01bbe6af2e (patch)
treee573cb89fc7428e85e7f346d40b86fba6f099aeb /posts/2009-04-27-a-simple-feed-aggregator-with-modern-perl-part-1.md
parentimage for jitterbug article. (diff)
downloadlumberjaph-68fe46bcaa439f607a11db1a20c7ab01bbe6af2e.tar.gz
more clean up.master
Diffstat (limited to 'posts/2009-04-27-a-simple-feed-aggregator-with-modern-perl-part-1.md')
-rw-r--r--posts/2009-04-27-a-simple-feed-aggregator-with-modern-perl-part-1.md4
1 files changed, 0 insertions, 4 deletions
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 1c58514..66fcb5d 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
@@ -7,8 +7,6 @@ Class\*
- 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 git server](http://git.lumberjaph.net/) 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.
### The database schema
@@ -128,6 +126,4 @@ This script will deploy for you the schema (you need to create the database firs
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.
-[The code is available on my git server](http://git.lumberjaph.net/p5-ironman-mymodel.git/).
-
> 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.