= gitea2rss(1)
:doctype: manpage
:Author: tastytea
:Email: tastytea@tastytea.de
:Date: 2019-04-17
:Revision: 0.0.0
:man source: gitea2rss
:man version: {revision}
:man manual: General Commands Manual
== NAME
gitea2rss - Generates RSS feeds from Gitea releases.
== SYNOPSIS
*gitea2rss* _URL of Gitea project_
== DESCRIPTION
gitea2rss fetches the releases from the Gitea API, converts the data into an RSS
feed and dumps it to stdout. You can use it as a CGI script to generate the
feeds dynamically or simply use cron to generate the feeds at fixed intervals.
If you want to use gitea2rss as a CGI script, you have to set
*GITEA2RSS_BASEURL* to the basis URL of your instance, without the trailing
slash. For example: _https://git.example.com_. The *QUERY_STRING* must contain
_repo=user/project_. The feed-URL for alice's project, cooltool, would be:
`https://rss.example.com/?repo=alice/cooltool`.
You can let Gitea automatically insert links to your RSS feeds by editing
`${GITEA_CUSTOM}/templates/custom/header.tmpl` and putting something like
this in it:
[source,html]
----
----
The generated RSS feed contains the *channel* elements _title_, _link_,
_description_, _generator_ and _lastBuildDate_ and the *item* elements _title_,
_link_, _guid_, _pubDate_ and _description_. Since Gitea has no individual pages
for each release, _link_ elements in *item* are set to the overview page for
releases.
== PROXY SERVERS
Since gitea2rss is built on libcurl, it respects the same proxy environment
variables. See *curl*(1), section _ENVIRONMENT_.
== EXAMPLES
`gitea2rss https://git.example.com/user/repo > repo.rss`
`https_proxy="socks4a://user:pass@127.0.0.1:9050/" gitea2rss
https://git.example.com/user/repo`
=== Example RSS feed
[source,xml]
----
First release. Everything works, as far as I can tell.]]> ---- == SEE ALSO *crontab*(1), *crontab*(5), *curl*(1) == REPORTING BUGS Bugtracker: https://schlomp.space/tastytea/gitea2rss/issues E-mail: tastytea@tastytea.de