From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: org to static site? Date: Tue, 05 Dec 2017 13:30:39 +0100 Message-ID: <87o9nd73ww.fsf@gmx.us> References: <86fu8w5oyf.fsf@gmail.com> <87fu8unqut.fsf@hyperbola.info> <86wp25kfgb.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57636) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMCNC-00042O-7l for emacs-orgmode@gnu.org; Tue, 05 Dec 2017 07:30:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eMCN9-0003GO-5G for emacs-orgmode@gnu.org; Tue, 05 Dec 2017 07:30:54 -0500 Received: from [195.159.176.226] (port=36206 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eMCN8-0003G7-UH for emacs-orgmode@gnu.org; Tue, 05 Dec 2017 07:30:51 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1eMCMz-0001aK-1O for emacs-orgmode@gnu.org; Tue, 05 Dec 2017 13:30:41 +0100 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: emacs-orgmode@gnu.org myglc2@gmail.com writes: > 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. I am happy that you found a method that works for you. As a contrasting point, I don’t see why you couldn’t do that with ox-publish.el in addition to maybe Make. Based on your description, I’d copy source files using org-publish-attachment to a publish dir and compiled files to the same dir via different projects in org-publish-project-alist. I don’t know how github works re CI, but with Gitlab you’d then mark the publish folder as an artifact folder that would be published. For each commit you’d then have a zip and a website with source and compiled data / code. If you have any suggestions on how to improve ox-publish to better suit please share them. > 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. For publishing something to the web I’d personally use CI or just cp. You could use git using :publishing-function or maybe :publishing-directory if tramp somehow supports git. Rasmus -- Tack, ni svenska vakttorn. Med plutonium tvingar vi dansken på knä!