Mr_Tom
Mr_Tom
Comments
-
Been considering doing some writing, so might be able to put something together. The mail server idea sounds interesting. I have ran my own for a number of years.
-
I used to use pine directly on the mail server years ago but I use Thunderbird pretty much on all PCs now.
-
Yeah that was more my point. The feature list if good, but at the current price I would expect the majority of the "upcoming" features to be already done.
-
I recently spoke with them regarding billing integration, and they suggested that there would be the option to use SolusIO as a platform for billing, which would be nice, but that board would seem to suggest it's not happening. There's a lot on there that should be done already as they're classing it as "ready" now it…
-
Didn't know about that one! That one might come in handy as they're currently using SES for order emails anyway.
-
I can help with Frankfurt if required.
-
Congrats on the new locations! Will hopefully be looking into some services there soon!
-
I think that's a mirror URL - you can just use https://test-ipv6.com/
-
It probably should be monitored if it's part of the package, but due to cost they might just be reliant on clients reporting issues with it - or their monitoring failed. I would say it's probably not uncommon for them to ask you to make sure it's not your site that has the issue before they investigate. I've had that…
-
You can do it apache style and create a site config for each site in /etc/nginx/sites-available and then create a symlink for each "active" site into sites-enabled. Then in your nginx.conf file just add include /etc/nginx/sites-enabled/*; In each of the sites own config file, you can then include any specific additional…
-
I think if they're offering redis across the server for all shared accounts then perhaps it should be monitored, but it depends on price. If it's cheap hosting, they might just monitor the server/port 80/etc directly and see addons like redis as low priority and just wait for users to report issues.
-
Edit - sorry, these should be inside the server {} block for the SSL section only - otherwise you'll be sending them for HTTP requests too. Either putting them in the block directly, or including another file is fine. I have a security.conf file which has these in and is included in the server {} block as required - but I…
-
Mine are setup inside the http {} block, but before the server {} blocks. These should be in the server {} block for the listen 443 ssl; server only to avoid sending them on http requests. They're actually in another file that's included by nginx.conf, but they could go direct into nginx.conf
-
Depends on the service. If it's an unmanaged VPS, then it's your issue. If it's managed it's theirs. If it's on a shared hosting platform, it's probably their issue but they will often assume its your issue if no one else is seeing issues.
-
I believe Ant's offer shows 1 IPv4 on the form, but my NL got deployed with 2.
-
Would https://prologic.github.io/tube/ be suitable? Not sure on the storage side of it though.
-
Surely it's cheap... being LES and all...
-
Nice offer, picked one up. Not a bad shout that.