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.

Sign up for GitHub

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

Jump to bottom

REFINERY_DATA_IMPORT_DIR is not set correctly on AWS #1139

Closed
hackdna opened this issue May 17, 2016 · 1 comment
Closed

REFINERY_DATA_IMPORT_DIR is not set correctly on AWS #1139

hackdna opened this issue May 17, 2016 · 1 comment
Assignees
@drj11
Labels
bug cloud critical deployment server
Milestone
Upton

Comments

@hackdna
Copy link
Member

hackdna commented May 17, 2016

Current value in config.json.erb is hardcoded to /vagrant/import. It should something like /data/import (similar to MEDIA_ROOT).
@hackdna hackdna added this to the Upton milestone May 17, 2016
@drj11
Copy link
Contributor

drj11 commented May 17, 2016

On it.

FWIW I've grepped the config.json on a live AWS instance and there don't seem to be any more mentions of vagrant:

$ grep vagrant ./config/config.json
  "REFINERY_DATA_IMPORT_DIR": "/vagrant/import",

@drj11 drj11 mentioned this issue May 17, 2016
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@drj11 drj11

Labels
bug cloud critical deployment server
Projects
None yet
Milestone
Upton
Development

No branches or pull requests
2 participants
@hackdna @drj11