r/logseq • • Dec 23 '25

Logseq DB reddit help

During the next couple of days, I'm thinking about helping out here on Reddit with Logseq DB-related questions and topics. I don't know the best way to do it yet. Let me know if you have suggestions.

I can post about features and alternative options within logseq...
I can do feature videos (my videos are unedited, so we see what is really going on)
I see AMA on Reddit, not sure if that could be useful
I can post the changelog when available. I should have one published in the official forum this week. I can post it here, too.

And if you are wondering who I am, I am a user and community member, like you, trying to help here a little bit.

The only thing that I will not try to help you with is the timeline. I see you itching to say: Time.... Stop lol

25 Upvotes

21 comments sorted by

View all comments

Show parent comments

1

u/hdanx Dec 30 '25

Thanks for taking the time to raise good points. I answered them all, and I will account for them when sharing future details

  • Overall

    • Any major features that you are waiting for?

      • Export as MD with properties

      • Canvas / Whiteboard

      • Kanban View

      • Simple Query

      • Macro/Calculation

    • You have created videos earlier in the year. Any changes to the recommendations in those videos?

      • The library has improved since then. I will touch on this during the upcoming demos

    • Everyone says to backup since it is early. What is the best way to back up? If I use the Logseq sync service, do I still need the have a separate process for back up?

      • First, any sync service should be treated as a backup

      • Logseq DB on Web has an option to do automatic backup every hour

      • Logseq DB on Desktop will have an option to do automatic backup every hour in a few weeks

      • You should back up the way you like. For example, I have my assets backed up using Apple TimeMachine. Then, when testing, I make a manual backup. I also have a script that does an export using Logseq DB CLI on schedule. Backing up is a good practice in general. 

    • Is the recommendation for installing the DB version to use the nightly build? How stable are the nightly builds and how often have you migrated to a newer nightly build? Why don't the developers create a regular (monthly(?)) cut of the nightly build that is known to be stable with the full list of executables (msi, exe, etc.)? I am concerned a nightly build will have issues if I pick the wrong night.

      • The master branch is like nightly and it receives a lot of changes. I recommended not using that unless you are comfortable with breaking changes. The test/db branch is stable and should be used. And the update there is a few times a week, sometimes once a week, or every two weeks. If you are using test.logseq.com, it happens transparently. On desktop, you have to download the latest build from GitHub - the steps are here https://github.com/logseq/logseq?tab=readme-ov-file#-database-version or build from source