You could always migrate to https://pagodabox.com/
PHP Fog to be discontinued on December 21st
41–50 of 59 posts
Re: PHP Fog to be discontinued on December 21st
#42Earlier quoted context omitted.
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...
That doesn't really seem to be about migrating, but about setting up an arbitrary php app with AppFog. Here's a few things that are wrong with it: * It assumes you have the directory locally. Can't it be downloaded from phpfog? * It doesn't say anything about copying environment variables. * It doesn't talk about making sure you have at least as much system resources. It should say how to find how much memory you had…
Please note: this is the first in a series of tutorials. This tutorial in particular is devoted solely to migrating application code. Tomorrow, we will post the first of two data migration tutorials that will walk users through the data migration process.
Re: PHP Fog to be discontinued on December 21st
#43I 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, Ruby, and other runtimes and deploy to a variety of infras.
AppFog is absolutely thriving right now and will be around for quite some time, we assure you.
Re: PHP Fog to be discontinued on December 21st
#44I 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.
[deleted]
Re: PHP Fog to be discontinued on December 21st
#45Earlier quoted context omitted.
AppFog is just as simple and way more powerful too.
But will WP work without a persistent file system? Doesn't that mean you can't upload pictures to your posts?
AppFog does not currently support persistent file systems, but we're working hard on adding this feature. In the meantime, we strongly recommend Amazon S3 as a persistent file store.
Re: PHP Fog to be discontinued on December 21st
#46A bit of a positive note here, I found that PHP Fog was more difficult to use than AppFog. I had some higher-level issues with Apache on the PHP version of AppFog that I brought up and were quickly addressed. It might sting now, but those that used PHPFog might like AppFog more.
You're right. I think people need to give AppFog a chance.
Once they do something like, for example, cloning an app in Singapore and re-deploying it in Ireland in less than a minute, they'll see the value in what we've built.
Re: PHP Fog to be discontinued on December 21st
#47Earlier quoted context omitted.
That doesn't really seem to be about migrating, but about setting up an arbitrary php app with AppFog. Here's a few things that are wrong with it: * It assumes you have the directory locally. Can't it be downloaded from phpfog? * It doesn't say anything about copying environment variables. * It doesn't talk about making sure you have at least as much system resources. It should say how to find how much memory you had…
Please note: this is the first in a series of tutorials. This tutorial in particular is devoted solely to migrating application code. Tomorrow, we will post the first of two data migration tutorials that will walk users through the data migration process.
I know, I know. It's all that was available at the time this was announced, a little over a month before free accounts are scheduled to be shut down. Some people are probably already migrating.
Is it true that appfog's filesystem is volatile? Does this mean that it could be wiped without a system fault or a user shutting down the system? If so, there doesn't seem to be a clear migration path to appfog for PHP users that are using the writable directory support. If not, it should probably be documented that writes will only go to the one instance and that if you're using multiple app server instances you need to set something up.
Re: PHP Fog to be discontinued on December 21st
#48This 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…
What are business hours when you are a developer platform used by developers globally?
Re: PHP Fog to be discontinued on December 21st
#49Other than dotCloud, what are some other PHP as a platform competitors?
We have plenty of PHP users on BitNami Cloud bitnami.org/cloud
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.
Re: PHP Fog to be discontinued on December 21st
#50Earlier quoted context omitted.
We have plenty of PHP users on BitNami Cloud bitnami.org/cloud
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 AWS infrastructure: CloudWatch, CloudFormation, Beanstalk, etc.