Supercharge Your Laravel Development and Get AI to Understand Your Models
Hey there, Laravel enthusiasts! Today, I'm diving into a nifty trick that'll make getting AI to understand your Laravel model structures a breeze. We'll harness the power of bash scripting and AI to analyze our migrations quickly and efficiently. Let's get started!
As our Laravel projects grow, so does the complexity of our database structures. Migrations pile up, relationships intertwine, and before you know it, you're drowning in a sea of Schema::create and up functions. Wouldn't it be great to get a bird's-eye view of our models without manually sifting through dozens of files? What if you could get AI to understand your Laravel project without adding every file to the chat window?
Here's where our dynamic duo comes in a clever bash one-liner and your favorite AI chat tool (like ChatGPT or Claude). We'll use bash to extract the relevant parts of our migrations and then feed that information to an AI for analysis and insights.
Here's the one-liner code to copy and paste:
First, let's break down our bash sorcery to understand what's going on in an easier-to-read format:
Just add | pbcopy to have it copied directly to your clipboard on Mac:
This command does the following:
Please copy the entire output from your terminal and paste it into your AI chat of choice with your preferred prompt. I usually start with this prompt:
Generate a diagram
Here are some additional prompts you can optionally pair with the output to extract valuable insights and improvements:
There you have it, folks! With this simple bash one-liner and the power of AI, you can transform how you analyze and understand your Laravel database structures and output code. Give it a try on your next project, and watch your productivity soar!
Remember, tools like these are meant to augment your skills, not replace them. Always review AI suggestions critically and trust your developer instincts.
How to Take Ownership of Files and Folders Using PowerShell
Ever had to take ownership of a bunch of files and folders? It's a pain, right? Well, not anymore!
Picture this: You've just gotten an external hard drive from a dead computer and need to access the files. But wait! You don't have the correct permissions. I had to do this, and setting the file permissions through Explorer was failing randomly. It appears that the folders all had different permissions, and the propagation was failing.
I've got a PowerShell script that'll save you time. It does two things:
First, here's the script. Don't worry, I'll break it down for you:
Let's break this down a bit:
There you have it, folks! A powerful little script to take control of your files and folders. No more permission headaches, no more "access denied" nightmares — just pure, unadulterated file access bliss.
Got questions? Hit me up in the comments. And don't forget to share this with your IT buddies – they'll thank you later!
Happy scripting!
How to Automatically Login into Laravel App in Your Local Dev Environment
I often find myself spinning up Laravel projects for prototypes and idea testing and then letting them sit until I can pick them back up. Logging in whenever I start work gets annoying, and there's no point in manually logging in to my local instance since my account is the admin. Fortunately, there are a few solutions to automate this process in Laravel. I'll delve into the various methods to automatically log in to your Laravel app in your local development environment, enhancing your workflow and boosting productivity.
One approach to automating the login process for the Laravel application is session-based auto-login. This method involves setting up a mechanism that automatically logs in a predefined user whenever the application is accessed in the local development environment.
Each solution below assumes you've seeded or registered a local user account in your database.
You can create a custom route in your Laravel routes file (routes/web.php) that triggers the auto-login functionality.
When you access the /auto-login route in your local development environment, Laravel will automatically log in the specified user, redirecting them to the desired page (in this case, /dashboard).
Another method to automate your Laravel application's login process is leveraging custom middleware designed for auto-login functionality. This approach provides more flexibility and control over the auto-login process, allowing you to define custom logic and conditions for authentication.
Generate a new middleware using the Artisan command make:middleware.
Register the custom middleware in the HTTP kernel (app/Http/Kernel.php) to apply it to the desired routes or groups of routes.
This method allows you to log in automatically as soon as you load the application, and it is the method I use most often. I added a check to ensure that the environment is local.
if ($this->app->environment('local')) {
$user = User::first();
if (isset($user)) {
$this->app['auth']->setUser(User::first());
}
}
If you don't have the user table seeded with a user, the above code will cause an error when running the seeders. I tweaked the code to check for the table's existence to avoid the error when running seeders.
Sometimes, you might want to seed your database with an admin user for testing purposes. Here's how you can do it:
Generate a new seeder class using the Artisan command make:seeder.
Within the generated UserSeeder class, define the logic to create an admin user.
Finally, run the seeder using the Artisan command db:seed.
Following these steps, you can seamlessly integrate auto-login functionality into your Laravel application's local development environment, reducing the time and effort spent on repetitive login tasks. Additionally, seeding your database with an admin user ensures that you have a user account available for testing and development purposes.
Installing font awesome pro with bun
After recently switching to bun.sh, I was trying to install Font Awesome Pro. It uses a private registry but their docs have not been updated to support non-npm package managers and bun does not yet support .npmrc files.
You can configure a private registry using an organization scope. First, you must get your auth token from your paid Font Awesome account by going to your account page, scrolling down to the Tokens section, and copying the token.
Copy and paste this string, and replace YOUR_TOKEN_HERE with the token you copied above:
Open the terminal and enter these commands:
Paste in the config above with your token and then hit CTRL+X to quit, and Y to save when prompted. Now you should be able to run
Using Laravel Vite with MAMP
As seen in other posts, I use MAMP quite a bit for my web development environment. I know I can run docker, or any of the other platforms out there but they use more memory and resources that I'd prefer to devote to my dev tools.
I started a new Laravel project and wanted to use MAMP but Vite was throwing errors due to the SSL not matching out of the box.
When adding
to my blade file, I'd get errors including:
I found articles saying to add --https or --host to my package json command but then I got this error:
Load MAMP Pro, add your host and generate your SSL certificates. For this example, we'll use set the host name to my-app.test, and assume you're storing the SSL keys in the default location.
Open vite.config.js and add the following 2 lines:
Then add this to defineConfig section:
You should now be able to run npm run dev and have no issues.
Sample full vite.config.js file for easy reference:
Add GTM to Gatsby using Helmet
One of my devs needed to add Google Tag Manager (GTM) to an older Gatsby project we built and he was running into issues implementing the GTM code provided by Google since the react-google-tag-manager package required a newer version of Gatsby and its dependencies.
The issue turned out to be that the strings needed to be escaped for Helmet/React to process it correctly. If you're using an older version of Gatsby, the snippet below should help you add GTM and call your events as needed. Just add it to your main template file.
How to deploy a React app to Amazon S3 using Gitlab CI/CD
I've been trying to build more CI/CD scripts using Gitlab to automate pipeline deployments for work. Here's a useful one for building and deploying a React app to Amazon S3.
You'll need to add a variable called S3_BUCKET_NAME to your repo or replace the variable with your bucket path.
How to use Backblaze B2 with Laravel
I am working on a Laravel project and decided to use a Backblaze bucket as it's cheaper for storage when compared to AWS S3. I couldn't find a tutorial on how to get it working from scratch and I tested a bunch of Laravel B2 libraries that didn't end up working. The good news is that you don't need a special B2 plugin and instead can use the S3 package recommended by the Laravel docs.
If you haven't added the flysystem-aws-s3 package, add it to your project using composer:
Login to your B2 account and create your bucket with your required settings. Once created, you'll want to create a new application key with the permissions you need for your app. You should get a confirmation once it's generated:
Open your .env file and locate the settings for AWS. You'll need to add one key that's not there by default:
Match the settings in your .env from the application key to the values below.
Now you should be able to call the Laravel storage system like normal:
How to Setup a CI/CD Pipeline for Storybook.js using Gitlab
I just spent a few hours setting up a Gitlab pipeline to deploy a Storybook.js site. Of course the end result ended up being much simpler than I made it out to be. Like everything else on my blog, I'm sharing in case anyone else can use the information to save time.
Just put this in your gitlab-ci.yml and it'll take care of caching the node modules and building your static version of Storybook to deploy.
How to Automate Sending Emails through Outlook interop using C#
I was tasked with a tricky issue in sending emails. Due to security concerns, the client's IT team was not willing to share SMTP information for their mail settings and was only willing to set up an account in Outlook directly on a dedicated machine without sharing the password with us to send the emails. The client's ask was to send emails through Outlook without letting users see the emails or Outlook itself.
Sending emails through Outlook can be done using Microsoft.Office.Interop.Outlook but the documentation is really lacking. If you need to do the same, I hope this will save you the hours of time it took me to figure out what ends up not being complex code.
Create a new desktop application project in Visual Studio. Install the Microsoft Office Interop for Outlook. I used the NuGet package manager to install it since it wasn't present on my system:
I created a static class to send the email through Outlook. Note that my error handling code was replaced with Debug.Writeline. Remember to modify it to handle errors or implement logging so it doesn't fail silently.
Email.cs:
Example on how to call the class:
email.html: