From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2@gmail.com Subject: Re: org to static site? Date: Fri, 01 Dec 2017 21:53:56 -0500 Message-ID: <86wp25kfgb.fsf@gmail.com> References: <86fu8w5oyf.fsf@gmail.com> <87fu8unqut.fsf@hyperbola.info> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48681) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eKxwI-000666-Qz for emacs-orgmode@gnu.org; Fri, 01 Dec 2017 21:54:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eKxwF-0001rK-PK for emacs-orgmode@gnu.org; Fri, 01 Dec 2017 21:54:02 -0500 Received: from mail-qk0-x22a.google.com ([2607:f8b0:400d:c09::22a]:38166) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eKxwF-0001rG-KA for emacs-orgmode@gnu.org; Fri, 01 Dec 2017 21:53:59 -0500 Received: by mail-qk0-x22a.google.com with SMTP id z203so15590266qkb.5 for ; Fri, 01 Dec 2017 18:53:59 -0800 (PST) In-Reply-To: <87fu8unqut.fsf@hyperbola.info> (Adonay Felipe Nogueira's message of "Fri, 01 Dec 2017 18:19:22 -0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Adonay Felipe Nogueira Cc: emacs-orgmode@gnu.org On 12/01/2017 at 18:19 Adonay Felipe Nogueira writes: > The best approach for me is also to use something such as org-publish, > and a simple static site server such as GNU Serveez. Have you used org-publish in earnest? I settled on the approach used in https://github.com/myglc2/emacsite only after trying out org-publish extensively. I needed source and generated content to sit together in the working tree of complex multi-level reproducible research projects and to be transparently revision controlled and hosted on the organization's Github Entreprise server. After studying both approaches I found the emacsite approach to work better than org-publish. Just to be clear, emacsite does not require GitHub. You can equally well serve the site from the development tree, or you can publish by doing git push to non bare git repos hosted on web servers. In this way emacsite effectively automates site publishing using make and git which I found to be more reliable than org-publish. I also needed to be able to easily preview live results generated on HPC development servers in order to share work in progress with colleges. emacsite supports this natively. A nice lightweight emacs-only way to serve this work is https://github.com/skeeto/emacs-http-server. -George