Skip to content

PARSE_SERVER_FILES_ADAPTER no longer works. #1659

Closed
@5amfung

Description

@5amfung

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!

Environment Setup

Running 2.2.7.

Steps to reproduce

  1. According to instructions, set PARSE_SERVER_FILES_ADAPTER to ./Files/S3Adapter.js as env variable and other env S3_ACCESS_KEY, S3_SECRET_KEY and S3_BUCKET accordingly.
  2. 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"
    }
  ],

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions