Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse is Bandwidth throttling non migrated apps from April 28th - But how do I add jobs & cloudcode to my migrated db? #1356

Closed
hjgabrielsen opened this issue Apr 4, 2016 · 6 comments

Comments

@hjgabrielsen
Copy link

Do I have to code everything from scratch myself?

As you all know Parse is Bandwidth throttling non migrated apps from April 28th - But how do I add jobs & cloudcode to my migrated db?

Does anyone have a working solution to this,

Right now I have :

DB
Cloudcode
Jobs running every 15 minutes..

Thats it..

@jon1010hill
Copy link

Hi

As long as you have migrated your database you shouldn't be throttled. You have some more time to move the application.

If you do not migrate your database by April 28, we will assume you do not consider the app's migration to be a high priority. Traffic to your app may be de-prioritized as we shift our focus to serving production apps that are being migrated according to our recommended schedule."

@hjgabrielsen
Copy link
Author

Yeah, i know,- but can I control my remote DB from parse panel? w/ cloudcode etc.. ?

@tanmays
Copy link

tanmays commented Apr 4, 2016

Also you should consider beginning to migrate as soon as you can. Follow the migration tutorial to get DB and CloudCode working on your self hosted parse server.

As for jobs, they are not supported by parse-server yet because of the sheer number of options available. A particular solution might work better on a particular hosting service, so its up to the developer to choose the best one that fits well with his setup.

I've been using Kue and Cron-Cluster module to add in background jobs and cron support, you may want to check that.

@flovilmart
Copy link
Contributor

@hjgabrielsen the parse.com dashboard will continue working with the migrated database, so you don't have to disrupt your workflow, the jobs, cloud code etc... will all keep working correctly.

@flovilmart flovilmart reopened this Apr 4, 2016
@UnlikelySassou
Copy link

Interesting info. I thought you had to use the open source dashboard as soon as you've migrated your database. So as long as we're still hitting api.parse.com (and not our own Parse Server instance), the data shown in Parse.com dashboard will sync perfectly, correct?

@flovilmart
Copy link
Contributor

That's right!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants