Add description page for Gitea API Protector

master
Hugo Thunnissen 2 years ago
parent 0ee3420855
commit d13e8891a4

@ -25,10 +25,10 @@
<p>
I regularly work on software projects that I make publicly available. Below is
a selected few of my projects that I am either currently working on or am
currenty the most proud of. If you want to see all of the open source projects
that I have worked on in the past, feel free to checkout the github or
snorbaart links above!
a selected few of my projects that I am either currently working on or am the
most proud of. If you want to see all of the open source projects that I have
worked on in the past, feel free to checkout the github or snorbaart links
above!
</p>
<div class="cardbox">
@ -48,7 +48,7 @@
</a>
<a href="projects/gitea-api-protector/index.html" class="card">
<header>Gitea Api Protector</header>
<header>Gitea API Protector</header>
<p>
Shield your gitea API from bad actors on public instances.
</p>

@ -1 +1 @@
3544450995 2099
381269847 2090

@ -1 +1 @@
1653402568
1653462513

@ -24,7 +24,7 @@
<section>
<header>Who Would This Be Useful For?</header>
<header>Who Might This Be Useful For?</header>
<section>
<header>The Lone Selfhoster</header>
<p>
@ -37,12 +37,12 @@
<header>The Cloud-Native Company</header>
<p>
While it hasn't been tested in large deployments, I think that this DNS YAML
could theoretically be a great addition for large bodies of people who work
on applications within the same infrastructure. Traditionally, DNS records
are something that is managed by sysadmins who edit zone files by hand, or
through self-service UIs that some employees are allowed to acces. If one
were to, in stead, use version controlled DNS YAML documents in combination
with CI/CD, the following things would be achieved:
could be a great addition for large bodies of people who work on applications
within the same infrastructure. Traditionally, DNS records are managed by
sysadmins who edit zone files by hand, or through self-service UIs that some
employees are allowed to acces. If one were to, in stead, use version
controlled DNS YAML documents in combination with CI/CD, the following things
would be achieved:
</p>
<ol>

@ -1 +1 @@
72850756 6424
2000627787 6392

@ -0,0 +1,26 @@
<header>Gitea API Protector</header>
<p>
I built the Gitea API Protector in response to a request for help that
maintainers of <a href="https://codeberg.org">codeberg.org</a> put out on the
fediverse in january of 2020. Codeberg was (and probably still is) one of the
largest public <a href="https://gitea.io">gitea</a> instances and as such was
having trouble with spam bots that would create spam issues on repositories
using the API. My solution was to lock new users out of API access and have
them apply for it through a pull request they could create using the gitea web
UI. The people from codeberg
were <a href="https://github.com/go-gitea/gitea/issues/9847#issuecomment-575799090">interested</a>,
but in the end they didn't end up going with my solution. Nevertheless the
software is fully functional and the codebase is small enough for people to
change it for their own use cases if they so desired.
</p>
<p>
A more elaborate explanation of the technical details an setup instructions can
be found in the README of the repository
on <a href="https://github.com/hugot/gitea-api-protector">github</a> or
on <a href="https://codeberg.org">codeberg.org</a>.
</p>
<!-- Local Variables: -->
<!-- sgml-basic-offset: 1 -->
<!-- End: -->
Loading…
Cancel
Save