As far as i can tell this seems to be a dashboard for payment processors, not a self hosted payment processor.
Comment on Selfhosting payment processing
alcea@feddit.org 1 day ago
Saame. Altho just regular webhosting for me Mine just disabled all domains as their antivir found a “”“potential backdoor php”“” - thats what they claimed* (just a php page parser) => just a cute “login to user 401” error on all domains. Why bother quarantining a single file if you can disable a customers entire webspace
Ordered a “Dell Wyse 5070 Thin Client Mini PC Server J5005 Celeron J4105 8gbRAM 64 gb SSD” and will selfhost my sites now…
Flip dependency.
Self host Akkoma. Selfhost Websites. Hack your router. Done.
What a weird world we live in. genshin_neuvillette_sad_rain That leaves domains. Can’t self host those
*their ““antivir”” claimed lots of things … its hilarious
TheMightyCat@ani.social 1 day ago
trailee@sh.itjust.works 1 day ago
You mean DNS? Absolutely can self host those if you have a stable IP address. I ran djbdns for years, although it was on a xen VPS slice in a datacenter, not in my home.
The information you file with your domain registrar includes at least two IP addresses (which can be the same) and names (which must be different) for the primary name resolvers for your domain. The registrar communicates those to the right upstream layer - in the case of .com, that means a query to a.gtld-servers.net asking for an NS record for example.com will get a response with your DNS server’s name (perhaps a.ns.example.com or ns1.example.com) as well as a “glue” answer (in the same response) of an A record that defines the IP address for that name. Any recursive resolver will then ask your server for the subdomain records.
You can update records on your nameserver at any time, but you’re subject to some delays in updating those glue records and it’s not automated, so you really don’t want them to be dynamic addresses.
It gets more complicated with DNSSEC.