51–59 of 59 posts
I would encourage App Fog to offer a "fully managed" migration option, even if it's for a token fee.
This sucks. But actually, I'm glad to hear it. Over the past 2 weeks (since we upgraded matchist to a PHP Fog dedicated server), their support team has basically dropped off the face of the earth. Their support live chat disappeared. Their phone number goes to voicemail. And there's no way to get a hold of them other than their ticketing system (which they respond to every few days if you're lucky). I loved PHP Fog w…
I'm very sorry to hear about your experience with our support team over the past few weeks. While there have been some changes to live chat we are still available via phone during business hours depending on volume and are highly responsive with tickets (hours turnaround if not quicker on average). Was there a particular ticket I can review for you to see what happened? I want to make sure we don't drop the ball here…
But regarding the business transition over at App Fog, you know what's really strange: Why does the 'dead simple' migration process start with creating a new account? Isn't it the same company? At the very least, if I were in charge of AppFog I wouldn't make everyone sign up again. Just saying.
Signing up for AppFog
First things first: score yourself a free AppFog account at console.appfog.com. It’s the same thing we’ve all done a million times: e-mail, password, and then e-mail verification.
Personally I will give AppFog a try. If you're the sort of person who liked PHP Fog, the alternatives are not THAT great. Here's a good roundup from last month: But regarding the business transition over at App Fog, you know what's really strange: Why does the 'dead simple' migration process start with creating a new account? Isn't it the same company? At the very least, if I were in charge of AppFog I wouldn't make…
Earlier quoted context omitted.
The problem with BitNami Cloud is that they are AWS only and the pricing model is highly opaque. You pay once for Bitnami and then AGAIN for AWS. According to AppFog's pricing you pay only one source, namely us and never Amazon or Rackspace or HP or anyone else, and pricing is solely RAM-based, which means that it's next to impossible to incur costs that you don't actively choose.
I don't get why you claim the pricing is opaque. If anything, it is completely transparent because we do not add any markup whatsoever to the AWS charges, so in most cases it will result in a much lower monthly bill. Regarding it being AWS-specific, Bitnami Cloud Hosting is, but the rest of the BitNami offering and images is available for other clouds such as Azure and HP. We also integrate well with the rest of the…
But the problem is that AWS pricing itself is not completely transparent. It's based on usage, which means that the bill at the end of the month can end up being an unpleasant surprise, as it has been for lots and lots of AWS users over the years. Who can know in advance what their usage figures will be?
RAM-based pricing means that the bill at the end of the month literally cannot be a surprise. We have four available plans, and monthly bills map directly and seamlessly onto those plans.
We run on AWS (among others) but WE pay AWS, not our customers, because we think that part of the mission of PaaS is to shield customers from the many disparate pricing models on different IaaS providers. Want to run on Rackspace via AppFog? Same price. Want to run on HP? Same price. Azure? Same price.
PaaS needs to abstract hardware away completely, even monetarily. Paying IaaS providers directly is not the way to do that.
Earlier quoted context omitted.
I don't get why you claim the pricing is opaque. If anything, it is completely transparent because we do not add any markup whatsoever to the AWS charges, so in most cases it will result in a much lower monthly bill. Regarding it being AWS-specific, Bitnami Cloud Hosting is, but the rest of the BitNami offering and images is available for other clouds such as Azure and HP. We also integrate well with the rest of the…
I totally get that, and no markup above and beyond AWS pricing seems like the way to go. But the problem is that AWS pricing itself is not completely transparent. It's based on usage, which means that the bill at the end of the month can end up being an unpleasant surprise, as it has been for lots and lots of AWS users over the years. Who can know in advance what their usage figures will be? RAM-based pricing means t…
Argh. PHPFog was my goto place for self-hosting Wordpress blogs, is AppFog as simple?
As a current customer since 7/11 (over a year) I am SHOCKED they aren't working on automating a process to migrate over to AppFog. I guess they don't want my business - off to heroku and/or ec2.
John, I am so sorry for the inconvenience, we are working on some tools to make the process easier, but for now here is a tutorial: http://blog.phpfog.com/2012/11/12/migrating-your-php-apps-fr...
You have my cc on file, a semi-happy customer and now you want me to do all this work? YOU should be doing all the work for the migration - think of it as a way to maintain revenue!!!!
I think the solution is to find another service. How can I trust appfog after this terrible surprise? Tomorrow I will receive an email. We are very sorry but appfog will be dicontinued.
AppFog is absolutely NOT being discontinued! We are incredibly proud of what we accomplished with PHP Fog, but we think that the AppFog is the true future of PaaS: polyglot and poly-infrastructure. We simply don't think that single-language PaaS on a single infrastructure is the future, and we're working on rolling all of the functionality from PHP Fog into AppFog, where you'll be able to deploy Node, Java, Python, R…