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.

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

Invalid bucket name #10

Open
cyberrspiritt opened this issue Jul 13, 2017 · 5 comments
Open

Invalid bucket name #10

cyberrspiritt opened this issue Jul 13, 2017 · 5 comments

Comments

@cyberrspiritt
Copy link

cyberrspiritt commented Jul 13, 2017

I've deployed the project over lambda and found that it is not able to read SOURCE_BUCKET and UPLOAD_BUCKET variables defined in .env file.

@IvanDreamer
Copy link

@cyberrspiritt Did you find a solution?

@cyberrspiritt
Copy link
Author

No I have not

@IvanDreamer
Copy link

@cyberrspiritt to fast-fix it instead to get in from .env I wrote it straight to optimizer.js

Second issue with logs permissions: to fix it you should rewrite paths
from:

var processedLog = './processed.log'; // file containing all precessed files
var skippedLog = './skipped.log'; // file containing all skipped files
var markerFile = './.marker'; // file containing current file marker

to:

var processedLog = '/tmp/processed.log'; // file containing all precessed files
var skippedLog = '/tmp/skipped.log'; // file containing all skipped files
var markerFile = '/tmp/.marker'; // file containing current file marker

@cyberrspiritt
Copy link
Author

Thanks. this works. Although im not able to set variables from env file

@grandadmiralmcb
Copy link

Try setting the variables in the lambda environment itself as a workaround

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

3 participants