And here @raphael also tries to develop #couchdb based #activitypub client: https://indieweb.social/@raphael@communick.com/114296648141461966
Interesting.
And here @raphael also tries to develop #couchdb based #activitypub client: https://indieweb.social/@raphael@communick.com/114296648141461966
Interesting.
Storing #RDF or #LinkedData is the easy part (I am working on #activitypub client, so everything is JSON-LD anyway), but as soon as I need to formulate queries like "Give me list of the activities from all the actors who are on the following collection of my user, sorted by published/updated date", the amount of data mangling that I need to do is already making me think "ok, why don't I just push all of this to sqlite?"
@Ulrich @Temperche Sorry if that is phrased in an unclear way.
#CouchDB is the database used by #flohmarkt and there is other software available for #yunohost that installs CouchDB. CouchDB is not part of the yunohost system and it could lead to problems if two packages mess with the same CouchDB configuration (the sytsem wide Debian package is installed).
If there is no CouchDB on your system, yet, flohmarkt will just install. If there's already a CouchDB running, flohmarkt could be integrated, but since I didn't have any test cases it will not install without forcing it to protect whatever you're running already with a dependency on CouchDB.
If you run into issues or have further questions: please open an issue on codeberg (or github) so we can discuss how to make the context more clear or improve the install routine.
Oh _no_
in #CouchDB, Mango querying does not mix with using "" as document key.
"One or more conditions is missing a field name."
Is there an #activitypub server that uses #couchdb (or any other database with #json support) as a backend and/or application server?
Stressful start to the year?
You have one less worry with #CouchDB
Our latest article covers @couchdb’s #checksums feature: a built-in safeguard that helps protect your data from the impact of ever-dreaded disk corruption.
It’s just one of the features that makes CouchDB your data’s safe place.
Full post on our blog: https://neighbourhood.ie/blog/2025/01/22/how-couchdb-prevents-data-corruption-checksums
We published a four part series about how to build a real-time multi-user Kanban board with @couchdb and @sveltejs
Its is complete with code for all steps, so it’s not just a draw-the-rest-of-the-owl tutorial:
1. Setup, intro, first steps: https://neighbourhood.ie/blog/2024/12/05/realtime-multiuser-kanban-board-with-couchdb
2. Automatic Conflict Resolution: https://neighbourhood.ie/blog/2024/12/11/automatic-conflict-resolution
3. Manual Conflict Resolution: https://neighbourhood.ie/blog/2024/12/18/manual-conflict-resolution-with-couchdb-and-svelte
4. Avoiding Conflicts with Resource Locking: https://neighbourhood.ie/blog/2025/01/15/resource-locking-with-couchdb-and-svelte
.0 releases get more press, but it wasn't the right thing to do, and #CouchDB chose the better path. Kudos to Apache CouchDB for sacrificing a marketing win for a *user* win. https://blog.couchdb.org/2024/09/27/3-4-1/
Beyond Tellerrand #btconf is in Berlin! In-person conferences are a thing again, and we’re really happy to connect with the #JS and #CouchDB communities face to face, collect stickers and share inspiring vibes.
Neighbourhoodies’ @janl is around — don’t miss saying hi!
If you weren’t able to make it, catch you in the comments soon. Subscribe so you don’t miss the talks when they’re up: https://www.youtube.com/btconf
Time is running out to download our Focus Guide: Open Source Databases. Get up to speed on the open source database ecosystem and learn which solution could be right for your organization. This focus guide is available free for a limited time thanks to our partner Percona
https://mailchi.mp/admin-magazine.com/open-source-databases
#OpenSource #database #FOSS #Percona #PostgreSQL #MySQL #MariaDB #CouchDB
For 12 years already, I've been on/off experimenting (and prototyping) to create a compendium & knowledge graph about computational & generative art, the different movements/genres/mediums (e.g. architecture, design, visual art, audio/music, sculpture, kinetic/motion, film/animation, text etc.), influences, definitions/references, people (artists, curators, writers, thinkers), collectives, organizations (foundations, galleries, museums), exhibitions/festivals, tools & tool makers, common techniques used, art platforms — everything tagged and also supporting to browse by time (centuries & decades, currently starting ~1600) and region...
Attached are some screenshots of my first prototypes from 2011/12 (using #CouchDB, then #neo4j for storage & my own tools for force-directed graph layout) and of the current prototype using #Logseq (https://logseq.com)... The latter is working great for now and feeling, I'm getting somewhere this time, also because I have to make it work (for work!). This is all still just a beginning, hundreds of more people, orgs, projects & references to import and re-check from older versions. The current contents are _very_ biased to my own network/trajectory in/through this space...
Ps. Following up with all the folks & materials I've included already, I'm realizing again and again just how I've been the most naïve and _worst_ person to monetize (mostly not even trying!) my art/contributions... For 20 years I've filed 90% of hundreds of my projects under "experiments", "sketches", "demos", "tutorials" (often also to help illustrate techniques of my open source tools), only to realize (not for the first time) almost everyone else of my old peers has been way less selective and been attaching way more importance to all of their outputs... Maybe one day I will learn, before it's too late...
Our Halloween episode is out!
Maybe you’re celebrating #hacktoberfest this month, or you’ve made a contribution to #CouchDB and are curious about how it ships with a release. Catch all the spooky details over on Dev.to. Let us know in the comments what you think of the new release!
https://dev.to/neighbourhoodie/what-goes-into-a-major-oss-release-a-couchdb-story-1l5c
#CouchDB 3.4.2 is out!
We held a Meetup recently to take a look at the big 3.4.0 feature release that includes #QuickJS and #Nouveau (full recordings: https://vi.to/hubs/couchdb-berlin).
While the Neighbourhoodies worked with Nouveau to prepare presentations, we came across 6 bugs that get fixes in this release — shoutout to Alex Feyerke for finding them! Haven’t upgraded? You’re running out of reasons not to As always, if your team need help, reach out.
Full release notes: https://docs.couchdb.org/en/stable/whatsnew/3.4.html
We’re going live shortly
Our online #CouchDB Meetup starts at 17:00 CET, so if you’re not getting up to much tonight, why not join us? Four-legged friends are welcome too!
We’ll be covering what’s new in 3.4.0 + 3.4.1, trying out the new #QuickJS beta, and introducing #Nouveau for fulltext search with @janl, @ninette and Alex Feyerke.
Sign up and discover all the talks: https://vi.to/hubs/couchdb-berlin
It’s tomorrow! Are you joining our Online #CouchDB Meetup from 17:00 - 18:30 CET, on Oct 9?
3.4.0 + 3.4.1 have been out for a couple weeks now, and they brought #QuickJS with them. It’s the new #JavaScript engine for CouchDB that speeds up queries and server-side processing.
Get a detailed introduction from @ninette in Talk #2 and learn why others are delighted about how it enhances custom functions.
Sign up and check out the others talks: https://vi.to/hubs/couchdb-berlin
#QuickJS and #Nouveau are a couple #CouchDB 3.4.0 + 3.4.1 updates you can see at our Oct 9 Meetup.
@janl will shed light on 3.4.1 + where 3.4.0 went. Alex Feyerke and @ninette will detail new features:
Talk #1: CouchDB 3.4.0 / 3.4.1 Release Retrospective (Jan Lehnardt)
Talk #2: Introducing QuickJS: CouchDB’s New JavaScript Engine (Ninette Adhikari)
Talk #3: First Steps With Nouveau, CouchDB’s New Fulltext Search (Alex Feyerke)
We’re excited to host you!
Sign up: https://vi.to/hubs/couchdb-berlin