Microsoft Hyper-V for Home Server<\/a><\/strong><\/p>\n\n\n\nYou may use TrueNAS \/ Proxmox \/ VMWare \/ VirtualBox any other Hypervisor to deploy the VM. Process is same inside the VM so it doesn’t matter in which platform this VM is running.<\/p>\n\n\n\n
For our use, we are creating a Hyper-V VM with 2 Cores and 2GB RAM along with 16GB vDisk on our Desktop PC running AMD Ryzen 5 CPU along with Windows 11 Pro. For a lightweight and little traffic WordPress website, this is more than sufficient, in fact, our website with very low traffic can run with a single core and 1GB RAM too.<\/p>\n\n\n\nPro Tip -><\/strong> During Ubuntu Server installation within your VM, while at the installation wizard, most of the things would stay default, just ensure to turn on the check box for “Install OpenSSH Server” for remote login.<\/p>\n\n\n\n\n\t\t\t\n\t\t\t\tLogin & Update Ubuntu Server<\/strong><\/p>\n\n\n\nFirst step after installation of Ubuntu Server in your VM is to log in and update the Ubuntu Server. You can use your host PC or any computer within the same LAN network to remotely connect to this Virtual Machine running your Ubuntu Server. Just open up “Command Prompt” in Windows and type the following command,ssh username@local.lan.ip.address<\/code><\/mark> -> here, username is the user name of your Ubuntu Server user and local lan ip address is the local LAN IP of the Ubuntu Server VM. In our case, it is following,ssh hunky@192.168.1.42<\/code><\/p>\n\n\n\nThe system will ask for the password, type the password (remember, for security reason, it won’t be visible) and log in to your Ubuntu Server. Once login, run these bellow commands one by one to update & then reboot the system.<\/p>\n\n\n\nsudo sutimedatectl set-timezone Asia\/Kolkata<\/code> -> Adjusting the Time Zone for ISTapt update && apt upgrade -y && rebootAdjusting the Swap\/Page File<\/strong>sudo su<\/code>swapoff \/swap.img && dd if=\/dev\/zero of=\/swap.img bs=1M count=512 && chmod 600 \/swap.img && mkswap \/swap.img && swapon \/swap.img<\/code>Installing Docker \/ Docker Compose<\/strong><\/p>\n\n\n\nAfter the update and reboot, log back into your Ubuntu Server and run the following commands one by one to install Docker and then Docker Compose,sudo su<\/code>apt install apt-transport-https ca-certificates curl software-properties-common -y<\/code>curl -fsSL https:\/\/download.docker.com\/linux\/ubuntu\/gpg | sudo gpg --dearmor -o \/usr\/share\/keyrings\/docker-archive-keyring.gpg<\/code>echo \"deb [arch=$(dpkg --print-architecture) signed-by=\/usr\/share\/keyrings\/docker-archive-keyring.gpg] https:\/\/download.docker.com\/linux\/ubuntu $(lsb_release -cs) stable\" | sudo tee \/etc\/apt\/sources.list.d\/docker.list > \/dev\/null<\/code>apt update && apt install docker-ce -y<\/code>reboot<\/code><\/p>\n\n\n\nWordPress Deployment<\/strong><\/p>\n\n\n\nWe are going to use the official Docker Container image from WordPress for this along with some other dependencies from their respective official docker images. Like, the MariaDB\/MySQL for database, phpmyadmin for database management, and a web-based file editor (FileBrowser) to access the wordpress files or database for DevOps requirements.<\/p>\n\n\n\n
Creating the Directory Structure<\/strong> & Deploying FileBrowsersudo su<\/code>cd \/home\/username<\/mark><\/code> -> replace this username with your ubuntu login username<\/p>\n\n\n\nThe copy paste this entire command and run it, remember to replace the username with your own ubuntu server user name before running it.<\/p>\n\n\n\n
mkdir -p wp\/fb && cd wp\/fb && cat << 'EOF' > docker-compose.yml\nservices:\n filebrowser:\n image: hurlenko\/filebrowser\n container_name: filebrowser\n user: \"${UID}:${GID}\"\n ports:\n - 8085:8080\n volumes:\n - \/home\/username<\/mark>\/wp:\/data\n - .\/:\/config\n environment:\n - FB_BASEURL=\/filebrowser\n restart: always\nEOF<\/code><\/pre>\n\n\n\nThis command will create a docker compose file for file browser along with the configuration code inside that file. Now it is time to run the command to pull the official file browser container image and run it in your local ubuntu server. To do that, run the following commands,sudo su<\/code>cd \/home\/username<\/mark>\/wp\/fb<\/code> -> Replace the username<\/mark> with your own ubuntu server user namedocker compose up -d<\/code><\/p>\n\n\n\nFile Browser should now be installed and accessible locally (within your LAN Network) via any browser at http:\/\/Ubuntu.Server.LAN.IP:8085 <\/p>\n\n\n\n
Earlier the default username and password used to be admin \/ admin for filebrowser but now, they have changed the process and creates a random password for each deployment. To find the filebrowser login password, you need to run folloiwng command and copy the password from section “User ‘admin’ initialized with randomly generated password: xxxxxxxxxx<\/mark><\/p>\n\n\n\ndocker logs filebrowser<\/code><\/p>\n\n\n\nYou can select that string using mouse highlighting and then press “enter” key in your keyboard to copy it. Now you have the password and user name is admin. So now we can login via http:\/\/ubuntu.vm.lan.ip:8085<\/p>\n\n\n\n\n\t\t\t\n\t\t\t\tEnsure to change this password with your own to complete the file browser installation.<\/p>\n\n\n\n
WordPress Docker Stack Deployment<\/strong><\/p>\n\n\n\nNow we shall create the docker compose file to deploy WordPress along with all the dependencies from their official docker images. We shall be using WordPress \/ MariaDB (for SQL) \/ phpMyAdmin (DB Manager) \/ Redis Server (Caching)sudo su<\/code>cd \/home\/username<\/mark>\/wp<\/code> -> Replace the username<\/mark> with your own ubuntu server user namecat << 'EOF' > docker-compose.yml\nservices:\n # MariaDB Database\n db:\n image: mariadb:latest\n container_name: wordpress_db\n restart: always\n environment:\n MYSQL_ROOT_PASSWORD: Change@Me<\/mark>\n MYSQL_DATABASE: wordpress\n MYSQL_USER: wordpress\n MYSQL_PASSWORD: Change@Me<\/mark>\n volumes:\n - .\/db_data:\/var\/lib\/mysql\n networks:\n - wordpress_network\n\n # Redis Cache\n redis:\n image: redis:latest\n container_name: wordpress_redis\n restart: always\n networks:\n - wordpress_network\n\n # WordPress Application\n wordpress:\n image: wordpress:latest\n container_name: wordpress_app\n restart: always\n environment:\n WORDPRESS_DB_HOST: db\n WORDPRESS_DB_USER: wordpress\n WORDPRESS_DB_PASSWORD: Change@Me<\/mark>\n WORDPRESS_DB_NAME: wordpress\n WORDPRESS_CONFIG_EXTRA: |\n define('WP_REDIS_HOST', 'redis');\n define('WP_REDIS_PORT', 6379);\n define('WP_CACHE', true);\n define('WP_MEMORY_LIMIT', '256M');\n define('WP_MAX_UPLOAD_SIZE', '250M');\n volumes:\n - .\/wordpress_data:\/var\/www\/html\n ports:\n - \"8000:80\"\n depends_on:\n - db\n - redis\n networks:\n - wordpress_network\n\n # phpMyAdmin for Database Management\n phpmyadmin:\n image: phpmyadmin:latest\n container_name: wordpress_phpmyadmin\n restart: always\n environment:\n PMA_HOST: db\n PMA_ARBITRARY: 1\n UPLOAD_LIMIT: 250M\n ports:\n - \"8080:80\"\n depends_on:\n - db\n networks:\n - wordpress_network\n\n# Define the network\nnetworks:\n wordpress_network:\n driver: bridge\n\n# Volumes for persistent data\nvolumes:\n db_data:\n driver: local\n driver_opts:\n type: none\n device: .\/db_data\n o: bind\n wordpress_data:\n driver: local\n driver_opts:\n type: none\n device: .\/wordpress_data\n o: bind\nEOF<\/code><\/pre>\n\n\n\nNow run the following command for deployment and installation,docker compose up -d<\/code>File Browser<\/td> phpmyadmin<\/td> WordPress<\/td><\/tr> http:\/\/Ubuntu.Server.LAN.IP:8095<\/td> http:\/\/Ubuntu.Server.LAN.IP:8080<\/td> http:\/\/Ubuntu.Server.LAN.IP:8000<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n
\n
\n\t\t\t\n\t\t\t\tFile Browser<\/figcaption><\/figure>\n<\/div>\n\n\n\n\n
\n\t\t\t\n\t\t\t\t\n
Do not proceed with the installation of WordPress yet. Before we proceed, we need to configure our domain name and cloudflare tunnel.<\/p>\n\n\n\n
Domain Name<\/strong><\/p>\n\n\n\nFirst step in this project is to register a domain name. In our case, although we have a domain name, but for this project, we are buying another domain name. It is LazyTourer.PW<\/mark>CloudFlare Setup<\/strong><\/p>\n\n\n\nYou will need to create a free cloudflare account from cloudflare.comAdding domain to CloudFlare Dashboard<\/strong>\n
\n
\n\t\t\t\n\t\t\t\t\n
\n\t\t\t\n\t\t\t\tEnter your domain name and ensure to select the FREE plan and click continue. Remember, we only need the free plan, do not avail any trial or such options. Just select the free plan, that is sufficient for the project and our need.<\/p>\n\n\n\n
\n
\n
\n\t\t\t\n\t\t\t\t\n
\n\t\t\t\n\t\t\t\tOn the next page, delete if any previous \/ existing DNS record is found. Ensure that there are no DNS records by deleting any such entries and continue to next step. In the next step, cloudflare will generate two NS record entry for your domain. Copy those two records into a notepad file. Then click continue in the bottom to complete the domain addition process.<\/p>\n\n\n\n
\n
\n
\n\t\t\t\n\t\t\t\t\n
\n\t\t\t\n\t\t\t\tAdding CloudFlare NS Records to your New Domain<\/strong>\n\t\t\t\n\t\t\t\tUsually it takes around 10\/15 mins for the records to get updated, but for some rare cases, it may take upto 48 hours for the records to update and the domain is shown active in your cloudflare account. You have to wait till the domain is shown active in your cloudflare account.
\n
\n\t\t\t\n\t\t\t\tCreating CloudFlare Tunnel<\/strong>\n
\n
\n\t\t\t\n\t\t\t\t\n
\n\t\t\t\n\t\t\t\tNow enter a name of the tunnel as per your liking and click next \/ save tunnel. This will bring you to the tunnel installation page. We are running Ubuntu Server in our VM, so we need the “debian” installation code.<\/p>\n\n\n\n\n\t\t\t\n\t\t\t\tNow click that little copy button in that, follow the on screen instructions if needed to copy the entire code. Remember the entire code is super long and hidden, so copy using that little button given in the web page and run it in your Ubuntu Server.<\/p>\n\n\n\n
Creating Domain \/ Sub Domains \/ Public Host Names<\/strong><\/p>\n\n\n\nAs of now, the tunnel setup is done but we need to create the domain \/ sub domains for our services (Main WordPress website, File Browser and phpmyadmin) for traffic routing and external web access. So at the bottom of the tunnel installation page of CloudFlare website, click next to proceed for public host name creating.URL<\/strong><\/td>Service<\/strong><\/td>Local Connection<\/strong><\/td><\/tr>lazytourer.pw<\/td> WordPress Main Website<\/td> localhost:8000<\/td><\/tr> files.lazytourer.pw<\/td> File Browser<\/td> localhost:8095<\/td><\/tr> db.lazytourer.pw<\/td> phpmyadmin<\/td> localhost:8080<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nAdd 3 public host names under this tunnel with following details,<\/p>\n\n\n\nSub Domain<\/strong><\/td>Domain<\/strong><\/td>Path<\/strong><\/td>Type<\/strong><\/td>URL<\/strong><\/td><\/tr>blank\/empty<\/td> your.domain<\/td> blank\/empty<\/td> HTTP<\/td> localhost:8000<\/td><\/tr> files<\/td> your.domain<\/td> blank\/empty<\/td> HTTP<\/td> localhost:8085<\/td><\/tr> db<\/td> your.domain<\/td> blank\/empty<\/td> HTTP<\/td> localhost:8080<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n\t\t\t\n\t\t\t\tAccess Via Web<\/strong><\/p>\n\n\n\nOnce you have created all three public host names, now your wordpress along with File Browser and phpmyadmin is available for outside web access. You can now access & proceed with the installation for WordPress via URL https:\/\/your.domain<\/p>\n\n\n\n
Dont forget to change the default password of your File Browser. The default user name & password is admin\/admin. So login via URL files.your.domain and change the password.<\/p>\n\n\n\n
Maintenance and Updates<\/strong><\/p>\n\n\n\nThere are 3 main things to update in this deployment. Operating System and Software \/ Docker Containers \/ WordPress Internal (Plugins \/ Themes).<\/p>\n\n\n\n
\n
\n
WordPress Internal<\/strong>\n
\n\t\t\t\n\t\t\t\tDocker Container Updates<\/strong>\n
\n
File Browser<\/strong>sudo su<\/code>cd \/home\/username<\/mark>\/WordPress\/FB<\/code> -> Replace this user name with your owndocker compose stop && docker compose pull && docker compose up -d<\/code><\/p>\n<\/div>\n\n\n\n\n
WordPress Stack<\/strong>sudo su<\/code>cd \/home\/username<\/mark>\/WordPress<\/code> -> Replace this user name with your owndocker compose stop && docker compose pull && docker compose up -d<\/code><\/p>\n<\/div>\n<\/div>\n\n\n\nUbuntu Server (OS) Update<\/strong>sudo su<\/code>apt update && apt upgrade -y && reboot<\/code><\/p>\n\n\n\nBackups<\/strong><\/p>\n\n\n\nThere are two ways of backing up.
Conclusion<\/strong><\/p>\n\n\n\nWe have shown you a detailed, step by step, easy to understand technical guide and tutorial on how to self host a highly secured and production ready wordpress in your home computer (PC or Laptop) with any Indian home internet connection. Now the question is should you really consider hosting your own website in your PC?<\/p>\n\n\n\n
Electricity Cost<\/strong>Domestic Internet Speed<\/strong>Comment \/ Question?<\/strong><\/p>\n\n\n\nIf you have any comments, question or suggestion on this, feel free to drop in below.<\/p>\n","protected":false},"excerpt":{"rendered":"
If you search the internet about this topic, you may find a vast majority of…<\/p>\n","protected":false},"author":1,"featured_media":1729,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"[]"},"categories":[14],"tags":[],"class_list":["post-1608","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/posts\/1608","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/comments?post=1608"}],"version-history":[{"count":51,"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/posts\/1608\/revisions"}],"predecessor-version":[{"id":1811,"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/posts\/1608\/revisions\/1811"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/media\/1729"}],"wp:attachment":[{"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/media?parent=1608"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/categories?post=1608"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lazytourer.com\/in\/wp-json\/wp\/v2\/tags?post=1608"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"\"](\"https:\/\/lazytourer.com\/in\/wp-content\/uploads\/2024\/11\/WordPress-Logo_Small_01.png\")