You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@oclef thanks, I feel a bit stoopid right now maybe its due to me coding all way and switching between js, php and python but where do I put my aws keys in.. ?
Also I just saw this when trying to deploy the latest parse example..
2016-02-09T01:36:19.232819+00:00 app[web.1]: > [email protected] start /app
2016-02-09T01:36:19.232821+00:00 app[web.1]: > node index.js
2016-02-09T01:36:19.232822+00:00 app[web.1]:
2016-02-09T01:36:20.517814+00:00 app[web.1]: /app/index.js:21
2016-02-09T01:36:20.517819+00:00 app[web.1]: filesAdapter: new S3Adapter(
2016-02-09T01:36:20.517820+00:00 app[web.1]: ^
2016-02-09T01:36:20.517821+00:00 app[web.1]:
2016-02-09T01:36:20.517823+00:00 app[web.1]: at Object.<anonymous> (/app/index.js:21:21)
2016-02-09T01:36:20.517822+00:00 app[web.1]: ReferenceError: S3Adapter is not defined
2016-02-09T01:36:20.537757+00:00 app[web.1]: npm ERR! Linux 3.13.0-71-generic
2016-02-09T01:36:20.517823+00:00 app[web.1]: at Module._compile (module.js:413:34)
2016-02-09T01:36:20.517824+00:00 app[web.1]: at Object.Module._extensions..js (module.js:422:10)
2016-02-09T01:36:20.517825+00:00 app[web.1]: at Module.load (module.js:357:32)
2016-02-09T01:36:20.517826+00:00 app[web.1]: at Function.Module._load (module.js:314:12)
2016-02-09T01:36:20.517826+00:00 app[web.1]: at Function.Module.runMain (module.js:447:10)
2016-02-09T01:36:20.517827+00:00 app[web.1]: at startup (node.js:139:18)
@oclef Looks useful. Did you consider making a pull request? I haven't tried to incorporate ParsePushAdapter which I just looked into, but this looks easier.
Activity
oclef commentedon Feb 9, 2016
You can set the FilesAdapter to use S3Adapter when you initialize the ParseServer like this
gateway commentedon Feb 9, 2016
@oclef thanks, have you tested it and do pffile saves go to s3 and a reference url goes in the database?
oclef commentedon Feb 9, 2016
Yes, I've tested. files goes to s3 and reference goes to mongo
gateway commentedon Feb 9, 2016
@oclef thanks, I feel a bit stoopid right now maybe its due to me coding all way and switching between js, php and python but where do I put my aws keys in.. ?
Also I just saw this when trying to deploy the latest parse example..
gnz00 commentedon Feb 9, 2016
@gateway You need to import the S3Adapter.
oclef commentedon Feb 18, 2016
An adapter I wrote to use AWS SNS as the push server. I've since setup my
own push server so I don't use it anymore. You can find it here
https://github.com/oclef/parseServer
Cheers,
Phong Le
On Thu, Feb 18, 2016 at 3:45 AM, Michael Bina [email protected]
wrote:
Predestination was doomed from the start.
michaelbina commentedon Feb 18, 2016
@oclef Looks useful. Did you consider making a pull request? I haven't tried to incorporate ParsePushAdapter which I just looked into, but this looks easier.
oclef commentedon Feb 18, 2016
Actually, this is what you will want to use
https://github.com/oclef/parse-server/tree/f2c6cc829927e084fb0a695c30ab701f1c923860
On Thu, Feb 18, 2016 at 3:45 AM, Michael Bina [email protected]
wrote:
Predestination was doomed from the start.
michaelbina commentedon Feb 18, 2016
Looks like it was forked a bit behind 2.0.8 so it's gonna take some merging.
oclef commentedon Feb 18, 2016
It worked, but it doesn't really conform with the architecture. TBH, it's better to just setup your own push server using the latest release.
gfosco commentedon Feb 20, 2016
S3 docs now available here: https://github.com/ParsePlatform/parse-server/wiki/Storing-Files-in-AWS-S3