Skip to content

Can I continue use Parse SDK after migrating Parse to my own hosting? #381

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

Closed
yeahio-coltd opened this issue Jan 31, 2016 · 5 comments
Closed

Comments

@yeahio-coltd
Copy link

Hello,

As the title said, I wonder if I can continue use Parse SDK.
If yes, what should I do to point my apps to new hosting?

@egorvas
Copy link

egorvas commented Jan 31, 2016

Yeah +1. Would like to see method Parse.server() such as in JS library

@ghost
Copy link

ghost commented Feb 1, 2016

Yeah you can use it with your own Parse Server hosting, just create the initialization like this:

Parse.Configuration configuration = new Parse.Configuration.Builder(this)
                .applicationId("Your Application ID")
                .clientKey("Your Client Key")
                .server("Your Server Url")
                .build();
Parse.initialize(configuration);

Note that your server url should end in / like http://localhost:1337/parse/ and you should have defined an client key inside your server file.

@yeahio-coltd
Copy link
Author

Yes, this works. But I have another issue when migrating my existing Parse backend to my own backend. I have photos on Parse, but after migrating to my own backend, the photo field is changed to url (string). I am not sure if my photos were moved to my backend or not. Any ideas?

@ghost
Copy link

ghost commented Feb 1, 2016

There is a long discussion about the ParseFile , at this moment there is no migration for the files hosted on Parse and that's why you have an URL.

@grantland
Copy link
Contributor

Thanks for stepping in @iulianvarzaru! I'll be closing this as resolved.

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

3 participants