FYI: The writer works for a AI-based security company and,well,seems to fit in there.

You can’t live in them directly, but I literally lived within 2min from there for a few years.

These clocks were installed far later than the towers.

The construction for the first one started in 1233.

The one with the part of the wall missing is from 1260, they are all part of the old defence walls of the city of Villingen.

I literally drove through two of them today.

Have you had a look at AgentDVR recently?

While it’s a ressource hog look into xwiki. It is well suited for what you want to do and afaik there I came around a basic asset management plugin once.

So does homebox and basically ever OSS software mentioned here. BTW: Got some source for that?

Depending on what your exact needs are,but Snipe-IT is surprisingly decent for a Home Asset Management System, even though it is mainly geared towards IT stuff.

Okay, you can’t start a story like that and then not tell us the cruiseship story in full glory.

Tbh, at the moment the maintainer seems to be have gotten the message - or at least tries to make it seem so. I would give him the benefit of doubt at this stage, at least for a while now.

Without Synapse migration it’s sadly still hard for longer established servers to migrate/impossible.

Xwiki is missing.

For me after a similar search it is the current winner. Even though it has it’d downsides. We came from Confluence and tested a LOT of systems. My spreadsheet of systems we considered has around 120 rows by now. (Not all pure wikis as we also moved away from jira and considered going down a “put the wiki into the servicedesk” route)

Pro:

• It is well tested in a enterprise enviromentand mighty

• It has all the features I personally found important for a company wiki, e.g. approval, versioning, templates, collaboration, integration api,etc.

• It is fairly easy to extend it yourself

• It is easy to host subwikis within the same installation with a self defined grade of independence - which is great for customer facing things,large projects with externals,etc.

• The development community is big and enterprise focus and release cycles are good. (Not like a certain .js) There is very little chance it will stall suddenly as the wiki has been adopted by a lot of large companies which seem to support it.

• It’s truely free,no “pay to get custom fields” bullshit.

• It’s truely self hosted.

• it can be hosted system side, if you are not into docker.

Contra:

• It is written in bloody Java

• (even though this sentence is redundant with the one above) It is a resource hog

• The look and feel is a bit outdated unless you customise it yourself. Then it is reasonably good.But there are basically no paid templates,etc.

• Paid support is only available through third parties it seems.

• It can be, well, slow to update…like physically slow. It is not hard to update,not at all…press a few buttons…but sometimes it takes ages.

A follow up is a absolutely regular thing and does not diminish neither study.

Nah, OP is just a troll. Most European countries by now have legislation to mandate them or are currently introducing these. All of them heavily advise them.

This is plain WRONG and DANGEROUS.

The issue is NOT the Americum but the natural degration of the photoelectric cells and the accumulation of dirt within the test chamber.

Even before that time the risk for false alarms is increased substantially by degration before the chances for sucessful alarming decrease rapidly. Due to that they actually withstand aging actually worse than ionisation based devices.

Sientific sources?

Here

here.

Here

Here

(Besides: Americum has a decay time of over 400 years,btw)

We kind of selfhost almost everything - while we operate a small server ourselves, the main burden is on a dedicated server setup. Basically a FreeIPA+Authentik+OpenCloud Stack as a base,with Redmine, Kimai, Zammad, Matrix, Jitsi and a few more apps. (Moodle, Seed DMS, Netbox, Zabbix, OPNsense, Vaultwarden, Forgejo, Ansible). Additionally we use a fair share of software remotely via RDP.

Backups are done onsite and to three different offsites, including cold storage backups.

As we all work fully remote this setup is also fairly adaptable and the switch to a (almost fully) Linux shop went far better than expected - my staff is fairly content with their setup (afaik).

The only thing I refuse to selfhost are email and VoIP.

Still mediocre compared to OPN/pfsense, IPfire, VyOs,etc.

I must admit I can’t find the exact guide I used anymore. Especially not a English one.

But the official guide should help you: https://www.zabbix.com/de/integrations/proxmox

I think whatever I used was pretty close to it. If you have any issues send me a DM.

(And tbf, I use both the Agent2 and the API in a perverse mixture. And for some nodes IPMI on top of it. It’s really kinky,but it does the job)

Absolutely, but unlike Ubiquiti they did not keep them under the rug that long. (Nevertheless: Both are shit for firewalling. Put a OPNsense before it?)

Zabbix is extremly nice.

Why?

• API Monitoring for Proxmox and Docker/Podman. Aka "you don’t need to setup monitoring for every container/LxC/VM. Do it once for the host,then everything gets autodiscovered.

• Active and passive agents as well as SNMP, IPMI,etc. can be combined as you like. Also does Website/service/application/database monitoring, SSG/Telnet checks and nowadys can even do Prometheus and MQTT/Modbus

• The proxy is really really worth it. It collects data from nodes you do not want exposed and relays them to the server. This includes all kind of inputs and is really easy to setup.

• Due to it being around for two decades there are a shitton of templares for devices - and it’s fairly easy to do your own.

• Unlike other systems (cough checkmk cough Grafana) there are no features that are only available to paying customers.

The most major downsides are the fact that it’s moderately to fairly ressource intensive to run in a small setup(but does consume less than others in large Setups) and it’s far less flashy dashboards. (Which are still powerful,though)

Not a fan. Absolutely not.

They had multiple security incidents which they kept under the rugs for a long time, they have the tendency to EOL devices without warning (which then means you need to replace your sometimes 9month old device or your whole enviroment can’t be updated), their lock-in into their ecosystem is much more complete as they can’t be used properly without their enviroment.(e.g. Omada devices can work without the Omada stuff, with Unifi you will always need a controller for some functions).

So if you realy need SDN features like Unifi look at Omada,otherwise Mikrotik is a solid alternative. (And OPNsense for firewall)