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

Very happy with a KIA EV6.

No longer valid. A shitton of companies are UG by now - I operate one myself. It is very rarely an issue,even back when it’s been just an UG we used.

They don’t need a GmbH, a UG would do it for less starting capital, BUT a joint stock company does not protect you from Scheinselbstständigkeit per se.

It’s a proper clusterfuck.

Read up on Scheinselbstständigkeit. Then talk to a tax advisor that is knowledgeable in that topic.

Only once you fully understood the implications you can proceed - and by understanding I mean realizing how utterly hard the law makes it for regular freelancers. And don’t get me wrong, but if you are unable to understand that topic due to language skills don’t do it. Not because it’s not possible to understand the legal situation through translating apps - but more because you will get a LOT of paperwork you must understand precisly because one wrong word will ruin you and cost your customers thousands. And which is often required to be send back within days. (Looking at you, DRV)

That being said classical admin work freelancing unlike actual consulting is almost impossible to do under the current laws.

Welcome to Germany/Austria,etc.

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.

So,here’s another update almost a month later.

Am I still happy with the U1?

Yes.

Am I happy about everything? No.

A few things that tend to get on my nerves.

• The lack of filament cutting is annoying and massively delays changing filaments. Argh.

• The filament roll placement is shit,especially when printing ASA and similar filaments that need to be really dry. (PEBA) Placing them out in the open turned out to be an issue, especially when you use a spool for frequent shorter prints. (E.g. one part of 5h today,another tomorrow,etc.) Especially annoying with the point above which makes simply chucking away four spools time consuming. I migitated that by using a almost closed system of containers - but I suffer from issues with the filament feeders occassionally as the axles for these tend to be an issue.

• ASA has shown mixed results with the improvised hood. (Aka a plastic bin, not fitting properly, holes between it and the printer covered with tape). After looking at it with a thermal camera its clear why: The large ventilation holes on the sides let a lot of air go through (tbf,the current location here is a bit exposed) and the headpad is not heating up fully uniform (but more uniform than the P1S in comparison). So I blame the ventilation holes. Smaller ASA prints are not a problems, larger ones are - especially with more unforgiving filaments. (E.g. Spectrum 275 works well, Black Forest doesn’t, Extrudr is somewhat okay) For testing purposes I tried to print with the holes covered and that worked well. But this creates it’s own issues - for PLA you need way more ventilation as the fans are FAR less powerful (even though louder) than in the P1S.

BUT I will improve things

• The acrylic glas panes arrived so I will install a proper hood now.
• The additional tempsensor will arrive tomorrow. I want trustworthy independent temperature values in the case before I block
• AND,biggest news, the Panda Breath has arrived and BIQU has published a manual how to install it perfectly into the U1. Will do so soon and expect most of the issues to be solved by that.

So this sounds negative,right? It isn’t! I am still very happy and the U1 solves a fuckton of isssues I had with the P1S. Multimaterial,automation, filament tracking, etc. For PLA my print results (with a bit of tuning) are on par with the P1S OR better for things that need support. (As you can use different materials far better than with AMS) And finally having proper clipper back and the options of the extended firmware is nice.

Funny thing: I got two aftermarket print plates from AliE and they are both providing much better grip than the snapmaker original.

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.

My 3D workshop? A somewhat large custom fitted closet. The printer sits on a extending/sliding base and there are shelves with the filament boxes (I use resealable containers).

The printer is fully enclosed (adapted U1 with a chamber heater, a chamber air filter), but the cabinet itself can also be ventilated with a exhaust going through a custom made filter array (HEPA and activated charcoal. A mate of mine is builds those for a living/has a PhD in it, so it is somewhat sophisticated) or unfiltered. Additionally I installed a light and various temperature probes in it.

These days a small display should arrive that I want to fit outside it, so I can control the printer, vents,etc. from there, via Home Assistant. In the long term I will also slowly replace the cheap hygrometers I now have with ZigBee ones so I can list all humidities in the display.

Additionally I have a Chitu E1 and a Gratkit for drying. While the Gratkit fits, I haven’t found a good space for the Chitu yet.

Next to the closet is a height adaptable desk I use for electronics and things like that so I have my post-processing tools there as well.

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)

My company is a part of critical infrastructure and we provide consulting in disasters (e.g. how to get a hospital back up and running). So we fall under European legislation to have certain precautions. And as I colocate in my companys rack…it’s easier. As the rack is in a room I rent to my company. (We are small and I am the founder,that makes it easier)

But yeah, we put a bit of thought in it. Waiting for Iris2 finally materialise so I can get rid of LTE finally.

I have a LTE Backhaul,but admittedly if the firewall itself craps out I would also be offline - but I can at least reboot it via a plain old GSM power plug. That thing does not directly reboot the firewall,though, but brings up a old raspberry (usb boot,I don’t trust sdcards) which then checks if outside connectivity is still available (so if the GSM power plug gets compromised it’s not an issue) and if not tries a shutdown or,if that is unsucessful, a powercut of the firewall. If that also doesn’t work it triggers a dry contact in the GSM plug which leads to the plug sending out a SMS so I know I am fucked and need to get someone with a key to the rack.