Suggestions for data storage

[Prikers]

Hi there,
Thanks for this great template, really neat.
I have a question related to data storage:

• There is information I want to store between app launchs (user settings and some data). For that, it seems that electron-store is the go-to option
• I want this data to be interactive with the UI so it will fit in a pinia store
• I usually use pinia-plugin-persistedstate to persist my pinia stores

I guess my question is: has anyone tried make these packages play nicely together? Or are there better options to achieve persistence of pinia stores between app launches?

Thanks!

[jooy2]

Hello and thank you for using the Vutron template!

I'm not sure if this is a useful answer, but I'll write it down to the best of my knowledge.

Yes, you are correct. The electron-store is one of the storage modules that preserves data even when the app is closed.

I initially considered adding this module as an example to the template, but I thought it would be confusing for beginners due to the non-simple initial setup and the fact that the data is managed by the main process. However, it's not an impossible solution by any means and I'm sure it's a model that could be useful in production if adapted.

Below is an example of a project with a different concept than Vutron, but using React + Electron + Vite, and electron-store (removed in the latest commit):

https://github.com/jooy2/retron/tree/b8c7b630cca4bf6965cb01d290a2a575cad79293

A second option is to use a solution like sqlite3 (https://github.com/TryGhost/node-sqlite3) or Realm (https://github.com/realm/realm-js), which also requires a lot of initial code to write and is more difficult, but has more advantages than electron-store, such as good compatibility, stability, data protection, and guaranteed maintenance.

Finally, if your persistent data is simple, you can also try Local Storage or Cookie, which are features of electron itself. These are the same as those used by web browsers, and are managed in separate storage files for each app.

I hope this short answer was helpful to you. Thank you.

[Prikers]

Thanks for your feedback, this is always helpful. I was able to use the electron-store within the main process and I exchange messages back and forth to the renderer process where data is stored in pinia stores (I persist them with pinia-plugin-persistedstate but not sure that's necessary).
I find the electron-store very easy to setup and use. In the past I had issues in the building process when using sqlite3 so I did not want to go down that road :-)
Thanks again for the feedback and the very helpful template!

[txl16095]

Hello, I am a novice learning Electron for the first time. I accidentally discovered this framework. I found that this framework is very friendly to novices. I can run it and make modifications easily. Again, thank you to the author. I plan to use this framework to write my first desktop program, which is about code snippet management. This requires the use of local storage technology. The author mentioned sqlite3 and Realm about storage. I looked at each and each has its own advantages and disadvantages, which makes it difficult for me to choose. Which one do you recommend me to use more?

[jooy2]

Oh, I just looked it up some more and it looks like there's also a third-party plugin for Pinia that allows for persistent statefulness!

https://github.com/prazdevs/pinia-plugin-persistedstate

[NotTsunami]

Late to the party, but as of the HEAD at the time of writing, simply installing and following the steps listed in the README for the Pinia plugin, the persistence worked out of the box and persisted the counter with no additional changes. No additional tooling necessary either! Commented in case anyone else stumbles on this issue and are unsure.