Ian
My feedback
5 results found
-
21 votes
An error occurred while saving the comment -
88 votes
An error occurred while saving the comment Ian
commented
Use Cloudflare for DNS, it's free, distributed, and VERY fast. They even have a free tier for CDN which works well for many sites.
Cloudflare has a great control panel that makes it very easy to change your MX records and point them to Google. It will take just a few minutes to set up.
It's always a great idea to have your DNS separate from your Registrar and Host (which should also be separate!) as it makes it a lot easier to change hosts or registrars should it be necessary.
An error occurred while saving the comment Ian
commented
This isn't really necessary or even possible. If you'd like Google Apps you can go to Google and purchase the number of users you need.
Set up your DNS to direct your incoming mail to Google and you're mostly done.
For best results add some domain aliases to make user login easier and set up mail authentication with Google.
-
84 votes
An error occurred while saving the comment Ian
commented
Amazon has been expanding Lightsail availability to more datacenters. It would be great to add this option to Cloudways!
Ian
supported this idea
·
-
23 votes
Cloudways
responded
Can you give us an example on how you would use this within the context of Cloudways service?
Cloudways Team
An error occurred while saving the comment Ian
commented
I would like this feature as well.
I use Cloudways because it allows me to very quickly create & destroy applications within a server, and because the configurations and upgrades are all managed by you guys instead of me. For many servers this makes perfect sense and I am happy to pay the premium for a Cloudways server to make this possible. It saves me time and I never have enough time.
However sometimes I need to run something that you guys don't yet offer, such as Elasticsearch 5.4, and I need to be able to access that from a Cloudways application. I have this exact scenario happening right now.
I only need to access the Elasticsearch server from the Cloudways application. I have set up the Elasticsearch server in the Tokyo VULTR datacenter and have set up the firewall rules so the ES port can only be accessed from my Cloudways server. Unfortunately because I don't have a private IP on my Cloudways server I have to use the public IPs for this when really it should be done with the private IPs. Using private IPs doesn't use the bandwidth allocation and is also a better thing to do from a security standpoint if external access is not necessary. Using private IPs should result in somewhat lower latency as well, something that is important for a service like Elasticsearch.
Even with having multiple Cloudways servers this would be a benefit as users could run some services on one Cloudways server and other services on another Cloudways server resulting in much better performance for higher traffic sites.
Ian
supported this idea
·
-
47 votesIan
supported this idea
·
Everyone looking at this, check out Thirty Bees which is now available on Cloudways. It's a fork of PS 1.6.1.x that fixes a huge number of PS bugs and has wildly better performance than PS 1.6 ever had. Many PS modules are fully compatible, others need minor changes. Same for themes. Development is ongoing and the community is growing!