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

File Upload destination, database, and server. #158

Closed
TAProgramming opened this issue Feb 1, 2016 · 1 comment
Closed

File Upload destination, database, and server. #158

TAProgramming opened this issue Feb 1, 2016 · 1 comment

Comments

@TAProgramming
Copy link

From what I gather, the current file upload facility in Parse Server saves a file to Hosted Parse (the same way it always has been), however work is underway for it to be saved to Amazon S3 (with the gridstore adapter #113 ).
This is while my database is hosted somewhere else (eg mongolab) and my instance of Parse server is hosted in another place (eg heroku).
The cost and workload of having 3 separate hosting paths to maintain is a little extreme for small businesses like mine.
I have seen that Google Datastore is a proposed option for database implementation in #20 .
What I would like to see is perhaps the option or capability of having my File Storage, NoSQL Database and Parse Server all on Google services (Cloud Storage, Datastore, App Engine) for example.
This minimises cost and hassle on my part as a client developer with limited backend experience.
How feasible is this to be implemented within the phasing out year?
Thanks. :)

@gfosco
Copy link
Contributor

gfosco commented Feb 2, 2016

The default in parse-server is to store the files in GridStore, which is part of your Mongo installation. See GridStore.js. S3 has just been added as an adapter. We welcome other file adapters to support other use cases. I expect many to be added in the near future.

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

2 participants