TOPIC: WGET
Updating fail2ban filters for WordPress
18th April 2024Not so long ago, WordPress warned me that some of its Fail2ban filters were obsolete because I have the corresponding WP-fail2ban plugin installed, and the software is present on the underlying Ubuntu Server system. The solution was to connect to the server by SSH and execute the following commands.
wget https://plugins.svn.wordpress.org/wp-fail2ban/trunk/filters.d/wordpress-hard.conf
wget https://plugins.svn.wordpress.org/wp-fail2ban/trunk/filters.d/wordpress-soft.conf
wget https://plugins.svn.wordpress.org/wp-fail2ban/trunk/filters.d/wordpress-extra.conf
sudo mv wordpress-*.conf /etc/fail2ban/filter.d/
The first three commands download the updated configuration files before the last moves them to their final location. It is tempting to download the files directly to that final location, only for wget to create new files instead of overwriting the old ones as required.
Updating Piwik using the Linux Command Line
28th November 2016Because updating Piwik using its web interface has proved tempestuous, I have decided to update the self-hosted analytics application on an SSH session. The production web servers that I use are hosted on Linux systems, so that is why any commands apply to the Linux or UNIX command line only. What is needed for Windows servers may differ.
The first step is to down the required ZIP file with this command:
wget https://builds.piwik.org/piwik.zip
Once the download is complete, the contents of the ZIP archive are extracted into a new subfolder. This is a process that I carry out in a separate folder to that where the website files are kept before copying everything from the extraction folder in there. Here is the unzip command, and the -o switch turns on overwriting of any previously existing files:
unzip -o piwik.zip
Without the required folder in the web server area to be updated, the next step is to do the actual system update that includes any updates to the Piwik database that you are using. There are two commands that you can use once you have specified the location of your Piwik installation. The second is needed when the first option cannot find where the PHP executable is stored. My systems had something more specific than these because both PHP 5.6 and PHP 7.0 are installed. Looking in /usr/bin was enough to find what I needed to execute in place of PHP below. Otherwise, the command was the same.
./[path to piwik]/console core:update
php [path to piwik]/console core:update
While the upgrade is ongoing, it prompts you to permit it to continue before it goes and modifies the database. This did not take long on my systems, but that depends on how much data there is. Once, the process has completed, you can delete any extraneous files using the rm command.
Adding Microsoft Core Fonts to Fedora 19
6th July 2013While I have a previous posting from 2009 that discusses adding Microsoft's Core Fonts to the then current version of Fedora, it did strike me that I hadn't laid out the series of commands that were used. Instead, I referred to an external and unofficial Fedora FAQ. That's still there, yet I also felt that I was leaving things a little to chance, given how websites can disappear quite suddenly.
Even after next to four years, it still amazes me that you cannot install Microsoft's Core Fonts in Fedora as you would on Ubuntu, Linux Mint or even Debian. Therefore, the following series of steps is as necessary now as it was then.
The first step is to add in a number of precursor applications such as wget for command line file downloading from websites, cabextract for extracting the contents of Windows CAB files, rpmbuild for creating RPM installers and utilities for the XFS file system that chkfontpath needs:
sudo yum -y install rpm-build cabextract ttmkfdir wget xfs
Here, I have gone with terminal commands that use sudo, but you could become the superuser (root) for all of this and there are those who believe you should. The -y switch tells yum to go ahead with prompting you for permission before it does any installations. The next step is to download the Microsoft fonts package with wget:
sudo wget http://corefonts.sourceforge.net/msttcorefonts-2.0-1.spec
Once that is done, you need to install the chkfontpath package because the RPM for the fonts cannot be built without it:
sudo rpm -ivh http://dl.atrpms.net/all/chkfontpath
Once that is in place, you are ready to create the RPM file using this command:
sudo rpmbuild -ba msttcorefonts-2.0-1.spec
After the RPM has been created, it is time to install it:
sudo yum install --nogpgcheck ~/rpmbuild/RPMS/noarch/msttcorefonts-2.0-1.noarch.rpm
When installation has completed, the process is done. Because I used sudo, all of this happened in my own home area, so there was a need for some housekeeping afterwards. If you did it by becoming the root user, then the files would be there instead, and that's the scenario in the online FAQ.
Trying out Firefox 3 Beta 3 on Ubuntu
20th February 2008Keeping an eye on future browser releases helps to avoid any shocks when maintaining publicly available websites. Therefore, it should come as no surprise that I have been giving Firefox 3 a whirl. As it happens, I have had it going on both Windows and Ubuntu. With the former, I have not encountered any obvious problems, but I am wondering if the new bookmarking system will mean anything to me. For installation on Ubuntu, I used the following command (I think that I culled it from Tombuntu but can't remember offhand...):
wget -P ~ ftp://ftp.mozilla.org/pub/firefox/releases/3.0b3/linux-i686/en-US/firefox-3.0b3.tar.bz2 && tar xjf ~/firefox-3.0b3.tar.bz2 -C ~
The nice thing about the above is that it places the test installation in your home directory and away from Firefox 2. It also works regardless of what Linux distribution you have. The profiles get shared between versions, so a backup would be a good idea before you start to tinker. As with the Windows version, page loading and rendering is faster in the new version, but I found a problem with printing that, I hope, will get sorted before the final release. Another area for attention is font rendering: it could be sharper for sans serif fonts on Ubuntu and serif fonts on Windows. Otherwise, it works well on both platforms and I like the way that open windows are saved on exit, an excellent idea carried over from Opera.
Running Photoshop Elements 5 on Ubuntu and openSUSE
23rd January 2008When you buy a piece of software and get accustomed to its ways of working, it is natural to want to continue using it. That applied to a number of applications when I moved over to Linux in the latter half of last year, and one of these was Adobe's Photoshop Elements 5.0, a purchase made earlier in the year. My way forward was to hang on to Windows by way of VMware. However, Elements fails to edit or save files in the Linux file system accessed through VMware's shared folders feature. I have yet to work out what's happening, but the idea of using a more conventional networking arrangement has come to mind.
Another idea that intrigued me was the idea of using WINE, the Windows API emulator for Linux. You can get it in the Ubuntu and openSUSE software repositories, but the WINE website has more to say on the subject. That's only the first stage, though, as you might see from WINE's Wiki page on Photoshop and its like. However, their advice is a spot incomplete, so I'll make it more explicit here. You need to run Winetricks from its online home as follows:
wget kegel.com/wine/winetricks; sh winetricks fakeie6
wget kegel.com/wine/winetricks; sh winetricks mdac28
wget kegel.com/wine/winetricks; sh winetricks jet40
The first line flicks a switch to fool Microsoft components to install thinking that they are installing into a Windows system with IE on board. Without this, the rest will not happen. The second installs Microsoft's native ODBC drivers; Elements will not function at all without these if my experience is any guide. The last step is to add JET support so that Elements' Organiser can get going. With all of these in place, having a working Photoshop Elements instance under Linux should be a goer. Apart from the odd crash, things seem to be working OK on Ubuntu and openSUSE seems hospitable too. Further experimentation may reveal more.
Update: The WINE Wiki has now been updated (and links back here!). As per dank's comment, the above lines can be condensed into what you see below:
wget kegel.com/wine/winetricks; sh winetricks fakeie6 mdac28 jet40