s/hostea.org/gna.org/
ci/woodpecker/push/woodpecker Pipeline was successful
Details
ci/woodpecker/push/woodpecker Pipeline was successful
Details
Signed-off-by: Loïc Dachary <loic@dachary.org>master
parent
fd67379f56
commit
3d76b7d7c9
GPG Key ID:
992D23B392F9E4F2
|
|
@ -2,7 +2,7 @@
|
|||
<img width="80px" alt="Hostea logo" src="./static/tmp-logo.png" />
|
||||
<h1>Hostea Website</h1>
|
||||
|
||||
[](https://woodpecker.hostea.org/Hostea/website)
|
||||
[](https://woodpecker.hostea.org/Hostea/website)
|
||||
[](http://www.gnu.org/licenses/agpl-3.0)
|
||||
|
||||
</div>
|
||||
|
|
@ -36,6 +36,6 @@ Build artifacts should be available in `./public/`
|
|||
## Deployment
|
||||
|
||||
This repository uses [Hostea
|
||||
Woodpecker-CI](https://woodpecker.hostea.org/) to build and
|
||||
[Hostea/Pages](https://gitea.hostea.org/Hostea/pages) to deploy on each
|
||||
Woodpecker-CI](https://woodpecker.gna.org/) to build and
|
||||
[Hostea/Pages](https://gitea.gna.org/Hostea/pages) to deploy on each
|
||||
commit.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
# The URL the site will be built for
|
||||
base_url = "https://hostea.org"
|
||||
base_url = "https://gna.org"
|
||||
|
||||
# Whether to automatically compile all Sass files in the sass directory
|
||||
compile_sass = true
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@ If you are into trouble and need assistance with a Gitea instance not hosted at
|
|||
|
||||
---
|
||||
|
||||
Do you already have an expertise running Gitea? You are welcome to join the [Gna! collective](https://forum.hostea.org/t/a-guide-to-hostea-governance/57), get in touch [in the forum](https://forum.hostea.org/c/site-feedback/2) or [the chat](https://matrix.to/#/#hostea:matrix.batsense.net).
|
||||
Do you already have an expertise running Gitea? You are welcome to join the [Gna! collective](https://forum.gna.org/t/a-guide-to-hostea-governance/57), get in touch [in the forum](https://forum.hostea.org/c/site-feedback/2) or [the chat](https://matrix.to/#/#hostea:matrix.batsense.net).
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ author = 'dachary'
|
|||
|
||||
The [instructions to upgrade a Gitea instance](https://docs.gitea.io/en-us/upgrade-from-gitea/#upgrade-from-binary) only require three to four steps. They work fine most of the time but the documentation is lacking a "Troubleshooting" section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.
|
||||
|
||||
An [inventory of the known upgrade issues](https://forum.hostea.org/t/things-to-know-about-gitea-upgrades/39) was started to figure out how to structure such a section in the documentation. The [release notes](https://blog.gitea.io/) were analyzed all the way back to [Gitea 1.9.6](https://github.com/go-gitea/gitea/releases/tag/v1.9.6) and the work is still in progress. Here is a sample of the tips that will be included:
|
||||
An [inventory of the known upgrade issues](https://forum.gna.org/t/things-to-know-about-gitea-upgrades/39) was started to figure out how to structure such a section in the documentation. The [release notes](https://blog.gitea.io/) were analyzed all the way back to [Gitea 1.9.6](https://github.com/go-gitea/gitea/releases/tag/v1.9.6) and the work is still in progress. Here is a sample of the tips that will be included:
|
||||
|
||||
* Upgrade directly to the latest Gitea version, there is no need to upgrade to intermediate versions.
|
||||
* If the upgrade from version x.y to version x.y+2 fails and there is a need to narrow down the problem, try upgrading to the latest minor version of each major version and verify it works.
|
||||
|
|
@ -35,7 +35,7 @@ There was hope to fix Gitea and in the following days they applied the workaroun
|
|||
|
||||
# Getting professional help
|
||||
|
||||
The [Hostea Clinic](https://hostea.org/gitea-clinic/) is a collective of individual and companies that provides professional services to Gitea admins. They are active members of the Gitea community who [help out](https://discourse.gitea.io/u/dachary/activity) as volunteers. They can also be hired to resolve the more complicated cases.
|
||||
The [Hostea Clinic](https://gna.org/gitea-clinic/) is a collective of individual and companies that provides professional services to Gitea admins. They are active members of the Gitea community who [help out](https://discourse.gitea.io/u/dachary/activity) as volunteers. They can also be hired to resolve the more complicated cases.
|
||||
|
||||
The Gitea instance that was in trouble required more than a few minutes of work and access to the database content for a proper diagnostic. They [proposed their assistance](https://discourse.gitea.io/t/blank-page-after-login/5051/13) but although [well received](https://discourse.gitea.io/t/user-research-about-gitea-upgrade-experiences-call-for-volunteers/5063/2), it was not accepted.
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ To summarize with a timeline, here is what happened:
|
|||
And in retrospect, here is what could have happened instead:
|
||||
|
||||
* J+1: The **problem is discovered** by users who see a blank page after login
|
||||
* J+1: The Gitea admin **[reaches out to someone at the Hostea Clinic](https://hostea.org/gitea-clinic/)**
|
||||
* J+1: The Gitea admin **[reaches out to someone at the Hostea Clinic](https://gna.org/gitea-clinic/)**
|
||||
* J+2: The [logs of the Gitea instance](https://discourse.gitea.io/t/blank-page-after-login/5051/12) are analyzed, **the root cause diagnosed** and [a patch](https://discourse.gitea.io/t/blank-page-after-login/5051/17) is created to fix it.
|
||||
* J+3: If necessary a Gitea binary is created with the patch and used as a temporary replacement until the next point release is published with [the backport](https://github.com/go-gitea/gitea/pull/19629). The Gitea admin runs the patched Gitea binary in the meantime. **There is no data loss**.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ tags = ['hostea', 'gitea', 'troubleshoot', 'problem', 'tutorial']
|
|||
author = 'dachary'
|
||||
+++
|
||||
|
||||
While helping people with their upgrades [in the Gitea forum](https://discourse.gitea.io/t/migration-from-1-2-to-1-16-8/5309) or [at the Hostea clinic](https://forum.hostea.org/t/gitea-upgrade-from-1-14-1-to-1-16-8/90), I realized that few Gitea admins know about the [`gitea doctor`](https://docs.gitea.io/en-us/command-line/#doctor) command and decided to write this blog post as a gentle introduction.
|
||||
While helping people with their upgrades [in the Gitea forum](https://discourse.gitea.io/t/migration-from-1-2-to-1-16-8/5309) or [at the Hostea clinic](https://forum.gna.org/t/gitea-upgrade-from-1-14-1-to-1-16-8/90), I realized that few Gitea admins know about the [`gitea doctor`](https://docs.gitea.io/en-us/command-line/#doctor) command and decided to write this blog post as a gentle introduction.
|
||||
|
||||
### An apple a day keeps the doctor away
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ However, if an Gitea installation was done differently and `$HOME/.gitconfig` ha
|
|||
|
||||
It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a **potential for breakage when upgrading to Gitea >= 1.17 because the location of the file changed**. It must be moved manually to the new location as follows:
|
||||
|
||||
* Figure out the directory where `$HOME/.gitconfig` must be moved by [running the doctor](https://hostea.org/blog/gentle-introduction-to-the-doctor/):
|
||||
* Figure out the directory where `$HOME/.gitconfig` must be moved by [running the doctor](https://gna.org/blog/gentle-introduction-to-the-doctor/):
|
||||
|
||||
```shell
|
||||
$ gitea --work-path /app/gitea -c /data/gitea/conf/app.ini doctor
|
||||
|
|
@ -44,4 +44,4 @@ OK
|
|||
|
||||
* Copy the `$HOME/.gitconfig` file to the **Repository Root Path** (which is `/data/git/repositories` in the example above).
|
||||
|
||||
The reason why this breaking change was introduced is to workaround [a rare problem](https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/) impacting Gitea installations relying on networked volumes.
|
||||
The reason why this breaking change was introduced is to workaround [a rare problem](https://gna.org/blog/unsafe-repository-is-owned-by-someone-else/) impacting Gitea installations relying on networked volumes.
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ This would have been a minor inconvenience if it only has an impact on adventuro
|
|||
|
||||
In 1.17.0-rc2, a custom .gitconfig must be moved manually to the [new git home directory](https://docs.gitea.io/en-us/config-cheat-sheet/#git-git) as follows:
|
||||
|
||||
* Figure out the directory where `$HOME/.gitconfig` must be moved by [running the doctor](https://hostea.org/blog/gentle-introduction-to-the-doctor/):
|
||||
* Figure out the directory where `$HOME/.gitconfig` must be moved by [running the doctor](https://gna.org/blog/gentle-introduction-to-the-doctor/):
|
||||
|
||||
```shell
|
||||
$ gitea --work-path /app/gitea -c /data/gitea/conf/app.ini doctor
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Hosting a Gitea instance on Hostea is now possible (but still experimental). It
|
|||
|
||||
The service is 100% infrastructure as code, published as [Ansible playbooks within Enough](https://lab.enough.community/main/infrastructure/-/tree/9e18ebbf675c8a65d1585d20b4cf6295af6e52ed/playbooks/hosteadashboard). It can be self-hosted on bare metal (with [libvirt](https://libvirt.org/)) or in the cloud (with [OpenStack](https://www.openstack.org/)): follow the [quick start](https://enough-community.readthedocs.io/en/latest/introduction.html#quick-start), configure playbooks for [hostea](https://enough-community.readthedocs.io/en/latest/services/hostea.html) and [the dashboard](https://enough-community.readthedocs.io/en/latest/services/hosteadashboard.html).
|
||||
|
||||
The organization supporting Hostea is a [horizontal collective](https://forum.hostea.org/c/governance-and-decisions/7) of individuals and organizations. The [revenue sharing model](https://forum.hostea.org/t/decision-revenue-sharing-model/92) is set to dedicate 25% of the income (more than the profits) to help the Free Software projects Hostea depends on such as Gitea, Enough, Django etc.
|
||||
The organization supporting Hostea is a [horizontal collective](https://forum.gna.org/c/governance-and-decisions/7) of individuals and organizations. The [revenue sharing model](https://forum.hostea.org/t/decision-revenue-sharing-model/92) is set to dedicate 25% of the income (more than the profits) to help the Free Software projects Hostea depends on such as Gitea, Enough, Django etc.
|
||||
|
||||
### The origin
|
||||
|
||||
|
|
@ -31,13 +31,13 @@ The most common mistake technical people do when creating a new piece of softwar
|
|||
|
||||
It took no longer than two weeks for the people involved in Hostea to decide to build the technical stack to run hostea instead of being reasonable and give up. It was just too tempting.
|
||||
|
||||
To keep the madness contained and enjoyable, it was decided to set a deadline to July 1st and to [define precise and realistic technical goals](https://gitea.hostea.org/Hostea/july-mvp/issues). It turned out to be an enjoyable experience: everyone learned a lot in the process and the outcome is something that can be reproduced. Most MVPs are a brittle pile of hacks designed to last a few weeks and be thrown away. But since a primary goal of the project was to create something self-hostable, it had to implement that feature and therefore be reproducible.
|
||||
To keep the madness contained and enjoyable, it was decided to set a deadline to July 1st and to [define precise and realistic technical goals](https://gitea.gna.org/Hostea/july-mvp/issues). It turned out to be an enjoyable experience: everyone learned a lot in the process and the outcome is something that can be reproduced. Most MVPs are a brittle pile of hacks designed to last a few weeks and be thrown away. But since a primary goal of the project was to create something self-hostable, it had to implement that feature and therefore be reproducible.
|
||||
|
||||
### A horizontal collective with a revenue sharing model
|
||||
|
||||
Another goal of Hostea is to deploy federated forges, even at an experimental stage. Instead of creating a centralized organization to support Hostea, it was decided to create [horizontal collective](https://forum.hostea.org/c/governance-and-decisions/7). It feels like a contradiction for a project committed to decentralization to be governed by a centralized organization.
|
||||
Another goal of Hostea is to deploy federated forges, even at an experimental stage. Instead of creating a centralized organization to support Hostea, it was decided to create [horizontal collective](https://forum.gna.org/c/governance-and-decisions/7). It feels like a contradiction for a project committed to decentralization to be governed by a centralized organization.
|
||||
|
||||
The collective is composed of individuals and organizations but, unlike exclusively volunteer based Free Software projects, it is for profit. Customers rent Gitea instances by the month and the income is used to pay for expenses. There is however a difficulty: by nature a horizontal collective cannot be incorporated as it would create a level of hierarchy. The [revenue sharing model](https://forum.hostea.org/t/decision-revenue-sharing-model/92) had to be set as an informal agreement between members where one of them receives the income and distributes it to the others, depending on their Hostea related expenses.
|
||||
The collective is composed of individuals and organizations but, unlike exclusively volunteer based Free Software projects, it is for profit. Customers rent Gitea instances by the month and the income is used to pay for expenses. There is however a difficulty: by nature a horizontal collective cannot be incorporated as it would create a level of hierarchy. The [revenue sharing model](https://forum.gna.org/t/decision-revenue-sharing-model/92) had to be set as an informal agreement between members where one of them receives the income and distributes it to the others, depending on their Hostea related expenses.
|
||||
|
||||
It also requires that 25% of the income (not the profits) is dedicated to help the Free Software projects that Hostea depends on such as Gitea, Enough, Django etc. It can be via a donation, by upstreaming a bug fix or any kind of work that is beneficial to the dependency.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ tags = ['hostea', 'forgefriends']
|
|||
author = 'realaravinth'
|
||||
+++
|
||||
|
||||
Introducing [Hostea](https://hostea.org), a project [Loïc
|
||||
Introducing [Hostea](https://gna.org), a project [Loïc
|
||||
Dachary](https://dachary.org) and [Aravinth
|
||||
Manivannan](https://batsense.net) are working on to create a full Free
|
||||
software development suite based on
|
||||
|
|
|
|||
|
|
@ -5,11 +5,11 @@ description = "Get help with your sick Gitea instance"
|
|||
|
||||
## How does it work?
|
||||
|
||||
You can get help from the community on the [Hostea forum](https://forum.hostea.org/c/clinic/5) or the [Gitea forum](https://discourse.gitea.io/): it is the best way to resolve simple issues. If you are in a hurry or the problem is serious you could:
|
||||
You can get help from the community on the [Hostea forum](https://forum.gna.org/c/clinic/5) or the [Gitea forum](https://discourse.gitea.io/): it is the best way to resolve simple issues. If you are in a hurry or the problem is serious you could:
|
||||
|
||||
1. Get in touch with the [doctor of your choice](#hostea-doctors)
|
||||
2. Upload your sick Gitea
|
||||
3. Once it is repaired download it back home (or decide it deserves a permanent residence at [Hostea](https://hostea.org))
|
||||
3. Once it is repaired download it back home (or decide it deserves a permanent residence at [Hostea](https://gna.org))
|
||||
4. Pay the doctor
|
||||
|
||||
## How much does it cost?
|
||||
|
|
|
|||
|
|
@ -25,6 +25,6 @@ If the disclaimer of warranty and limitation of liability provided above cannot
|
|||
|
||||
## Hosting
|
||||
|
||||
The services and this web site, as well as all sub-domains, are exclusively maintained and used by the individuals composing the Hostea. They can be reached at contact@hostea.org.
|
||||
The services and this web site, as well as all sub-domains, are exclusively maintained and used by the individuals composing the Hostea. They can be reached at contact@gna.org.
|
||||
|
||||
For details, see [the documentation](https://enough-community.readthedocs.io/).
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ We will make a good faith effort to:
|
|||
|
||||
## What about my data?
|
||||
|
||||
Users of Hotea's services can ask contact@hostea.org to:
|
||||
Users of Hotea's services can ask contact@gna.org to:
|
||||
|
||||
* Delete their account on a service when it is not a feature available to the user (for instance Nextcloud)
|
||||
* Retrieve data associated with their account on a service that does not already provide full access
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Hostea hosts, via application software, content in private spaces that are not p
|
|||
|
||||
## Support
|
||||
|
||||
Support requests should be filed as an issue in https://gitea.hostea.org/Hostea/support/issues.
|
||||
Support requests should be filed as an issue in https://gitea.gna.org/Hostea/support/issues.
|
||||
|
||||
## Publicly available content published on Gitea instances
|
||||
|
||||
|
|
@ -39,9 +39,9 @@ Disaster recovery involves rebooting the machine that was lost using a backup, e
|
|||
|
||||
## GDPR compliance
|
||||
|
||||
A user can request deletion or anonymisation of the data they are unable to delete themselves by sending a request to contact@hostea.org.
|
||||
A user can request deletion or anonymisation of the data they are unable to delete themselves by sending a request to contact@gna.org.
|
||||
|
||||
A user can request an copy of the data held by Hostea that they are unable to download themselves by sending a request to contact@hostea.org.
|
||||
A user can request an copy of the data held by Hostea that they are unable to download themselves by sending a request to contact@gna.org.
|
||||
|
||||
## Editorial responsibility
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
[[ doctors ]]
|
||||
nick = "dachary"
|
||||
name ="Loïc Dachary"
|
||||
website = "https://gitea.hostea.org/dachary/hostea/issues"
|
||||
website = "https://gitea.gna.org/dachary/hostea/issues"
|
||||
picture = "/people/dachary.png"
|
||||
|
||||
[[ doctors.reviews ]]
|
||||
|
|
@ -17,7 +17,7 @@ remarks = "https://discourse.gitea.io/t/blank-page-after-login/5051/14"
|
|||
[[ doctors ]]
|
||||
nick = "realaravinth"
|
||||
name ="Aravinth Manivannan"
|
||||
website = "https://gitea.hostea.org/realaravinth/hostea/issues"
|
||||
website = "https://gitea.gna.org/realaravinth/hostea/issues"
|
||||
picture = "/people/realaravinth.jpg"
|
||||
|
||||
[[ doctors.reviews ]]
|
||||
|
|
@ -40,7 +40,7 @@ remarks = "Nice"
|
|||
[[ doctors ]]
|
||||
nick = "easter-eggs"
|
||||
name ="Easter-eggs"
|
||||
website = "https://gitea.hostea.org/easter-eggs/clinic/issues"
|
||||
website = "https://gitea.gna.org/easter-eggs/clinic/issues"
|
||||
picture = "/people/easter-eggs.png"
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ set_ssh_remote() {
|
|||
repository_owner=$(echo $http_remote_url | cut -d '/' -f 4)
|
||||
repository_name=$(echo $http_remote_url | cut -d '/' -f 5)
|
||||
ssh_remote="git@$remote_hostname:$repository_owner/$repository_name"
|
||||
ssh_remote="git@gitea.hostea.org:Hostea/website.git"
|
||||
ssh_remote="git@gitea.gna.org:Hostea/website.git"
|
||||
git remote add $SSH_REMOTE_NAME $ssh_remote
|
||||
}
|
||||
|
||||
|
|
@ -79,7 +79,7 @@ deploy() {
|
|||
git -c core.sshCommand="/usr/bin/ssh -oStrictHostKeyChecking=no -i $SSH_ID_FILE"\
|
||||
push --force $SSH_REMOTE_NAME $2
|
||||
curl -vv --location --request \
|
||||
POST "http://hostea.org:5000/api/v1/update"\
|
||||
POST "http://gna.org:5000/api/v1/update"\
|
||||
--header 'Content-Type: application/json' \
|
||||
--data-raw "{ \"secret\": \"$1\", \"branch\": \"$2\" }"
|
||||
fi
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ build() {
|
|||
}
|
||||
|
||||
no_absolute_url() {
|
||||
sed -i 's/https:\/\/hostea.org//g' $(find public -type f | grep html)
|
||||
sed -i 's/https:\/\/gna.org//g' $(find public -type f | grep html)
|
||||
}
|
||||
|
||||
clean() {
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
<div class="blog__container">
|
||||
<h1 class="blog__title">{{ section.title }}</h1>
|
||||
|
||||
<p>Hostea is a <a href="https://hostea.org/gitea-clinic">Clinic</a> to get help when a Gitea instance throws errors after an upgrade and the admin is not sure how to troubleshoot the problem. It opened in May 2022 and welcomes new patients. It will also provide dedicated Gitea hosting, including CI and more: subscribe <a href="https://hostea.org/blog/atom.xml">to the blog</a> or the <a rel="me" href="https://mastodon.online/@hostea">Mastodon account</a> to keep up to date.</p>
|
||||
<p>Hostea is a <a href="https://gna.org/gitea-clinic">Clinic</a> to get help when a Gitea instance throws errors after an upgrade and the admin is not sure how to troubleshoot the problem. It opened in May 2022 and welcomes new patients. It will also provide dedicated Gitea hosting, including CI and more: subscribe <a href="https://hostea.org/blog/atom.xml">to the blog</a> or the <a rel="me" href="https://mastodon.online/@hostea">Mastodon account</a> to keep up to date.</p>
|
||||
|
||||
<ul class="blog__list">
|
||||
{% for page in section.pages %}
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@
|
|||
<a href="/privacy-policy" title="Privacy Policy">Privacy</a>
|
||||
<span class="footer__column-divider--mobile-only">|</span>
|
||||
<a
|
||||
href="https://gitea.hostea.org/Hostea"
|
||||
href="https://gitea.gna.org/Hostea"
|
||||
rel="noreferrer"
|
||||
target="_blank"
|
||||
title="Status"
|
||||
|
|
|
|||
|
|
@ -10,9 +10,9 @@
|
|||
<li class="index-banner__features">Dedicated <a href="https://hosteadashboard.gna.org/register/">Gitea hosting</a> and <a href="https://woodpecker-ci.org/">Woodpecker CI</a> from 10€/month</li>
|
||||
<li class="index-banner__features">Clinic to <a href="/gitea-clinic/">heal sick Gitea</a> instances</li>
|
||||
<li class="index-banner__features">100% <a href="https://www.gnu.org/philosophy/free-sw.html">Free Software</a></li>
|
||||
<li class="index-banner__features">Radically <a href="https://forum.hostea.org/t/about-governance-and-decisions-in-hostea/55">Transparent</a></li>
|
||||
<li class="index-banner__features">Run by a <a href="https://forum.hostea.org/t/about-governance-and-decisions-in-hostea/55">horizontal collective</a></li>
|
||||
<li class="index-banner__features">25% of the income <a href="https://forum.hostea.org/t/decision-revenue-sharing-model/92">dedicated to sustain Free Software dependencies</a></li>
|
||||
<li class="index-banner__features">Radically <a href="https://forum.gna.org/t/about-governance-and-decisions-in-hostea/55">Transparent</a></li>
|
||||
<li class="index-banner__features">Run by a <a href="https://forum.gna.org/t/about-governance-and-decisions-in-hostea/55">horizontal collective</a></li>
|
||||
<li class="index-banner__features">25% of the income <a href="https://forum.gna.org/t/decision-revenue-sharing-model/92">dedicated to sustain Free Software dependencies</a></li>
|
||||
<li class="index-banner__features">Committed to <a href="https://forgefriends.org/blog/2022/06/30/2022-06-state-forge-federation/">further forge federation</a></li>
|
||||
</ul>
|
||||
<button class="index-banner__main-action-btn">
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@
|
|||
{{ macros::nav_link(link="/blog/", name="Blog") }}
|
||||
{{ macros::nav_link(link="https://matrix.to/#/#hostea:matrix.batsense.net", name="Chat") }}
|
||||
{{ macros::nav_link(link="/gitea-clinic/", name="Clinic") }}
|
||||
{{ macros::nav_link(link="https://forum.hostea.org", name="Forum") }}
|
||||
{{ macros::nav_link(link="https://forum.gna.org", name="Forum") }}
|
||||
{{ macros::nav_link(link="https://mastodon.online/web/@hostea", name="Mastodon") }}
|
||||
</div>
|
||||
<div class="nav__spacer"></div>
|
||||
|
|
|
|||
Loading…
Reference in New Issue