You can have 'reliable' storage that is managed by a company.You can easily access your files from ALL of your web servers.This service lets you store all of your files in a central location. Instead: what you should do is use a file storage service (usually Amazon S3) to store your files in a central location. This can lead to confusing / odd behavior where each webserver has a copy of the same file(s), etc. The reason why is that disk space is limited. If your application writes files to your webserver disk, it won't scale very much. The reason Heroku does this is because they try to force you to write scalable software. Heroku's filesystem is EPHEMERAL, this means that you should treat it like it doesn't exist. On Heroku, you can indeed write files to the filesystem, but they will DISAPPEAR after a short period of time. Here's where things are going to get complicated for a moment. This will correctly write your file into the images folder like you want. Instead, you want to write to: Request(uri).pipe(fs.createWriteStream(_dirname+'/public/images/'+filename)).on('close', callback) ), you're trying to write to a non-writable part of Heroku's filesystem. If this code is running in your app.js, it means that by going BACK a folder (eg.
Now, in your code pasted above, you show: Request(uri).pipe(fs.createWriteStream(_dirname+'/./public/images/'+filename)).on('close', callback) Heroku puts all your code into a folder called app. So, on Heroku's filesystem, this means your project looks like this: /app In your case, your code is running in app.js, which is in the 'root' folder of your project. On Heroku, you can't write to the folder BELOW the root of your project. You just have the wrong path in your project.
0 kommentar(er)
