Caddy is one of the webserver. It is simple enough to be used as a quick development server and strong enough to be used in productions.<\/p>\n
Basic Features of Caddy :
\nAn easy, intuitive way to configure your site. It’s not scripting, and not hard to memorize.
\nCaddy can be extended with plugins. All server types, directives, DNS providers, and more features are plugins! They’re easy to write and get compiled in directly.
\nWhen the going gets tough, Caddy gets going on more CPUs. Go’s scheduler understands Go code, and goroutines are more lightweight than system threads. So yeah, it’s fast.
\nCaddy can be configured to run system commands at startup and shutdown. Useful when your site requires other processes running.
\nCaddy can write a log of all its significant events, especially errors. Log to a file, stdout\/stderr, or a local or remote system log!<\/p>\n
Step 1 -> Installing the Caddy on CentOS :<\/p>\n
$ wget -s https:\/\/getcaddy.com | bash<\/pre>\nType and execute the above command to install caddy server’s binary files.<\/p>\n
The command output will look like this:<\/p>\n
Downloading Caddy for linux\/amd64…
\nhttps:\/\/caddyserver.com\/download\/linux\/amd64?plugins=
\nExtracting…
\nPutting caddy in \/usr\/local\/bin (may require password)
\n[sudo] password for sammy:
\nCaddy 0.10.2
\nSuccessfully installed<\/p>\nTo verify the caddy binary files location, use the below command<\/p>\n
$ which caddy<\/p>\n
Steps 2 -> Creating User and Group for Caddy<\/p>\n
To create user named caddy let’s type:<\/p>\n
$ sudo adduser -r -d \/var\/www -s \/sbin\/nologin caddy<\/p>\n
Here \/var\/www is the home directory for the user caddy.<\/p>\n
Step 3 -> Configuring Directories for Caddy’s files<\/p>\n
First, create a directory that will house the main Caddyfile, which is a configuration file that tells Caddy what websites should it serve and how.<\/p>\n
First, create a directory for the main Caddyfile, which is a configuration file that tells Caddy what websites should it serve and how.<\/p>\n
sudo mkdir \/etc\/caddy<\/p>\n
Change the owner of this directory to the root user and its group to www-data so Caddy can read it.<\/p>\n
sudo chown -R root:caddy \/etc\/caddy<\/p>\n
In this directory, create an empty Caddyfile which we’ll edit later.<\/p>\n
sudo touch \/etc\/caddy\/Caddyfile<\/p>\n
Create another directory in \/etc\/ssl to store the SSL private keys and certificates that it automatically obtains from Let’s Encrypt.<\/p>\n
sudo mkdir \/etc\/ssl\/caddy<\/p>\n
Caddy needs to be able to write to this directory when it obtains the certificate, so make the owner the caddy user<\/p>\n
sudo chown -R caddy:root \/etc\/ssl\/caddy<\/p>\n
Then make sure no one else can read those files by removing all the access rights for others.<\/p>\n
sudo chmod 0770 \/etc\/ssl\/caddy<\/p>\n
Make a directory that should be completely owned by caddy.<\/p>\n
sudo mkdir \/var\/www<\/p>\n
sudo chown caddy:caddy \/var\/www<\/p>\n
Step 4 -> Configuring Caddy as a System Service<\/p>\n
While Caddy does not install itself as a service, the project provides an official systemd unit file. This file does assume the directory structure we set up in the previous step, so make sure your configuration matches.<\/p>\n
Download the file from the official Caddy repository. The additional -o parameter to the curl command will save the file in the \/etc\/systemd\/system\/ directory and make it visible to systemd.<\/p>\n
<\/p>\n
$ sudo curl -s https:\/\/raw.githubusercontent.com\/mholt\/caddy\/master\/dist\/init\/linux-systemd\/caddy.service -o \/etc\/systemd\/system\/caddy.service<\/p>\n
<\/p>\n
Let’s open the file with vi or your favourite text editor to modify the file slightly to make it use our unprivileged caddy user to run the server.<\/p>\n
$ sudo vi \/etc\/systemd\/system\/caddy.service<\/p>\n
\/etc\/systemd\/system\/caddy.service
\n; User and group the process will run as.
\nUser=www-data
\nGroup=www-data<\/p>\nFind the above lines and Change both values to caddy as follows:<\/p>\n
; User and group the process will run as.
\nUser=caddy
\nGroup=caddy<\/p>\nSave and close the file to exit.<\/p>\n
To make systemd aware of the new service file.<\/p>\n
$ sudo systemctl daemon-reload<\/p>\n
Enable Caddy to run on boot.<\/p>\n
$ sudo systemctl enable caddy.service<\/p>\n
To verify that the service has been properly loaded and enabled to start on boot by checking its status.<\/p>\n
$ sudo systemctl status caddy.service<\/p>\n
The output should look as follows:<\/p>\n
\u25cf caddy.service – Caddy HTTP\/2 web server
\nLoaded: loaded (\/etc\/systemd\/system\/caddy.service; enabled; vendor preset: disabled)
\nActive: inactive (dead)
\nDocs: https:\/\/caddyserver.com\/docs<\/p>\nYou have now configured Caddy as a system service which will start automatically on boot without the need to run it manually.<\/p>\n
Step 5 -> Host a Test Website<\/p>\n
This command will create an index.html file in the website directory we created earlier with just the one line of text, <h1>CADDY WEBSITE<\/h1>, inside.<\/p>\n
echo ‘<h1>CADDY WEBSITE<\/h1>’ | sudo tee \/var\/www\/index.html<\/p>\n
Open the Caddyfile you created in Step 2 using vi or your favorite text editor.<\/p>\n
http:\/\/ {
\nroot \/var\/www
\ngzip
\n}<\/p>\nThen save the file and exit. Let’s explain what this specific Caddyfile does.<\/p>\n
Once the configuration file is ready, start the Caddy service.<\/p>\n
$ sudo systemctl start caddy<\/p>\n
First, replace the address definition of http:\/\/ with your domain. This removes the insecure connection forced by HTTP and provides a domain name for the TLS certificate. Second, provide Caddy with an email address using the tls directive inside the server block.<\/p>\n
The modified Caddyfile should look as follows, with your domain and email address substituted in:<\/p>\n
example.com {
\nroot \/var\/www
\ngzip
\ntls anbupriyan@example.com
\n}<\/p>\nSave the file and exit the editor. To apply the changes, restart Caddy.<\/p>\n
$ sudo systemctl restart caddy<\/pre>\n<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Caddy is one of the webserver. It is simple enough to be used as a quick development server and strong<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[1],"tags":[],"class_list":["post-164","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/posts\/164","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/comments?post=164"}],"version-history":[{"count":5,"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/posts\/164\/revisions"}],"predecessor-version":[{"id":173,"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/posts\/164\/revisions\/173"}],"wp:attachment":[{"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/media?parent=164"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/categories?post=164"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxresellerwebhosting.in\/blog\/wp-json\/wp\/v2\/tags?post=164"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}