Dear Next.js Afficionado,
Are you aware that there are bad people who make money by getting access to expensive stuff like online courses, software, etc., and later reselling them for peanuts?
What shm**ks, right?
So if you have valuable files that you want to give away to subscribers or customers only, then you need to protect those files.
For example, let’s say your employer creates a detailed guide that helps the customers solve a specific problem. They want to put this guide on the website and collect emails in exchange for it.
So how do you stop the bad actors from getting its URL and putting it on social media, blogs, forums, and other public online places?
That’s the topic of my newsletter this week…
I wrote for a similar use case where I needed to restrict access to a free template.
So if you are interested, use the button below to sign up and discover the following:
- Three feasible ways to protect a file
- How to choose the proper protection
- Lots of code snippets
- Why you should never put valuable files in Next.Js’ public folder
- What’s a “signed URL,” and when it’s useful
This newsletter issue almost hits the 1000-word mark, so if you’re not in the mood for heavy reading… don’t have time… or open this email on your smartphone, then you can bookmark it for later.
It’s not super urgent. Just the typical stuff every geek likes to read about, right?
Sign up for my free newsletter, and you will get a link to this newsletter issue in your email box. What’s more – you will start receiving notifications every time I publish a new issue on a hot, advanced topic.