It makes a lot of sense as 800MWh available within ms (especially directly linked to a major grid hub like it is the case here, Laufenburg is famous for it as it’s also the point where the swiss and German grids meet) is the wet dream of every grid planer that has to stabilize a network. That is around 12% of the whole average power draw of Switzerland. Which is impressive.
We need more of these.
There are various working redux flow large capacity batteries operating already (as mentioned in the article as well), e.g. Daillan, in Japan, this one is just a tad bit larger
Codeberg is operated by a German registered chairty foundation - the can’t legally be bought at all.
Hard aka impossible to buy a German registered charity.
FYI: The writer works for a AI-based security company and,well,seems to fit in there.
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.
Yeah, but not that many.
Usual setup nowadays: One monitor for the main CAD (computer aided dispatch) forms, one for map overview, eventually a third one for a unit overview(theye are often done on the map monitor these days), one for external data (browser window, video feeds,etc.), one below as a touchscreen for communication control (VoIP/Radio).
Most EMS Dispatch clients I have switched to a three+one touch setup ages by now and rather use a central dashboard for some less important views and feeds.
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.
Personal recommendation: Start with a selfhosting support software like Casa, Yuno or (my recommendation) Cloudron. Start hosting the app there with frequent backups and occasionally export into regular Bitwarden as a failsafe.
And when you are comfortable switch over to properly self hosted Vaultwarden.
Just adding: Passkeys do migitate a lot of these issues as well.
At the point someone pulls off a valid MIM attack - which is basically a requirement here unless the whole BW/Vaultwarden server gets compromised- that is the least of someones problems. MIMs are incredibily hard these days.
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)
Passbolt seems to be a upcoming competitor. It’s EU based, OSS, etc., but has not been audited as much as BW and has not achieved feature parity so far.
But it looks very promising.