Meteor-files: Can't find Google cloud keyFilename location

[Spanomaly]

I'm having an issue with using the Google cloud upload on production.
In the demo code, for keyFileName we add a path to our Google cloud key.json. That works fine on my local dev machine, but I can't figure it out once the app is compiled and deployed on production with mup.

If on my dev machine, my key is at /server/key.json

How does that translate to a file location on a deployed production machine?

[dr-dimitru]

Hello @Spanomaly ,

Use /private directory, it is stale.
From the docs:

All files inside a top-level directory called private/ are only accessible from server code and can be loaded via the Assets API. This can be used for private data files and any files that are in your project directory that you don’t want to be accessible from the outside.

[Spanomaly]

Thanks @dr-dimitru , that works great.

[nikhilgoswami]

{ Error: ENOENT: no such file or directory, open meteor/local/private/googleStorageJson.json'
W20180829-19:10:30.627(5.5)? (STDERR) errno: -2,
W20180829-19:10:30.627(5.5)? (STDERR) code: 'ENOENT',
W20180829-19:10:30.627(5.5)? (STDERR) syscall: 'open',
W20180829-19:10:30.628(5.5)? (STDERR) path: '/.meteor/local/private/googleStorageJson.json' }

path for keyFilename: '../../../private/googleStorageJson.json'
keyFilename: '/googleStorageJson.json'
also dont work

Is there something I am missing?

[dr-dimitru]

@nikhilgoswami obviously the path is wrong. Try meteor-root package to define absolute path.

[nikhilgoswami]

This worked for me thanks

[dr-dimitru]

@nikhilgoswami glad it helped

Please, support this project by:

• Star on GitHub
• Star on Atmosphere
• Check other packages we have made
• Share on Facebook and Twitter
• Donate via PayPal