{"id":482510,"date":"2026-06-05T10:12:35","date_gmt":"2026-06-05T10:12:35","guid":{"rendered":"https:\/\/savepearlharbor.com\/?p=482510"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-29T21:00:00","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=482510","title":{"rendered":"Mini Bucket 3.6.2: From Beta to Release. Full Installation with Screenshots and Comments"},"content":{"rendered":"
\n

Why Debian 9, PHP 7.0, and no frameworks. And how to set up HTTPS in 5 minutes.<\/p>\n

<\/figure>\n

Foreword for those who haven’t read the first article<\/h4>\n

Last time, I told the story<\/a> of how I wanted to make a couple of pages for SAMBA and NFS, but ended up with a NAS control panel of 20+ pages. I named the project Mini Bucket.<\/p>\n

Important: That version was a beta. Raw, with rough edges, but alive. Its goal was to demonstrate the concept. And people got interested. So, it needs to be polished.<\/p>\n

Now \u2013 version 3.6.2. A ton of problems have been fixed, security has been added, a separate domain, forum, and wiki have appeared. Today, I’ll walk you through the installation step-by-step with screenshots.<\/p>\n

But first \u2013 a quick summary of what has changed. Then \u2013 pure practice.<\/p>\n

What\u2019s Fixed in 3.6.2 (The Main Points)<\/h4>\n

Security: Critical Holes Closed<\/h3>\n

In the beta, worker files, cron scripts, temporary files, and logs were located in the web server zone. Technically, you could send a request to an executable file without authorization \u2013 no API key, no login\/password.<\/p>\n

Fixed: All critical files have been moved to\u00a0\/var\/www\/minib\/<\/code>, outside the website’s folder. The Apache configuration has been revised. Temporary files and logs are now inaccessible from the outside.<\/p>\n

Logic and Bugs<\/h3>\n