Description
Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
- You've met the prerequisites.
- You're running the latest version of Parse Server.
- You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
Running 2.2.7.
Steps to reproduce
- According to instructions, set
PARSE_SERVER_FILES_ADAPTER
to./Files/S3Adapter.js
as env variable and other envS3_ACCESS_KEY
,S3_SECRET_KEY
andS3_BUCKET
accordingly. - Parse.File is still saved to mongodb instead of S3.
Now that S3Adapter is moved to an external package parse-server-modules/parse-server-s3-adapter. I'm guessing PARSE_SERVER_FILES_ADAPTER
is no longer correct in the documentation. I don't see any mention in the README of enabling S3 using env variable neither. It would be nice to have PARSE_SERVER_FILES_ADAPTER
continue to work as I only enable S3 on staging and production. Other development environments are default to storing to mongodb.
Logs/Trace
No error from log. Log shows that the file was saved.
For example
"photos": [
{
"__type": "File",
"url": "http://localhost:1337/files/myAppId/e35f8f0f4bbd2d1b8c83a250f0fd0172_image.png",
"name": "e35f8f0f4bbd2d1b8c83a250f0fd0172_image.png"
}
],