yara

@yara@feddit.de
0 Post – 3 Comments
Joined 1 years ago

Most tutorials I read nowadays include some parts where the author suddenly writes: This setting is terrible and should never be enabled in a production environment, however since this is just a demo I'll use it either way! So in the end I usually have to stick to the official documentation + forum posts... I really dont understand (money and clicks...) how someone can be proud of their tutorials when they aren't even remotely production ready...

Do you have any people working in IT besides you? If not its probably a bad idea to shift everything to inhouse. Management gonna like it up until something happens. And their is always something that will happen in the fast moving IT world. Do you have multiple backups inplace? Any offsite and immutable? Any person besides you who gonna regularly validate them and fix them if problems arrise? If the answer to any of this is no, don't do it. There is a reason for these it solutions provider and why they are usually not cheap. Just find someone better instead of trying to cheap out.

If proxmox is too difficult I would probably remove pretty much every free/ open source options and move to something like synology since it seems like you're working at a small company.

Proxmox offers paid support though and is a finished solution. Since the vmware acquisition multiple people I consult at work moved some of their systems to proxmox.

1 more...

I'm running truenas scale as hypervisor (migrated from proxmox to try to save electricity costs)

  • Opnsense as Firewall
  • Ansible (debian)for Patching and infrastructure management
  • zabbix (debian) for monitoring
  • plex (debian) media server
  • Omada controller (access points) (ubuntu)
  • homeassistant (hass OVA) for home automation
  • nginx (debian) as reverse proxy