The Mijingo Blog

Latest news, updates, free tutorials, and more from Mijingo.

Manually Installing Craft 3

by Ryan Irelan

During the beta and RC period of Craft 3, the only supported installation option was using Composer. But not everyone wants to–or can–use Composer.

How do we install Craft without Composer?

Follow along in this video for step-by-step instructions (including some gotchas you should know about).

This was recorded from a live Twitch stream.

Want to learn even more with Craft (and save yourself a lot of time)? My Craft Essentials bundle covers Craft 2 & 3.

Installing and Configuring Laravel Valet for Craft

by Ryan Irelan

In this lesson, Ryan walks through how to install and use Laravel Valet and then uses it to run a local copy of Craft CMS 3.

Craft 3 Remote Volumes with AWS S3

by Ryan Irelan

Watch as Ryan converts a Local Folder Assets Volume to Amazon S3. The video includes setting up an S3 bucket, creating a IAM policy, group, and user.

Splitting Up a Git Repository

by Ryan Irelan

Here’s the situation: you have a Git repository and you want to split it up into smaller repositories. Perhaps you have an application that has grown to large and you need to break out parts of into their own application (as services) or maybe as their libraries.

Whatever your reason is, the task is the same: how do I get this big Git repository broken out into two (or more)? And how do I do that while also maintaining the history of the changes in the directory I’m splitting out?

That is our most important requirement: we don’t want to lose the history of the files that we’re splitting up from the repository.

Let’s go through the steps.

Dry Run Before Adding to Git Repository

by Ryan Irelan

One focus in my Git classroom training is to give my students the knowledge and power to fix things when something goes wrong. I have an entire section on it (as well as in my video course series.

But it’s also important to test things before you do them so you can avoid things going wrong!

One way to do that in Git is to use the --dry-run flag with git-add.

Let’s say I have a bunch of changes and I just want to check what will happen when I run git-add to stage them for commit. Unstaging a staged change isn’t a big deal but I like to avoid problems (and fixing them!) if I can.

git add . --dry-run

Using this command I’m adding all changed files (the . means everything) but I’m only doing a simulation. When this happens I’ll get a list of files that will be included in the add and staged for the next commit.

A handy tip for the next time you want to see what happens before you do it.