@ -13,15 +13,20 @@ Pages are served up with nginx running on an Ubuntu 22.04 VM. The site is self-h
lives on a machine in a datacenter. Hosting services are supplied by a private provider. The site source is stored on a self-hosted git instance and rendered by a githook.
lives on a machine in a datacenter. Hosting services are supplied by a private provider. The site source is stored on a self-hosted git instance and rendered by a githook.
Content not stored in the git (images, external files) are stored in an external folder and automatically symlinked in on site creation.
Content not stored in the git (images, external files) are stored in an external folder and automatically symlinked in on site creation.
Pi-Star Dashboard is reverse proxied through nginx running at my QTH, with some security disabled to embed it. PiScrape also runs on the PiStar hardware, reverse proxied
the exact same way.
Email is hosted on a seperate dedicated VPS using [Mail-In-A-Box](https://mailinabox.email/).
Email is hosted on a seperate dedicated VPS using [Mail-In-A-Box](https://mailinabox.email/).
<h3>QTH Infrastructure</h3>
### QTH Infrastructure
Some things, like <ahref="https://log.nq4t.com"target="_blank">log.nq4t.com</a>, are hosted at my QTH. Here I have <ahref="/images/nq4tlab.jpg"target="_blank">3 Xen hypervisors</a> running various services related to my home internet. Most of these VM's are running
Some things, like <ahref="https://log.nq4t.com"target="_blank">log.nq4t.com</a>, are hosted at my QTH. Here I have <ahref="/images/nq4tlab.jpg"target="_blank">3 Xen hypervisors</a> running various services related to my home internet. Most of these VM's are running
Alpine linux, however nginx runs on an Ubuntu based VM and pfSense is FBSD based. The home connection is a gigabit fiber connection which recently got IPv6 connectivity.
Alpine linux, however nginx runs on an Ubuntu based VM and pfSense is FBSD based. The home connection is a gigabit fiber connection which recently got IPv6 connectivity.
I also run an Asterisk server for traditional VoIP service, as well as trunks to HamsOverIP and Hamshack Hotline. Dual instances of pi-hole provide DNS for my entire
I also run an Asterisk server for traditional VoIP service, as well as trunks to HamsOverIP and Hamshack Hotline. Dual instances of pi-hole provide DNS for my entire
network, with pfSense forcing all DNS activity to them. If you like <ahref="/images/qthlab-dark.jpg"target="_blank">loads of blinking lights</a> and loud noises, it's perfect.
network, with pfSense forcing all DNS activity to them. If you like <ahref="/images/qthlab-dark.jpg"target="_blank">loads of blinking lights</a> and loud noises, it's perfect.
Pi-Star (and PiScrape) are running on a Raspberry Pi 3B+ on the wired network. It lives physically in the shack.
I also host <ahref="http://stats.allstarlink.org/stats/48032"target="_blank">AllStar Node 48032</a> here for the local club, <ahref="https://w4ovh.net"target="_new">Ole Virginia Hams.</a> It serves as a hub for our repeaters, as well as allowing IAXRPT access for smartphone/PC voice
I also host <ahref="http://stats.allstarlink.org/stats/48032"target="_blank">AllStar Node 48032</a> here for the local club, <ahref="https://w4ovh.net"target="_new">Ole Virginia Hams.</a> It serves as a hub for our repeaters, as well as allowing IAXRPT access for smartphone/PC voice
access to the repeaters. As I've often said, "I just feed it power and internet." I also reverse-proxy Supermon2 for management of the node. The system is largely managed by
access to the repeaters. As I've often said, "I just feed it power and internet." I also reverse-proxy Supermon2 for management of the node. The system is largely managed by
I'm not much of a programmer, but what I have developed related to ham radio now has a page; link in sidebar/menu. Not all the projects have a page created, but
they do have Git repositories you can look at in the meantime.
nq4t
2 years ago