Skip to main content

yum command for clearing cache and make

Whilst updating nodejs and npm on a Centos 6 or 7 server running Apache, I hit a few walls and as a matter of process found some commands that are handy to run before doing a deep dive in Google.


Cleaning the cache

sudo yum clean all
rm -rf /var/cache/yum/*

To make the cache

sudo yum clean all; sudo yum makecache

If you want to run several commands use semi-colon as noted above.


ls commands in Apache / Linux

This page shows a growing list of common commands for viewing and managing your Centos server.

ls syntax
$ ls [options] [file|dir]

ls command main options:

Installing Laravel on Apache

Installing Laravel on an Apache server was going to be a no fuss process said no developer!  Research done.  Documentation looks good and easy to follow.  Time to load Laravel.


The set-up

The install notes on Laravel are easy to follow.  Beginning with checking that your server is able to install Laravel.

PHP version on Apache Centos 7

I need to set the default php-version of a subscription to php7.3.  The current server php version is PHP 7.1.33 (cli) (built: Oct 25 2019 11:33:58) ( NTS ).

Using a shell program (I used Terminal) from the home directory I ran:

export PATH=/opt/plesk/php/7.3/bin:$PATH;

centos 6 use

service httpd restart

centos 7 use

composer memory_limit

A recent attempt to run an update composer (regular activity for many of us), I had a memory limit issue.  This was surprising because the memory setting via Plesk is set to 2G.  Yet through Terminal it was showing only 128MB.  What gives??  

The error I was seeing:

Installing Erlang XMPP on Apache

I'm writing these steps primarily for myself as a reference.  However, if someone else finds them useful to great.

Adding XMPP framework to your server.  Initially I was going to add Prosody, however as I'm working off an Apache server with Centos 6.10 this quickly proved to a goal that was out of reach.  Instead, I pivoted and redirected to Erlang.  

Input box page not saving

We had an issue recently where saving a page in the admin area produced one of the following outcomes:

Subscribe to apache