Hi Eric,

still trying to figure out whats wrong with my set-up. Did you had time to look intio it.

It seems somehow elnode does not play well anymore with the current version of ehtml.

Or something like this.

I can access elnodes standard services and I can create new services like described in the elnode wiki.

However, following the README of ehtml. I receive the early posted error message. This is not an emacs-based error or any sort of crash. It seems to be something which is "well" handled by elnodes error catching.

Would be glad if you could give us some advice how to deal with that or how to test further. We are in the middle of setting up a groupware wiki. Two of us are org-mode users and the others do not really care what markup-language that might have to use. Thus, it gives us the comfort to stick with org-mode and we only have to decide to go the ehtml/emacs way or the gollum/org-ruby way. Even more luckily this is not a decision forever, since the files remain to be native org-files on both systems, I believe we could switch at anytime.

This is again a nice example of the pure text based org-mode paradigm.

Thanks

Torsten

On 7 October 2013 17:02, Torsten Wagner <torsten.wagner@gmail.com> wrote:

Hi Eric,

thanks for the email. I will give org-ehtml a try. Do you still actively maintain it. We would rely rather heavily on it ( a group of about 10 people) and I would be happy to know that I do not ride a dead horse. On the other hand you get a bunch of beta-testers ;)

Could you agree with the following comparison:

* gollum
- standalone application, based on git and org-ruby.
- can use different makeup-languages
- can be integrated in a larger environment (read something about using Apache Webserver)
- enables the creation and editing of pages via webbrowser (a minimal org-mode editor is available)
- basic settings of the theme (top, footer, sidebar).

* org-ehtml
- part of org-mode requires emacs and elnode
- makes use of the new exporter
- ...

... because I tried to give it a test but it did not work out.

I tried a test instance via the following commands (and its outputs)

(ert "org-ehtml")
->
Selector: "org-ehtml"
Passed: 0
Failed: 0
Total: 0/0

Started at: 2013-10-07 16:44:00+0200
Finished.
Finished at: 2013-10-07 16:44:00+0200

(setq org-ehtml-docroot "/home/torsten/test-wiki/")
->
"/home/torsten/test-wiki/"

(elnode-start 'org-ehtml-handler :port 8888)
->
((8888 . #<process *elnode-webserver-proc*>))

When I start it according to the README, all I get when calling http://localhost:8888/simple.org is:
<h1>Server error</h1>
No errors are given in any log-buffer I could find.
Not sure where the problem appears. A test of elnode according to the elnode README worked out ok
(defun my-test-handler (httpcon)
  "Demonstration function"
  (elnode-http-start httpcon 200 '("Content-type" . "text/html"))
  (elnode-http-return httpcon "<html><b>HELLO!</b></html>"))

(elnode-start 'my-test-handler :port 8010 :host "localhost")
Might it be, that the elnode API changed and that the handler function need some rewrite?
All the best
Torsten
On 4 October 2013 16:03, Eric Schulte <schulte.eric@gmail.com> wrote:

Check out org-ehtml. See the original announcement [1] and the repo on
github [2]. It might need some attention as the Org-mode export API is
constantly in flux, but it does work to allow editing of Org-mode pages
through a web page.

Cheers,

Footnotes:
[1] http://thread.gmane.org/gmane.emacs.orgmode/58773/focus=58884

[2] https://github.com/eschulte/org-ehtml

--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D