Marko Korhonen
730fb3a4a1
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
30 lines
1.4 KiB
Plaintext
30 lines
1.4 KiB
Plaintext
= Forgejo with AsciiDoc support
|
|
|
|
image::https://ci.korhonen.cc/api/badges/FunctionalHacker/forgejo-asciidoc/status.svg[link="https://ci.korhonen.cc/FunctionalHacker/gitea-asciidoc"]
|
|
|
|
The official Forgejo Docker image does not support AsciiDoc rendering, so I
|
|
wanted to create an image which has support out of the box.
|
|
|
|
== Pull from my Forgejo instance
|
|
Visit the link:/FunctionalHacker/forgejo-asciidoc/packages[Packages section] for more information.
|
|
The server is running behind 4G broadband so it might be a bit slow to download. Considering pulling
|
|
the other layers first from link:https://forgejo.org/download[the official image] first to
|
|
speed up the download.
|
|
|
|
== Configuration
|
|
In addition to pulling this image instead of the official one, you need to
|
|
configure the renderer. You can follow the
|
|
https://docs.gitea.io/en-us/external-renderers/#appini-file-configuration[official docs]
|
|
to achieve that.
|
|
|
|
== Updates
|
|
This image is based on the latest official Forgejo image.
|
|
I will update it whenever I notice the Forgejo team update their image and
|
|
I have the time to do it.
|
|
|
|
== Support
|
|
This image comes with no support whatsoever. The Dockerfile is based on the
|
|
official Forgejo image and it is literally 2 lines long so there is not much to go wrong here.
|
|
If, for whatever reason you feel that there must be something wrong with my image, you
|
|
can email me at mailto:forgejo@functionalhacker.korhonen.cc[forgejo@functionalhacker.korhonen.cc]
|