Ticket #17 (closed enhancement: worksforme)
Downloadable Wiki-in-a-box
| Reported by: | Randy Selzler <RSelzler@…> | Owned by: | sheep |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | Hatta Wiki | Version: | |
| Keywords: | Cc: |
Description
A downloadable (or clonable) standard Wiki-in-a-box (or boxes)
would make it easier to get started and to provide accurate
bug reports.
The contents should include ready make examples
for each basic feature of the Wiki.
It should unpack into a small, but functional Wiki tree
(smiley collection, logo, Home, Menu, style.css, Locked,
Category, Markup help, sandbox, orphan, wanted, upload,
download, etc.) and hatta.conf and hatta.wsgi and ???
The current zip file is a good start, but is missing the
smiley collection and ready made example pages.
The standard-box would be a good reference for bug reports.
For example, problems could be reported relative to it and...
1) software versions and combinations
2) configuration changes
3) page content changes
For example, I'm currently attempting to document 2 bugs that
involves combinations of hatta.conf, smiley icons and pages
that reference them. It would be easier to document it relative
to a standard configuration... if icon_pages=Icons and
Icons page exists and smiley icons exist and everything
has been committed to Mercurial, then the page
content is not rendered or the Menu is not rendered or both...
--version command line option is needed.
--verbose might be useful
Would it be possible to print (or render a page) that
describes exactly which modules, versions and locations
were actually being loaded and used by Hatta?
Given all the interactions between Virtualenv, PYTHONPATH,
PYTHONHOME, PATH, etc. its nearly impossible for a newbie
like me to determine what is actually being used.
Just an idea... adjust as desired.

You mean something like this? http://download.hatta-wiki.org/hatta-devel.zip (read the instructions inside). I suppose it's a better idea than Hacking.
Yes, something like that.
In hind sight, a repository might be more appropriate than
a zip file, because it could track the "standard" hackers box,
which will no doubt evolve with time.
I wouldn't dismiss the Hacking page too quickly.
Its hard to predict which would attract more attention
and support.
It looks like the essential modules are there, but as a newbie
I'll have to think about how to invoke/install/activate them.
I need to explore an digest the zip contents more.
I'd populate the docs directory with a small set of
baseline pages (Home, Menu, Locked, ...) and Icons and
javascript, etc. ... and hatta.conf, hatta.wsgi, ...
You've encourage me to boldly hack the Hatta site pages,
if I see a way to improve them. Improvements are often
subjective and risk offending someone else, but I'll try.
You are the wizard behind this project and my skin is relatively
tough. Your comments and criticism are welcome and in fact
encouraged, because that's how I'll learn.