Using any Content Management System (CMS) software, in first place, there is no silver bullet for creating a site that can fully survive an upgrade with no developer assistance needed. It’s the same for Drupal website as well.
This is why certain things to be taken care of when planning a Drupal website development project that can save maintenance time down the road.
Mistake#5: Keeping Extraneous File In The VSC Repository.
Image asset files, holiday pictures, or database dumps are generally pushed to the repository which is very unhealthy practice. Try to keep the VCS as clean and small as
possible
Mistake#4: Missing Out Of Date Development And Staging Environments.
Say for instance, developers conduct testing only in production because the other environments have old data or no connection to an external service. Ensure to maintain testing environments as similar to production as possible. This way you can easily copy from production and execute tests to assure that changes will work when moved to production.
Mistake#3: Out-Of-Date Code For Core And Contributed Modules.
At times, businesses prefer out of date code thinking to save some money. But keeping all modules and core as current as possible saves you in a long run.
Mistake#2: The Thought- Repair Better Than Maintenance
As a matter of fact, Drupal is a well-architected CMS that will continue to perform for a long time. However, keeping things up to date ensures a good experience for your visitors. If unnoticed, chances are there for site to get hacked which is much more costly
Mistake#1: Less Security During Deployment
Any developer can take a snapshot of production to install on their laptop which means anybody can misuse it. Allow developers to take snapshots and have other access to development and staging environments without giving access to the production environment only for the most trusted users.
Summing up, Keep your code under version control and review all logs periodically, including Apache, Drupal, and MySQL.
No comments:
Post a Comment