Urbanists.Social

1 post1 participant0 posts today

stibHey <a href="https://aus.social/tags/mysql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mysql</a> thing-knowers. I've just installed mysql 9.2, and <a href="https://aus.social/tags/php" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#php</a> 8 on a <a href="https://aus.social/tags/WindowsServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WindowsServer</a>. When I try to use mysqli_connect in my php application I get the error `mysqli_connect(): The server requested authentication method unknown to the client [caching_sha2_password]` On the mysql side the user is identified with caching_sha2_password. All the answers to this problem I've found seem to be quite old, and they all recommend altering the user to `mysql_native_password`. This seems like a retrograde step, but I gave it a go, and when I tried to do that I got `Error 1524 HY0000: Plugin mysql_native_password is not loaded`. I know exactly enough mysql and php to cause headaches for people who know what they're doing, is anyone able to help out? <a href="https://aus.social/tags/AskFedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AskFedi</a> <a href="https://aus.social/tags/Webserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Webserver</a>

RavenCaddy Web Server 2.10 released with encrypted ClientHello (ECH) support, post-quantum key exchange, ACME profiles, libdns 1.0 APIs, global DNS config<a href="https://github.com/caddyserver/caddy/releases/tag/v2.10.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/caddyserver/caddy/releases/tag/v2.10.0</a><a href="https://mastodon.bsd.cafe/tags/caddyserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyserver</a> <a href="https://mastodon.bsd.cafe/tags/caddyreverseproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddyreverseproxy</a> <a href="https://mastodon.bsd.cafe/tags/webserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webserver</a> <a href="https://mastodon.bsd.cafe/tags/reverseproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reverseproxy</a> <a href="https://mastodon.bsd.cafe/tags/acme" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#acme</a> <a href="https://mastodon.bsd.cafe/tags/postquantumcryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#postquantumcryptography</a>

LinuxiacCaddy 2.10 web & reverse proxy server lands with support for ECH, post-quantum key exchange, global DNS config, and wildcard certs by default. <a href="https://linuxiac.com/caddy-2-10-web-server-debuts-enhanced-tls-privacy/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linuxiac.com/caddy-2-10-web-server-debuts-enhanced-tls-privacy/</a><a href="https://mastodon.social/tags/caddy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#caddy</a> <a href="https://mastodon.social/tags/webserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webserver</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

Crazy-to-Bike<a href="https://23.social/@janw" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@janw@23.social</a> <a href="https://fediworld.de/tags/NC" rel="nofollow noopener noreferrer" target="_blank">#NC</a> ist extern auf meinem <a href="https://fediworld.de/tags/Webserver" rel="nofollow noopener noreferrer" target="_blank">#Webserver</a>. Der hat viel mehr Rechenleistung und ausreichend Speicher. Ich brauche nicht alles in NC, aber <a href="https://fediworld.de/tags/Collabora" rel="nofollow noopener noreferrer" target="_blank">#Collabora</a> sollte flüssig laufen. Wenn NC daheim laufen und von extern erreichbar sein soll, würde ich das über <a href="https://fediworld.de/tags/VPN" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> oder einen <a href="https://fediworld.de/tags/SSH" rel="nofollow noopener noreferrer" target="_blank">#SSH</a> Tunnel machen.

Third spruce tree on the left<a href="https://sakurajima.moe/@mangaispolitical" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mangaispolitical</a> Alternatively, you can put <a href="https://mas.to/tags/writefreely" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#writefreely</a> AND another webservice for your images behind <a href="https://mas.to/tags/Ngnix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ngnix</a>. Lets say `wf.yourdomain` and `images.yourdomain`DirtSWS is a little <a href="https://mas.to/tags/single" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#single</a> <a href="https://mas.to/tags/binary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#binary</a> <a href="https://mas.to/tags/webserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webserver</a> that does nothing but host <a href="https://mas.to/tags/static" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#static</a> <a href="https://mas.to/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a> and files, with a simple single-file remote upload capability. Here's a sample site: <a href="https://static.awadwatt.com/index.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://static.awadwatt.com/index.html</a>

.:\dGh/:.I wonder what PHP would win if the codebase was rewritten entirely in Rust.My bet? Given the Rust ecosystem, we would be months away of truly async, green threads, non blocking IO, and a complete performant web server implementation.Cc <a href="https://phpc.social/@thephpf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thephpf</a> <a href="https://fosstodon.org/@php" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@php</a> <a href="https://phpc.social/@phpfig" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@phpfig</a> <a href="https://phpc.social/@phpc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@phpc</a> <a href="https://mastodon.social/tags/PHP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PHP</a> <a href="https://mastodon.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Programming</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDevelopment</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> <a href="https://mastodon.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareDevelopment</a> <a href="https://mastodon.social/tags/Web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Web</a> <a href="https://mastodon.social/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a> <a href="https://mastodon.social/tags/ProgrammingLanguages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProgrammingLanguages</a> <a href="https://mastodon.social/tags/WebServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebServer</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://mastodon.social/tags/OSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSS</a> <a href="https://mastodon.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://mastodon.social/tags/ThePHPFoundation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ThePHPFoundation</a>

Jan ☕🎼🎹☁️🏋️‍♂️Does anyone know of a good <a href="https://fedi.kcore.org/tags/container" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#container</a> stack to run your typical websites on?You know, webserver (apache + php), database (mysql/pgsql), possible cache, ...<a href="https://fedi.kcore.org/tags/lamp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lamp</a> <a href="https://fedi.kcore.org/tags/lapp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lapp</a> <a href="https://fedi.kcore.org/tags/webserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webserver</a> <a href="https://fedi.kcore.org/tags/docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#docker</a>Looking to move some stuff from various places to one, but I really do want to segregate the sites.

Rutger van Sleen<a href="https://mastodon.nl/tags/Vraag" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vraag</a> aan <a href="https://mastodon.nl/tags/Ziggo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ziggo</a> gebruikers: ik heb momenteel ons modem in bridge-mode staan. Onze huisserver doet zorgt voor <a href="https://mastodon.nl/tags/internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#internet</a>/#netwerk. Om er voor te zorgen dat internet/netwerk het blijft doen (met zicht op mijn ziekteverloop), denk ik er aan om het modem dat gedeelte weer zelf te laten doen. Maar, ik wil nog dat de <a href="https://mastodon.nl/tags/webserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webserver</a> daar achter blijft werken. Ik krijg maar moeilijk bevestiging dat <a href="https://mastodon.nl/tags/poortforwarding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poortforwarding</a> van 80/443 goed werkt. Ervaringsdeskundigen die me hier kan verlossen? <a href="https://mastodon.nl/tags/dtv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dtv</a>

Recent searches

Search options

Administered by:

Server stats:

#webserver