I love the docs ability to create databases from my docs. That would be super useful for work and research activities.
deleted by creator
I’m in the engineering business. We have a PDM system that we check-in copies of component 3D models, PDF drawings and DOCs. Once your team has collaborated enough, you have a copy…once a week/day/hour depending on your preference. That way you can collaborate and keep frozen records and rev controlled documents.
deleted by creator
Oh, you mean a spreadsheet?
No, because with the above you can have rich objects in databases (for example, a dynamically updated list of medical events, each with all the attributes I want, attachments etc.), and almost arbitrarily deep nesting of databases. The idea to have databases with pages is one of the key features that made notion successful. It allows to structure knowledge without duplication, in addition to provide some other no-code features.
Spreadsheets are not even close.
Exactly. Engineering research test write ups and results could be quickly searched for in a good document database.
Dont know why we need another foss office but im certainly not going to complain.
Now explain this to EU based corporations, which in my opinion needs to be the focus on making the change. They drive the economy. All major assets in software income are being routed to American firms through their licenses.
What was wrong with libre?
The web browser is the future, especially for a crappy document editor and spread sheet.
Then just use Word online.
Not FOSS and probably not privacy friendly
Pretty sure Libre only does local document collaboration, having it online is helpful for teams far from each other or who simply don’t have the infrastructure for their own central server of this kind.
Well this has been running in our Nextcloud and works pretty well collaboratively :) https://github.com/CollaboraOnline/online not sure how it scales, but definitely an alternative that can be built on
Thanks for this; I may use it to build out my NextCloud server. I’ve already used it to replace shared calendars and contacts.
If you’re using Nextcloud All In One then it’s easy to enable it in the AIO settings.
If you’re not, I suggest looking into it. It’s the new officially recommended way of installing and it’s been great.
Nextcloud has an export/import data function but at the time I did it I only had a few GB of data so not sure how well it scales.
Really cool. I tried to sign up but you have to be part of an officially recognized organization in France and input their registration number as part of the process.
Yeah I thought this was open to the general public, I didn’t realize that it was not
I’m sure it will be. This is a government funded thing in the early stages so I can see how they would set it up that way.
I definitely don’t want the government attached to my personal files, in any country.
Nice. Where is the source, on github (I didn’t see it but I only skimmed)? Federated? Self-hostable?
https://github.com/suitenumerique/docs
Self-hostable, needs Minio (or any S3 compatible system).
Github: https://github.com/suitenumerique/docs
Self-hostable, but it seems like an absolute behemoth of an application if their “non-production-use-only” docker-compose file is to be believed, and I couldn’t find any production-ready deployment instructions on a quick skim. No obvious signs of federation and I didn’t see anything on their roadmap, not sure it would make a lot of sense for this though.
Deployment instructions start with the prerequisite that you have a full kubernetes cluster with ingress laying around, so… yeah. It looks like it’ll be on the heavy side.
From briefly looking over the toot, I think the German version is called openDesk (bad choice as there seems to be some interior design software with the same name) there is a community version you can self host in a docker container. They apparently also have distro packages for Debian and Ubuntu but they seem to have stopped development on those.
Here’s a link: https://opendesk.eu/en/
openDesk is a complete suite of open source software. I guess Docs could at some point become a part of it. But it‘s not the same thing.
ZenDiS is awesome by the way.
and why so?
Living under a rock eh?
I mean I didn’t see any alarming need of a Google doc alternative, so I might actually be under a rock
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?
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.
Where are you getting that pricing?
https://www.infomaniak.com/en/ksuite/myksuite
1.90€ per month for 1TB
Yeah, it is called Word. Works on all computers, is free to use the web based version, and is the world standard.
It does not work on my work-computer, since office macros and some formatting renders differently across versions. Other required software constraints make windows unusable for me.
Word won’t install on machine.
LibreOffice does, though.
Hey, this is a Python project, use underscores.
Proprietary bullshit
Maybe I missed something, but since when Word is not only an alternative to an office suite, but also a web-based one?
deleted by creator
But even a web-based version of Word can’t be a Google Docs alternative, because Word can’t into spreadsheets and presentations.
It’s just for the French civil service, right?
removed by mod
What does this do over what the collabora tools in Nextcloud do?
NGL I keep forgetting NextCloud has collaboration tools.
No America’s club
Just checked the part about self-hosting. While it’s probably possible to handle things with a less heavy approach, their only “easy to use” example right now is to have a full-blown kubernetes cluster at hand or run locally in the source directory. That’s a bit much.
Please develop this self hosted version using sandstorm
It makes hosting a breeze with one click installation
In the README there’s also instructions for Docker Compose, although it’s quite the compose file, with SIXTEEN containers defined. Not something I’d want to self-host.
it seems to contains development containers and external services containers. So the compose file is more for local dev it seems
What i do find weird is the choice for Django for the backend. Python is incredibly slow, and django rest framework is even worse.
Honestly, k8s is super easy and very lightweight to run locally if you know the rights tools. There are a few good options but I prefer k3d. I can install Docker/k3d and also build a local cluster running in maybe 2 minutes. It’s excellent for local dev. Even good for production in some niche scenarios
I don’t like the approach of piling more things on top of even more things to achieve the same goal as the base, frankly speaking. A “local” kubernetes cluster serve no purpose other than incredible complexity for little to no gain over a mere docker-compose. And a small cluster would work equally well with docker swarm.
A service, even made of multiple parts, should always be described that way. It’s easy to move “up” the stack of complexity, if you so desire. Having “have a k8s cluster with helm” working as the base requirement sounds insane to me.
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”.
Thanks for the response!
I personally haven’t rolled a k8s or k3s cluster, so it’s always felt a bit abstract to me. I probably should though, to demystify it to myself in my work environment.
Complex is definitely what I have noticed when I see my devops team PR into the ingress directories.
I guess the abstract issue I see, that ties in to the meme i shared above, is that sometimes around deploys where we get blips of 503/4’s and we appear to be unable to track them down. Is it the load balancer? Ingress? Kong? The fact that there is so many layers make infra issues rough to debug
I mean yeah it’s all very complex for sure. Managing a cluster is very involved and k8s administration is typically a completely separate role from dev/devops. I am comfortable with the idea and I still run my selfhosted setup on docker because it’s easier and I have no personal use for multi-node setups.
However when you get down to it pretty much everything in k8s solves a real problem that in a “traditional” infra would require lots of ad-hoc bullshit. The ingress system of k8s is, at a high level, a standardized recreation of the typical “haproxy+nginx+ad-hoc provisioning” setup you’d find in a “classical” private cloud deployment. TLS in, send to nginx, nginx chooses a relevant healthy back-end and reverse proxies the request. K8s doesn’t really do anything crazy complex, the complexity is just inherent to having a many-to-many mapping of HTTP requests while optionally supporting multi-zone setups with local affinity and lifecycle management/awareness.
But unlike with a traditional deployment there’s not a greybeard guru in the back who deployed it all and knows the ins-and-outs so it’s quite common that the complexity is not understood and underappreciated by the “admins”. That complexity is a blessing when you need to leverage it but a curse when you lack the expertise to understand what is happening holistically.
Kind of like a linux distro… It’s amazing when it works but when libpam throws an error and you don’t even know what that library is or does, well you’re in for a fun evening.
Kubernetes is not really meant primarily for scaling. Even kubernetes clusters require autoscaling groups on nodes to support it, for example, or horizontal pod autoscalers, but they are minor features.
The benefits are pooling computing resources and creating effectively a private cloud. Easy replication of applications in case of hardware failure. Single language to deploy applications, network controls, etc.
Yea I’m not a fan of helm either. In fact, I avoid charts when possible. But kustomize is great.
I feel the same way about docker compose. If it wasn’t already obvious, I’m biased in favor of k8s. I like and prefer that interface. But that’s just preference. If you like docker compose, great!
There’s one point where I do disagree however. There are scenarios where a local k8s cluster has a good and clear purpose. If your production environment runs on k8s, then it’s best to mirror that locally as much as possible. In fact, there are many apps that even require a k8s api to run. Plus, being able to destroy and rebuild your entire k8s cluster in 30s is wonderful for local testing.
Edit: typos
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!
Seconding k3d (and, by extension, k3s). If you’re in a market for sth suitable for more upstream-compliant clustering solution (k3s uses SQLite instead of etcd, iirc), RKE2 is also a great choice
k8s is overkill for a lot of homelabs. Using docker compose is a fraction of that complexity
Yes if single node, kinda if 2-3 nodes, no for anything above that IMHO.
There are many reasons to use k8s. Managing multiple nodes is one good one. But more importantly, k8s gives you an api-driven runtime environment. It’s really not comparable to docker compose.
