There are a number of excellent tutorials. I recommend this one:
Basically, you are going to create a .htaccess file in the directory you want to protect. This .htaccess file will have a line in it, AuthUserFile, that will point to an htpasswd file.
Authtype Basic
AuthName "RESTRICTED - cloudkicker"
AuthUserFile <path to your htpasswd file>
Require valid-user The htpasswd file should be placed outside of your web directory (e.g., /etc/apache2/myhtpasswdfile). This htpasswd file will contain a username and a password hash, like this:
testuser:{SHA}3S7bh+qet6Mv1AVydtOh+rhhwdU= You can generate this file in linux by typing:
htpasswd -c /path/to/my/htpasswd testuser Both git fetch and git pull talk to a remote repository, but they do very different things to your…
Sometimes the change you need already exists, just on the wrong branch. A hotfix lands…
Email is still one of the most important communication channels inside modern applications. Password resets,…
Nginx is a high-performance web server and reverse proxy trusted by some of the largest…
ufw (Uncomplicated Firewall) sits on top of iptables (or nftables on newer systems) and replaces…
When you share a server with a team or investigate unexpected activity, the first question…