ReadMe’s Post

ReadMe powers the API documentation for 5000+ companies with only 20 engineers. Of those 20, only 1 engineer—Ryan Park—focuses on infrastructure. A big source of leverage is the managed services they build upon, including Render. Learn why, after 8 years on Heroku, ReadMe chose to migrate to Render—and how they did it with under 2 minutes of downtime: https://lnkd.in/eHaCtCrz

I decided to change the backend setup for the post-scheduling feature of my first SaaS project. Previously, I had AWS Lambda functions with EventBridge running every minute to query the scheduled posts and send them to LinkedIn with its API. As for the separation of concerns, the setup had two lambda functions, one for posts only with text and the other for posts with text and images. Although AWS is easy to setup and maintain, the monthly cost would account for a moderate sum. Since my first SaaS project is a side project, I have to bootstrap, have to think about the costs of running it. My initial goal is to run it under $80/month, this includes, hosting, db, emails and everything in between. Therefore, spinning up a VPS and having Cron jobs running the post-scheduling functions was the way to go. It's a bit of work setting up the VPS and securing it by adding a limited user, hardening SSH access, editing SSH Daemon options, etc. Also since there's no CloudWatch with this setup, added logging to each post-scheduling function. Added logrotate to rotate the logs once everyday, keeping a history of 7 days, so the logs don't get out of hand over time and it's easy to maintain. Bootstrapping a solo side project is fun! 🔥🚀 Thanks for reading. #buildingpublic

Everybody using Terraform should read and signs this https://opentf.org/ #terraform #hashicorp

Terraform is forked to form OpenTF. OpenTF's goal is to ensure Terraform remains truly open source. This open-source initiative already has 4.1K stars on GitHub. #opensource #terraform #hashicorp #communities #infrastructureascode

This was fast! Exciting times ahead for the Terraform Ecosystem and for Open Source in general. It's been demonstrated before that OSS communies can move really swiftly. It'd be, therefore, very interesting to see whether OpenTF will be able to innovate faster than the mothership. One thing is clear, there's no "one size fits all" approach when we look at possible OSS business and GTM strategies. It's important, thpugh, to keep strong ties with the contributor community, which was, apparently, not the case here. The difficult aspect is, of course, how to deal with the service provider businesses that grow around successful OSS projects. It has to be a clear direction from the beginning, IMHO. Either one embraces it and doesn't go into conflict later or makes it clear that it's not welcome. https://lnkd.in/eMmNiaEy

What's your take on HashiCorp's new license? What do you think the future holds? Will there be any changes? Are you considering a switch from Terraform to another IaC tool? #terraform #license #BusinessSourceLicense #bsl https://lnkd.in/dQzp7MBE

The time is now!! OpenTF Announces Fork of Terraform ❤️💪 Here is my contribution of joining the manifesto: https://lnkd.in/eRg9yMC9 Two weeks ago, HashiCorp announced they are changing the license to all their core products, including Terraform, to the Business Source License (BSL). In an attempt to keep Terraform open source, we published the OpenTF manifesto, and the community response was huge! Over 100 companies, 10 projects, and 400 individuals pledged their time and resources to keep Terraform open-source. The GitHub repository for the manifesto already has over 2.5k stars, and the number is growing quickly! The manifesto outlined the intent of the OpenTF initiative in two steps — the first was to appeal to HashiCorp to return Terraform to the community and revert the license change they were making for this project. The second, in case the license was not reverted, was to fork the Terraform project as OpenTF. #opensource #terraform #community #devops #infrastructure

🚀 Just Completed day 68 :- explored the power of meta-arguments in Terraform - Count and For_each! 🤖 These handy tools streamline Infrastructure as Code (IaC) by simplifying resource multiplication. With 'count', you can create multiple instances of a resource effortlessly. 'For_each' takes it further, allowing you to create resources with unique configurations or attributes. Check out my article for a deep dive into how to use these Terraform features effectively: [https://lnkd.in/dnNttrdt] Shubham Londhe #Trainwithshubham #Terraform #InfrastructureAsCode #CloudComputing #LinkedInLearning https://lnkd.in/dnNttrdt

Open Source is really at the heart of business operations today. HashiCorp has recently decided to follow suit of Red Hat and tried to find a balance between a commercial license for competing offerings and still benefiting from #OSS adoption. Well, it looks like these strategies don't work well for infrastructure level software. Now a group of companies calls for a potential fork and a foundation to support it. Learning from Debian, this is a great model. They've been at it for 30 years and it's still going strong! BTW, here's a great episode of Changelog https://lnkd.in/e3k6gChy about it. Will be interesting to see if it really comes to that. Terraform is the #1 revenue generating product for Hashicorp. However, the market pitch has been all around building adoption through OSS for all parts of their stack (Vault, etc). Many businesses/projects use their libraries a lot, as well, and the recent licensing decision has created a lot of desire to abandon their ecosystem. So, will they go back? Or risk creating short term support for their share price but loose the adoption (standardization) support mid to long term? Or will something like BSL become a new normal? https://lnkd.in/e-xB4csQ

Terraform is going to be forked! You can imagine why, but in case you are surprised you can read more at the link below. OpenTF will be released as #opensource version 1.6.0.