git log -n 1 --pretty=format:%H -- my/file.php
Servers
Search git for line of code
Any branch, any commit, here’s how you search for a line of code in Git.
git log -S '$this->isTheCodeIAmLookingFor();' --all --source -- path/to/file/to/check.php
This will return the commit number and branch.
Ready to rock PHP 7.3 Docker LAMP Stack
I have built a full LAMP stack that comes with the following:
- Apache
- PHP 7.3.3
- Mariadb
- MailHog
- XDebug
- HTTPS Virtualhost with holding page
Here’s how you get a full LAMP stack up and running in no time at all, which will be identical on any platform.
Firstly, install Docker and Virtualbox if you don’t have them. Then create a default base VM.
https://www.docker.com/community-edition
docker-machine create --driver virtualbox default
OK. So, first thing you need to do is start your VM:
docker-machine start docker-machine env eval $(docker-machine env)
You should run eval $(docker-machine env) in any other terminal tabs you open too, this sets up environment vars for setting up docker. Take a note of that IP address, and edit your /etc/hosts file
192.168.99.100 awesome.scot
Ok, lets clone the LAMP stack:
git clone https://github.com/delboy1978uk/lamp cd lamp
This is another one off, build the image.
docker-compose build
That’s it! Now start your docker image like this
docker-compose up
and you can finally open your browser to
https://awesome.scot
Bypass HSTS on local dev sites
HTTP Strict Transport Security will BLOCK your dev site if it is using a self signed certificate. And once the browser has given you that, it remembers it, so fixing it doesn’t help until you fix Firefox/Chrome.
Firefox
- Close any tabs
- Ctrl + Shift + H (Cmd + Shift + H on Mac)
- Find the site in question
- Right click, forget about this site
- Close and reopen browser
- Add certificate exception this time 😎
Chrome
- chrome://net-internals/#hsts
- type the hostname into the Query Domain
- If found, enter the domain in the Delete domain section 😎
Stop git committing chmod changes
Pretty self explanatory. Just do this:
git config core.fileMode false
The documentation says this about it:
core.fileMode If false, the executable bit differences between the index and the working copy are ignored; useful on broken filesystems like FAT. See git-update-index(1). True by default.
Here’s a warning from a guy on StackOverflow:
core.fileMode is not the best practice and should be used carefully. This setting only covers the executable bit of mode and never the read/write bits. In many cases you think you need this setting because you did something like chmod -R 777, making all your files executable. But in most projects most files don’t need and should not be executable for security reasons.
The proper way to solve this kind of situation is to handle folder and file permission separately, with something like:
find . -type d -exec chmod a+rwx {} \; # Make folders traversable and read/write
find . -type f -exec chmod a+rw {} \; # Make files read/write
If you do that, you’ll never need to use core.fileMode, except in very rare environment.
Fixing missing Authorization Headers
It’s something to do with using PHP FPM / Fast CGI, and auth headers being disable for that.
So we add this to the directory entry of the .htaccess:
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
You now have your missing header back!
Line Endings in Git with Windows
Devving on Windows is a PITA.
Anyway, ever seen a message like this?
warning: LF will be replaced by CRLF in tests/unit/Del/Console/CommandTest.php. The file will have its original line endings in your working directory. warning: LF will be replaced by CRLF in tests/unit/Del/Console/CommandTest.php. The file will have its original line endings in your working directory.
We only want LF. To squelch this crap, run the following:
git config core.autocrlf false
Yay.
