5 ms·
They were probably our (Virtualmin) biggest user for a few years. They used the Open Source version so we didn't see much revenue from it (occasionally their us
by SwellJoe 7y ago
They were probably our (Virtualmin) biggest user for a few years. They used the Open Source version so we didn't see much revenue from it (occasionally their users would upgrade to the commercial version), but they sponsored a few Solaris-related features in Virtualmin/Webmin and sent us patches now and then. The shared hosting stuff that used Virtualmin was TextDrive, and once they moved to container-based products they stopped including a control panel at some point (and they're container management stuff didn't use our tools for that), so we lost touch with them.
Edit: It's also how Twitter used Virtualmin in their early days, as they were hosted at Joyent. (I didn't know this until Evan Williams told me at a YC event. That was pretty cool.)
- jmarneweck 7y agoEvan was a lifetimer. Twitter's mail was routed via one.textdrive.com if memory serves me correctly using a truck load of aliases to redirect to offsite email accounts. It was a pleasure dealing with the Virtualmin team on issues we had on Virtualmin on Joyent and TextDrive's shared hosting services. Replying to the "Wins over GCE/AWS above that I can't reply to": They had various: * The ability to run workloads at near bare metal speeds (their using Solaris Containers). * Manta (ability to perform compute operations on their storage service without having to download files and reupload files). * Their work on getting a better user experience in zones with pkgsrc (thanks to all the hard work of Filip and Jonathan). * Better performance and having the ability to spend less money on resources and reducing the instance count for folks moving off AWS to Joyent. I was involved in a number of these migrations.
- Nux 7y agoThat's a nice bit of trivia! Had no idea Twitter started on Virtualmin at Joyent.