Skip to content

History / Migrating an Existing Parse App

Revisions

  • Updated Migrating an Existing Parse App (markdown)

    @drew-gross drew-gross committed Feb 24, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @drew-gross drew-gross committed Feb 24, 2016
  • Add links to landing pages.

    @hramos hramos committed Feb 24, 2016
  • Add ObjectRocket to migration guide.

    @hramos hramos committed Feb 23, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 23, 2016
  • Recommend a testing against as DB snapshot.

    @drew-gross drew-gross committed Feb 22, 2016
  • We have schemas!

    @drew-gross drew-gross committed Feb 22, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 22, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 22, 2016
  • Revert be9fcd86fdd72d0579fcd1e8bb8606eefeeb39d7...baeca35b68b31a16581d43a5bae855042469c072 on Migrating an Existing Parse App

    @hramos hramos committed Feb 22, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 22, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 22, 2016
  • Move supported/unsupported list from README to wiki.

    @hramos hramos committed Feb 22, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 19, 2016
  • Updated Migrating an Existing Parse App (markdown)

    James Yu committed Feb 11, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 6, 2016
  • Updated Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 6, 2016
  • Created Migrating an Existing Parse App (markdown)

    @hramos hramos committed Feb 5, 2016