11–20 of 24 posts
I think ReadMe's approach is pretty good, and I applaud them for making the move.
Our aim is a bit different from others, as we focus exclusively on "actual" on-premises (local virtual machines), as opposed to "on someone else's premises" (AWS).
[1] http://blog.unscramble.co.jp/post/128610241043/production-re...
Here at Coveralls.io we can't recommend Replicated enough. We were able to migrate our internally-developed, Github Enterprise style packaged VM delivery approach over to their system in a couple weeks. But I'd say the real value is in not needing to support an additional deployment platform -- their Docker based approach is like Heroku for on-prem, it abstracts the infrastructure details and just works.
One difference is that I decided to stick with a raw Docker container rather than going with Replicated (who are really nice people, don't get me wrong). In my case, everything runs on a single horizontally-scaled server so it's pretty easy to get running "manually". Also, all the potential customers I asked said that they were comfortable managing their own Docker environment, and some would actually prefer to get Docker images since they'd be easier for them to manage than "virtual appliance" VMs.
Another difference was that I use Firebase for the app's datastore and Google doesn't (and likely never will) offer an on-premises version. This was a show-stopper for nearly all customers, but it turned out that offering at-rest encryption of sensitive data with a key that never leaves their premises was sufficient to get through many of the security reviews. This obviously won't be acceptable to everyone but it can be useful to know that even if you have a fundamental dependency on an external third-party service there may be a way to keep using it in your "on-premises" product.
I recently made an on-premises version of https://reviewable.io . I'd like to second most everything said in the article: use a flag, remove SaaS dependencies where possible, otherwise convert to use standardized services (SMTP) or apps that they can deploy internally as well (Sentry). It took me rather longer than a week but the ROI was still excellent. One difference is that I decided to stick with a raw Docker con…
Can we trade customers? Last year I've had to install our software in a CentOS 5.5 system. With no root access. Can't say compiling Python 2.7 and all that crap to run on a user account was much fun, but hey, at least they're billable hours.
Large, and especially public, companies seem to be the worst. SMBs were happy to receive a VM or OpenVZ image.
Another shootout to replicated, the service mentioned to go from SaaS to on-premise. We are using it for our own offering at Enthought, and can't recommend it enough either. Good support, reactive to customer feedback. I wish more companies were like that
I recently made an on-premises version of https://reviewable.io . I'd like to second most everything said in the article: use a flag, remove SaaS dependencies where possible, otherwise convert to use standardized services (SMTP) or apps that they can deploy internally as well (Sentry). It took me rather longer than a week but the ROI was still excellent. One difference is that I decided to stick with a raw Docker con…
Quick edit: That's vertical scaling if you have a single server that you make bigger.
I recently made an on-premises version of https://reviewable.io . I'd like to second most everything said in the article: use a flag, remove SaaS dependencies where possible, otherwise convert to use standardized services (SMTP) or apps that they can deploy internally as well (Sentry). It took me rather longer than a week but the ROI was still excellent. One difference is that I decided to stick with a raw Docker con…
> single horizontally-scaled server Quick edit: That's vertical scaling if you have a single server that you make bigger.
Here at Coveralls.io we can't recommend Replicated enough. We were able to migrate our internally-developed, Github Enterprise style packaged VM delivery approach over to their system in a couple weeks. But I'd say the real value is in not needing to support an additional deployment platform -- their Docker based approach is like Heroku for on-prem, it abstracts the infrastructure details and just works.
I can't find any details on Replicated pricing, is it reasonable? It seems like a product which would be nigh impossible to replace once installed at a customer site (making the customer do anything risks cancellations).