Download
We're evolving to serve you better! This current forum has transitioned to read-only mode. For new discussions, support, and engagement, we've moved to GitHub Discussions.

Publii, Dropbox and syncing the db.sqlite file

  • #2006
    Avatar photo[anonymous]

    Hello Publii developers,

    I use Dropbox to share the code of a website between me and a customer, and I notice that sometimes it takes a very long to sync the db.sqlite file.

    1. Is it possible that Publii locks the db.sqlite file and prevents it for syncing (uploading and/or syncing)?
    2. Is it true that you need to restart Publii in order to see a change in the db.sqlite file (and by this way in a post)?

    I have run some test but I can’t find (yet) a clear pattern of what is happening.

    Verhoeckx

    #2024
    Avatar photo[anonymous]

    Do people here have a good experience with Dropbox and working together on a site?

    #2033
    Avatar photo[anonymous]

    Hi,

    Publii uses the db.sqlite file directly (not in a memory), so yes – it is possible that Publii locks that file.

    At this moment Publii is not prepared for a parallel work. It is still good if you want to create a website with other people not in parallel.

    #2054
    Avatar photo[anonymous]

    Hi Tomasz,

    So what do think is the best workflow?

    I think that I have to ask my customers to close Publii after they have edited a post (or several posts)?

    If they (and me) do that:

    1. They unlock the db.sqlite file.
    2. Get the new content when they start Publii the next time.

    Verhoeckx

    #2056
    Avatar photo[anonymous]

    It seems to be the only solution in my opinion, but to be honest – it does not sound like a fluid workflow. Unfortunately at this moment I cannot propose anything better :/

    #2057
    Avatar photo[anonymous]

    Hi Tomasz,

    I have to agree with you!

    Publii is absolutely a wonderful and efficient system. The fact that it’s a client application makes it really accessible for customers and this is one of the reasons (besides the speed and the unhackable setup) that I chose Publii for building the next couple of websites. The fact that’s a client application has only one drawback: you have to sync the files in order to be able to work together (which creates the problem above). In an ideal situation Publii would run on a server and you would have to access it there. But as I understood from Bob this isn’t possible at the moment. If it would, Publii could become the next ‘WordPress killer’. Having said that: I also understand that it takes a lot of time, energy and money to develop this. (and I can’t help you because I don’t know how to program with Node.js and Vue).

    #2203
    Avatar photo[anonymous]

    Hello Tomasz,

    Can I ask you a question?

    The coming weeks I will work on two websites simultaneously.
    Do you happen two know what happens when you open/start Publii?
    Does is open both db.sqlite files or only the one that you are currently using?

    Verhoeckx

    #2204
    Avatar photo[anonymous]

    The reason I ask is that when Publii opens both db.sqlite files, and I’m constantly working in one of the websites, I block an other user for editing the sqlite file of the other website. This would be very impractical.

    #2205
    Avatar photo[anonymous]
    #2206
    Avatar photo[anonymous]

    Ah, that’s good news! Perfect!! Thanks!