Parse is shutting down soon and having a deadline for Database Migration 28th April 2016.
Currently I still have 2 production apps that is live on parse.com, but due to some tight schedule, I am afraid that I won't able to complete my parse database migration on time. Is there any way that can keep my app traffic prioritize even after the due date 28th April 2016?
I can't find any contact to Parse Support Team, that's why I'm asking the question here.
Thank you.
https://github.com/ParsePlatform/parse-server/wiki/Migrating-an-Existing-Parse-App
28th April 2016 is the RECOMMENDED date for migrating to self hosted MongoDB.
Just migrate the database. You don't need to migrate everything now. You have more time to do it. I will explain you supposing you will migrate to https://www.back4app.com
After the migration, both parse.com dashboard, back4app.com dashboard, https://api.parse.com and https://parseapi.back4app.com will be connecting to the same recent migrated database in back4app servers. It means that parse.com api and dashboard will keep working and the same data will also be available both in parse.com and back4app.com.
Therefore until the date you publish the new app connecting to parseapi.back4app.com, all your current customers will keep connecting to api.parse.com that will connect to the migrated database in the back4app servers. Everything will be working fine.
Then you have to test and prepare all your app and once you are comfortable you publish the new version of your app. When published, your clients will start updating their apps. The updated ones will be connecting to back4app.com and others to parse.com. But everything will be working fine because it is the same database.
The scenario described above will work until Feb 2017 and that's why it is important to start the migration process and then the publishing of the new app as soon as possible. So your clients will have more time to update their apps.
Related
I've built an internal app that is used only for the organization. The app works fine - it has a form which users fill in and save. It works for few hours that the form is stored in the database, but after a few hours the database is seemingly purged and the app shows no data - as if it's been started for the first time. I checked the log, but couldn't find anything. What and where can I check to find out what's going on? Could it be the case that since I'm using free heroku, it restarts after 24 hours.
I'm trying to downgrade a heroku postgres db from standard to hobby basic. As I'm not fully using the web app currently but there is still some data in there that needs to be kept. How can I downgrade? (some downtime is fine).
Update: managed to setup and promote a new database based on the inststructions below, but i can't deprovision the old one.
heroku info shows:
Heroku's instructions for upgrading with pg:copy will also work for downgrading. Here's the summary:
Provision a new database
Enter maintenance mode to prevent database writes
Transfer data to the new database
Promote the new database
Exit maintenance mode
If your app isn't live (not being actively written to), you can skip the maintenance mode steps.
Once you've done that, you can deprovision your old database.
I'm working to revive an app that was originally hosted on Parse. I have access to a Bitbucket with the app code but the database itself was not migrated before Parse.com shut down. I would like to run the app through Parse Server (using mlab and heroku) but all documentation I've found online requires use of the Parse migration tool (Which is no longer available).
I understand that I can use the Parse Server example project on github and paste in my own app code to set up my app. Do I do paste in my code before or after deploying to Heroku/mlab? Also, which files should I keep from the parse-server-example and which should I delete? Are there other steps I should be aware of that become necessary without access to the Parse migration tool?
Unfortunately you can't migrate your database off of the Parse.com hosted service after January 30th, 2017.
Since you don't have a database to migrate, you can start a new Parse Server project from scratch. You can just follow the Getting Started With Heroku + mLab Development steps on the parse-server-example project, and add any existing cloud functions to the /cloud directory once you've cloned the project.
As a server rookie and Parse user, I need to migrate and I intend to migrate to Parse Server, likely with Heroku and mLab.
Once I have clicked Migrate and Finalise in the Parse Dashboard, all data from my original Parse client code goes to the new database, right?
Once migrated, I can just push an update of my client code with the new Parse Server SDK pointing to the new server?
My main over ruling question is do I need to do any management on the client side, sending data to both servers? Or does Parse migration handle this?
I think you are mixing two different things. Read the tutorial
Simply
Step 1
You should move your data from Parse.com to self hosted database (mLab or mongoDB and more...), this step means that api.parse.com will use the "external" database but you will still use the code and server from Parse.com (when you send query to your app it goes to api.parse.com and than it access the database) - do this till end of April 2016
Step2 move from api.parse.com to your own instance of Parse server (the one you download from github or install it on heroku). You will need change you code in your app because it wont use api.parse.com fro mthis point... - till end of July 2016
On github the developers still say that it is not "production ready". You should only migrate your database and build the whole server later. You can read the discussion here
I want to understand how people are handing an update to a production app on the Parse.com platform. Here is the scenario that I am not sure about.
Create an called myApp_DEV. The app contains a database as well as associated cloud code.
Once testing is complete and ready for go-live I will clone this app into myApp_PRD (Production version). Cloning it will copy all the database as well as the cloud code.
So far so good.
Now 3 months down the line I want have added some functionality which includes adding some cloud code functions as well as adding some new columns to the tables in the db.
How do I update myApp_PRD with these new database structure. If i try to clone it from my DEV app it tells me the app all ready exists.
If I clone a new app (say myApp_PRD2) from DEV then all the data will be lost since the customer is all ready live.
Any ideas on how to handle this scenario?
Cloud code supports deploying to production and development environments.
You'll first need to link your production app to your existing cloud code. this can be done in the command line:
parse add production
When you're ready to release, it's a simple matter of:
parse deploy production
See the Parse Documentation for all the details.
As for the schema changes, I guess we just have to manually add all the new columns.