In this post we are going to provision HTTPS certificate from Let's Encrypt and use that in our SSL termination program nginx. We are going to use Ansible for this automation.
This is a quick post where I talk about getting started strategies with Open edX as a developer. In this post I am documenting the process of edx installation on my local system for evaluating.
There are a few words, like unit testing, integration testing, mocking, dependency injection, object oriented proramming which are all related to each other. In this post I'm going to talk how, and then it will start to make sense to you.
Every year in January, I write about what I actually did happen and what I actually planned for that year. I also write about my most significant learnings in the year. Any lifestyle changes made is also included.
If you are following this series from start, you know that we can already create user from our API. But we have our tests failing right now, which is kind of smelly. In this post, we takle with the problem in our hand and discuss some methods we can do it with. One of them is dependency injection.
In the last post in the series we did the project setup and seen some FastAPI basics along with red-green-refactor mantra of TDD. In this post, we talk about setting up the database and and implementing the user registration.
In the last post in this series, we saw how we can execute a piece of a code when something is uploaded to the S3 bucket. We saw all the configuration we might have to go through. We also saw how we can test our trigger manually and automatically when object is uploaded. At last, we also came accross a trouble and shooted it. In this section, we will continue our venture.
Today I'll go through how get and configure a HTTPS certificate from Let's Encrypt for all the subdomain. I have already posted about how we can automate installation of Jenkins & Nginx with Ansible. I have also done a post where I talk about how to enable HTTPS on a non-wildcard basis i.e. only for the root domain and not on subdomain.
I have been tinkering with this new framework and have a little bit of experience with FastAPI as of now. What I've though of is to do a post about authentication and authorization. I'm sure going to do a registration and login system and nothing fancy this time. I am going to use JWT as authorization mechanism.
You know what is difference between a senior software enginner and a junior? One of the diffrence is that senior develop organised thinking over the span of time. Why not practice it from the start?
In this post, we are going to see how we can use existing AWS infrastructure to create thumbnail for uploaded images. In this venture, we are going to use S3 trigger to execure Lambda function to do whatever we want. But in this case, we'll create thumbnail so that we can save on some bandwidth when only a smaller version of image is required on the frontend. So let's get started.
I don't claim to be a DevOps expert. I just know some basic ssh and scp, that's all. I have done whatever server configuration till date by ssh'ing into instances and then configuring them by hand. But now-a-days I feel like spinning up and destroying a server has increased in my life style.
There are a plenty of VPN providers out there. What's common between all of them? You can't trust them. They may have a no-log policy but as a company, there is always a tendency that they might share our browsing data to some third party. In this post you'll learn how you can spin up your own VPN with Amazon AWS.