Supermicro and ASRock Rack both make standard form-factor mini-ITX and micro-ATX server-class motherboards with dedicated IPMI ports that would fit in a shallow-depth rack-mounted chassis.
JoeB-
joined 1 year ago
Navigate to "Containers" and click on container name to access "Details". Then click on "Console". See the screenshot below...
My thoughts on buying a system with proprietary components...
Pros
- Buying typically is cheaper than building.
- Saves the effort of matching hardware when DIYing.
Cons
- Requires searching eBay (or other marketplace) for compatible proprietary hardware when a component fails.
- Some proprietary systems (looking at you hp) can be picky with some replacement components like RAM.
...which for me is uptil 192.168.1.1 - 192.168.1.253 (I cannot edit this, it's an ISP router)
Are you certain that you cannot set the DHCP range on your ISP's router? I suggest researching this option a bit further, including contacting your ISP tech support. I have never heard of an ISP-provided router not allowing customers to change the DHC range.
Other options include:
- disabling the DHCP server on your ISP-provided router and enabling the DHCP server on your Pi-hole with a limited DHCP range as needed, or
- replace the ISP-provided router with your own router, which could save money if the ISP charges a monthly rental fee.
Single host - Just Docker run + Portainer - Also using Macvlans so most containers have hostnames and static IPs on my LAN. K8s is cool, but I have no need for container orchestration.
Choosing a service to NOT selfhost is a subjective descision.
I host 18 Proxmox VMs and 20 Docker containers at home. I also was selfhosting a WebDAV server for synchronizing my Joplin notes between devices and Vaultwarden for managing my Bitwarden vault, but decided to push the Joplin synchronization target to Dropbox [free] and to use Bitwarden's free cloud solution for my passwords and secure notes. I did this because I will need immediate access to these two critical sources of information should my house burn down, or get blown over by a tornado. I have extremely strong passcodes for these and trust the hosts.
This was strictly a personal decision. YMMV.
OP, your poll needs an "All of the above" option. That would be my choice.
In a nutshell, I have no interest in the feature bloat being introduced into Plex. I want a simple media server. Jellyfin provides this, and includes basic features like hardware transcoding and live-TV. I migrated from Plex [free] to Jellyfin a couple of years ago and haven't looked back.
I also am in the Apple ecosystem and pay $10 USD per year for the Infuse app, which is more polished IMO than both the native Jellyfin and Plex clients.
I use Homepage. There are plenty of other options, but I prefer Homepage because of it's speed and simplicity. Many landing page apps allow for customizing on the page itself. Homepage is configured using YAML files, and therefore static, so family members will not be able to make changes, or accidentally break it, once you have it set up.
Here is a screenshot of my... Homepage.
I use custom images and icons uploaded to Dropbox in... icons-72x72-png.zip
These are kept in volumes for persistence...
--volume homepage_config:/app/config \
--volume homepage_icons:/app/public/icons
--volume homepage_images:/app/public/images \It may be me, or Reddit could be flaking out, but it appears that everyone except you and I have deleted their comments. I also cannot reply to your comment about N8N, so I am commenting again. Weird...
I recommended Pushover in my previous comment. To address your initial question, I'm running Docker containers for Mailrise, which provides an SMTP gateway that embeds Apprise code, and also Apprise standalone. I use Mailrise for services that support only SMTP notifications (e.g. Proxmox). Mailrise translates an email message and, using Apprise code, submits it to Pushover. I use Apprise standalone for receiving notifications from Healthchecks, which monitors cron jobs. Healthchecks supports a number of notification services, but standalone Apprise was the best fit for me.
As I understand, Apprise has its own light-weight HTML API for creating and configuring notification endpoints. It can create a webhook endpoint, but I don't believe it receives messages as webhooks.
Like me, you probably will need multiple services. I tossed up an N8N container out of curiosity. It can accept a webhook and then act on it. It also supports Pushover. So, it looks like a webhook to N8N can be translated to a Pushover notification. Using Mailrise (for SMTP messages) along with N8N (for webhook and other messages) should provide the extensibility you're looking for.
Again, I highly recommend Pushover. Receiving notifications from many different sources, that are organized into "applications" with their own icons, in one mobile app is a tremendous benefit... to me anyway.
does it also report DHCP reservations?
Thanks, and yes, Type "static" are DHCP reservations.
Where do you do DHCP, on the PFSense or somewhere else?
Yes, on pfSense. I use the Python function written by pletch/scrape_pfsense_dhcp_leases.py (on Github) that scrapes the pfSense status_dhcp_leases.php page. Then added my own function for querying my TP-Link APs using SNMP to determine which AP a wireless DHCP client is connected to.
I can throw the script up on Dropbox if you are interested. I am mediocre at writing Python, so it is pretty specific to my environment.
view more: next ›
That’s a lot of Linux ISOs.