Web Solutions and Technical Support Resources
Ansible Playbook to Install WordPress with LAMP
This article will guide you on the step to follow to use #Ansible Playbook to install #WordPress with #LAMP on #Ubuntu 18.04.
In Ansible, the role is the primary mechanism for breaking a #playbook into multiple files. This simplifies writing complex #playbooks, and it makes them easier to reuse. The breaking of playbook allows you to logically break the playbook into reusable components.
To start using Ansible:
1. Prerequisites.
2. Install Ansible.
3. Establish a manual connection to a managed node.
4. Run your first network Ansible command.
5. Create and run your first network Ansible Playbook.
6. Gathering facts from network devices.
Configure Reporting Services in SQL Server
The article will guide you on the steps to follow to configure #reporting services after renaming the #SQL server. Also , you will learn how to rename the SQL server instance.
To Configure #Report Server After Renaming SQL Server #Instance:
1. Go to #Database Setup page.
2. Enter SQL Server name in Server Name and then click Connect.
3. If Reporting Services is configured using the server name, you must update the database connection information whenever the server name is changed.
To change the service account for SQL Server Reporting Services:
i. Open Reporting Services Configuration Manager, and then connect to the instance of SQL Server Reporting Services.
ii. Click #Microsoft service Identity on the left pane.
iii. Change the account and the password in the Account text box and the Password text box, and then click Apply.
Harden the security of Django
This article will guide you on steps to #harden the #security of #Django. We leveraged python-dotenv for handling secrets and settings.
Our sensitive mostly kept in settings.py file. We can protect that data using Python Decouple #Library. It is the library for separating parameters from the source code.
To make Django secure:
1. Use #SSL.
2. Change the URL.
3. Use 'django-admin-honeypot'.
4. Require stronger passwords.
5. Use two-factor authentication.
6. Use the latest version of Django.
7. Never run 'DEBUG' in production.
Install imagemagick on CentOS
This article will guide you on steps to #install #ImageMagick and fix its errors. Basically, ImageMagick is used to manipulate the digital images.
ImageMagick helps to create, edit, compose, or convert #bitmap images. It can read and write images in a variety of formats (over 200) including #PNG, JPEG, GIF, HEIC, TIFF, DPX, EXR, WebP, Postscript, PDF, and #SVG.
To install ImageMagick from the source:
1. First #download the latest version of the program sources - ImageMagick.
2. Unzip the package to a folder of choice.
3. In the folder where you have unzipped ImageMagick run the configuration script.
4. If no errors were found, you can start the install process.
RoundCube CONNECTION FAILED Database Error
This article will guide you on the different methods to fix Database Error: Connection Failed error shows up due to database errors or #PHP #errors.
Establishing a Database Connection #Error basically means that for some reason or another the PHP code was unable to connect to your #MySQL database to retrieve the information it needs to fully build that page. That's why the error is always shown on a blank page because there is no information about your site as it is not connected to your database.
Establishing a Database Connection Error Occur due to:
1. Incorrect Login Credentials.
2. Corrupt #Database
Exim error 53 How to fix it
This article will guide you on how to fix Exim #error #53 which occurs as a result of #database corruption or due to any server related #problems.
If you find the following error in your EXIM logs, it means that your EXIM #databases could be corrupted.
defer (-53): retry time not reached for any host
The fix is to rebuild exim #databases. To rebuild #exim databases you can run the following commands as root:
/usr/sbin/exim_tidydb -t 1d /var/spool/exim retry > /dev/null
/usr/sbin/exim_tidydb -t 1d /var/spool/exim reject > /dev/null
/usr/sbin/exim_tidydb -t 1d /var/spool/exim wait-remote_smtp > /dev/null
/scripts/eximup --force
