grist-core

I added an Zenko Scality CloudServer S3-compatible Storage backend to a selfhosted Grist [1] instance. This allowed me to create forms with attachements in Grist (e.g. users can upload photos). I experimented with several and settled on Zenko Scality CloudServer [2]: - MinIO [3] is somewhat deprecated and not really open source anymore. Its future is unsure. - GarageHQ [4] looks pretty great and I wished I could have used this, but it is not yet feature-complete with S3 protocol and specifically missing the versioning feature (I reported this [5]) - Zenko Scality works out of the box; it is a bit too "big" for my context (aimed at thousands of parallel users) and uses 500MB memory; but it does the job for now. I posted my compose here [6]. Since then (~months ago), it works really well and I am happy with Zenko Scality S3. [1]: https:

I feel like a lot of these types of apps could just be spreadsheets. Maybe a "smart" spreadsheet like Grist[0] executing Python code. Am I off-base there? [0] https://github.com/gristlabs/grist-core

Grist. Let them sink happily into spreadsheets powering everything. https://github.com/gristlabs/grist-core

Grist forms support uploads since 2025 https://github.com/gristlabs/grist-core/pull/1655 Since it is relevant here: support for uploads was code written by a French contributor, and reviewed by a developer working for the French gov (ANCT/DINUM) and a developer working for Grist Labs. Grist Labs has since maintained and improved on it. The forms feature itself was inspired by an integration built by Camille Legeron at ANCT.

I agree. However, so many of my use cases include a one-to-many relationship that I was outgrowing excel/sheets too quickly. Once a project added a VLOOKUP, it hit an inflection point in complexity. I spun up a local Grist instance in my org, using SAML with our org's email authentication. It's intuitive enough that I've replaced a few shared spreadsheets with it (now with rowwise permissions) and powerful enough that I've also replaced a few internal CRUD apps. https://github.com/gristlabs/grist-core

I'm quietly adding "pull requests" for data to Grist https://github.com/gristlabs/grist-core/issues/1829 - been wanting to do this for a long time. I tried doing this years ago as a stand-alone project and it was too much. I wrote a data diff/patch/merge tool called "daff" that worked okay. But I've always wanted to add this to a proper spreadsheet tool like Grist. I really want people working on data projects to be able to work more like coders, with pull requests and reviews. Not all data projects are as curated as that, sometimes your data is just a big soup, but when it is curated, there should be a better workflow.

Yes, there are lots of PR listed here : https://github.com/gristlabs/grist-core/pulls?q=is%3Apr+labe...

> The French government agency ANCT Données et Territoires has also made significant contributions to the codebase. From the Grist-core readme : https://github.com/gristlabs/grist-core

The open-source project Grist Core (https://github.com/gristlabs/grist-core) is developed in the United States, with contributions from some French gov tech team.

Grist [1] desktop [2] is a (kind of) local "wrapper app" over an sqlite database. It is "As extendible as it is flexible" [3] The problem is I feel the tabular DB format is "too raw" for some usecases. I prefer Outliner/DB combos (like the upcoming logseq DB version) or maybe one of the local Notion alternatives. [1] https://github.com/gristlabs/grist-core [2] https://github.com/gristlabs/grist-desktop [3] https://www.getgrist.com/product/#:~:text=As%20extendible%20...

Grist? https://github.com/gristlabs/grist-core Via https://news.ycombinator.com/item?id=38080951

Grist Labs | Systems Engineer | Full-time | NYC OR REMOTE +/- 3hrs | https://getgrist.com We're looking for someone to make our modern spreadsheet software run everywhere. To apply, there's a puzzle. Just do: docker run -it gristlabs/grist-twist and poke around. If the words battery correct horse staple mean something to you, you might have an advantage. The heart of the software you'll be working with: https://github.com/gristlabs/grist-core/ More information about job and company: https://www.getgrist.com/job-systems-engineer/ The essential requirement for the job is comfort working with operating systems and containers, and having some back-end programming experience. People with a dev-ops background will do well. If you have strong open source experience, even better. Have you seen people install your popular software in weird and

i want exactly the opposite - something that does not try to be a spreadsheet, but gives me a grid view of a database table, with concurrent edits a la google sheets, and lets me access the same data from my webapp backend. i have been searching for this for literally years, all the time maintaining an app as a google sheets script, because much as i would prefer something self-hosted and customisable, that collaborative grid view is the ideal user interface from my users' point of view. so far nothing has fit the bill - basetool (https://github.com/basetool-io/basetool) might have but it's discontinued and underdocumented, and i'm not really a web developer so i don't feel up to the challenge of getting it running and integrated into an app. grist actually came really close from a ui perspective, but it was too focused on being a spreads