This repository is for version 2 of my blog. The version 3 is hosted on a private repository. However, the content of my blog is now open source and everyone can contribute: benjamincrozat/content
This is the source code of my blog, benjamincrozat.com. This blog was built with the TALL stack and gets more than 50,000 visitors per month.
My Pirsch Analytics dashboard that is publicly accessible.
My Google Search Console. You can see the growth since I launched in September 2022.
I feel obligated to mention that my relative success is not correlated to my tech stack. I just want to own my piece of real estate online and do whatever I want with it. If you also want to create your blog, I don't recommend to copy and paste anything I did. While the code works for my specific needs, it might not be the ideal solution for everyone. But if you're curious, there you go, enjoy!
- I don't need pull requests. This is a project I'm working on alone, and I only have time for the bad code I write myself. 😅
- This isn't an opportunity for mentoring. Please try to resolve your issues on your own. If you tried your hardest, then you can open a new discussion! Also, feedback is welcome (but useful feedback, not something like "whAt aBoUt SrP DudE?"
- The code from this codebase won't help you rank on Google. Getting organic traffic requires hard work, to write content people search for (aka smart work), and lots and lots of patience. I actually wrote about my journey on the blog.
This is a small project. It certainly won't teach you how to maintain apps at huge scales. That being said, you can learn about:
- Simplicity. Most developers underestimate its benefits. I love figuring out how to do more with less.
- Using the GPT API from OpenAI to create features that were unthinkable not so long ago.
- Creating admin pages using Filament.
- Testing. This is a crucial part in ensuring everything don't break and Google does not penalize me. Because I can be forgetful, distracted and overconfident sometimes. These are flaws of human beings that can easily be mitigated by machines. By the way, I don't aim for 100% code coverage, I don't think this metric reflects the stability of the codebase.
- How to use various frontend technologies such as Livewire v3, Volt, Alpine.js, and Tailwind CSS.
- I don't care about code coverage and static analysis, so you won't find that here.
- This is pure and plain Laravel. If you know the framework, you can find your way around the codebase.
- The tests are organized just like the source code. Most of the time, it makes it easier to know what is tested and what is not.
- My commit history is garbage. I'm sorry and I know it's wrong. But when you are working alone on a project, it's hard to maintain discipline for such things.
- PHP 8.2+
- MySQL 8+
The instructions below have been written assuming that you are using Laravel Valet. But you can run the project in whichever environment you want (Herd, Docker with Laravel Sail, Laragon, etc.).
Clone the repository and cd into it:
git clone [email protected]:benjamincrozat/benjamincrozat.com.git
cd benjamincrozat.comCreate a .env file and generate the app key:
cp .env.example .env
php artisan key:generateInstall the dependencies:
composer installCreate the database:
mysql -u root -e "CREATE DATABASE benjamincrozat"Migrate the database with some fake data:
php artisan migrate --seedInstall the frontend dependencies and build the assets using Bun (use NPM or Yarn if you prefer):
bun install && bun run buildTo run the tests, execute the following command:
php artisan testOnce the tests are green in the CI environment, a webhook from Laravel Forge is called, which triggers the deployment.
Some details about the production environment:
- I host the blog on a $6 DigitalOcean VPS that's managed by Ploi.
- I use Sentry to monitor errors in the production environment only.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent