101010.pl

:projetstodon: ShalienDear <a href="https://mastodon.projetretro.io/tags/fediadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediadmin</a>, regarding the current ongoing full force assault on our services by AI scrappers with all the risks associated (costs, services stability, data being stolen and so on) I can only recommend the setting up of <a href="https://mastodon.projetretro.io/tags/techaro" class="mention hashtag" rel="nofollow noopener" target="_blank">#techaro</a> <a href="https://mastodon.projetretro.io/tags/anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#anubis</a> requests filter to "weight the souls of incoming HTTP requests"I tested it so far on <a href="https://mastodon.projetretro.io/tags/alpine" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpine</a> <a href="https://mastodon.projetretro.io/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> deployed services with either <a href="https://mastodon.projetretro.io/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddy</a> , <a href="https://mastodon.projetretro.io/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> / <a href="https://mastodon.projetretro.io/tags/httpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#httpd</a> and <a href="https://mastodon.projetretro.io/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> for the following services <a href="https://mastodon.projetretro.io/tags/nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#nextcloud</a>, <a href="https://mastodon.projetretro.io/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a>, <a href="https://mastodon.projetretro.io/tags/forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#forgejo</a>, <a href="https://mastodon.projetretro.io/tags/lemmy" class="mention hashtag" rel="nofollow noopener" target="_blank">#lemmy</a>, <a href="https://mastodon.projetretro.io/tags/funkwhale" class="mention hashtag" rel="nofollow noopener" target="_blank">#funkwhale</a>, <a href="https://mastodon.projetretro.io/tags/bookwyrm" class="mention hashtag" rel="nofollow noopener" target="_blank">#bookwyrm</a> and a <a href="https://mastodon.projetretro.io/tags/minecraft" class="mention hashtag" rel="nofollow noopener" target="_blank">#minecraft</a> <a href="https://mastodon.projetretro.io/tags/mapviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#mapviewer</a> with little hassle and no big issuesFollowing the use of <a href="https://mastodon.projetretro.io/tags/anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#anubis</a>, all scrapper (AI and regular) logs dropped drastically and bandwitch usage was cut by two third on the mastodon instance and half for the others servicesDo yourself and your users a favor try it : <a href="https://github.com/TecharoHQ/anubis" rel="nofollow noopener" translate="no" target="_blank">https://github.com/TecharoHQ/anubis</a>

AskUbuntuNo apache subversion/svn package on 24.04? <a href="https://ubuntu.social/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> #2404 <a href="https://ubuntu.social/tags/svn" class="mention hashtag" rel="nofollow noopener" target="_blank">#svn</a><a href="https://askubuntu.com/q/1552927/612" rel="nofollow noopener" translate="no" target="_blank">https://askubuntu.com/q/1552927/612</a>

AskUbuntuSomebody knows Ubuntu 24 LTS update roadmap for Apache? <a href="https://ubuntu.social/tags/upgrade" class="mention hashtag" rel="nofollow noopener" target="_blank">#upgrade</a> <a href="https://ubuntu.social/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a><a href="https://askubuntu.com/q/1552578/612" rel="nofollow noopener" translate="no" target="_blank">https://askubuntu.com/q/1552578/612</a>

AskUbuntuUbuntu 24.04 and apache2 .htaccess <a href="https://ubuntu.social/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> #2404 <a href="https://ubuntu.social/tags/webserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#webserver</a><a href="https://askubuntu.com/q/1551692/612" rel="nofollow noopener" translate="no" target="_blank">https://askubuntu.com/q/1551692/612</a>

Menel :xmpp:After seeing Improving snac Performance with Nginx Proxy Cache from <a href="https://snac.it-notes.dragas.net/itnotes" class="u-url mention" rel="nofollow noopener" target="_blank">@itnotes@snac.it-notes.dragas.net</a> via <a href="https://snac.it-notes.dragas.net/itnotes/p/1738139676.258050" rel="nofollow noopener" target="_blank">https://snac.it-notes.dragas.net/itnotes/p/1738139676.258050</a> <a href="https://it-notes.dragas.net/2025/01/29/improving-snac-performance-with-nginx-proxy-cache/" rel="nofollow noopener" target="_blank">https://it-notes.dragas.net/2025/01/29/improving-snac-performance-with-nginx-proxy-cache/</a> I decided to prematurely optimize and adjust this for my apache2 httpd server in debian where I run snac. I've never done any caching etc before so it was a nice adventure to learn something new. The documentation helped and in the end it wasn't very hard. I learned a bit about some http headers and regex on the way too. Basically it works like this: Enable the relevant modules: <pre>a2enmod expires cache cache_disk </pre>Be sure "htcacheclean" is running to clean up old disk cache. (under debian see /etc/default/apache-htcacheclean or else the relevant systemd service) Then add to the snac virtualhost config: <pre>CacheRoot /var/cache/apache2/mod_cache_disk CacheQuickHandler off CacheLock on # Optional while testing stuff; CacheDetailHeader on # My Instance ist not at the root, but under "/social"; so this needs to be adapted for most I guess: <LocationMatch "^/social/[^/]+/s"> CacheEnable disk ExpiresActive On ExpiresDefault "access plus 30 days" </LocationMatch> </pre>This will use the disk cache to cache everything under the /s/ Path, same as the original ngnix tutorial, Utilizing the mod_expires to generate the appropriate cache headers (for lazy ones like me), In this case caching it for 30 days. Further reading and all options explained under <a href="https://httpd.apache.org/docs/2.4/caching.html" rel="nofollow noopener" target="_blank">https://httpd.apache.org/docs/2.4/caching.html</a> ff Thanks for the initial tutorial <a href="https://snac.it-notes.dragas.net/itnotes" class="u-url mention" rel="nofollow noopener" target="_blank">@itnotes@snac.it-notes.dragas.net</a> <a href="https://snikket.de/social?t=fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fediverse</a> <a href="https://snikket.de/social?t=hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hosting</a> <a href="https://snikket.de/social?t=itnotes" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITNotes</a> <a href="https://snikket.de/social?t=networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Networking</a> <a href="https://snikket.de/social?t=apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> <a href="https://snikket.de/social?t=httpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#httpd</a> <a href="https://snikket.de/social?t=ownyourdata" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ownyourdata</a> <a href="https://snikket.de/social?t=server" class="mention hashtag" rel="nofollow noopener" target="_blank">#Server</a> <a href="https://snikket.de/social?t=snac" class="mention hashtag" rel="nofollow noopener" target="_blank">#Snac</a> <a href="https://snikket.de/social?t=snac2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Snac2</a> <a href="https://snikket.de/social?t=social" class="mention hashtag" rel="nofollow noopener" target="_blank">#Social</a> <a href="https://snikket.de/social?t=tipsandtricks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tipsandtricks</a> <a href="https://snikket.de/social?t=tutorial" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tutorial</a> <a href="https://snikket.de/social?t=web" class="mention hashtag" rel="nofollow noopener" target="_blank">#Web</a> <a href="https://snikket.de/social?t=debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a>

bazkie 👩🏼‍💻 bitplanes 🎵*EDIT thanks for all the (similar) answers! 😁 I had always thought a web server only would serve files owned by the web user, regardless of those file mode settings! I was mistaken! :)Apache2 (on Debian) questionUhh, I put a file owned by root in my web server dir, and now I can download it from my browser.. is that supposed to be possible or do I have to change some settiing? 😅I thought only files from the www user should be viewable/downloadable?<a href="https://beige.party/tags/Apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apache2</a> <a href="https://beige.party/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

BustikillerI'm getting used to <a href="https://mastodon.social/tags/moodle" class="mention hashtag" rel="nofollow noopener" target="_blank">#moodle</a> on <a href="https://mastodon.social/tags/android" class="mention hashtag" rel="nofollow noopener" target="_blank">#android</a> and I was a bit surprised to find restrictions like number of downloads or push notification devices. As far as I can tell, this restriction is not in the server, but in the app itself. The app has a free tier and paid plans, but I'm not used to seeing this kind of restrictions on free software (<a href="https://mastodon.social/tags/Apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apache2</a> licensed).<a href="https://mastodon.social/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

Jools [Friendica]Ich habe den Artikel "Friendica auf dem Raspberry Pi installieren" noch mal überarbeitet bzw. erweitert.Hinzugekommen sind die Installation von <a href="https://missocial.de/search?tag=Apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apache2</a>, <a href="https://missocial.de/search?tag=MariaDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#MariaDB</a> und die benötigten PHP-Module, sowie die Konfiguration des Virtuellen Hosts für Friendica.So ist nun eine komplette Installationsanleitung daraus entstanden. 🙈Hier geht es zur Anleitung: 👉 <a href="https://blogzwo.me/raspberry-pi/friendica-auf-dem-raspberry-pi-installieren.html" rel="nofollow noopener" target="_blank">Friendica auf dem Raspberry Pi installieren - Blog:Zwo.me</a><a href="https://missocial.de/search?tag=friendica" class="mention hashtag" rel="nofollow noopener" target="_blank">#friendica</a>, <a href="https://missocial.de/search?tag=FriendicaInstallation" class="mention hashtag" rel="nofollow noopener" target="_blank">#FriendicaInstallation</a>, <a href="https://missocial.de/search?tag=apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a>, <a href="https://missocial.de/search?tag=mariadb" class="mention hashtag" rel="nofollow noopener" target="_blank">#mariadb</a>, <a href="https://missocial.de/search?tag=php" class="mention hashtag" rel="nofollow noopener" target="_blank">#php</a>, <a href="https://missocial.de/search?tag=virtualhost" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualhost</a>, <a href="https://missocial.de/search?tag=raspberrypi" class="mention hashtag" rel="nofollow noopener" target="_blank">#raspberrypi</a>

TOVThe Linux Lite logo is a yellow feather to represent the lightweight Linux distribution that works exceptional well on older hardware. The Linux distribution is "light as a feather." <a href="https://www.linuxliteos.com/index.html" rel="nofollow noopener" translate="no" target="_blank">https://www.linuxliteos.com/index.html</a>But the Apache2 HTTP server also has a feather as a logo, but Apache2 is not considered lightweight compared to other web servers like Nginx or Lighttpd. <a href="https://httpd.apache.org/" rel="nofollow noopener" translate="no" target="_blank">https://httpd.apache.org/</a><a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/LinuxLite" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxLite</a> <a href="https://fosstodon.org/tags/Apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apache2</a>

DorianHey folks, wenn man einen Reverse Proxy benötigt, um einen Dienst mit Let's Encrypt anzubieten.. was nehmen nehmen die resourcenbewussten jungen hippen Menschen von heute da so?<a href="https://mas.to/tags/reverseproxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#reverseproxy</a> <a href="https://mas.to/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> <a href="https://mas.to/tags/lighttpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#lighttpd</a> <a href="https://mas.to/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a>

VictoriaMetricsWe've tried to provide good reasons for why changing a software license from truly <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> to some source-available license makes little sense from a business perspective (in our opinion & experience).We won't be changing the <a href="https://mastodon.social/tags/Apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apache2</a> license for our products. Our main goal is to provide users with good products & help them use these efficiently. Read more in our latest blog post: ➡️<a href="https://victoriametrics.com/blog/open-source-software-licenses-vs-revenue-growth-rates/" rel="nofollow noopener" translate="no" target="_blank">https://victoriametrics.com/blog/open-source-software-licenses-vs-revenue-growth-rates/</a>

Tiago FKestra, Open Source Declarative Data Orchestration <a href="https://kestra.io/" rel="nofollow noopener" translate="no" target="_blank">https://kestra.io/</a><a href="https://bolha.us/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://bolha.us/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://bolha.us/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a>.0 <a href="https://bolha.us/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a>

FoxApache2 permissions “hack” It’s not stupid if [the last part] works, right? Right? 1. We need a new group: website 2. We need a user: frank 3. Simple website where everything is put into /var/www/html/ sudo addgroup website sudo adduser frank website sudo adduser www-data website Let’s see if Frank belongs to the right groups: groups frank The result should look so… --- <a href="https://3xn.nl/projects/2024/08/04/apache2-permissions-hack/" rel="nofollow noopener" translate="no" target="_blank">https://3xn.nl/projects/2024/08/04/apache2-permissions-hack/</a> --- <a href="https://cytag.nl/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> <a href="https://cytag.nl/tags/chown" class="mention hashtag" rel="nofollow noopener" target="_blank">#chown</a> <a href="https://cytag.nl/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#html</a> <a href="https://cytag.nl/tags/newgrp" class="mention hashtag" rel="nofollow noopener" target="_blank">#newgrp</a> <a href="https://cytag.nl/tags/ownership" class="mention hashtag" rel="nofollow noopener" target="_blank">#ownership</a> <a href="https://cytag.nl/tags/permissions" class="mention hashtag" rel="nofollow noopener" target="_blank">#permissions</a>

teledyn 𓂀<a href="https://mstdn.ca/tags/pixelfed" class="mention hashtag" rel="nofollow noopener" target="_blank">#pixelfed</a> vs <a href="https://mstdn.ca/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> is maddening. I have umask 002 in systemd for both, 0775/0664 0770/0660 for public & private, and failing on thumbnails, the fresh image folder on upload is 750. Grrrr.And no idea at all why the /api/v1/* calls are all 404 or 500; webfinger sees an acct, but the acct cannot receive, api is closed..env includes…ACTIVITY_PUB="true" AP_REMOTE_FOLLOW="true" AP_INBOX="true" AP_OUTBOX="true" AP_SHAREDINBOX="true"Time for some deep breaths, fresh air, maybe dinner too.

Yehor 🇺🇦This is just beautiful! The best <a href="https://techhub.social/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> client for <a href="https://techhub.social/tags/FreshRSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreshRSS</a>. You should check it out, if not yet: <a href="https://github.com/Ashinch/ReadYou/" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Ashinch/ReadYou/</a>Still need to get used to some <a href="https://techhub.social/tags/MaterialYou" class="mention hashtag" rel="nofollow noopener" target="_blank">#MaterialYou</a> principles.Oh, and I set up <a href="https://techhub.social/tags/FreshRSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreshRSS</a> on my <a href="https://techhub.social/tags/SynologyNAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SynologyNAS</a> the way it should be. No <a href="https://techhub.social/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a>. Just <a href="https://techhub.social/tags/MariaDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#MariaDB</a>, <a href="https://techhub.social/tags/WebStation" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStation</a>, <a href="https://techhub.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> and <a href="https://techhub.social/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a>. Everything from the official <a href="https://techhub.social/tags/Synology" class="mention hashtag" rel="nofollow noopener" target="_blank">#Synology</a> packages.<a href="https://techhub.social/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://techhub.social/tags/SelfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosted</a> <a href="https://techhub.social/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a> <a href="https://techhub.social/tags/HomeServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeServer</a> <a href="https://techhub.social/tags/RSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RSS</a>

Justin 🇻🇦Gonna rebuild my home server soon. Moving from a Pi 4 running Ubuntu server with Apache to an oldish laptop (i7-6500U, 8gb RAM). Any recommendations for a fresh start?Proxmox? Ansible? Dockerize everything? Caddy? Traefik? Nginx? Some kinda crazy clustering thing? Backup strategies?Any suggestions for the pi? Don't get to do a fresh start very often, so if I can do things better, I'd love advice now.<a href="https://rcsocial.net/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://rcsocial.net/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> <a href="https://rcsocial.net/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://rcsocial.net/tags/server" class="mention hashtag" rel="nofollow noopener" target="_blank">#server</a> <a href="https://rcsocial.net/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a> <a href="https://rcsocial.net/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a> <a href="https://rcsocial.net/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> <a href="https://rcsocial.net/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> <a href="https://rcsocial.net/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> <a href="https://rcsocial.net/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> <a href="https://rcsocial.net/tags/raspberrypi" class="mention hashtag" rel="nofollow noopener" target="_blank">#raspberrypi</a> <a href="https://rcsocial.net/tags/laptop" class="mention hashtag" rel="nofollow noopener" target="_blank">#laptop</a> <a href="https://rcsocial.net/tags/server" class="mention hashtag" rel="nofollow noopener" target="_blank">#server</a> <a href="https://rcsocial.net/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>

Wilda SoftwareWirtualne hosty to taka rzecz, którą ustawia się relatywnie rzadko i gdy trzeba to zrobić, to człowiek szuka poradników, bo już zapomniał. Ale są też tacy, którzy nie wiedzą, czym są owe hosty. Przypominamy nasz artykuł na ten temat.<a href="https://social.wildasoftware.pl/tags/VHosts" class="mention hashtag" rel="nofollow noopener" target="_blank">#VHosts</a> <a href="https://social.wildasoftware.pl/tags/virtual" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtual</a> <a href="https://social.wildasoftware.pl/tags/host" class="mention hashtag" rel="nofollow noopener" target="_blank">#host</a> <a href="https://social.wildasoftware.pl/tags/konfiguracja" class="mention hashtag" rel="nofollow noopener" target="_blank">#konfiguracja</a> <a href="https://social.wildasoftware.pl/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> <a href="https://social.wildasoftware.pl/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a><a href="https://wildasoftware.pl/post/wirtualne-hosty-czym-sa-ich-konfiguracja?ref=mastodon" rel="nofollow noopener" target="_blank">https://wildasoftware.pl/post/wirtualne-hosty-czym-sa-ich-konfiguracja?ref=mastodon</a>

Jason ReedCan anyone point me to a resource for setting up urls to aliases for directories outside of root directory. I can't find the link and search engines are worthless since AI has been added. <a href="https://toot.community/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a>

bonoky 🇬🇧<a href="https://mastodon.nzoss.nz/@lightweight" class="u-url mention" rel="nofollow noopener" target="_blank">@lightweight</a> Thanks for the information Dave. I have a spare <a href="https://fosstodon.org/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a> so I might give it another go. I have read up about <a href="https://fosstodon.org/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a>; I think I understand the idea, but couldn’t get my head around managing it all - it seems to add another layer of complexity to the mix. I find configuring & managing <a href="https://fosstodon.org/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> on its own quite difficult so having several web based applications in one container sound quite fraught.

Recent searches

Search options

Administered by:

Server stats:

#apache2