I ran composer install today, and was rather surprised to find that the
intl module wasn’t installed?! Then I remembered I had installed package updates etc, and it turned out I had BOTH PHP 7.3 AND PHP 7.4 installed!
All my sites were developed on 7.3, so I had to switch back.
update-alternatives --list php
Typing that command in will output something like this:
Now you can see the available versions. To switch versions, I simply typed
sudo update-alternatives --set php /usr/bin/php7.3
I just noticed 1.5GB of pointless cron emails on my server.
To stop this, just crontab -e and send to /dev/null
* * * * * /your/cron/script >/dev/null 2>&1
find text within a bunch of files within a folder simply by typing this:
grep -nr 'whatever' .
Where r is recursive, and n gives you the line number. 🙂
Just a quick note here, if you are running out of space on your Linux machine and need to find the files taking up the most room, try this command!
du -hsx * | sort -rh | head -10
Now that my VM is completely configured through puPHPet’s puphpet/files/exec-once shell scripts, I had to change PHP settings for the legacy 5.3 install. At first I echoed the setting out and concatenated it onto the end of the string, however the setting was already uncommented above.
The answer is to use sed to find and replace the line of text, like this!
cat /etc/php.ini | sed -e "s/short_open_tag = Off/short_open_tag = On/" >> /etc/php.ini
cat ~/.ssh/id_rsa.pub | ssh user@host ‘cat >> .ssh/authorized_keys’
Ansible is a bit like puPHPet, in that it provisions Vagrant boxes etc. My latest project is using PPI Framework 2, and provisions with Ansible, so I had to get everything installed.
Essentially we just clone from the Github repo and install a few python things:
$ git clone git://github.com/ansible/ansible.git --recursive
$ cd ansible
$ source hacking/env-setup
$ sudo easy_install pip
$ sudo pip install paramiko PyYAML Jinja2 httplib2 six
And that should be you. Run ansible from the terminal in ay folder now and you should get all the available options etc. Have fun!
As you all know by now, I love puPHPet. And I like tinkering with things. Which of course leads to the occasional breaking of things. And then I realised, okay, your sites files are being mounted into this virtual machine, what about the databases though?
The great thing about puPHPet and Vagrant is you can build a full server up from scratch in minutes. The one downside is that it cant be smart enough to uninstall things. If you add lines to your config.yaml it will install something, but removing those lines means puPHPet won’t even know it was there, so how would it know to uninstall it? The exceptions of course being the ones which have their own config.yaml entry, with an install: ‘1’ or install: ‘0’
Anyway, I generated me a new config and was about to blitz my old VM when the usual gut instinct checks kicked in, and the DB sprung to mind immediately. So I made a quick backupdbs.sh shell script (courtesy of a StackOverflow post) which makes individual sql files for each of your DB’s. I decided I would keep the script in my mounted sites folder in a bin directory. So hence it lives in /var/www/bin/backupdbs.sh
databases=`mysql -u $USER -p$PASSWORD -e "SHOW DATABASES;" | tr -d "| " | grep -v Database`
for db in $databases; do
if [[ "$db" != "information_schema" ]] && [[ "$db" != "performance_schema" ]] && [[ "$db" != "mysql" ]] && [[ "$db" != _* ]] ; then
echo "Dumping database: $db"
mysqldump -u $USER -p$PASSWORD --databases $db > `date +%Y%m%d`.$db.sql
To back everything up, vagrant ssh into the machine, then (you’ll probably need to switch user to www-data) do the following:
sudo su www-data
Now you’ll find all your DB’s SQL files date stamped in the folder! You can continue to break, tweak, fix, and run your VM to your hearts content 😀
If you are using the Bash terminal, or the Mac OSX Terminal, time to get rid of it! You need Zsh! (pronounced zoosh). From the Github page:
Oh My Zsh is an open source, community-driven framework for managing your zsh configuration. That sounds boring. Let's try this again.
Oh My Zsh is a way of life! Once installed, your terminal prompt will become the talk of the town or your money back! Each time you interface with your command prompt, you'll be able take advantage of the hundreds of bundled plugins and pretty themes. Strangers will come up to you in cafés and ask you, "that is amazing. are you some sort of genius?" Finally, you'll begin to get the sort of attention that you always felt that you deserved. ...or maybe you'll just use the time that you saved to start flossing more often.
So, what are you waiting for? Give it a spin!
curl -L https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh | sh
Or using wget:
wget https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh -O - | sh
Well worth a try! https://github.com/robbyrussell/oh-my-zsh
This problem was infuriating. After having upgraded my Vagrant Box to run PHP 5.6, I was looking forward to trying out phpdbg, the new built in debugger that ships with PHP 5.6.
It turns out that Debian use their own moronic naming system for their PHP package commands. I was typing in phpdbg into the shell, and all I got in return was ‘command not found’.
I tried sudo apt-get install php5-phpdbg, yet it told me that it was already the latest version!
I eventually found it in the /usr/bin folder, under the name php5dbg. Why?
For reference, you can run this command to help find it: (if dpkg is installed)
dpkg -L <pkgname> | grep '/bin/'
What a waste of time, I hope this helps someone.