DEV Community: Seth Phat

Free API to render HTML to PDF - RenderPDF.io

Seth Phat — Tue, 16 Apr 2024 06:42:32 +0000

Hey guys,

I wanna share with you guys about RenderPDF.io 🔥

A developer-friendly API to render PDFs - RenderPDF.io

RenderPDF.io makes rendering HTML to PDF super easy & simple 😎

We provide awesome & hassle-free API and let you use it within a few clicks.

A simple API call = A rendered PDF ready to be served to your customers 🔥.

// TypeScript
const httpClient = axios.create({
  baseUrl: 'https://renderpdf.io/api'
  headers: {
    Authorization: 'Bearer YOUR_API_KEY',
  },
});

function renderPdf(htmlContent: string): Promise<string> {
  return httpClient.post('/pdfs/render-sync', {
    htmlContent,
    // add more options here if you need
  }).then((res) => res.data.fileUrl));
}

// a "Hello World" PDF ❤️
const pdfUrl = await renderPdf('Hello World');

Homepage: https://renderpdf.io
Documentation: https://docs.renderpdf.io
Get your FREE API KEY at: https://renderpdf.io/login

Engine

Why RenderPDF.io?

We all know that rendering PDFs is a not-so-fun job. Most people would have to research libraries, try/test out a lot of CSS, even we have to deploy & manage stuff. Which costs a lot of time & effort.

I've been there, using wkhtmltopdf and a lot of CSS styling went wrong, have to Google for hours, etc.

RenderPDF.io will definitely make your life easier. I've been using TailwindCSS for my Invoicing PDFs and it is just lovely and beautiful.

Thank you

Get your FREE API KEY today and love your life 🥰

Thank you for reading!

🌹 Awesome development tools for PHP 2023

Seth Phat — Sat, 21 Oct 2023 07:36:49 +0000

Hi guys,

Time flies, PHP is still being used and popular in the world 😎

Getting started and working with PHP is totally fast & awesome nowadays, we have plenty of tools to skyrocket your development experience (DX).

Let's check them out 😉

😎 IDEs

PHPStorm (my go-to IDE)
Visual Studio Code (has plenty of PHP plugins)

🚀 Laravel Herd

A super tool to install & switch PHP versions, nginx included 😎

The pain of managing the PHP version is no more. Goodbye XAMPP.

Home page: https://herd.laravel.com/

🔋 DBNgin

Get your desired database up and running in no time. Including MySQL, PostgreSQL and Redis 🥰

Home page: https://dbngin.com/

✉️ MailTrap

A simple Email service to help us test the email content, recipients,...

No installation is required, we only need to sign up, get the SMTP credentials, and rock your development 🔥

Home page: https://mailtrap.io/

💼 TablePlus

An elegant database management tool, super easy to use, has super high UX, and multiple helpers as well.

We can use it free but limited to 2 tabs. However, the premium version is great and worth the investment.

Home page: https://tableplus.com/

(the author of DBNgin)

(Optional) 🌹 DevToolz

An opinionated development toolz made for developers.

I crafted from my experience. Super useful in your development process.

I hope you'll like it, free to use & open-sourced: https://tools.sethphat.dev/

There will be more tools to come, stays tuned ❤️!

Conclusion

Well, those are the basic tools that you'll need to install & use to achieve the best DX.

Those are the tools I am using every day, and totally satisfied ⭐️

Have fun coding 😉!

P/s: Check out my blog for other topics related to Backend, Scalable & High-perf: https://sethphat.dev

⭐️ Optimizes your response using Laravel Resource Reducer

Seth Phat — Sun, 24 Sep 2023 02:34:40 +0000

Hey guys,

I'm delighted to share my latest work on the performance of your Laravel API endpoints 😉.

Check out: Laravel Resource Reducer 😎

Before delving into Laravel Resource Reducer, it's essential to understand the drawbacks of the existing Laravel Resource 👀.

Laravel Resource

I assume that you all are already familiar with Laravel Resource, aren't you? If not, you can explore it here: https://laravel.com/docs/10.x/eloquent-resources

Simplest tl;dr:

Laravel Resource is a layer to compute your Eloquents into the Responses

Problems

Let's say, we have an endpoint v1/users which returns an array of users:

[
    'data' => [
        [
            'id' => 1,
            'name' => 'Seth Phat',
            'email' => 'me@sethphat.com',
            'created_at' => '2023-01-01',
            'role' => 'ADMIN',
            'avatar_url' => '...',
        ],
        [
            // ... user 2,
        ],
        // ... more
    ],
]

Everything is suitable for the listing page, such as rendering users in the table.

However, if we want to use a dropdown of users on another page (for example, to assign a user as a reviewer), then, you won't need all the returned fields, you only need: id & name (or additionally, email)

=> The CONs while reusing the above endpoint:

Redundant fields returned 🥲
Slower response 🥲
You will end up creating a new endpoint just for the dropdown 🥲 Development takes more time & the team has to maintain more 🥲

Moreover, if you have relationship(s) defined in your UserResource and you wish to bulk them up in the response, then you will need to do eager-loading before transforming UserResource, thus you'll have these CONs:

Always need to do the eager-loading in the outer layer 🥲
- And maintain that 🥲
n*n response size because it bulked up with enormous data 🥲
Definitely: slower response 🥲

Now that you know the current problems. Let's jump into the super solution 😎

Meets Laravel Resource Reducer

Laravel Resource Reducer helps you to optimize every API request by:

Reduce the response's size, get what you need ⭐️
Responses to API consumers faster 🚀
Computation only starts when required, save CPU & memory 😎
Built-in relationship access by using dot notation 👀
Eager-loading on steroids (automated eager-loading, no more N+1 pain) 🔋

A simple yet super effective method to skyrocketing your API responding times 🥰

If you know about GraphQL, To query for data, we need to define which fields we want to retrieve. Laravel Resource Reducer is heavily inspired from GraphQL approach. ❤️

Usage (from API Consumer)

Let's say, we have this endpoint: v1/users which returns User[]

User has these fields: id, name, email, avatar_url, created_at, role (relationship)

Simply add _f[] or _fields[] query param

Get id, name:
- https://my-api.com/v1/users?_fields[]=id&_fields[]=name
Get id, email, and the role name (relationship)
- https://my-api.com/v1/users?_f=id,email,role.name

Isn't it awesome? 😎

Implementation

Resource Reducer

class UserResource extends JsonReducerResource
{
    public function definitions(Request $request): array
    {
        return [
            'id' => fn () => $this->id,
            'email' => fn () => $this->email,
            'created_at' => fn () => $this->created_at,
            'role' => RoleResource::makeRelation('role'),
        ];
    }
}

Remember to wrap your fields with in closures, to defer execution 😎

Return responses

// UserController@index
return UserResource::collection($users)->response();

// UserController@show
return (new UserResource($user))->response();

The usage is as same as Laravel Resource 😉

Final words

If this package is helpful, please give it a ⭐️⭐️⭐️.

Consider using Laravel Resource Reducer to optimize & skyrocket your API endpoints 💪

Thank you and have a great day!

🔋 Laravel Resource Reducer: optimizes your API responses

Seth Phat — Fri, 08 Sep 2023 03:59:24 +0000

If this package is helpful, please give it a ⭐️⭐️⭐️. Thank you!

GitHub Repository: https://github.com/shipsaas/laravel-resource-reducer

Documentation: https://reducer.shipsaas.tech/

Ever thinking about how to speed up your application by optimizing the response? 👀

Laravel Resource Reducer helps you to optimize every API request by:

Reduce the response's size, get what you need ⭐️
- Defer execution and allow on-demand data
Responses to consumers faster 🚀
- No more BIG FAT JSON every item/request
Computation only starts when requires, save CPU & memory 😎
Built-in relationship access by using dot notation 👀
Eager-loading on steroids (automated eager-loading, no more N+1 pain) 🔋

A simple yet super effective method to skyrocketing your API responding times 🥰

If you know about GraphQL, To query for data, we need to define which fields we want to retrieve.
Laravel Resource Reducer is heavily inspired from GraphQL approach. ❤️

Supports

Laravel 10+
PHP 8.2+

Compatibility

Single Eloquent Model ✅
Collection of Eloquent Models ✅
Pagination ✅ (🟡 we have to use Resource::collection for the time being)
(Planned) Collection of Arrays
(Planned) Collection of Objects

Installation

composer require shipsaas/laravel-resource-reducer

API Consumer Usage

Use the query _f or _fields, Reducer supports both ways:

http://api/users?_f=id,name,role.name,created_at
http://api/users?_fields[]=id,_fields[]=email

No more unnecessary fields and faster response TODAY 😎

Backend Implementation

Resource Class

Same as Laravel Resource, using our JsonReducerResource as the parent class.

class UserResource extends JsonReducerResource
{
    public function definitions(Request $request): array
    {
        return [
            'id' => fn () => $this->id,
            'email' => fn () => $this->email,
            'created_at' => fn () => $this->created_at,
        ];
    }
}

Remember to wrap your accessor in a Closure/Callable.
This ensures computation won't start (wait for the right time 😉).

Return the data

Same as today as how we are using Laravel Resource:

// UserController@index
return UserResource::collection($users)->response();

// UserController@show
return (new UserResource($users->first()))->response();

Conclusion

If this package is helpful, please give it a ⭐️⭐️⭐️. Thank you!

📃 😎 DocKing: manage document templates & render PDFs microservice

Seth Phat — Wed, 26 Jul 2023 04:35:52 +0000

DocKing is a document management service/microservice that handles templates and renders them in PDF format, all in one place.

You can utilize DocKing as a shared microservice, which can be integrated & used in any services from your big product.

Documentation: DocKing's doc
GitHub Repo: https://github.com/shipsaas/docking

DocKing is well-tested & production-ready 😉🏎️🚀

LIVE DEMO 🔥

URL: https://docking-demo.shipsaas.tech/ (feel free to hit the APIs)
Console: https://docking-demo.shipsaas.tech/console#/
- Password: None

Features 🚀

Manage your document templates 📰🧾.
Render HTML based on your desired data for a specific template, then export it as PDF 🏃‍.
Supports multiple state-of-the-art PDF Engines 🍻.
Webhook notification after PDF rendered (for async flow) 🚀
Built-in UI-console to manage the templates & files (for internal use) 🔋.
DocKing can perfectly fit for the horizontal scaling based on your needs 😉.

Diagram of how it works

From the diagram above, DocKing is standing as a "shared-microservice".

Billing Service can manage their bill templates and render the PDFs.
Order Service can manage their order templates and render the PDFs.
Contract Service can manage their contract templates and render the PDFs.
...

Give it a ⭐️⭐️⭐️ if it's helpful, many thanks 🥹

PHP CurrencyFX Library

Seth Phat — Sat, 27 May 2023 09:18:30 +0000

Hi all,

I'm happy to share the latest library I've been working on.

It is called CurrencyFX.

Let's check it out 😆

Introduction

CurrencyFX is a PHP Library that helps you retrieve FX Rates from multiple online services, batteries-included 🔋🔋🔋

Repository: https://github.com/shipsaas/currency-fx

Requirement: PHP 8.1+

Additionally, Laravel 10 (for Laravel auto integration)

100% tested and covered under Unit, Integration & E2E tests (assert against the real services)

Installation

composer require shipsaas/currency-fx

# (Optional) For Laravel users
php artisan vendor:publish --tag=currency-fx-configs

Supporting Services / Batteries

Usage

Simply initialize the class with the required parameters (which are the API Key, Credentials). And it is ready to use in no time.

$service = new CurrencyCloudService($host, $loginId, $apiKey);
$rateResponse = $service->getRates('USD', 'SGD');

if (!$rateResponse->isOk()) {
    // failed to get the rate from third party service
    // do something here
}

$rate = $rateResponse->getOkResult()->rate; // float (1.4xxx)

Laravel Usage

(Please add the needful ENVs before using, check out the currency-fx.php for more info)

use CurrencyFX\Services\CurrencyLayerService;
use CurrencyFX\Services\ExchangerRatesApiIoService;

// use the global "app"
app(CurrencyLayerService::class)->getRates('USD', 'EUR');

// DI
class TransferService
{
    public function __construct(
        private ExchangerRatesApiIoService $rateService
    ) {
    }

    public function transfer(): TransferResult
    {
        $rateRes = $this->rateService->getRates('EUR', 'GBP');
        if ($rateRes->isError()) {
            return TransferResult::error(...);
        }

        $rate = $rateRes->getOkResult()->rate;
    }
}

Final Words

Thank you, please give it a ⭐️⭐️⭐️ to support the project.

Don't forget to share with your friends & colleagues, so they can also build their own SaaS products as well 🚀

Cheers!

Reasons why you should do pet projects

Seth Phat — Sat, 10 Sep 2022 06:14:48 +0000

Hi guys,

As a Software Engineer who works in Web Development. I want to share to you guys the "why" & benefits of doing pet projects, based on my experience and achievements.

TL;DR: improve hard skills (from code to server), enrich CV and could be your new Startup.

What is Pet Projects?

Put it simply, they are your own projects to solve any problems that you wanted to solve.

You can do anything that you want, that's your own world. Nobody tells you to do so, it's just you, based on your ideas.

Reasons & Benefits

Improve your hard skills

In real life, not everything you wanted to do, you get to do it on your daily work. Eg: my company is using Java, I want to use Go but there is no way to use it.

By working on pet projects, you can use anything that you want, any languages, any tools, create your best structure, patterns,...

Hands-on experience is always better.

During the time you work on your pet projects, problems will come, obstacles will block your way. But once you solved them, it'll become valuable experience.

Once your projects grow, you'll grow with it.

Learn about Deployment / Cloud

Once your project is done, let's deploy it ONLINE so you can share it to everybody about your work, ask for suggestions,...

Within this phase, you will learn a lot of valuable things like:

Domain: how it works, DNS,...
Server:
- Setup necessary software(s) for your app
- Deploy
  - Manual deploy
  - Automate deploy - CI/CD
- Securities

Yes, it's gonna cost some bucks, some advice:

You can always find for a cheap domain to buy, just Googling it.
There are a lot of providers that selling cheap VPS (Virtual Private Server), starting from $5 USD

Learn about SEO - Search Engine Optimization

After your app is up and LIVE. In order to have visitors, you need to learn about SEO - Search Engine Optimization.

Some basic stuff will be:

Register your website to all the popular Search Engines, eg: Google, Bing, DuckDuckGo,...
Prepare sitemap.xml for the Search Engines
Optimizing your page render speed
Render your HTML content SEO-friendly
Prepare good meta tags
Readable URL (slug)
Share your website on Social Media publicly

Website or web-app won't get many visitors at first. Let's wait and keep it running, at least 6 or 12 months.

Enrich your CV

You can list your project(s) in your CV and share the achievements.

It could be an additional point to the interviewer. To prove that you have the particular experience on these kinds of Technies.

It could become your own Startup

What if my project solves problems/pain of a lot of people?

What if there are more and more people going to use my web app.

What if....?

OMG congrats, that's a great starting point to invest more and make it become your own Startup. At this point, you can think and plan to monetize your app.

That's a big achievement, isn't it?

If not, well, we can try another idea next time. At least I improved my hard skills 😉

My Achievements so far

I have 2 pet projects, they are up and running. And yes, it is monetized. Both are running more than 2 years. Yes, achievements come little and little, let's wait for the magic happen slowly 🌷 no need to push hard or anything.

1st is having around 15k visitors per day, monetized via Ads ⭐.
2nd is having 100+ paid subscribers 🐱‍🏍.

Now I'm doing the 3rd project with cool idea and really looking forward to publishing it in the next 2 months 😝

Thanks and I hope this topic helps and motivates you guys!

Laravel: Generate phpDoc properties for your Eloquent models

Seth Phat — Sat, 03 Sep 2022 09:24:52 +0000

Hi guys,

We all know that Laravel's Eloquent is using PHP's magic methods (__get & __set) for the columns, accessors, relationships,... and much more.

When the development happens, it hards for us to know which "properties" that we can use for a particular Eloquent models. We have to remember the columns' names, the relationship names,... It is a big pain, IKR?

An alternative that we got - is using the phpDoc block and add the properties, eg:

/**
* @property-read int $id // column
* @property string $name // column
* @property-read Country|null $country // relationship
* ...
*/
class User extends Model
{

With this way, it is super IDE-friendly (eg PHPStorm) and increase your productivity a lot.

Butttt, doing the manually work is not so fun, is it? So here am I with the EloquentDocs generator.

Repo: https://github.com/sethsandaru/eloquent-docs

Installation

Simply hit this to install, dev only:

composer require sethphat/eloquent-docs --dev

Laravel auto-discovery will automatically do the magic 😉

Usage

View properties of your model

php artisan eloquent:phpdoc App\Models\User

It will show up all the properties (columns, relationships,...) for you to preview, before performing the write

Write properties to your model

php artisan eloquent:phpdoc App\Models\User --write

It will write the phpDoc block to your model (overwrite if your model already has a phpDoc block)

Optionally, use short class names

php artisan eloquent:phpdoc App\Models\User --short-class

From * @property-read App\Models\Country|null $country to * @property-read Country|null $country

Next Goals

Ability to scan a whole folders and replace the phpDoc blocks automatically.
Add more helper/suggestion methods for Eloquent models

Thanks guys, have a great productive works with Laravel!

[Laravel/Eloquent] Why you should avoid using Accessors?

Seth Phat — Sat, 20 Aug 2022 08:13:02 +0000

Hi Laravel developers,

As you may know, Laravel's Eloquent provides you a fancy way to create a "getter" and transform/access the data as how you want. Example:

// App/Models/User 

public function getFullNameAttribute(): string
{
    return sprintf('%s %s', $this->first_name, $this->last_name);
}

// Seth Phat
$user->full_name;

Looks cool, isn't it?

But, you have to avoid it as soon as you can, here are the reasons.

1/ Conflicts between the table's columns

As the example above, we can't tell the different between an accessor and a table's column. It is too similar how we access the data.

When your projects grow, more and more features come to join, overusing the accessors will create a big pain in your codebase:

You can't tell the different between the columns and the accessors in your code.
Maintenance and tech debt will rise high.
Confuse new people when they're reading the code, logic,...
You have to open a SQL Manager (eg TablePlus) all the time to see what is it.
...

2/ Maintain phpDoc manually

The more accessors you have, the higher time to maintain the phpDoc of your Model class.

To make it IDE-friendly, code suggestions,... you have to add your accessors into the phpDoc of your class, example:

/**
* @property-read string $full_name // Accessor
* @property-read string $sex // Accessor
*/

Imagine you created 10 accessors, you have to add it 10 times. Or when you don't need it anymore, you need remove both the accessor and the doc attribute.

Not so fun, IKR?

3/ Hard to mock

When TDD comes to play, you want to write test. You want to mock your Eloquent model. The mocking process itself is a big pain.

Eloquent will check what attribute wanna access then return the data via __get() magic method. And to mock:

$user = $this->createMock(User::class):
$user->expects($this->exactly(3))
    ->method('__get')
    ->willReturnOnConsecutiveCalls(
        'Seth Phat', // full_name
        'Male', // sex
        // ... more and more
     );

And I believe nobody would like that mocking process above. It is super hard to maintain.

So what should I use?

A good'ol getter method is simply perfect. IDE-friendly, no need to maintain phpDoc, super easy to mock:

public function getFullName(): string
{
    return sprintf('%s %s', $this->first_name, $this->last_name);
}

Mock:

$user = $this->createMock(User::class):
$user->expects($this->once())
    ->method('getFullName')
    ->willReturn('Seth Phat');
// mock more...

With that mocking process, write test is totally enjoyable and easy to maintain.

Limitation

Can't use appends & hidden
- Alternatively: you can use Laravel's Resource response and preferred to use this way instead of return a whole Eloquent Model

Final

That's my experience for this one. How about you guys?

Cheers!

Go Gin&Gorm: Route Model Binding

Seth Phat — Sat, 14 May 2022 15:02:46 +0000

Howdy guys,

From my daily work, I'm using PHP & Laravel. One of the feature that I really like & helpful is "Route Model Binding".

Basically, you just need to define your routes and add the Model into the path, magic happens, you'll:

Get the Model instance and ready-to-use in the Controllers/Middlewares/Requests.
Receive 404 not found if the record didn't exists.

With Go, we have to build things for our needs, indeed.

Inspired by Laravel Route Model Binding, I built a Middleware for Gin which will help me to achieve that and I don't have to do Find then return error if not exists from the Controller. Extracted that to another layer.

Repo for the Middleware - sethsandaru/go-route-model-binding

Please give it a ⭐ if you actually like/going to use it 💖

Feature

Eg: users/:user => Find the User model instance

If exists: bind it to the Gin's context via c.Set so you can retrieve it
If not: return 404 resource not found

It definitely makes our life easier, doesn't it? I hate to do like: "find record, not exists/error => return 404" in the controller, cuz it's not fun and make my controller's methods a bit longer

Q: Does it support multiple params eg: "users/:user/update-categories/:category"?
A: Yes

Mapping - Explicit Binding

Since it won't be as smart as Laravel's way. We need to define a map in order to map your route params with a gORM model.

var routeModelMapping = map[string]modelMapping{
    "entity": makeModelMapping(&models.Entity{}, "uuid"),
    "user": makeModelMapping(&model.User{}, "uuid"),
    // ...
}

Access from Controllers

I love the term Controller and always using MVC in all of my applications.

func (controller *entityController) Show(c *gin.Context) {
    entity, _ := c.Get("entity")
    respondOk(c, entity)
}

func (controller *userController) Show(c *gin.Context) {
    user, _ := c.Get("user")
    respondOk(c, user)
}

In order to get the correct type, we have to do typeAssertion - guide here

Conclusions

PROs:
- Automatically retrieve Model instances using gORM
- 404 not found will be returned if instance not found
- Extracted the find and check exists out of the Controller
CONs:
- Have to do typeAssertion in order to get the real type

Hopefully you'll like this, just like me hehee.

Once again, here is the repo Middleware - sethsandaru/go-route-model-binding

Please give it a ⭐ if you actually like/going to use it 💖

I'm using that Middleware from my open-source project (WIP) Pheasant - Dynamic CRUD Management

Have a nice weekend and happy go-coding!

TDD/Unit Testing with Laravel from a Real-life Project

Seth Phat — Sat, 04 Sep 2021 03:26:02 +0000

Hey guys,

I know for many developers out there, everybody always want to learn how to write unit testing, working with TDD (is basically code, write test, code, write test,....).

But the thing is, every time you Google "how to write unit test", you'll get a bunch of articles. But most of them are just telling you the "definition" with some BS examples, that's all, like:

You need to write this test, that test,...
Write a func a + b = c then write test for the func assertEquals(2, plus(1,1))
...

Right? As a newbie (in term of unit testing), how I suppose to write a freaking test with that?

We're living in the world where we write code that interacting with many things eg: Database, Services,... and a+b=c is not gonna help you anything.

To learn more about unit test (especially from scratch), the best way should be: Learning from a Real-life Project.

So, I did prepare a simple Real-life Project using Laravel to help you guys learn unit testing.

Meet KivaNote

Repository: https://github.com/sethsandaru/kiva-laravel-tdd

A simple application which provides APIs for Simple Note app.

Test definition in KivaNote

Unit Test
- Where we're going to test methods of the Class
Quick Test
- Same as Unit, but this test won't involve database, all we need to do is mocking then testing.
Feature Test
- HTTP Test to test the endpoints, checking the results,...

What did I cover?

All endpoints
Mostly all methods that the application is gonna use

Coverage is 87%, which is absolutely high and would give us a lot of confident.

Where should I start?

First let's have a overall look at the project
- Routes
- Controllers
- Requests
- Services
Second, let's read the test cases, you would know what you need to test and how to write tests

Future improvements

Yes of course, I'm going to find more external services to integrate with the project so I can write more tests (testing external services)

KivaNote has integrated with ImgBB, but seems like it's too easy haha. But it'll help.

Final words

Thanks, hope you guys enjoy it and give it a ⭐ on GitHub if it helps.

Nice day guys!!

Laravel Mail Switcher

Seth Phat — Sat, 08 May 2021 04:30:28 +0000

Hi guys,

Today I want to share a simple Library that I made for Laravel Application. It called Laravel Mail Switcher.

Github Repository: https://github.com/sethsandaru/laravel-mail-switcher

Use-case

You have a personal Laravel Application (small or medium) or even you're a Startup. Of course, you have a tight budget.

So you probably can't spend much money on Email Provider Services to send out your email to your Users/Customers.

There are a lot of Email Provider Services out there that actually give you a specific amount per month (for free) to send out emails.

So, with Laravel Mail Switcher, you will have a big advantage to achieve that. It will automatically switch to another email credential once the old one is out of usage for the current week/month.

You don't have to change the ENV every time one of the services is running out of usage.

You don't need to manually check to see if the email is running out.

All you need to do is prepare the credential/information and let Laravel Mail Switcher will do that for you.

Email Services with Free Usage

Mailgun: 5000 emails for 3-month (about 1666/month)
Mailjet: 6000 emails per month (but 200 per day)
Sendgrid: 100 emails per day (3000/month)
Socketlabs: 2000/month (first month: 40000)
Sendinblue: 300 per day (9000/month)

And many more... With Laravel Mail Switcher, you can manage the credentials and use all of them until the free usage ran out! Your applications would save a lot of money for emails!!

How to install?

Requirement

Laravel 8.x
PHP 7.4 or later

Installation

composer require sethsandaru/laravel-mail-switcher

Visit this: Setting Guide to complete the installation!

In Conclusions

Personally, I got some personal projects and with this opportunity, I don't have to worry about emails anymore (Really budget projects 🤣)

Thanks for reading! Give it a ⭐ if you find out it's useful!