// archives


This tag is associated with 24 posts

ClouSE 1.0 is generally available

OblakSoft is pleased to announce general availability of the Cloud Storage Engine for MySQL (ClouSE) version 1.0.  Whether you want to use ready-to-run WordPress for Amazon Cloud / Google Cloud, configure your own WordPress installation with WP2Cloud plugin, or use ClouSE to deploy your own applications, ClouSE lets you tap the power of cloud storage to store your data extremely durably and make serving the content highly scalable.

We would like to thank more than 2,000 registered Beta users and early adopters who helped us to deliver a compelling feature set with outstanding quality.  After months of rigorous Beta testing and live production use (e.g. www.ecoustics.com has been running on ClouSE for more than a year) we believe that the product is ready for commercial use.

To get to generally available version 1.0 from the Beta we’ve implemented a couple of major features: (more…)

Stop Heartblead in WordPress to Cloud

If you’re running a WordPress to Cloud instance you may be affected by the heartdbleed bug. You are not alone (it’s estimated that the bug affects 66% of the Internet), but you need to take action to protect your website. Fortunately, it’s very easy to do with Webmin or command line.


OblakSoft Cloud Storage Engine Newsletter, June 2013

ClouSE 1.0b.1.8 is released

OblakSoft is pleased to announce the release of ClouSE Beta version 1.0b.1.8.  This is a minor maintenance release that addresses a couple pain points, while we’re working on a release candidate that will bring the built-in point-in-time recovery and other major features.

Here is the summary of changes:

MySQL on Cloud Storage: ClouSE upgrade made easy

Updating ClouSE can now be done with one command

With more than a thousand registered users worldwide, guiding customers through the upgrade process is getting hard, so we decided to automate the servicing steps.  Now the update-clouse script can be used to update ClouSE binaries to the current version.  This script ships with the ClouSE binary distribution.

Here is an example of updating ClouSE using the Webmin console.

WordPress on S3: DNS and HTTPS configuration

Getting a WordPress-on-S3 website up and running is a piece of pie with our step-by-step guide, but making the website live requires a couple more pieces of the puzzle to fit together.

Today I’m going to talk about configuring DNS and HTTPS for WordPress on S3. DNS stands for Domain Name System and it is the technology that makes it possible to use friendly names for web sites. HTTPS stands for Hypertext Transfer Protocol Secure and it is the technology that makes secure connections possible.


MySQL on Cloud Storage: do it yourself with one command

Cloud Storage Engine (ClouSE) installation and configuration is now fully automated. Try new ClouSE installer and you’ll have cloud storage access configured in no time.

OblakSoft is pleased to announce the release of Cloud Storage Engine (ClouSE) installer that can be used to deploy and configure ClouSE with your MySQL server. Now ClouSE can be deployed with just one command. The installer will guide the user through the configuration process, prompt for Cloud Storage connection parameters, and install ClouSE into MySQL.

Presented is a step-by-step guide for ClouSE installation and configuration, from downloading the binaries to running the installer. The guide was designed by request of WordPress-to-Cloud users, however it is fully applicable to any generic ClouSE installation.

The slides have notes, they are a little hard to discover with the SlideShare interface, look for a tab below the slide that looks like “Notes on Slide #”.

WordPress on S3: do it yourself from Artem Livshits

Let us know how we can further streamline cloud adoption for your MySQL applications.

OblakSoft Cloud Storage Engine Newsletter, March 2013

ClouSE 1.0b.1.7 is released

OblakSoft is pleased to announce the release of Cloud Storage Engine (ClouSE) for MySQL Beta version 1.0b.1.7.  In this release we added support for a variety of environments to address the platform diversity of our growing customer base.

Here is the summary of changes that are included into 1.0b.1.7:

WordPress on S3: going pro

WordPress-on-S3 makes professional website administration as easy as pie.

OblakSoft is pleased to announce availability of the ready-to-run WordPress-on-S3 / Yapixx AMI with enhanced configuration, performance, and website administration features.  Now website owners can use Webmin and phpMyAdmin for secure website administration over the Internet, and pre-configure Cloud Storage Connection for the instance.


WordPress on Google Cloud Storage: step-by-step

By popular demand, here is the step-by-step guide for configuring WordPress with Google Cloud Storage.

The slides have notes, they are a little hard to discover with the SlideShare interface, look for a tab below the slide that looks like “Notes on Slide #”.

WordPress on S3: how to prevent hotlinking

Now that you use Amazon S3 to store and serve media files in scalable fashion, how would you prevent undesirable hotlinking to your files?

Hotlinking to cloud storage URLs

Hotlinking (or direct linking, inline linking) is when other sites link to or embed the image (or other media file, e.g. video) directly without providing a link to the source page. Oftentimes hotlinking happens without meaning any harm: people just want to share a picture with their Facebook friends, or post it to forums they like or etc. Regardless of intention, though, hotlinking may be harmful to your business: the media file gets downloaded from your site and consume the bandwidth that you pay for, but the user doesn’t get to see your page depriving you of ad revenue, etc.

With WordPress-to-Cloud solution all media files are stored in the cloud storage such as Amazon S3. Now it is the cloud storage (and not your web server) that serves the images and other media files. Even though this approach reduces load on your web server and hotlinking is unlikely to cause scalability problems, you are still paying for the bandwidth.



Twitting ...