I tried a couple of LDAP solutions out there; Windows Server AD, Open LDAP, Samba4 in Debian, TurnKey Solutions LDAP before finally settling on Zentyal. It has a nice to use web GUI and can work in conjunction with AD RSAT tools that I have installed in a throwaway Windows VM for when I need more granular controls the web GUI can’t do.
All my Debian VM’s and laptops connect to Zentyal AD via SSSD.
I just cannot find a use case for Nextcloud. I have gone as far as installing it and sync’ing it with my LDAP for user auth and sync pictures from my phone to my NAS. All the other features are just a big ole m’eh for me.
This has just been my experience, so maybe I’m missing something that would just make it all click and make me not live without it. So far though, I’ve spun up and spun down an instance 3 times and never missed it afterwards.
Zabbix for agent / snmp based statistics.
Uptime Kuma for up/down states with a webhook notification into Discord so I get instant alerts on my phone when one goes down.
Not sure I fully understand the use of two domains. Does RHEL IDM do more for Linux machines compared to a Windows DC?
For my setup, I have a single Server 2019 AD Domain Controller that my Linux VM and laptop connect to using SSSD for domain level authentication.
That’s an error on my part, apologies. I copy/pasted and tried to redact my url from the APP_URL=https://bookstack.example.com section and ended up deleting the entire line; yay replying from mobile. :|
I currently use Bookstack on Docker in Unraid but the above docker compose snippet is from when I used a debian VM with docker installed on it to run my docker stacks.
Here you go, this is my docker compose. You can modify the pieces as you see fit.
version: ‘3’ services:
bookstack:
image: lscr.io/linuxserver/bookstack
container_name: bookstack
environment:
- PUID=${PUID}
- PGID=${PGID}
- APP_URL=
- DB_HOST=bookstack_db
- DB_USER=bookstack
- DB_PASSWORD=${BS_DB_PASS}
- DB_DATABASE=bookstackapp
volumes:
- ${DATA_DIR}/bookstack:/config
ports:
- 6875:80
restart: unless-stopped
depends_on:
- bookstack_db
bookstack_db:
image: lscr.io/linuxserver/mariadb
container_name: bookstack_db
environment:
- PUID=${PUID}
- PGID=${PGID}
- MYSQL_ROOT_PASSWORD=${BS_DB_PASS}
- TZ=${TIMEZONE}
- MYSQL_DATABASE=bookstackapp
- MYSQL_USER=bookstack
- MYSQL_PASSWORD=${BS_DB_PASS}
volumes:
- ${DATA_DIR}/bookstack/mariadb:/config
restart: unless-stopped
I stand corrected. It has been a few years since I had a working r210ii in my homelab & my remembering of the technical guide was rusty.
For future people, section 6.3 has the list of supported CPU’s.
https://i.dell.com/sites/content/shared-content/data-sheets/en/Documents/r-210-2-technical-guide.pdf
I’m going to go a different route than your question. If you have a spare m.2 slot and room in your PC, you can install a m.2 network adapter. I recently installed a m.2 to 2.5gbe adapters in a Dell 3060 SFF as a proof of concept at home for getting Proxmox ceph cluster working over 2.5gbe.
I use Apache Guacamole with Duo 2FA and LDAP authentication. All of it is self hosted and sitting behind Nginx for SSL. Works great aside from when I’m in the office and they do some security te blocking that I’m too lazy to find a work around for as I rarely go into the office.
I would stick with the 7020’s or get something smaller like a Beelink unit that seems to be all over tech YouTube right now.
The r210 is loud due to it being a 1U server. The upgrade path on the r210ii is very limited. Look up the Dell Technical Guide for the r210ii to get a list of what you can upgrade them to as far as CPU and RAM requirements. It only takes up to 32gb of ECC UDIMM which I always found more expensive than ECC RDIMM. For CPU, the best CPU it can take is only a 4 core, with no hyperthreading.
Experience: I have run two r210ii’s before moving to three r230’s before finally going big to a r730xd. In the past month, I have migrated away from the r730xd to a Dell 5820T and 3x Dell 3070 SFF PC’s to combat the noise and heat generation in my home office.
Two users and a handful of service accounts. I use it so I have a centralized user authentication system instead of managing multiple individual user accounts.