To keep users happy user experience is everything. As a developer it’s also nice when code just looks pretty and is extremely functional.
Apps like Reddit for example you may not want to require a name. What I do on those is make the name nullable or sometimes replace it with a first name/last name fields. You might also want a username that’s also a slug for that user account.
The flow that we’re building in this tutorial is basically this:
Register and supply email, username, password. On the profile, you can have other fields like name, phone, etc. …
Today we’re going to learn the magical art of infinite scrolling pagination. More specifically, we will be building a Laravel Livewire component that will scroll infinitely like you might see on Twitter or Facebook feeds.
The “infinite scrolling” or “infinite pagination” livewire component will dynamically query data using cursor pagination which helps keep things efficient.
This should be a pretty simple tutorial, so let’s get started!
It’s assumed that you’ve already set up a laravel project and have tailwindcss installed and set up. …
I can’t state how many times I have an idea for a side project. Start it, and scrap it. A lot of that is my ADHD, but one thing that I hate about Laravel’s installer and boilerplate is I ALWAYS have to edit the .env.
There’s a few things though that never change from project to project.
I always run a script that creates a symlink from ~/sites/appname ~ path/to/app/public.
My default NGINX site config automatically creates all .test domains for any symlink…
We don’t need to know every intrinsic detail, who has time for that? Maybe if we worked for a company that gave us 20% off to work on self-learning. …
Imagine being able to simply create a new project (we’ll use laravel for an example), run the command:
$ laravel new testapp && cd testapp && nsc
Then automatically having testapp.test work in the browser and show your laravel site.
This is what I created and it works beautifully. Laravel is my framework of choice, but you can tweak things to work for most things if you try.
Aka how to create a dynamic catch-all nginx config. (Mostly for laravel, but should work w/ any flow if you make some mods).
I absolutely hate editing configs all the time, and I probably create new laravel installs all the freaking time.
Today I finally got sick of the old workflow:
$ sudo cp /etc/nginx/sites-available/site1.test /etc/nginx/sites-available/site2.test
$ sudo ln -s /etc/nginx/sites-available/site2.test /etc/nginx/sites-enabled/site2.test
### edit site2.test
$ sudo systemctl restart nginx
I develop on arch linux and don’t much like vagrant, docker, etc for local development. I’d rather go barebones with php-fpm and nginx.
I also develop mostly under my home…
Systemd is a system manager and “init system” that is the standard for most linux distros as of 2019. If you’re just getting started with linux or have been using older versions and wanting to get up to date with the latest & greatest practices in linux-land then you definitely need to know how to get around systemd.
This particular article will be…
Often when I’m trying out new devtools like for instance prisma or hasura, I notice that I’m constantly adding new docker images, containers, etc.. These take up valuable space on my system and can really add up fast.
I often don’t need to come back to these docker instances later on and if I do, there’s usually no foul in just starting from scratch. Till recently I’d just google how do I remove docker containers and images then go through 1 by 1 and remove everything.
It’s not that hard to do, but it gets tedious after awhile, so I…
The idea for this post comes from the recent twitter battle between YCombinator founder Paul Graham and Matthew Prince the founder of Cloudflare over how many of the startups who struggled still had safety nets.
I struggle daily as a freelancer and founder wannabe. Currently I’m working w/ a startup where I ‘sometimes’ get paid, last month I put in 200 hours, but billed for 40 because that’s all they could afford as their app was left in tatters by a shitty Indian outsourcing team.
It’s a mobile app and the backend (php/laravel) has zero code coverage or testing. Instead…
Everyone is always excited to live on the bleeding edge. Iterate fast, drive hard, go to market as soon as possible. Money is a major factor for almost all startups and time is money. To save money the CTO will often work as the solo-developer.
But what happens when that developer gets hit by a bus, or finds a better opportunity?
What happens the next day, when your server goes down and you have nobody to call to fix it?