On 4/19/2013 8:56 AM, Ville M. Vainio wrote:
I get the feeling that Pelican would provide a "less custom" approach,
and it seems to support rst out of the box.
Have you looked into Pelican and found it to be inappropriate to your
needs? Right now, I'm thinking creating a Leo outline that integrates
with pelican and github pages could be the right approach.
I just prefer tighter control. Pelican seems a bit too "heavy" for what
I do with my sites, but it could be perfect for this sort of thing!
Pelican:
http://docs.getpelican.com/en/3.1.1/
Reg. Heroku vs GH-pages - Heroku free tier has the problem of having
few secs "spin up" delay unless it gets hits regularly, while IIUC gh
pages are serving instantly at all times.
That may be true for larger apps, i.e. ones with databases... I've never
once noticed it with my blog, and that has extremely humble traffic. GH
pages is certainly viable and easy to use, though. It's a good choice. :)
-->Jake
On Fri, Apr 19, 2013 at 3:28 PM, Jacob Peck <[email protected]
<mailto:[email protected]>> wrote:
My blog, at http://blog.suspended-chord.info/, is hosted with
Heroku's free hosting tier. It runs on a modified version of toto
(official: http://cloudhead.io/toto, my version:
https://github.com/gatesphere/toto), which is a ruby-based static
site generator. All articles are simple markdown files (which was
actually the reason behind my markdown_support branch -- I wanted
to blog in Leo), and you publish them by simply pushing a commit
to Heroku. As an added twist, all resources/downloads/source code
snippets are stored on github, meaning my blog is completely
hosted in the cloud, for free.
I'm working on making a nicer version of a homebrew python static
site generator that I used for my main webpages and a few other
projects. It's essentially the same idea, with markdown-based
articles, but I much prefer the jinja2 template engine that I'm
using with it.
Anyway, it's a fun little system. I could totally set one up and
hand out git credentials if someone wants to buy a domain name.
Next week sometime I should be able to swing it, if people want to
go this route.
:)
-->Jake
On 4/19/2013 1:26 AM, Ville M. Vainio wrote:
Where do you host the blog?
Can you compare your system e.g. with using Jekyll and GitHub pages?
My experience is that Wordpress and Blogger suck for technical
blogs (we want to do version control etc), and Jekyll and GH
pages could be one option for this.
Aside from hosting, one technical comms problem we need to solve
is how to show leo tree snippets in a readable fashion (optimally
with syntax highlight), and make it convenient to do (so everyone
can stick to that convention, and/or we can integrate support for
that in the blog engine)
On Fri, Apr 19, 2013 at 6:02 AM, gatesphere <[email protected]
<mailto:[email protected]>> wrote:
+1
I think this is a great idea.
As a side note, my blog is maintained completely by Leo --
blog engine code and all!
-->Jake
On 4/18/2013 10:13 PM, HaveF wrote:
+1
do better attach a mini leo file when introduce some tips of
leo?
And maybe the posts of blog should be labeled with level of
difficulties?
On Fri, Apr 19, 2013 at 4:53 AM, Kent Tenney
<[email protected] <mailto:[email protected]>> wrote:
+1
All it needs is someone to create it.
I'd expect it should be Edward, unless in the spirit of
delegation someone steps up to be the 'Keeper of the
LeoBlog'
Then, either issue permissions, or agree that submissions
go through the Keeper.
On Thu, Apr 18, 2013 at 3:26 PM, Matt Wilkie
<[email protected] <mailto:[email protected]>> wrote:
> +1
>
>
> On Thu, Apr 18, 2013 at 1:01 PM, Ville M. Vainio
<[email protected] <mailto:[email protected]>> wrote:
>>
>> How about we set up a blog dedicated to cool things
you can do with Leo?
>>
>> We could take turns advertising various cool hacks
that are there, either
>> shorter or longer articles with screenshots etc.
>>
>> --
>> You received this message because you are subscribed
to the Google Groups
>> "leo-editor" group.
>> To unsubscribe from this group and stop receiving
emails from it, send an
>> email to [email protected]
<mailto:leo-editor%[email protected]>.
>> To post to this group, send email to
[email protected]
<mailto:[email protected]>.
>> Visit this group at
http://groups.google.com/group/leo-editor?hl=en.
>> For more options, visit
https://groups.google.com/groups/opt_out.
>>
>>
>
>
> --
> You received this message because you are subscribed
to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving
emails from it, send an
> email to [email protected]
<mailto:leo-editor%[email protected]>.
> To post to this group, send email to
[email protected]
<mailto:[email protected]>.
> Visit this group at
http://groups.google.com/group/leo-editor?hl=en.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>
--
You received this message because you are subscribed to
the Google Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to
[email protected]
<mailto:leo-editor%[email protected]>.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
Visit this group at
http://groups.google.com/group/leo-editor?hl=en.
For more options, visit
https://groups.google.com/groups/opt_out.
--
--
Sincerely,
HaveF
--
You received this message because you are subscribed to the
Google Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to
[email protected]
<mailto:[email protected]>.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
Visit this group at
http://groups.google.com/group/leo-editor?hl=en.
For more options, visit
https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the
Google Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to [email protected]
<mailto:leo-editor%[email protected]>.
To post to this group, send email to
[email protected] <mailto:[email protected]>.
Visit this group at
http://groups.google.com/group/leo-editor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the
Google Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/leo-editor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:leo-editor%[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/leo-editor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
