rafbgarcia
I’m trying to do this:
Main app has the database.
A package will hold a GraphQL API and its resolvers that use that database.
How can I accomplish that?
Thanks!
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security











Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
nbap
Hi @rafbgarcia,
you may specify the Repo on a configuration key in your app config file.
e.g
In the main app
config.exsIn your package
And reference the repo anywhere in your package like this
I guess that will do but of course, you can tweak a little to adapt it to your needs.
rafbgarcia
Hi @nbap,
Thanks for the reply, it actually worked.
However, I’m trying to
use Absinthe.Ecto, repo: Application.get_env(:enderecify_api, :repo)and when I attempted to publish the package I get** (RuntimeError) You mustuse Absinthe.Ecto, repo: MyApp.Repowith your application's repo..Any ideas how to get around that?
rafbgarcia
I managed to get around that using a FakeRepo lol.
mgwidmann
What you should do is have your Ecto schemas and GraphQL resolvers in the same package with the Ecto Repo, but don’t add it to your supervision tree. In order to do that you’ll have to configure the
:otp_apppart so your Ecto schema/GraphQL package’s repo. This would mean your non-main package would just define schemas, resolvers and a repo but wouldn’t start them or do anything (they’re just plain modules then). Be warned though, compilation will fail if you do not configure it! (i.e. in tests or other areas) This would look something like:Then in your main app do the following in config:
Finally in your main app supervision tree: