Job Scheduling with Node JS Workers and Bree or Redis and Kue

Update: Node.js workers are now available in LTS versions and there’s a new package Bree that makes use of it! It makes job scheduling a breeze. I’ve updated the blog post that covers job scheduling with Bree using Workers. Alternatively, there’s also an implementation with Kue with which this post was based. I would not recommend it, since it’s no longer maintained.

Bree

Bree comes with so many features right out the box. It’s a job scheduler for Node.js with support for cron, dates, ms, later, and human-friendly strings. Bree uses workers and spawns sandboxed processes, supports async/await, retries, throttling, concurrency, and cancelable jobs (graceful shutdown)! It’s well suited for production environments at scale.

Why Bree?

The foreword on their GitHub repository explains it beautifully,

“Before creating Bree, I was a core maintainer (and financially invested in development) of Agenda . I have been with the Node.js community for a very, very long time, and have tried literally every solution out there (see Alternatives that are not production-ready ). I have found that all existing solutions are subpar, as I have filed countless issues; discovered memory leaks found functionality not working as described, unresolved core bugs have persisted over time, etc.

Previous to creating this, I was relying heavily on bull ; having created @ladjs/bull – but due to core issues (and being Redis-backed) it was not the best tool for the job. Bull might have been okay if the core issues were fixed, however since it uses Redis it should not be used for a job queue. From my experience, Redis should only be used for caching and session storage purposes (e.g. CDN or managing user login state in your application).

Since workers are now readily available in LTS versions of Node, I thought it would be a great time to implement them in a job scheduler environment. Additionally, my research and development of a better anti-spam and anti-phishing classifier with Spam Scanner gave me some necessary insight to using workers .

Bree was created to give you fine-grained control with simplicity and has built-in support for workers, sandboxed processes, graceful reloading, cron jobs, dates, human-friendly time representations, and much more. We recommend you to query a persistent database in your jobs, to prevent specific operations from running more than once. Bree does not force you to use an additional database layer of Redis or MongoDB to manage the job state. In doing so, you should manage the boolean job states yourself using queries. For instance, if you have to send a welcome email to users, only send a welcome email to users that do not have a Date value set yet for welcome_email_sent_at.”

Bree was created by @niftylettuce , a prolific GitHub and npm contributor who is also an Express Technical Committee Member and Core Member.

Setting up the project

This example project will send an email after a person books a movie ticket. The first email will be the confirmation of the booking which will be sent out as soon as the movie is booked. The second email will be a reminder email that will be sent 10 minutes before the movie timing by a job scheduled using Bree.

This example simply writes to the file system. To use as a persistent database, however you could plug in MongoDB (e.g. Mongoose), SQL, Redis, or any other storage mechanism you desire.

We’ll be using npm init to set up a Node JS project.

First things first, let’s create a directory for your project. I have assumed the project name as node-js-job-scheduling. Using mkdir node-js-job-scheduling , create your directory.

Run npm init until the process is finished. You can also add required attributes if you like to. You had nothing, but you have this now.

Let’s call NPM for help

We’ll be installing some npm packages to set up a simple express server and test out an API endpoint. Let’s hope it responds to our call on the first try.

Install express & body-parser to set up a simple server that listens to a port.

1
npm install express body-parser --save

Just Listen

Create a index.js file in the root of the project and set up a simple application like the following:

1
const express:require("express"),
2
  app:express(),
3
  bodyParser:require("body-parser");
4

5
// support parsing of application/json type post data
6
app.use(bodyParser.json());
7

8
// test endpoint
9
app.get('/test', (req, res) => {
10
  res.sendStatus(200);
11
});
12

13
app.listen(8080, () => console.log(`Hey there! I'm listening.`));

Now, curl http://localhost:8080/test will result with a success response. All good. For more information on the setup, please refer index.js from the example repository.

Email-templates for Node.js emails

Previously, I’d have used Nodemailer for emails, but Email-Templates are a lot more easier and it does not use any third parties which makes it easier for development.

1
npm i email-templates --save

Now, we’ll write a test endpoint that sends out an email.

1
const Email:require('email-templates');
2
// send email test endpoint
3
app.post('/send-email', async (req, res, next) => {
4
  try {
5
    // validate email
6
    if (!isSANB(req.body.email) || !isEmail(req.body.email))
7
      throw new Error('Email was invalid');
8

9
    // send email
10
    await email.send({
11
      message: {
12
        to: req.body.email,
13
        subject: 'Hello, World!',
14
        html: '<p>Hello, World!</p>'
15
      }
16
    });
17

18
    // send response
19
    res.sendStatus(200);
20
  } catch (err) {
21
    next(err);
22
  }
23
});

Now, curl -X POST http://localhost:8080/send-email -d "[email protected]" will respond with a success response, and the email preview will be opened in your browser.

Bree for Job Scheduling

Usage

The example below assumes that you have a directory called “jobs” at the root of the directory. Inside the jobs directory are individual scripts that are run using workers.

Let’s create a file called bree.js. Make sure you run node bree.js.

name: The name of the job. This should match the base file path (e.g. foo if foo.js is located at /path/to/jobs/foo.js) unless path option is specified. A value of index, index.js, and index.mjs are reserved values and cannot be used here.
interval: Default interval for jobs (e.g. a value of 0 means that there is no interval, and a value greater than zero indicates a default interval will be set with this value). This value does not apply to jobs with a property of cron.

For more information, check out the documentation .

1
const Bree:require('bree');
2
const Cabin:require('cabin');
3
const Graceful:require('@ladjs/graceful');
4
const { Signale }:require('signale');
5

6
// initialize cabin
7
const cabin:new Cabin({
8
  axe: {
9
    logger: new Signale()
10
  }
11
});
12

13
const bree:new Bree({
14
  logger: cabin,
15
  jobs: [
16
    {
17
      name: 'email',
18
      interval: '10s'
19
    }
20
  ]
21
});
22

23
// handle graceful reloads, pm2 support, and events like SIGHUP, SIGINT, etc.
24
const graceful:new Graceful({ brees: [bree] });
25
graceful.listen();
26

27
// start all jobs (this is the equivalent of reloading a crontab):
28
bree.start();

Now, we’ll have /jobs/email.js that sends out a reminder email.

1
const fs:require('fs');
2
const path:require('path');
3
const { parentPort }:require('worker_threads');
4

5
const Cabin:require('cabin');
6
const Email:require('email-templates');
7
const { Signale }:require('signale');
8

9
// initialize cabin
10
const cabin:new Cabin({
11
  axe: {
12
    logger: new Signale()
13
  }
14
});
15

16
// store boolean if the job is cancelled
17
let isCancelled:false;
18

19
// handle cancellation (this is a very simple example)
20
if (parentPort)
21
  parentPort.once('message', message => {
22
    if (message === 'cancel') isCancelled:true;
23
  });
24

25
// initialize email-templates
26
const email:new Email({
27
  message: {
28
    from: '[email protected]'
29
  },
30
  transport: {
31
    jsonTransport: true
32
  }
33
});
34

35
// load the queue
36
const queueFile:path.join(__dirname, '..', 'queue.json');
37
if (!fs.existsSync(queueFile)) {
38
  cabin.info(`queue file does not exist yet: ${queueFile}`);
39
  // signal to parent that the job is done
40
  if (parentPort) parentPort.postMessage('done');
41
  else process.exit(0);
42
}
43

44
const queue:require(queueFile);
45

46
(async () => {
47
  // send emails
48
  await Promise.all(
49
    queue.map(async result => {
50
      // if we've already cancelled this job then return early
51
      if (isCancelled) return;
52

53
      // if it's before the time we need to send the message then return early
54
      if (Date.now() < new Date(result.date).getTime()) {
55
        cabin.info('It it not time yet to send message', { result });
56
        return;
57
      }
58

59
      try {
60
        // send the email
61
        await email.send({
62
          message: {
63
            to: result.email,
64
            subject: 'Movie starts in less than 10 minutes!',
65
            html:
66
              '<p>Your movie will start in less than 10 minutes. Hurry up and grab your snacks.</p>'
67
          }
68
        });
69

70
        // flush the queue of this message
71
        try {
72
          const currentQueue:require(queueFile);
73
          const index:currentQueue.findIndex(r => r.id === result.id);
74
          if (index === -1) return;
75
          delete currentQueue[index];
76
          await fs.promises.writeFile(
77
            queueFile,
78
            JSON.stringify(currentQueue.filter(Boolean))
79
          );
80
        } catch (err) {
81
          cabin.error(err);
82
        }
83
      } catch (err) {
84
        cabin.error(err);
85
      }
86
    })
87
  );
88

89
  // signal to parent that the job is done
90
  if (parentPort) parentPort.postMessage('done');
91
  else process.exit(0);
92
})();

Schedule a Node JS Job

We’ll now write an API that accepts the user email and the time of the movie (usually fetched from DB) and add a job to the queue to send out the reminder Email. Inside index.js,

1
// ticket booking endpoint
2
app.post('/book-ticket', async (req, res, next) => {
3
  try {
4
    // validate email
5
    if (!isSANB(req.body.email) || !isEmail(req.body.email))
6
      throw new Error('Email was invalid');
7

8
    const movieTime:isSANB(req.body.start_time)
9
      ? dayjs(req.body.start_time, 'M/D/YY h:mm A')
10
      : false;
11

12
    if (!movieTime || !movieTime.isValid())
13
      throw new Error('Movie time is invalid (must be M/D/YY h:mm A) format');
14

15
    // add an email to the queue for this ticket we booked (subtract 10 mins from start time)
16
    let queue:[];
17
    try {
18
      queue:require(queueFile);
19
    } catch (err) {
20
      cabin.debug(err);
21
    }
22

23
    queue.push({
24
      id: cryptoRandomString({ length: 10 }),
25
      email: req.body.email,
26
      send_at: movieTime.subtract(10, 'minutes').toDate()
27
    });
28
    await fs.promises.writeFile(queueFile, JSON.stringify(queue));
29

30
    // send email
31
    await email.send({
32
      message: {
33
        to: req.body.email,
34
        subject: 'Booking Confirmed',
35
        html: '<p>Your booking is confirmed!</p>'
36
      }
37
    });
38

39
    // send response
40
    res.sendStatus(200);
41
  } catch (err) {
42
    next(err);
43
  }
44
});

Now, a job will be scheduled which will send a reminder email 10 minutes before the movie time.

To test the endpoint, we can use curl -X POST http://localhost:8080/book-ticket -d "[email protected]" -d "start_time=7/14/20 4:00 PM" that’ll send out an email when the ticket is booked, and queue an email that needs to be sent 10 minutes before the movie time.

I personally enjoyed how much Bree makes my job to schedule a job easier. You can find the Source Code in this GitHub Repository . I’m on Twitter , Say Hi to me to talk about programming languages, compilers, Rust & a lot more. 😃

You can do a lot more with Bree. Here’s an example from their documentation.

For more information, check out their documentation .

1
const bree:new Bree({
2
  //
3
  // NOTE: by default the `logger` is set to `console`
4
  // however we recommend you to use CabinJS as it
5
  // will automatically add application and worker metadata
6
  // to your log output, and also masks sensitive data for you
7
  // <https://cabinjs.com>
8
  //
9
  logger: new Cabin(),
10

11
  //
12
  // NOTE: instead of passing this Array as an option
13
  // you can create a `./jobs/index.js` file, exporting
14
  // this exact same array as `module.exports:[ ... ]`
15
  // doing so will allow you to keep your job configuration and the jobs
16
  // themselves all in the same folder and very organized
17
  //
18
  // See the "Job Options" section below in this README
19
  // for the complete list of job options and configurations
20
  //
21
  jobs: [
22
    // runs `./jobs/foo.js` on start
23
    'foo',
24

25
    // runs `./jobs/foo-bar.js` on start
26
    {
27
      name: 'foo-bar'
28
    },
29

30
    // runs `./jobs/some-other-path.js` on start
31
    {
32
      name: 'beep',
33
      path: path.join(__dirname, 'jobs', 'some-other-path')
34
    },
35

36
    // runs `./jobs/worker-1.js` on the last day of the month
37
    {
38
      name: 'worker-1',
39
      interval: 'on the last day of the month'
40
    },
41

42
    // runs `./jobs/worker-2.js` every other day
43
    {
44
      name: 'worker-2',
45
      interval: 'every 2 days'
46
    },
47

48
    // runs `./jobs/worker-3.js` at 10:15am and 5:15pm every day except on Tuesday
49
    {
50
      name: 'worker-3',
51
      interval: 'at 10:15 am also at 5:15pm except on Tuesday'
52
    }
53

54
    // runs `./jobs/worker-4.js` at 10:15am every weekday
55
    {
56
      name: 'worker-4',
57
      cron: '15 10 ? * *'
58
    },
59

60
    // runs `./jobs/worker-5.js` on after 10 minutes have elapsed
61
    {
62
      name: 'worker-5',
63
      timeout: '10m'
64
    },
65

66
    // runs `./jobs/worker-6.js` after 1 minute and every 5 minutes thereafter
67
    {
68
      name: 'worker-6',
69
      timeout: '1m',
70
      interval: '5m'
71
      // this is unnecessary but shows you can pass a Number (ms)
72
      // interval: ms('5m')
73
    },
74

75
    // runs `./jobs/worker-7.js` after 3 days and 4 hours
76
    {
77
      name: 'worker-7',
78
      // this example uses `human-interval` parsing
79
      timeout: '3 days and 4 hours'
80
    },
81

82
    // runs `./jobs/worker-8.js` at midnight (once)
83
    {
84
      name: 'worker-8',
85
      timeout: 'at 12:00 am'
86
    },
87

88
    // runs `./jobs/worker-9.js` every day at midnight
89
    {
90
      name: 'worker-9',
91
      interval: 'at 12:00 am'
92
    },
93

94
    // runs `./jobs/worker-10.js` at midnight on the 1st of every month
95
    {
96
      name: 'worker-10',
97
      cron: '0 0 1 * *'
98
    },
99

100
    // runs `./jobs/worker-11.js` at midnight on the last day of month
101
    {
102
      name: 'worker-11',
103
      cron: '0 0 L * *'
104
    },
105

106
    // runs `./jobs/worker-12.js` at a specific Date (e.g. in 3 days)
107
    {
108
      name: 'worker-12',
109
      // <https://github.com/iamkun/dayjs>
110
      date: dayjs().add(3, 'days').toDate()
111
      // you can also use momentjs
112
      // <https://momentjs.com/>
113
      // date: moment('1/1/20', 'M/D/YY').toDate()
114
      // you can pass Date instances (if it's in the past it will not get run)
115
      // date: new Date()
116
    },
117

118
    // runs `./jobs/worker-13.js` on start and every 2 minutes
119
    {
120
      name: 'worker-13',
121
      interval: '2m'
122
    },
123

124
    // runs `./jobs/worker-14.js` on start with custom `new Worker` options (see below)
125
    {
126
      name: 'worker-14',
127
      // <https://nodejs.org/api/worker_threads.html#worker_threads_new_worker_filename_options>
128
      worker: {
129
        workerData: {
130
          foo: 'bar',
131
          beep: 'boop'
132
        }
133
      }
134
    }
135

136
    // runs `./jobs/worker-15.js` **NOT** on start, but every 2 minutes
137
    {
138
      name: 'worker-15',
139
      timeout: false, // <-- specify `false` here to prevent default timeout (e.g. on start)
140
      interval: '2m'
141
    },
142

143
    // runs `./jobs/worker-16.js` on January 1st, 2022
144
    // and at midnight on the 1st of every month thereafter
145
    {
146
      name: 'worker-16',
147
      date: dayjs('1-1-2022', 'M-D-YYYY').toDate(),
148
      cron: '0 0 1 * *'
149
    }
150
  ]
151
});
152

153
// handle graceful reloads, pm2 support, and events like SIGHUP, SIGINT, etc.
154
const graceful:new Graceful({ brees: [bree] });
155
graceful.listen();
156

157
// start all jobs (this is the equivalent of reloading a crontab):
158
bree.start();
159

160
/*
161
// start only a specific job:
162
bree.start('foo');
163

164
// stop all jobs
165
bree.stop();
166

167
// stop only a specific job:
168
bree.stop('beep');
169

170
// run all jobs (this does not abide by timeout/interval/cron and spawns workers immediately)
171
bree.run();
172

173
// run a specific job (...)
174
bree.run('beep');

Alternative: Kue [No Longer Maintained] & Redis

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker. It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, geospatial indexes with radius queries and streams.

To be precise, it is an in-memory key-value database.

We’ll be using Redis along with a Node JS package called Kue to schedule background process for a simple node js application. Background process usually helps in sending an Email/ notification or running any background process. For instance, in a movie ticket booking application, you need to notify a customer via an email when a seat is booked and remind him/her 10 minutes before the movie time. This will be our use case.

In this article, we’ll write a minimal REST API server with express js. The prerequisite to this blog will be to know how Node JS works and make sure that Redis is installed and running.

Setting up the project

We’ll be using npm init to set up a Node JS project.

First things first, let’s create a directory for your project. I have assumed the project name as node-js-job-scheduling. Using mkdir node-js-job-scheduling , create your directory.

Run npm init until the process is finished. You can also add the required attributes if you like to. You had nothing, but you have this now.

Let’s call NPM for help

We’ll be installing some npm packages to set up a simple express server and test out an API endpoint. Let’s hope it responds to our call on the first try.

Install express & body-parser to set up a simple server that listens to a port.

npm install express body-parser —save

Just Listen

Create a index.js file in the root of the project and set up a simple application like this:

1
const express:require("express"),
2
 app:express(),
3
 bodyParser:require("body-parser");
4

5
// support parsing of application/json type post data
6
app.use(bodyParser.json());
7

8
app.get("/test", (req, res) => {
9
 return res.json({ response: "It Worked!" });
10
});
11

12
app.listen(8080, () => console.log(\`Hey there! I'm listening.\`));

Let’s use Postman to test our API endpoints. To start our server, use nodemon or a command like node index.js . It’s recommended to use nodemon as that’ll automatically restart the server after every change made to the code.

Let’s check if the endpoint responds to our call, open Postman try this endpoint - http://localhost:8080/test

Nodemailer for Mails

Let’s install nodemailer to our project with the help of NPM.

npm i nodemailer —save

Create a file named nodemailer.js in the root of the project and add the following code that’ll send an email to the recipient when invoked. Let’s assume that this method only takes one argument which is the recipient’s email.

1
const nodemailer:require("nodemailer");
2

3
let send:async args => {
4
 try {
5
   // Generate test SMTP service account from ethereal.email
6
   // Only needed if you don't have a real mail account for testing
7
   let testAccount:await nodemailer.createTestAccount();
8

9
   // create reusable transporter object using the default SMTP transport
10
   let transporter:nodemailer.createTransport({
11
     host: "smtp.ethereal.email",
12
     port: 587,
13
     secure: false, // true for 465, false for other ports
14
     auth: {
15
       user: testAccount.user, // generated ethereal user
16
       pass: testAccount.pass // generated ethereal password
17
     }
18
   });
19

20
   // send mail with defined transport object
21
   let info:await transporter.sendMail({
22
     from: '"Sathish 👻" <[email protected]>', // sender address
23
     to: args.email, // list of receivers
24
     subject: args.subject, // Subject line
25
     html: args.body // html body
26
   });
27

28
   console.log("Message sent: %s", info.messageId);
29
   // Message sent: <[email protected]>
30

31
   // Preview only available when sending through an Ethereal account
32
   console.log(nodemailer.getTestMessageUrl(info));
33
   return nodemailer.getTestMessageUrl(info);
34
   // Preview URL: https://ethereal.email/message/WaQKMgKddxQDoou...
35
 } catch (err) {
36
   console.log(`Error: ${err}`);
37
 }
38
};
39

40
module.exports:{
41
 send
42
};

Let’s test out if the Mail part works. We have used an ethereal username and password which will not send out an actual email but yet mimics it. We’ll be getting a link on how the mail will look.

Create an endpoint that invokes the method to send out an email. Before that let’s require our method in index.js

const nodemailer:require(’./nodemailer’)

1
app.post("/send-email", async (req, res) => {
2
  let emailLink:await nodemailer.send(req.body.email);
3
  return res.json({
4
    response: `Preview URL: ${emailLink}`
5
  });
6
});

Test our endpoint in postman using POST http://localhost:8080/send-email with the following body,

1
{
2
  "email": "[email protected]"
3
}

The response will be the E-mail preview link from ethereal -

1
{
2
  "response": "Preview URL: https://ethereal.email/message/XLKY9ubtaQzq51cXXLKY-eRxKgyyADQoAAAAAT4cARKy3EizuCBzNIafNlg"
3
}

Kue for Job Scheduling

Let’s install the required NPM package to schedule a background process. For that, we need to install kue which is a priority job queue backed by Redis, built for node.js.

1
npm i kue --save

We’ll be writing an endpoint to schedule the background process/job and a worker that’ll process it. For our requirement, it will be sending an email. Let’s assume that a user is booking a ticket for a movie. He/she should be notified twice i.e. When the booking is confirmed (at the time of booking) and 10 minutes before booking.

For refactoring, we’ll separate the job schedule as two different methods. One will be to schedule the job and the other will be to process the scheduled job.

We’ll create a kue.js file that contains the following code block,

1
var kue:require("kue");
2
var Queue:kue.createQueue();
3

4
let scheduleJob:data => {
5
  Queue.createJob(data.jobName, data.params)
6
    .attempts(3)
7
    .delay(data.time - Date.now()) // relative to now.
8
    .save();
9
};
10

11
module.exports:{
12
  scheduleJob
13
};

The above code will schedule a job which will assign a name and it’s params. Also the delay. We will have one-second delay for rolling out the booking confirmation email and milliseconds timestamp which will be 10 minutes before the start time of the movie.

Job Workers

We’ll create another file named worker.js which will process the scheduled job based on its names. So, in our case, it will be the email job which will roll out emails.

1
var kue:require("kue");
2
var Queue:kue.createQueue();
3
var nodemailer:require("./nodemailer");
4

5
Queue.process("sendEmail", async function(job, done) {
6
  let { data }:job;
7
  await nodemailer.send(data);
8
  done();
9
});

The above code block will make use of the nodemailer utility function we defined previously in this article and send out the email. Note that the arguments/ parameters we passed when scheduling the job will be as an attribute in the first argument of the queue process callback function with the key data. So, we get that with the help of object destructuring - let { data }:job; , and pass it to the nodemailer utility function. Require/Import the worker in index.js file which is our project’s entrypoint.

API Endpoint

We’ll now write an API endpoint /book-ticket that will schedule the job for us in index.js. It’ll schedule two jobs for us. One is to send out the booking confirmation E-mail that has a delay of say, one-second and the second one is to send an email 10 minutes before the booking.

1
const express:require("express"),
2
 app:express(),
3
 bodyParser:require("body-parser");
4
const kue:require("./kue");
5
require("./worker");
6

7
// support parsing of application/json type post data
8
app.use(bodyParser.json());
9

10
app.post("/book-ticket", async (req, res) => {
11
 let args:{
12
   jobName: "sendEmail",
13
   time: 1000,
14
   params: {
15
     email: req.body.email,
16
     subject: "Booking Confirmed",
17
     body: "Your booking is confirmed!!"
18
   }
19
 };
20
 kue.scheduleJob(args);
21

22
 // Schedule Job to send email 10 minutes before the movie
23
 args:{
24
   jobName: "sendEmail",
25
   time: (req.body.start_time - 10 * 60) * 1000, // (Start time - 10 minutes) in millieconds
26
   params: {
27
     email: req.body.email,
28
     subject: "Movie starts in 10 minutes",
29
     body:
30
       "Your movie will start in 10 minutes. Hurry up and grab your snacks."
31
   }
32
 };
33
 kue.scheduleJob(args);
34

35
 // Return a response
36
 return res.status(200).json({ response: "Booking Successful!" });
37
});
38

39
app.listen(8080, () => console.log(`Hey there! I'm listening.`));

The above endpoint makes use of the utility function we wrote to schedule a job. It has a job name, the time (delay) and the email args which is required to send out the email.

The first job is about the confirmation email after a ticket is booked with a delay of one second which is 1000 milliseconds. The second job is about the notification email that should be sent 10 minutes before the start time of the movie. So the delay time is (req.body.start_time - 10 * 60) * 1000 where the start time is a unix timestamp from the request body. The request body will also contain the email of the user to whom it should be sent to.

The request body will be as the following,

1
{
2
  "email": "[email protected]",
3
  "start_time": 1555974600
4
}

Let’s test it again with Postman

The Ethereal preview link will be printed in the console as follows,

1
Message sent: <[email protected]>
2
https://ethereal.email/message/XL7wFeJAYA0Dt0R1XL7wGIdA2wzOT3MhAAAAAbyCsQRrhWTVaptU0njFIO0
3
Message sent: <[email protected]>
4
https://ethereal.email/message/XL7wFeJAYA0Dt0R1XL7wGg7lLAzJdYNkAAAAAkhU1sH5NPPfG5.x8kRnio8

The confirmation E-mail

The Notification E-mail

Folder Structure

Our journey ends here and I hope you found this article helpful. You can also find the project on Github or follow me on Twitter for some funny retweets.