In the world of hosting, “Green Hosting” seems to have a variety of definitions that sometimes include using renewable energy sources but in general means being more environmentally friendly. iNode Cloud servers are hosted at the Equinix datacenter in Sydney which has been designed by green in mind. Here are three reasons iNode Cloud hosting equates to Greener Hosting: 1. Less physical space = smaller data centers = less industrial building. Because of the higher densities of cloud server models, the overall data center structure can be smaller, requiring less land space taken up and less building materials to be used in construction. 2. Fewer physical servers. Allocating a physical server for every project need obviously requires quite a few resources to be consumed during the manufacturing process of the hardware. Some of these materials are recyclable, but not all, and even then just because something is recyclable doesn’t mean it’s ideal to consume those resources in the first place. iNode Cloud servers greatly reduces the need for hardware production, as multiple projects can exist on a single cloud server. 3. Lower power use. Data centers use a lot of power. I’ve read criticism of data centers by environmentalists – and that’s justified to an extent – especially with older data centers that haven’t been updated and are less efficient. iNode Cloud servers consume only a small portion of the power that a physical dedicated hosting server requires. Utilization of our cloud server hosting is a much more efficient model for power consumption, whether utility provided or renewable. More information can be found at the Equinix Website If you want a greener...

Cloud computing is the future of hosting. Find out what you need to know about Public, Private & Hybrid Cloud Computing with this Infographic guide from inodecloud.com. If you like it, share it or leave us a...

Before starting iNode Cloud, I have been with Crazy Domain, Go Daddy and various other hosting companies only to be offered bad service and slow and inconsistent downtimes and there’s no shortage of web hosting companies that do this, Hence why i decided to start iNode Cloud. Sometimes web hosts have technical problems or make mistakes, but when should you stick it out and when should you cut your losses and move on? Here are the top six signs your web host isn’t up to the job. 1. Your website is flaky and keeps going down No surprises here. If your website is unavailable or keeps throwing up errors, visitors will leave and not come back. Unless you’re offering something unique or already have a loyal following, this can kill your website in a very short time. Overloaded servers and inadequate networks are likely causes of problems with your web host. Sometimes a web hosting company will start strong but get progressively worse as it gains more customers; a victim of its own success. To be fair, it’s not always the fault of the web host. If your site is making unreasonable demands like using huge amounts of memory or processing time, there’s going to be trouble. Ideally, your web host will notice and prompt you to upgrade to a package with higher limits. The best ones will cover you if you get a sudden burst of traffic from the front page of Digg, and ask you to upgrade if it becomes a habit. Having too much traffic is a good problem to have, but if your site is not scaling, you should look...

MySQL Replication is incredibly simple to get up and running and this post will instruct you through it. Simple Master -> Slave Replication MySQL allows you to build up complex replication hierarchies, such as multi-master, chains of read slaves, backup databases at a remote site or any combination of these. This article focuses on a simple single master to single slave setup. This article also assumes that 2 MySQL Servers have been installed but that there is no existing data in the master that needs to be copied to the slave – it’s not complex to add that extra requirement and it will be covered in a future post. Server “masterhost” (192.168.0.31) is to be our master and “slavehost” (192.168.0.34) the slave. Step 1: Edit the configuration files & start the MySQL Servers The first step in setting up replication involves editing the “my.cnf” file on the servers that will serve as the master and slave. A default is provided with the MySQL installation but in case there is already a production MySQL database running on these servers, we provide local configuration files “master.cnf” and “slave.cnf” that will be used when starting up the MySQL servers. At a minimum we’ll want to add two options to the [mysqld] section of the master.cnf file: log-bin: in this example we choose inodecloud-bin.log server-id: in this example we choose 1. The server cannot act as a replication master unless binary logging is enabled. The server_id variable must be a positive integer value between 1 to 2^32 master.cnf: [mysqld] server-id=1 log-bin=black-bin.log datadir=/home/inode/mysql/master/data innodb_flush_log_at_trx_commit=1 sync_binlog=1 Note: For the greatest possible durability and consistency in...

If you’re a developer or work in IT, you’ve likely heard of Docker. It’s a 3 year old open source technology that has grown exponentially during its existence. And now, it’s beginning to turn heads in even the most regulated industries. First let’s explore what Docker actually is for those that are unfamiliar. “Docker is an open platform for developers and sysadmins to build, ship, and run distributed applications,” according to the Docker website. The technology consists of two tools, the Docker Engine and the Docker Hub. The Docker Engine is a, “portable, lightweight runtime and packaging tool,” while Docker Hub is a, “cloud service for sharing applications and automating workflows.” The technology is particularly appealing for developers because it is now easier than ever to make sure you develop, test and deploy using the same environment as your colleagues, resulting in less issues caused by differences or missing libraries. Docker also offers developers the flexibility to quickly run their apps anywhere, whether its on laptops, VMs or QA servers. More simply put, “Docker helps developers build and ship higher-quality applications, faster.” Sysadmins are finding the technology useful as well, because of the ability to standardize development environments among other reasons. “Docker helps sysadmins deploy and run any app on any infrastructure, quickly and reliably.” Docker seems to be on the same disruption path as GitHUB, which shook the source control systems, or more lately, how composer “revolutionized” the way we deploy components of a PHP and Symfony application. On the business side, the benefits may be huge. By simplifying the way we deploy apps and creating more manageable...