undefined | Better HN

0 pointsbenatkin13y ago0 comments

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 with phpfog to make sure you have enough with appfog.

* It doesn't cover data migration.

* Even without covering data migration, it could at least have covered migrating the database configuration, but it doesn't.

* It leaves with an appfog domain name. It should say how to switch them.

* Too much of the post is devoted to going through AppFog's features.

* It has some cheesy marketing for AppFog like "af-plus-php-equals-win" and "Lots more functionality where that came from".

I don't think I could bring myself to call it a migration tutorial.

0 comments

luc_perkins13y ago

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.

benatkinOP13y ago

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.

j / k navigate · click thread line to collapse