New pages
From Sea of Fate
Jump to navigationJump to search
11 May 2026
- 21:1521:15, 11 May 2026 Minecraft (hist | edit) [21,482 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== We are to have some Minecraft servers on the Homelab. The general setup will be to have a Velocity server in front several Minecraft host VMs. Velocity works in a similar way to a Nginx reverse proxy whereby Pfsense forwards all Minecraft traffic to the Velocity server including the SNI and Velocity redirects traffic to the required hostname based on the DNS name. Cloudflare does not reverse proxy Minecraft traffic on the free tier and as we do not...")
7 April 2026
- 15:2615:26, 7 April 2026 Silvan Reporter (hist | edit) [1,519 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== The Intention of the Silvan Reporter is to generate reports on the current state of the Homelab. it will also be able to show the current status of all of the entire network. ==Outline== The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all o...")
3 March 2026
- 20:0320:03, 3 March 2026 Linux Commands (hist | edit) [7,990 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== we have a random collection of commands that we should remember but just in case a re listed and explained here for our convenience. ==STORAGE & INODES== * df -h : Check disk space (Is the 2TB NVMe or 800GB SSD full?). * df -h <path> : Show Human-readable Free space on the disk partition containing that directory. * df -h /mnt/fast_scratch how much room is left in the volume fast_scratch * df -i /mnt/fast_scratch : Check Inode usage (Crucial for the Gu...")
28 February 2026
- 10:5410:54, 28 February 2026 Apache & Nginx (hist | edit) [120,754 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== The purpose of this guide is to delineate the strategic integration of the Apache HTTP Server and Nginx within a modern web infrastructure, specifically focusing on the deployment of a robust, tiered hosting environment. In the contemporary landscape of system administration, the choice is rarely between one server or the other; rather, it is about how to leverage the specialized strengths of each to create a platform that is both highly performant and...")
- 10:5110:51, 28 February 2026 Reference Notes (hist | edit) [895 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== We do sometimes forget the notes that we made to do some of the common tasks like creating a new website or checking the state of the drives and although they are quite easy to do and we have done them before they are easily forgotten. To that end we need a ready reference section that just points to all of these easy setup jobs with some sort of reference notes to remind us of how and why we did them like we did. == Apache & Nginx | Apache & Nginx D...")
- 03:3503:35, 28 February 2026 Bookstack (hist | edit) [7,879 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== We wanted an alterative notebook application for the evolution of the Home Lab. As we already a ''' webserver''' setup already and the install was not going to need much in the way of resources like nextcloud or new libs we have added it as another vhost on '''Plum''' instead of another ''' Virtual Machine'''. One the advantages of using an existing webserver are that the supporting services that are already i...")
24 February 2026
- 00:4100:41, 24 February 2026 Homelab Dashboard (hist | edit) [5,876 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== We have decided to setup a homelab dashboard to monitor and administer the entire estate of Virtual machines, Proxmox hosts and all of the services that we have created. initially we will use the dashy dashboard but may well change for something else if dashy proves to be to difficult or in some way unsuitable. ==Dashy Setup== in the interests of security for this sensitive project we are extending your "Full-Chain TLS" SME standard to Blackberry. Thi...")
22 February 2026
- 07:5207:52, 22 February 2026 Unified Monitoring Stack (hist | edit) [30,566 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== Mango, located at 192.168.110.133 on the Infra network, is the unified successor to the Pineapple/Granadilla/Victoria triad. It serves as the central "brain" for the home lab's observability. Mango natively scrapes metrics from all Virtual Machines and the Proxmox host (Pear), stores them in a high-performance VictoriaMetrics time-series database, and provides a Grafana interface for visualization. By consolidating these services, we reduce network ove...")
16 February 2026
- 11:4811:48, 16 February 2026 Letsencrypt SSL Certs (hist | edit) [14,850 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== We chose to use Letsencrypt SSL certificates in addition to the Cloudflare origin certs because we occasionally need to serve SSL websites and services directly and while the cloudflare origin certs work well and are easy to setup, they are not publicly recognised. To set up the ACME LetsEncrypt service (specifically using acme.sh) on '' Raisin''' with Cloudflare DNS, we will want to use a wildcard cert so that we don't have to keep on...")
15 February 2026
- 19:4719:47, 15 February 2026 Kiwi & OpenAlex failure while indexing the 2026 Import (hist | edit) [7,316 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction==")
- 18:4218:42, 15 February 2026 Problems & Solutions (hist | edit) [601 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== We need to keep a problem log of all network problems as they occur")
- 14:5414:54, 15 February 2026 Management kiosk (hist | edit) [1,686 bytes] Wikisailor (talk | contribs) (Created page with "==Introduction== The Homelab has many quite a few servers and services now and some of the are quite sensitive. We could administer them from the internet but at the moment that is too much of a security risk to setup for the limited gain so for now we will restrict that to the LAN so to that end we have dedicated management consoles on a restricted VLAN. To begin with we had a single console with the hostname lemon and that was the sole means of administration but it b...")