Enable CDN in Prestashop and Resolve related issues - How to do it ?
This article covers how to enable CDN on PrestaShop for our customers.
You can Speed up your website with the PrestaShop CDN addon.
Faster loading leads immediately to happier users and higher conversions.
Making your pages load faster will also improve your SEO.
Google ranks faster websites higher, so you'll soon receive more visitors from search engines.
To How to Enable CDN for Prestashop:
1. Make sure Prestashop is installed and work normally.
2. Login to Prestashop admin panel (e.g. http://prestashop.testing.com.my/admin1234/)
3. Navigate to Advanced Parameters > Performance.
4. Scroll down the page to Media servers and fill in the CDN hostname.
5. Click Save at the top right corner to save the setting.
Error: Function lookup() did not find a value for the name DEFAULT_EXEC_TIMEOUT
This article covers how to fix this issue found while installing OpenStack with packstack.
In the case you installed packstack with epel repo enabled, you need to uninstall it and all the dependences, and re-install it after disabling epel, so all the proper versions of dependencies are installed correctly.
1. To begin, ensure that epel repo is disabled and try again.
2. Run the following commands:
# yum autoremove epel-release
# yum autoremove openstack-packstack
# yum clean all
# yum install -y openstack-packstack
VNC error 'Timed out waiting for the response from the host computer' - Fix it Now ?
This article covers methods to fix VNC 'Timed out waiting for the response from the host computer' error for our customers.
1. You can try adding a firewall rule:
$ sudo /sbin/iptables -I INPUT 1 -p TCP --dport 5901:5910 -j ACCEPT
2. Or directly modify the file /etc/sysconfig/iptables file and add a line:
-A INPUT -p tcp -m state --state NEW -m tcp --dport 5901:5910 -j ACCEPT
3. Restart the iptables service:
$ service iptables restart
4. If there is no iptables.service file, use yum to install it:
$ yum install iptables-services
5. Then Run the command,
$ sudo /sbin/iptables -I INPUT 1 -p TCP --dport 5901:5910 -j ACCEPT
The firewall does not need to be restarted, nor does it execute flush privileges, and then connect with the VNC client and find that the connection is up.
Empty Screen in Nagios XI for Wizard - Fix it Now ?
This article covers ways to fix 'Empty Screen in Nagios XI' for our customers. In some pages of XI you may come across empty screens, such as no configuration wizards appearing under the Configure menu.
When plugins, components or wizards are not installed through the proper menus, this creates problems in Nagios XI, such as "wiping out" all wizards, so they can not be viewed in the Web interface, blank pages in the Web browser and other weird behaviors.
To fix this Nagios error:
Remove the problematic component/wizard by running in terminal as a root:
$ rm -rf /usr/local/nagiosxi/html/includes/components/somedashlet
$ rm -rf /usr/local/nagiosxi/html/includes/components/somecomponent
$ rm -rf /usr/local/nagiosxi/html/includes/configwizards/somewizard
Improve phone support efficiency - Facts you need to know ?
This article covers some key points to improve phone support efficiency.
In the contact centre environment, becoming more efficient involves reviewing internal processes, eliminating unnecessary steps and duplicate handling, and often implementing new processes.
The main aims are to reduce call handling times and improve first call resolution.
Methods to Boost Contact Centre Efficiency:
1. Migrate to a cloud hosted solution
Cloud hosted technology solutions don't rely on equipment infrastructure, and therefore scale from five agents to one thousand and back again without incurring any downtime.
2. Improve your self-service options
Customers want choice. They want to be able to take care of routine and straightforward interactions themselves.
3. Implement automatic call distribution
Poor call traffic distribution results in customers being sent to the wrong department, which ties up personnel and delays them in getting on with helping the right people.
4. Improve your verification process
The average time to verify the identity of a user using Personal Verifiable Questions (PVQs) is 45-90 seconds.
5. Offer a call back service
A cost-effective way to improve team efficiency, and the customer experience, is to use call-backs to defer calls until a later time.
There are two options for call backs.
i. Virtual queuing – whereby the customer's place in the queue is held and called when her turn arrives
ii. A timed call-back, where customers are offered a selection of time slots for their call-back. This option allows you to schedule the call back to take place during a "trough" period, and so keeps staff productive during quieter periods.
Activate python virtualenv in Dockerfile - How to perform it ?
This article covers how to Activate python virtualenv in Dockerfile.
Basically, to package Python application in a Docker image, we often use virtualenv. However, to use virtualenv, we need to activate it.
Therefore, there is no point in using virtualenv inside a Docker Container unless you are running multiple apps in the same container, if that's the case I'd say that you're doing something wrong and the solution would be to architect your app in a better way and split them up in multiple containers.
There are perfectly valid reasons for using a virtualenv within a container.
You don't necessarily need to activate the virtualenv to install software or use it.
Try invoking the executables directly from the virtualenv's bin directory instead:
FROM python:2.7
RUN virtualenv /ve
RUN /ve/bin/pip install somepackage
CMD ["/ve/bin/python", "yourcode.py"]
One solution is to explicitly use the path to the binaries in the virtualenv.
In this case we only have two repetitions, but in more complex situations you’ll need to do it over and over again.
Besides the lack of readability, repetition is a source of error.
As you add more calls to Python programs, it's easy to forget to add the magic /opt/venv/bin/ prefix.
It will (mostly) work though:
FROM python:3.8-slim-buster
RUN python3 -m venv /opt/venv
# Install dependencies:
COPY requirements.txt .
RUN /opt/venv/bin/pip install -r requirements.txt
# Run the application:
COPY myapp.py .
CMD ["/opt/venv/bin/python", "myapp.py"]
The only caveat is that if any Python process launches a sub-process, that sub-process will not run in the virtualenv.
