From: Erik Edrosa <erik.edrosa@gmail.com>
To: Amirouche Boubekki <amirouche@hypermove.net>,
Guile User <guile-user@gnu.org>
Cc: guile-user <guile-user-bounces+amirouche=hypermove.net@gnu.org>
Subject: Re: Lessons learned building a small blog engine
Date: Tue, 10 Oct 2017 22:22:24 -0400 [thread overview]
Message-ID: <80fb0173-3f20-36aa-8d63-d6d19c2d72b7@gmail.com> (raw)
In-Reply-To: <7d34fc6c4173012f3d8e1127816bd1f5@hypermove.net>
On 10/09/2017 03:17 PM, Amirouche Boubekki wrote:
> On 2017-10-09 21:14, Amirouche Boubekki wrote:
>> On 2017-10-09 13:36, Amirouche Boubekki wrote:
>>> Héllo all,
>>>
>>>
>>> Last week end I tried to build a blog engine.
>>>
>>> git clone https://github.com/a-guile-mind/presence
>>>
>>
>> Now, accept to following challenge:
>>
>> Try to add an article on http://presence.hyperdev.fr/
>>
>> Tips: For that you need to read the code.
>>
>> Happy hacking!
>
> Another tips: You need to workaround at least two bugs.
>
> Please post a mail on the mailing list if you succeed.
>
Managed to add an article. The key is to look at the routes in the
scheme code and then sort of follow it. The bugs prevent you from easily
progressing but you can still proceed if you follow the routes. Thank
you Amirouche for the fun little challenge.
- Erik (OrangeShark)
prev parent reply other threads:[~2017-10-11 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 11:36 Lessons learned building a small blog engine Amirouche Boubekki
2017-10-09 19:14 ` Amirouche Boubekki
2017-10-09 19:17 ` Amirouche Boubekki
2017-10-09 21:24 ` Arne Babenhauserheide
2017-10-11 2:22 ` Erik Edrosa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80fb0173-3f20-36aa-8d63-d6d19c2d72b7@gmail.com \
--to=erik.edrosa@gmail.com \
--cc=amirouche@hypermove.net \
--cc=guile-user-bounces+amirouche=hypermove.net@gnu.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).