France and Germany, in joint collaboration, have developed a Google Docs alternative - and its awesome! (Netherlands are currently onboarded)
-
What about Collabora Online? It integrates nicely into Nextcloud, but I am not sure about pricing for business use.
https://www.collaboraonline.com/collabora-online/
Guide for self hosting:
https://collabora-online-for-nextcloud.readthedocs.io/en/latest/install/Thanks I'll definitely check that out. I've seen some posts about it working on Synology Nas devices so that's very interesting.
-
Don't know what a Foss is
In case you didn't understood by now, it's free open source software
-
Don't know what a Foss is
I was going to make a joke but honestly it's refreshing and a good sign that Lemmy is starting to get used by people who don't know what FOSS means now. Welcome.
-
This post did not contain any content.
If I can copy and paste with thought having to install the offline plugin, then I'm in.
-
Don't know what a Foss is
Nice to see Lemmy is not just a place for complete nerds!
FOSS is free and open-source software. In simple terms, it is any program for which the source code (i.e. the actual code that forms the program, its entire backbone) is available for anyone to see and modify as they see fit, without any technical or legal limitations.
This is normally seen as very positive, because everyone with the knowledge of respective programming languages can inspect the program to see it doesn't do anything malicious, and everyone can change the program to their needs. Also, the original creator of the program does not have power to put any limitations on its use, like introducing payment requirements, or deleting important features, because everyone can immediately spawn a version of the program that doesn't have these changes, while still having the rest.
-
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.
-
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.
-
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.
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.
-
Right up until you are doing compliance and governance and you realize docs are actually a terrible terrible source of truth for any automated systems. We’re 3 years into a project at a healthcare company to rip google sheets and docs out of our apps and replacing them with Postgres, bigquery, dbt and dagster.
It’s simply not okay to have your database be something anyone with write access to a doc can fuck up a formula by accident on. Your medical bills being maintained by random formulas on dozens of linked spreadsheets maintained by hand by random people on different teams is part of why they are impossible to unwind. By the time someone audits it, it’s printing different numbers than when your bill was rendered and it’s version control doesn’t work to roll it back without breaking dozens of other things.
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.
-
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.
-
While both of those are great software. Unless I'm not aware of something they aren't cloud/network based office suites like Google docs and office 365.
It seems this is an alternative to office software where you can work simultaneously and share documents in the same cloud/network.
I don't think there is an alternative to office 365 and Google docs at this point that is open source. So this seems like a great project and I'll definitely be considering it for our company.
There is nextcloud and others you can self host at least.
-
Doesn't do collaborative online editing and that seems what this is about. But there are foss alternatives already, collabora/nextcloud, cryptpad etc.
-
There's onlyoffice for cloud based office
Onlyoffice seems a little slack on the security and updates. I saw the warnings in the desktop package, have they made sure the online offerings are secure?
-
I have been using collaboration with Microsoft products for decades with little issue.
You've had 60+ people all in a single Excel spreadsheet on Sharepoint all making changes at the exact same moment and never once had a issue of a document lock or file corruption? Its okay to have a preference for one product over the other, but when you're blinded by brand loyalty where you can see no wrong with your preferred product, it makes you lose credibility.
Just chipping in here but I gather 60 concurrent editors is pushing what most people have experienced - so thanks for your perspective!
Most I've dealt with is about 5 (in Excell) - and the actual changes were not really being made frequently or by all parties. The worst part was the project manager altering the view and fucking up everyone else's perspective (even though each had their own?!) - Classic PM stuff.
Does Sheets and the rest of the Google suite handle this well?
-
Just chipping in here but I gather 60 concurrent editors is pushing what most people have experienced - so thanks for your perspective!
Most I've dealt with is about 5 (in Excell) - and the actual changes were not really being made frequently or by all parties. The worst part was the project manager altering the view and fucking up everyone else's perspective (even though each had their own?!) - Classic PM stuff.
Does Sheets and the rest of the Google suite handle this well?
Does Sheets and the rest of the Google suite handle this well?
It does.
I'll also be the first to say that many of these use cases should not be using a spreadsheet for the kind of work that is occurring and a database is much more appropriate, but we know "should" rarely is present in modern companies or enterprises.
-
Doesn't do collaborative online editing and that seems what this is about. But there are foss alternatives already, collabora/nextcloud, cryptpad etc.
-
This post did not contain any content.
-
It looks closer to the markdown style of formatting though, and I doubt it has page formatting, or other more advanced formatting, or extensions, or a large selection of fonts. Honestly, even though docs has pageless formatting now, most people don't use it when they should, making everything unnecessary harder to read, so this will be better in that regard at least. This is probably good enough for 95% of what people use Docs for, but I wouldn't call it a replacement.
I haven't used it because I don't have a French government account, so correct me if I'm wrong about any of that.
Edit: it looks like it only has 1 font and no page formatting
There is a public demo instance. The link and test credentials are on the GitHub page.
-
This post did not contain any content.
Is there a German-hosted instance? The URL https://docs.numerique.gouv.fr/login/ is making me wanna barf and no way I'm clicking it to risk seeing more Fr*nch.
-
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.
Right. But you can’t do that in a live system like google docs. You can have a workflow to export copies, but the live doc is the one bigquery and linked docs utilize to function against your app. It’s actually a feature of the same tooling that makes using them like a database possible that causes it to not be versionable. So even if you export copies as you update it, you can’t move the system back to those copies without breaking other parts of the system.
Other systems for modeling data have better version control for running parallel versions of models if you need to recover how data had been constructed in an older state. It’s an incredibly bad idea to do this with Google docs at scale
