France and Germany, in joint collaboration, have developed a Google Docs alternative - and its awesome! (Netherlands are currently onboarded)
-
Nice, DINUM is doing a lot so great to see go beyond with supra national collaboration!
I'm using NextCloud (Germany and international open source community) hosted on Webo (Slovenia) with data centers in Germany and Helsinki (so I bet on Hetzner). I'm happy with it but I'll keep on eye on https://github.com/suitenumerique/docs
I'd be curious, they use Minio which puts S3 first. Does it mean Docs (the official instance) is relying on AWS?
If so IMHO that's not a great default EU sovereignty.
-
I'd be curious, they use Minio which puts S3 first. Does it mean Docs (the official instance) is relying on AWS?
If so IMHO that's not a great default EU sovereignty.
FWIW if others are curious https://github.com/suitenumerique/docs/issues/755 opened an issue
-
This post did not contain any content.
and why so?
-
I'd be curious, they use Minio which puts S3 first. Does it mean Docs (the official instance) is relying on AWS?
If so IMHO that's not a great default EU sovereignty.
I would assume (without having looked at the codebase) that if they use minio they are, by default, not reliant on AWS.
Minio is its own S3 implementation which can be self-hosted.
S3, being an AWS protocol originally has
AWSenvironment variables all over the place but that does not necessarily mean a reliance on the service. Rather, they rely on the protocol and you bring your own S3 endpoint I would assume. be that minio, hetzner or what have you. -
A lot of government programs don't really make sense and are there just to put a name on a CV sadly.
Collabora Online does exactly that and is primary licensed under Mozilla Public License.They could have easily expanded Collabora. But you know, can't stamp your name on it.
To be fair, though a new project might not be as efficient as improving another, projects learn off each other, and sometimes it's good to have developmental 'competition', and variety.
-
We already have kDrive you get 1TB storage for only 2€ a month, it's based in Switzerland
Is there an open source implementation of kDrive as well?
-
FWIW if others are curious https://github.com/suitenumerique/docs/issues/755 opened an issue
I thought that MinIO is a Open-Source S3 implementation, which you can just install on your own system. S3 is a "protocol" here IIUC.
Is your complaint that they are using the S3 protocol, because it was invented and is controlled by AWS?
Or that some services might use it without MinIO, directly on AWS?
-
Is there an open source implementation of kDrive as well?
It is already open-source. All of the source code is on their github and, for docs, they use an implementation of onlyoffice very similar to the one in Nextcloud
-
I would assume (without having looked at the codebase) that if they use minio they are, by default, not reliant on AWS.
Minio is its own S3 implementation which can be self-hosted.
S3, being an AWS protocol originally has
AWSenvironment variables all over the place but that does not necessarily mean a reliance on the service. Rather, they rely on the protocol and you bring your own S3 endpoint I would assume. be that minio, hetzner or what have you.Thanks for the clarification, that makes sense, closing the issue then.
-
I thought that MinIO is a Open-Source S3 implementation, which you can just install on your own system. S3 is a "protocol" here IIUC.
Is your complaint that they are using the S3 protocol, because it was invented and is controlled by AWS?
Or that some services might use it without MinIO, directly on AWS?
Seems I misunderstood, if it's solely the branding (of that implementation) then it's fine. I thought they relied on AWS itself.
-
It is already open-source. All of the source code is on their github and, for docs, they use an implementation of onlyoffice very similar to the one in Nextcloud
Oh that is good to know then. At a cursory glance I only saw the clients' software available as github repositories and the German and French wikipedia pages called it a proprietary service.
-
Honestly, a lot of the time I don't understand why a lot of businesses use k8s.
At my company especially, we know almost exactly what our traffic will look like from 9am-5pm. We don't really need flexible scaling, yet we still use it because the technology is hyped. Similar to cloud, we certainly don't need to be spending as much as we do, but since everyone else is on or migrating to the cloud, we are as well.
The "problem" with k8s is not that it's abstract-y (it's not inherently any more abstract than docker), it's that it's very complex and enterprise-y.
The need for such a complex orchestration layer is not necessarily immediately obvious, until you've worked on a complex infra setup that wasn't deployed with kubernetes. Believe me when you've seen the depths of hell that are hundreds of separately configured customer setups using thousands of lines of ansible playbooks, all using ad-hoc systems for creating containers/VMs, with even more ad-hoc and hacked together development and staging environments, suddenly k8s starts looking very appetizing. Instead of an abominable spaghetti of bash scripts, playbooks, and random documentation, one common (albeit complex) set of tools understood by every professional which manages your application deployment & configuration, redundancy, software upgrades, firewall configs, etc.
A small self-hosted production kubernetes cluster doesn't have to be hard to operate or significantly more expensive than bare-metal; you can buy 3U of rack space, plop in 3 semi-large servers (think 128 GB plus a few TB of SSD RAID), install rancher and longhorn, and now you've got a prod cluster large enough for nearly every workload such that if you ever need to upgrade that means you have so many customers that hiring a k8s administrator will be a no-brainer.
Or you can buy minutes from AWS because CapEx is the absolute devil and instead you pay several times as much in OpEx to make it someone else's problem. But if you're doing that then you're not comparing against "installing things the old-fashioned way".
-
This post did not contain any content.
-
it’s easier to develop for just the browser than for Mac, Windows, and Linux.
They also work on android and IOS. You are also not dependent on the different toolkits. Also it is so much more performant.
I’ve never found them to be more performant, and i can’t understand the logic of why a programme running inside another programme would be more performant except in comparison to unoptimised alternatives.
I’ve never used a web app that i thought was better than a local app. But i definitely understand why developers prefer them.
-
Wait LibreOffice has a cloud?
-
We already have kDrive you get 1TB storage for only 2€ a month, it's based in Switzerland
Where are you getting that pricing?
-
Where are you getting that pricing?
https://www.infomaniak.com/en/ksuite/myksuite
1.90€ per month for 1TB
-
It's pretty easy if you use NextCloud with the AIO image, but if you're doing anything fancier than that, strap in because there aren't many decent tutorials.
strap in because there aren’t many decent tutorials
Yeah I've noticed. It was rough figuring out how to set up a reverse proxy with SSL too. Self-hosting is a process.
-
I won't argue with the ups and downs of each technos, but I recently looked into docker swarms and it was all I expected kubernetes to be, without the hassle. And I could also get a full cluster with services restored from scratch in 30s. But I am obviously biased towards it, too
Did not realize swarm was still a thing, not trying to be offensive here.
My best find was using traefik as a reverse proxy in docker (compose). It is easily configurable through container labels and pulls resource definitions straight from docker. It is awesome!
-
and why so?
Living under a rock eh?
