Skip to content

PARSE_SERVER_FILES_ADAPTER no longer works. #1659

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
3 tasks done
5amfung opened this issue Apr 27, 2016 · 7 comments
Closed
3 tasks done

PARSE_SERVER_FILES_ADAPTER no longer works. #1659

5amfung opened this issue Apr 27, 2016 · 7 comments

Comments

@5amfung
Copy link

5amfung commented Apr 27, 2016

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"
    }
  ],
@thibauddavid
Copy link

According to readme , you should set filesAdapter: "parse-server-s3-adapter"in index.js

@thibauddavid
Copy link

@StephenWilson This is not an alternative way to do it, readme specifies Set your environment variables: blablabla **And** update your config / options

@5amfung
Copy link
Author

5amfung commented May 6, 2016

@Tibabal So the instruction on the wiki page is outdated?

@thibauddavid
Copy link

@5amfung Seems so, yes... @gfosco could you update the wiki (linked above) specifying filesAdapter: "parse-server-s3-adapter" must be added in index.js ?

@mmeester
Copy link

so it's not possible anymore to set it up with environment variables?

@5amfung
Copy link
Author

5amfung commented May 10, 2016

I guess not. I created a new env variable and set it to parse-server-s3-adapter when I want files going to S3. But of course, you have to set S3_ACCESS_KEY and all those as well.

var api = new ParseServer({
  // ...
  filesAdapter: process.env.FILES_ADAPTER || undefined
});

@flovilmart
Copy link
Contributor

Closing due to lack of activity, please update to latest parse-server version and reopen if the issue persist.

Don't forget to include your current:

  • node version
  • npm version
  • parse-server version
  • any relevant logs (VERBOSE=1 will enable verbose logging)

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

4 participants