Skip to main content

Handle File Upload with Express and Multer

Express undoubtedly has become a popular framework for building web applications based on Node.js. It is shipped with support for handling file uploading using middleware that takes the user requests, parses the contents for the files, and provides the next handler with the files information. The following snippet shows a basic example of handling files uploading in Express using Multer.

const multer = require('multer');

const storage = multer.diskStorage({
  destination: (req, file, cb) => {
    // store files to "uploads/" directory
    cb(null, 'uploads/');
  },
});

const upload = multer({ storage });

// initiate an upload handler that can accept multiple fields and multiple files
const uploadHandler = upload.fields([
  { name: 'galleryImages', maxCount: 10 }, 
  { name: 'userFiles', maxCount: 2 },
]);

app.post('/upload', uploadHandler, (req, res) => {
  res.json(req.files);
});

The sample above can be used if we just want to store our files in the disk storage of our server. If we want to store it somewhere else, for example in the cloud storage, we can perform an additional action after we get the files information from req.files object.

If we want a more uncomplicated solution, without a need for additional action for managing files manually, we can look for a custom Multer storage engine in the NPM repository that aligns with our intention. In our common use cases for building web-based applications, we usually store the files in the cloud, especially in the object storage that is compatible with S3 protocols, to decouple our application with the storage. Then, we oftentimes need to resize some image files to be more optimized to be displayed on the web like for the thumbnails.

In that scenario, we can utilize my library named multer-object-storage which provides a storage engine that can handle both disk storage and S3-compatible object storage uploading. Besides, it can handle image resizing before the uploading process ensued. The following snippet shows how to configure this storage engine to store files both on disk and object storage.

require('dotenv').config();
const express = require('express');
const multer  = require('multer')
const { ObjectStorage } = require('multer-object-storage');
const app = express();
const port = 3000;

const storage = new ObjectStorage({
  
  // optional: set file name generator 
  filename: function (req, file, cb) {
    cb(
      null,
      Math.ceil(Math.random() * 10000) + file.originalname,
    );
  },

  // optional: set destination directory for disk saving 
  destination: function (req, file, cb) {
    cb(null, 'uploads/');
  },

  // optional: set list of image resize options, based on Sharp resize options
  resize: function (req, file, cb) {
    cb(null, {
      // set allowed image mime-types that can be resized
      mimeTypes: ['image/jpg', 'image/jpeg', 'image/png'], 
      options: [
        {
          width: 200,
          height: 150,
          // by default, file name will be appended by string with format "w{width}-h{height}"
          fileNameTail: 'thumb', 
        },
        {
          width: 300, // height will be auto based on image ratio
        },
      ],
    });
  },

  // optional: set S3-compatible object storage credentials
  bucket: function (req, file, cb) {
    cb(null, {
      name: process.env.BUCKET_NAME,
      endpoint: process.env.BUCKET_ENDPOINT, // include protocol, eg. https://sgp1.digitaloceanspaces.com
      accessKeyId: process.env.BUCKET_ACCESS_ID,
      secretAccessKey: process.env.BUCKET_SECRET_KEY,
    });
  },
});

const upload = multer({ storage });

// allows 5 fields with name "image" and 2 fields with name "file"
const uploadHandler = upload.fields([{ name: 'image', maxCount: 5 }, { name: 'file', maxCount: 2 }]);

// send a multipart form-data that contains files to this endpoint
app.post('/upload', uploadHandler, (req, res) => {
  res.json(req.files);
});

app.listen(port, () => {
  console.log(`Listening on port ${port}`)
});

We can test the program above using Postman by sending a POST request with a multipart form-data payload to http://localhost:3000. We will get a result with a format that is similar to the following example.

// ...
"image": [
   {
      "fieldname": "image",
      "originalname": "my-image.jpg",
      "encoding": "7bit",
      "mimetype": "image/jpeg",
      "destination": "uploads/",
      "filename": "123-my-image.jpg",
      "path": "/path/to/uploads/123-my-image.jpg",
        "size": 111083,
        "url": "https://x.myspaces.com/123-my-image.jpg",
        "width": 669,
        "height": 562,
        "resize": [
          {
            "path": "/path/to/uploads/123-my-image-thumb.jpg",
            "url": "https://x.myspaces.com/123-my-image-thumb.jpg",
            "width": 200,
            "height": 150
          },
          {
            "path": "/path/to/uploads/123-my-image-thumb.jpg",
            "url": "https://x.myspaces.com/123-my-image-w300hauto.jpg",
            "width": 300,
            "height": null
// ...

We can read more on its documentation on the repository page.


Comments

Popular posts from this blog

Increase of Malicious Activities and Implementation of reCaptcha

In recent time, I've seen the increase of malicious activities such as login attempts or phishing emails to some accounts I manage. Let me list some of them and the actions taken. SSH Access Attempts This happened on a server that host a Gitlab server. Because of this case, I started to limit the incoming traffic to the server using internal and cloud firewall provided by the cloud provider. I limit the exposed ports, connected network interfaces, and allowed protocols. Phishing Attempts This typically happened through email and messaging platform such as Whatsapp and Facebook Page messaging. The malicious actors tried to share a suspicious link lured as invoice, support ticket, or something else. Malicious links shared Spammy Bot The actors leverage one of public endpoint on my website to send emails. Actually, the emails won't be forwarded anywhere except to my own email so this just full my inbox. This bot is quite active, but I'm still not sure what...

Configuring Swap Memory on Ubuntu Using Ansible

If we maintain a Linux machine with a low memory capacity while we are required to run an application with high memory consumption, enabling swap memory is an option. Ansible can be utilized as a helper tool to automate the creation of swap memory. A swap file can be allocated in the available storage of the machine. The swap file then can be assigned as a swap memory. Firstly, we should prepare the inventory file. The following snippet is an example, you must provide your own configuration. [server] 192.168.1.2 [server:vars] ansible_user=root ansible_ssh_private_key_file=~/.ssh/id_rsa Secondly, we need to prepare the task file that contains not only the tasks but also some variables and connection information. For instance, we set /swapfile  as the name of our swap file. We also set the swap memory size to 2GB and the swappiness level to 60. - hosts: server become: true vars: swap_vars: size: 2G swappiness: 60 For simplicity, we only check the...

Deliver SaaS According Twelve-Factor App

If you haven't heard of  the twelve-factor app , it gives us a recommendation or a methodology for developing SaaS or web apps structured into twelve items. The recommendation has some connections with microservice architecture and cloud-native environments which become more popular today. We can learn the details on its website . In this post, we will do a quick review of the twelve points. One Codebase Multiple Deployment We should maintain only one codebase for our application even though the application may be deployed into multiple environments like development, staging, and production. Having multiple codebases will lead to any kinds of complicated issues. Explicitly State Dependencies All the dependencies for running our application should be stated in the project itself. Many programming languages have a kind of file that maintains a list of the dependencies like package.json in Node.js. We should also be aware of the dependencies related to the pla...

Kenshin VS The Assassin

It is an assassin versus assassin.

Handling PDF Generation in Web Service

If we are building a website that requires a PDF generation feature, there are several options for implementing it based on the use cases or user requirements. First, we can generate the PDF on the client side using any available client library. It is suitable if the use case is to print out some data that is already available inside certain website components, and we want to maintain the styles of the components in the document. Second, we can do it fully in the back-end using any library available, such as PDF-lib, jsPDF, and so on. This approach is suitable if we want to keep the data processing or any related business functions in the back-end server. This second approach might have disadvantages, such as the difficulty of maintaining the design assets and styles which are already on our website. Third, it is using a hybrid approach, where certain processes are handled on the client side, and some are handled on the back-end. In this post, I want to discuss more about the...

Free Cloud Services from UpCloud

Although I typically deploy my development environment or experimental services on UpCloud , I do not always stay updated on its announcements. Recently, I discovered that UpCloud has introduced a new plan called the Essentials plan, which enables certain cloud services to be deployed at no cost. The complimentary services are generally associated with network components or serve as the foundation for other cloud services. This feature is particularly useful when retaining foundational services, such as a load balancer, is necessary, while tearing down all services and reconfiguring the DNS and other application settings each time we temporarily clean up infrastructure to reduce costs is undesirable.  When reviewing the service specifications of the cloud services in the Essentials plan, they appear to be very similar to those in the Development plan. The difference in service levels is unclear, but it could be related to hardware or resource allocation. For instance, the loa...