CharlesIrvine
Persistence and library applications - need advice
I have a open source GenServer based library application. It currently persists data in a CubDB database. I would like to migrate from CubDB to Postgres. I have used Ecto/Postgres before with a Phoenix web app, but I’m unsure of how things will work if I’m adding Ecto/Postgres to a library app.
It would be great if I could get some general pointers on the steps that I will need to take. What will users of my library need to do to support both my libraries persistence and their own persistence needs. Will there be two databases, one for my library and a separate one for the using application?
Marked As Solved
garrison
I think the canonical example for this is the way Oban handles migrations.
Personally I have a library which just generates migrations directly into my application (codegen), but that’s because it’s intended for my own use only ![]()
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance








