Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Is there an Apache plugin which will translate .adoc to HTML on the fly and serve the rendered result, rather than the source markup? I've browsed the archives and web search without turning up obvious matches. The use case is to reflect an internal gitlab repository through Apache, conceptually similar to github.io, and rendering README.adoc in the webserver would be very helpful for this.
Of course individuals can install something like Asciidoctor.js Preview on the client side, but a lot of our users will be marketing people and lawyers who won't be up for that sort of thing. Jon |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Administrator
|
Jon, I'm not aware of one. In the case of GitLab, I know that it already supports rendering .adoc files using github/markup (which, in turn, uses Asciidoctor). For something more low-level, I imagine the specification effort will help with this as we could see a C implementation out of it. That's going to integrate a lot better with Apache httpd. Integrations will be something the working group will help advocate for and promote. Best Regards, -Dan On Fri, Jul 31, 2020 at 7:57 PM oddhack [via Asciidoctor :: Discussion] <[hidden email]> wrote: Is there an Apache plugin which will translate .adoc to HTML on the fly and serve the rendered result, rather than the source markup? I've browsed the archives and web search without turning up obvious matches. The use case is to reflect an internal gitlab repository through Apache, conceptually similar to github.io, and rendering README.adoc in the webserver would be very helpful for this. -- Dan Allen (he, him, his) | @mojavelinux | https://twitter.com/mojavelinux |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In reply to this post by oddhack
Is live-rendering really needed? If the sources are in source control a hook could be used to generate the static html and you could serve that.
Otherwise it may be possible to use Apache as a proxy and have the gitlab instance serve the rendered content (just) for adoc files. It depends on what exactly you want to achieve. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Not essential, no. That is a viable alternative.
The annoying thing is that we can't serve HTML / PDF out of the gitlab web interface, nor processed .adoc out of Apache, so it's difficult to get a view of the repo that does both things. We're constrained to a self-hosted gitlab server here, alas. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
So are Gitlab Pages insufficient or does the gitlab instance need to remain isolated?
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
To elaborate on dalai's response:
Alexander Schwartz (alexander.schwartz@gmx.net)
https://www.ahus1.de |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In reply to this post by dalai
Unfortunately, the content must remain private. Otherwise we'd just use github.io to begin with.
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Administrator
|
Access to GitLab Pages can be restricted, both on GitLab.com and self-hosted instances. -Dan On Mon, Aug 3, 2020, 18:32 oddhack [via Asciidoctor :: Discussion] <[hidden email]> wrote: Unfortunately, the content must remain private. Otherwise we'd just use github.io to begin with. |
Free forum by Nabble | Edit this page |