Submitted by katir on Sat, 02/28/2015 - 15:46 Pro Licensee
We are planning to migrate 9 domains from a dedicated server to Digital Ocean Cloud "Droplets" (Ubuntu 14.04) There is a strong case for putting some of these on their own "Droplet" -- our current VirtualMin license allows for 10 domains -- I am about to renew, which will happen before migration. Would my current license this cover installation on the different cloud instances, as long as the total aggregate of domains being managed is<=10?
Or do you have to pay for installation on each server?
Status:
Active
Comments
Submitted by andreychek on Sat, 02/28/2015 - 15:54 Comment #1
Howdy -- the current pricing is per-server.
You would need multiple Virtualmin licenses in the case you're describing.
We have been discussing a way to have one license cover domains across multiple servers, though we unfortunately don't have such a license yet.
However, if you're looking at buying multiple Virtualmin Pro licenses, we'd be happy to give you a free Cloudmin for Physical Systems license if you like, which can make managing multiple Virtualmin systems easier.
If you have several Virtualmin systems, Pro or GPL, it can provide a single place where you can go to perform sysadmin tasks, perform upgrades, access backups, run commands, and the like.
Feel free to let us know if you have any additional questions!
Submitted by katir on Sat, 02/28/2015 - 16:15 Pro Licensee Comment #2
OK... Since the minimum price is for 10 domains... so if we took these 9 domains apart and ran them on three separate cloud instances.. then that will be $145.00 (my current license will renew at $45.00 for 10 plus two new ones)
OK understood. And thanks for the CloudMin for Physical Systems offer to manage them... I need to keep working out a business plan. Digital Oceans HD space is a little low for our needs and I am loath to complicate the framework by creating offsite buckets for media... so I have some business planning to do.
Does CloudMin help with use cases like... e.g
current framework
/home/somedomain/public_html/media -- has lots of big files, infrequently accessed but immediately available to the CMS because it is in the DOCROOT (code simply creates paths $_SERVER_DOCROOT &/media/someaudio file)
where we might want to move that content to another machine, it gets complicated.
Submitted by andreychek on Sat, 02/28/2015 - 16:23 Comment #3
Using Cloudmin, you can move a Virtual Server from one server to another. Is that what you're asking?
If you have some large files that you want to store on a different machine, but you want to keep the main domain where it is -- you could always create a new sub-domain on one of your servers for that, and use that new sub-domain for serving those larger files.
Submitted by katir on Sat, 02/28/2015 - 16:36 Pro Licensee Comment #4
Actually I think you answer two questions:
1) Yes, if Cloudmin can help move a Virtual Server from one server to the other that would be fantastic! I usually do it all by hand and it is very painful and nerve-wracking.. I will definitely talk to you more about that in the days ahead.
2) No, sub-domain is not what I was looking for. The idea that someone here had was to configure Ubuntu so that a remote S3 bucket could "masquarade" as a mounted volume on the web server, so the the web server file system would see the directory structure as local.
http://www.maketecheasier.com/mount-amazon-s3-in-ubuntu/
But I get nervous when looking at the set up and config required... it looks highly vulnerable to failure... customizations deep in the guts of the OS on the box are not my style... in the end it can cost you more in support fees than it would cost to just pay for another 200GB of local HD space...We are not talking about huge amts of data here... but Digital Oceans pricing plans are very shy on Disk space. e.g. 16GB ram and 8 core is plenty processing power for us, but the 120 GB SSD drive that comes with that plan is not big enough... but I don't need terrabytes of more space... just another 300 GB would do... and it looks like overkill to start getting into CDN for such small amount of data (small by my standards...)
A subdomain may be better, easier to configure and not dependent on OS config on the web server... a little mod_rewrite magic and it could work...