RE: No ...blog/html/index.html
50 views
Skip to first unread message
Vlad Riscutia
Oct 21, 2013, 10:04:50 AM10/21/13
to tinker...@googlegroups.com
Are you by any chance trying to build a blog with no posts? The index.html is generated during build by aggregating the latest 10 posts.
From: David Carmean
Sent: 10/20/2013 10:19 PM
To: tinker...@googlegroups.com
Subject: Re: No ...blog/html/index.html
FWIW, for now I've hacked my way around this by creating a symlink and monkey-patching tinkerer.master_doc in conf.py:
index.rst -> master.rst
and import tinkerer
import tinkerer.paths
+tinkerer.master_doc = 'index'
import tinkerer.paths
+tinkerer.master_doc = 'index'
On Sunday, October 20, 2013 6:48:54 PM UTC-7, David Carmean wrote:
Hi,
Just found the project, and I see an old "issue" that might be related but .. either the patch wasn't merged or this is something different.
When I call 'tinker --build', I get an index.html in the project root, which tries to auto-refresh to .blog/html/index.html. However,
the second index.html does not exist. Instead, I have a "master.html" which seems to have the content that "index.html" should but .. it's own "home" link is broken because it tries to go to 'index.html'.
So far, searching and grepping haven't led me to a solution. Some version info, including extras that may(?) be interfering (?)
Tinkerer version 1.2.1
readthedocs-sphinx-ext==0.2.0
Sphinx==1.1.3
sphinx-argparse==0.1.3
sphinx-better-theme==0.13
sphinx-bootstrap-theme==0.3.2
sphinxcontrib-epydoc==0.6
sphinxcontrib-fancybox==0.3.2
sphinxcontrib-fulltoc==1.0
sphinxcontrib-inheritance==0.5
sphinxcontrib-programoutput==0.8
sphinxcontrib-programscreenshot==0.0.5
sphinxcontrib-rawfiles==0.1.1
sphinxcontrib-sqltable==1.0
sphinxcontrib-taglist==0.2
sphinx-http-domain==0.2
sphinxtheme-simple==0.1
Jinja2==2.7.1
MarkupSafe==0.18
Pygments==1.6
reportlab==2.7
rst2pdf==0.93.dev
Python 2.7.5
( FWIIW I found this project when I was looking at OctoPress and thinking to myself "Ruby.. ewww!" :)
You received this message because you are subscribed to the Google Groups "tinkerer-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tinkerer-dev...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
David Carmean
Oct 21, 2013, 10:36:29 AM10/21/13
to tinker...@googlegroups.com
Yes, I am. Seems like a reasonable way to start a new blog when I've had nothing to say yet :)
Vlad Riscutia
Oct 21, 2013, 10:52:32 AM10/21/13
to tinker...@googlegroups.com
Well, as soon as you have something to say, the issue will go away :)
Yes, I am. Seems like a reasonable way to start a new blog when I've had nothing to say yet :)
On Monday, October 21, 2013 7:04:50 AM UTC-7, vladris wrote:
Are you by any chance trying to build a blog with no posts? The index.html is generated during build by aggregating the latest 10 posts.
FWIW, for now I've hacked my way around this by creating a symlink and monkey-patching tinkerer.master_doc in conf.py:
index.rst -> master.rstand
import tinkerer
import tinkerer.paths
+tinkerer.master_doc = 'index'
David Carmean
Oct 21, 2013, 7:15:35 PM10/21/13
to tinker...@googlegroups.com
In all seriousness, what is your model for starting a new blog site from scratch?
If you 'tinker --build' the pages and commit/upload them (e.g. to gh-pages), the default
index.html does try to send you to the "real" index.html. Does your "domain model", so to speak,
actually not yet have the use case where there are [0..9] posts? What if all I have for now are "pages"?
I'm willing to write some test cases to illustrate what I mean....
Vlad Riscutia
Oct 21, 2013, 8:33:38 PM10/21/13
to tinker...@googlegroups.com
Expected usage is to write one post before building/publishing. In general, users tend to have something they want to write when they start a blog. I understand your scenario, though it might not be that common.
Thank you,
Vlad
Thank you,
Vlad
Yarko Tymciurak
Oct 21, 2013, 8:48:15 PM10/21/13
to tinker...@googlegroups.com
I think David _is_ writing one post: a page-type (none of "post" type) - and there-in lies the confusion:
The assumption that a valid site _must_ have one blog-post style component of content before tinker successfully renders.
David wants to have a non-blog site, generated by tinkerer.
David: you can also just use sphinx directly to do this (and even to post blog posts, if you like - nothing preventing that; or, just link to tinker blog-only site from within a sphinx shell). For an example, see ericholscher.com (Eric is behind readthedocs.org, which hosts sphinx documentation).
Cheers,
Yarko
On Mon, Oct 21, 2013 at 7:33 PM, Vlad Riscutia <riscut...@gmail.com> wrote:
Expected usage is to write one post before building/publishing. In general, users tend to have something they want to write when they start a blog. I understand your scenario, though it might not be that common.
Thank you,
Vlad
--In all seriousness, what is your model for starting a new blog site from scratch?If you 'tinker --build' the pages and commit/upload them (e.g. to gh-pages), the defaultindex.html does try to send you to the "real" index.html. Does your "domain model", so to speak,actually not yet have the use case where there are [0..9] posts? What if all I have for now are "pages"?I'm willing to write some test cases to illustrate what I mean....
On Monday, October 21, 2013 7:52:32 AM UTC-7, vladris wrote:Well, as soon as you have something to say, the issue will go away :)
You received this message because you are subscribed to the Google Groups "tinkerer-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tinkerer-dev...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Reply all
Reply to author
Forward
0 new messages