How Cloudfuji (S11) uses Cloud Foundry to make open source Apps big business

http://blog.cloudfoundry.com/2012/06/07/cloudfuji-accelerates-delivery-of-its-open-source-application-store-with-cloud-foundry/

by sgrove • 14 years ago

59 16 14 years ago

blog.cloudfoundry.com

jasontraff• 14 years ago

Love these guys and the work they're doing!

seltzered_• 14 years ago

Love what you're doing, but I couldn't figure out how to export my fatfreecrm data in case I ever have to move away from cloudfuji. Is there a way to do this?

sgrove5• 14 years ago

There isn't a standard way right now, though we'd be happy to add that in! In the most manual case, we can give you any kind of database export you'd like.

Our goal is to make the data for a user owned by the user - so when you move from Fat Free CRM to Salesforce, your data follows you without any special config at all.

If anyone contacts us for a data export right now, we'll take care of it ourselves and send it over :)

shykes6• 14 years ago

Cloudfoundry is really intriguing to me. On the one hand cf-based vendors point out the awesome acceleration effect of many companies contributing to a common codebase. Yet they all emphasize their unique value-add compared to vanilla cf and everyone else - which they do by maintaining a private fork and not contributing back upstream. Aren't these 2 things mutually exclusive and slightly hypocritical?

sgrove5• 14 years ago

We're not a Cloud Foundry company, we really don't care about PaaS that much. We just needed something that fit our unique use case and that, in case the PaaS vendor didn't feel the same sense of urgency that we did for something we need, we could add in ourselves - I'm sure you're very familiar with that, Solomon. We're happily sending changes upstream whenever they're sufficiently high quality for everyone else.

So, 1.) We didn't want to (poorly) re-invent it ourselves, and 2.) We didn't find any existing provider that was able to match our schedule and needs. Cloud Foundry let us side-step both of those problems and launch. We'd be dead by now if we had waited.

shykes6• 14 years ago

Hi shrove, thanks for the precision. You have a point - you're tackling a particular edge case in deployment which most paas providers are neglecting, leaving you vulnerable to shifting priorities in their roadmap. It makes sense for you to take your destiny into your own hands, so to speak.

My question was triggered by your article but not particularly targeted at you - I was hoping to start a philosophical conversation on the pros and cons of running a business on top of IP which you don't own. So far I don't see any takers ;)

wattersjames2• 14 years ago

Solomon, wait, just 2 days ago you said CF was throw away code and not on your radar? Care to explain your pivot to 'intriguing'?

https://twitter.com/solomonstre/status/209895170194423808

shykes6• 14 years ago

Hi James, in this tweet I'm referring to phpfog, which has been publicly deprecated (the polite term for "throwing away the code") in favor of a cloudfoundry deployment. Not necessarily a bad move in their situation... but yes, as a result it is not a very fearsome contender in the paas market.

johnx123-up• 14 years ago

Is custom domain possible? I heard that CF doesn't support custom domain.

sgrove5• 14 years ago

Yup, custom domains are possible on Cloudfuji, because we're running the vast majority on Cloud Foundry OSS, which does support custom domains.

CloudFoundry.com doesn't support custom domains yet while it's in beta, but I'm sure it's on its way and should be available as they make their way out of beta.

How Cloudfuji (S11) uses Cloud Foundry to make open source Apps big business

Related Stories