{"id":50222,"date":"2025-07-14T09:21:50","date_gmt":"2025-07-14T09:21:50","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=50222"},"modified":"2025-07-14T09:21:50","modified_gmt":"2025-07-14T09:21:50","slug":"xampp-lampp-tutorials-list-of-production-files-to-cleanup-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/xampp-lampp-tutorials-list-of-production-files-to-cleanup-guide\/","title":{"rendered":"XAMPP – LAMPP Tutorials: List of Production Files to Cleanup Guide"},"content":{"rendered":"\n

Here\u2019s a comprehensive and updated tutorial<\/strong> on which files should be cleaned up regularly in a production environment running XAMPP (under \/opt\/lampp<\/code>), what each file\/folder is<\/strong>, and how to automate cleanup safely<\/strong>.<\/p>\n\n\n\n

\n\n\n\n

XAMPP Production File Cleanup Guide<\/strong><\/h1>\n\n\n\n

Keeping Your \/opt\/lampp<\/code> Environment Healthy<\/h2>\n\n\n\n
\n\n\n\n

1. Why Regular Cleanup Is Important<\/strong><\/h3>\n\n\n\n
    \n
  • Performance:<\/strong> Old logs and cache files fill up disk space and slow down the system.<\/li>\n\n\n\n
  • Security:<\/strong> Sensitive info in old logs can be a risk if not managed.<\/li>\n\n\n\n
  • Reliability:<\/strong> Overfilled disk can cause XAMPP\/MySQL\/Apache to crash or refuse new data.<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    2. Key Locations in \/opt\/lampp<\/code> to Clean<\/strong><\/h2>\n\n\n\n

    The typical XAMPP folder structure<\/strong> on Linux (like \/opt\/lampp<\/code>) includes:<\/p>\n\n\n\n

      \n
    • \/opt\/lampp\/logs\/<\/code> \u2014 Apache and XAMPP logs<\/li>\n\n\n\n
    • \/opt\/lampp\/apache\/logs\/<\/code> \u2014 Apache server logs<\/li>\n\n\n\n
    • \/opt\/lampp\/mysql\/data\/<\/code> or \/opt\/lampp\/var\/mysql\/<\/code> \u2014 MySQL data and logs<\/li>\n\n\n\n
    • \/opt\/lampp\/php\/logs\/<\/code> \u2014 PHP logs<\/li>\n\n\n\n
    • \/opt\/lampp\/temp\/<\/code> or \/opt\/lampp\/tmp\/<\/code> \u2014 Temporary files<\/li>\n\n\n\n
    • \/opt\/lampp\/htdocs\/<\/code> \u2014 Website files (may have user\/app caches, uploads, sessions)<\/li>\n\n\n\n
    • Any storage\/<\/code> directories for frameworks like Laravel<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

      3. What Files Should Be Cleaned Regularly?<\/strong><\/h2>\n\n\n\n

      Below are the files and folders to clean, with what they do<\/strong> and how to handle them safely<\/strong>:<\/p>\n\n\n\n

      \n\n\n\n

      A. Apache Log Files<\/strong><\/h3>\n\n\n\n
        \n
      • Location:<\/strong> \/opt\/lampp\/logs\/<\/code> and \/opt\/lampp\/apache\/logs\/<\/code><\/li>\n\n\n\n
      • Files:<\/strong>\n
          \n
        • access.log<\/code><\/li>\n\n\n\n
        • error.log<\/code><\/li>\n\n\n\n
        • Any rotated log files (e.g., error.log.1<\/code>, access.log.1<\/code>, .gz<\/code>, etc.)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • Why:<\/strong> These logs can get huge, fast.<\/li>\n\n\n\n
        • How:<\/strong>\n
            \n
          • Delete<\/strong> old rotated\/compressed logs (e.g., *.gz<\/code>, .1<\/code> files)<\/li>\n\n\n\n
          • Truncate<\/strong> main logs regularly (to avoid interrupting Apache): > \/opt\/lampp\/logs\/access.log > \/opt\/lampp\/logs\/error.log<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n

            B. PHP Error Logs<\/strong><\/h3>\n\n\n\n
              \n
            • Location:<\/strong> \/opt\/lampp\/php\/logs\/<\/code><\/li>\n\n\n\n
            • Files:<\/strong>\n
                \n
              • php_error_log<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
              • Why:<\/strong> Captures PHP warnings\/errors, can grow large.<\/li>\n\n\n\n
              • How:<\/strong>\n
                  \n
                • Truncate<\/strong> periodically: > \/opt\/lampp\/php\/logs\/php_error_log<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n

                  C. MySQL Log and Error Files<\/strong><\/h3>\n\n\n\n
                    \n
                  • Location:<\/strong> \/opt\/lampp\/var\/mysql\/<\/code> or \/opt\/lampp\/mysql\/data\/<\/code><\/li>\n\n\n\n
                  • Files:<\/strong>\n
                      \n
                    • hostname.err<\/code> (e.g., ip-172-31-34-212.err<\/code>)<\/li>\n\n\n\n
                    • mysql-bin.*<\/code> (binary logs, if enabled)<\/li>\n\n\n\n
                    • Slow query logs (mysql-slow.log<\/code>, if enabled)<\/li>\n\n\n\n
                    • Old rotated logs (*.old<\/code>, *.BAK<\/code>, etc.)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                    • Why:<\/strong> Large logs waste space; old binlogs aren\u2019t needed after backup\/replication.<\/li>\n\n\n\n
                    • How:<\/strong>
                      • Truncate<\/strong> the error log (never delete while MySQL is running): > \/opt\/lampp\/var\/mysql\/ip-172-31-34-212.err<\/code><\/li>
                      • Remove<\/strong> old binlogs (only if not needed for recovery\/replication): rm \/opt\/lampp\/var\/mysql\/mysql-bin.00000*<\/code><\/li><\/ul>NEVER delete ibdata1<\/code>, ib_logfile*<\/code>, aria_log*<\/code>, or any database folders\/files here.<\/strong><\/li>\n<\/ul>\n\n\n\n
                        \n\n\n\n

                        D. Temporary Files<\/strong><\/h3>\n\n\n\n
                          \n
                        • Location:<\/strong> \/opt\/lampp\/temp\/<\/code>, \/opt\/lampp\/tmp\/<\/code>, and project storage\/framework\/cache<\/code>, storage\/framework\/sessions<\/code>, etc.<\/li>\n\n\n\n
                        • Files:<\/strong>\n
                            \n
                          • Upload temp files, session files, cache<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                          • Why:<\/strong> Safe to delete files not recently accessed (stale session, cache, failed uploads).<\/li>\n\n\n\n
                          • How:<\/strong>\n
                              \n
                            • Example to remove files older than 2 days: find \/opt\/lampp\/temp\/ -type f -mtime +2 -delete find \/opt\/lampp\/tmp\/ -type f -mtime +2 -delete<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
                              \n\n\n\n

                              E. Application\/Framework Cache & Session Files<\/strong><\/h3>\n\n\n\n
                                \n
                              • Laravel example:<\/strong>
                                \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/sessions\/<\/code>
                                \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/cache\/<\/code>
                                \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/views\/<\/code><\/li>\n\n\n\n
                              • Why:<\/strong> Sessions, cache, and compiled views are safe to clear out if old.<\/li>\n\n\n\n
                              • How:<\/strong> find \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/sessions\/ -type f -mtime +1 -delete find \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/cache\/ -type f -mtime +1 -delete find \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/views\/ -type f -mtime +1 -delete<\/code><\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n

                                F. Old Backup Files<\/strong><\/h3>\n\n\n\n
                                  \n
                                • Location:<\/strong> Wherever you store old .sql<\/code>, .tar<\/code>, .gz<\/code>, etc. (often \/backups\/<\/code> or \/opt\/lampp\/htdocs\/backups\/<\/code>)<\/li>\n\n\n\n
                                • Why:<\/strong> Don\u2019t keep too many old backups.<\/li>\n\n\n\n
                                • How:<\/strong> find \/opt\/lampp\/htdocs\/backups\/ -type f -mtime +7 -delete<\/code> (Deletes backup files older than 7 days.)<\/em><\/li>\n<\/ul>\n\n\n\n
                                  \n\n\n\n

                                  4. What Should You NEVER Delete?<\/strong><\/h2>\n\n\n\n
                                    \n
                                  • Database data files (ibdata1<\/code>, ib_logfile0<\/code>, etc. in var\/mysql\/<\/code>)<\/li>\n\n\n\n
                                  • Anything inside database directories (unless you want to drop\/delete a database)<\/li>\n\n\n\n
                                  • Application files, user uploads, etc. (unless verified as junk)<\/li>\n\n\n\n
                                  • XAMPP config files<\/li>\n<\/ul>\n\n\n\n
                                    \n\n\n\n

                                    5. Automating Cleanup With a Cron Job<\/strong><\/h2>\n\n\n\n

                                    Here\u2019s a sample script<\/strong> you could run daily or weekly via cron:<\/p>\n\n\n

                                    #!\/bin\/bash<\/span>\n\n# Clean Apache logs (keep last 7 days)<\/span>\nfind \/opt\/lampp\/logs\/ -type f -name \"*.gz\"<\/span> -mtime +7<\/span> -delete\nfind \/opt\/lampp\/apache\/logs\/ -type f -name \"*.gz\"<\/span> -mtime +7<\/span> -delete\n\n# Truncate current log files<\/span>\n> \/opt\/lampp\/logs\/access.log\n> \/opt\/lampp\/logs\/error.log\n> \/opt\/lampp\/php\/logs\/php_error_log\n\n# Truncate MySQL error log<\/span>\n> \/opt\/lampp\/var<\/span>\/mysql\/ip-172<\/span>-31<\/span>-34<\/span>-212.<\/span>err\n\n# Clean temp files older than 2 days<\/span>\nfind \/opt\/lampp\/tmp\/ -type f -mtime +2<\/span> -delete\nfind \/opt\/lampp\/temp\/ -type f -mtime +2<\/span> -delete\n\n# Clean Laravel\/Framework session & cache files older than 1 day<\/span>\nfind \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/sessions\/ -type f -mtime +1<\/span> -delete\nfind \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/cache\/ -type f -mtime +1<\/span> -delete\nfind \/opt\/lampp\/htdocs\/your_project\/storage\/framework\/views\/ -type f -mtime +1<\/span> -delete\n\n# Clean old backup files (older than 7 days)<\/span>\nfind \/opt\/lampp\/htdocs\/backups\/ -type f -mtime +7<\/span> -delete\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                                      \n
                                    • Save this as cleanup_xampp.sh<\/code><\/li>\n\n\n\n
                                    • Make it executable:
                                      chmod +x cleanup_xampp.sh<\/code><\/li>\n\n\n\n
                                    • Add to crontab for daily execution (example at 2:30am): 30 2 * * * \/path\/to\/cleanup_xampp.sh<\/code><\/li>\n<\/ul>\n\n\n\n
                                      \n\n\n\n
                                      6. Monitoring Disk Usage<\/strong><\/h2>\n\n\n\n
                                        \n
                                      • Regularly check usage: du -sh \/opt\/lampp\/*<\/code><\/li>\n\n\n\n
                                      • Be proactive; if logs grow rapidly, increase cleanup frequency or log rotation.<\/li>\n<\/ul>\n\n\n\n
                                        \n\n\n\n
                                        7. Security and Best Practices<\/strong><\/h2>\n\n\n\n
                                          \n
                                        • Always review before deleting\u2014automate with care<\/strong>.<\/li>\n\n\n\n
                                        • Take regular full backups before aggressive cleaning, especially before touching anything in var\/mysql\/<\/code>.<\/li>\n\n\n\n
                                        • Set up logrotate<\/strong> for Apache, PHP, and MySQL logs for better management.<\/li>\n\n\n\n
                                        • Document your cleanup routines for the team.<\/li>\n<\/ul>\n\n\n\n
                                          \n\n\n\n
                                          Summary Table<\/strong><\/h2>\n\n\n\n
                                          Location<\/th>What to Clean<\/th>Command Example<\/th>Notes<\/th><\/tr><\/thead>
                                          \/opt\/lampp\/logs\/<\/code><\/td>Apache logs<\/td>> access.log<\/code><\/td>Rotate\/truncate; don\u2019t delete active logs<\/td><\/tr>
                                          \/opt\/lampp\/php\/logs\/<\/code><\/td>PHP logs<\/td>> php_error_log<\/code><\/td><\/td><\/tr>
                                          \/opt\/lampp\/var\/mysql\/<\/code><\/td>MySQL error logs<\/td>> hostname.err<\/code><\/td>Never delete core DB files<\/td><\/tr>
                                          \/opt\/lampp\/tmp\/<\/code> \/opt\/lampp\/temp\/<\/code><\/td>Temp files<\/td>find ... -mtime +2 -delete<\/code><\/td>Only old files<\/td><\/tr>
                                          \/opt\/lampp\/htdocs\/project\/storage\/<\/code><\/td>Sessions, cache<\/td>find ... -mtime +1 -delete<\/code><\/td>Framework-specific<\/td><\/tr>
                                          \/opt\/lampp\/htdocs\/backups\/<\/code><\/td>Old backups<\/td>find ... -mtime +7 -delete<\/code><\/td>Optional<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                          \n\n\n\n
                                          Conclusion<\/strong><\/h2>\n\n\n\n
                                          Regular cleanup of log, temp, and cache files under \/opt\/lampp<\/code> keeps your production XAMPP environment healthy, secure, and reliable<\/strong>.
                                          Never delete database or config files, always backup before cleaning<\/strong>, and automate your routines for peace of mind!<\/p>\n\n\n\n
                                          \n\n\n\n
                                          <\/p>\n\n\n\n
                                          <\/p>\n","protected":false},"excerpt":{"rendered":"
                                          Here\u2019s a comprehensive and updated tutorial on which files should be cleaned up regularly in a production environment running XAMPP (under \/opt\/lampp), what each file\/folder is, and how to automate… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-50222","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50222","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=50222"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50222\/revisions"}],"predecessor-version":[{"id":50223,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50222\/revisions\/50223"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=50222"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=50222"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=50222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}