Find all the WordPress we have
How many WordPress do you have? You know it? Sometimes I don’t… and that doubt generates a question for me: how can I know how many I have and if they are updated?
How many WordPress do you have? You know it? Sometimes I don’t… and that doubt generates a question for me: how can I know how many I have and if they are updated?
Security, nowadays, is no longer enough with a username and a password, whether it is more or less secure. A second authentication factor is now required.
One of the usual recommendations that are made for WordPress for better optimization is not to use the native WP-Cron system, but to make calls using a task scheduler.
On many occasions we need to test a plugin, a theme or some specific Functionality of WordPress, but it is very likely that you are lazy to have to do a complete installation to test a functionality.
When accessing a server it can be done by SSH, and by default with a username and password. But if you have to give access to other people, it is best to give them access through an SSH key generated for each user.
With the RGPD, the LOPD and the ePrivacy the measurement has become more complicated and, if we want everything to work correctly and we can measure first hand we have to use a system in which cookies are not a problem.
Surely you use the “top” or even “htop” tool to make it look more colorful when analyzing the state of your server’s resources, but this only analyzes the processes…
With the Logwatch tool we can receive every day in our mailbox a summary of the analysis of the server logs to know what has happened on the machine.
Every so often we have updates of MariaDB versions, and it can be interesting to make an update between major versions. How are they carried out?
In the same way that we want to know how much traffic a website supports and for which we can do a stress test, we can also apply the same technique to the database.