-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Elixir client #1833
Add Elixir client #1833
Conversation
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hey, can I also request that this PR also updates https://github.com/electric-sql/electric/blob/main/website/docs/api/clients/elixir.md -- shout if you want to sync on what we should document there. |
c23c3a4
to
03226a2
Compare
yeah. we really need the client in hex to make the separate phoenix integration work. |
a4b6e2d
to
c5fb512
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we merge this?
c5fb512
to
227b4b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
139cfe1
to
b683205
Compare
Fleshing out deployment guide. To support it, added a sync service config page in the api docs section and specific integrations pages for various deployment platforms. Quite a lot to review here. Check out the: - [Sync service config page at /docs/api/config](https://deploy-preview-1836--electric-next.netlify.app/docs/api/config) - [Updated Typescript client page at /docs/api/clients/typescript](https://deploy-preview-1836--electric-next.netlify.app/docs/api/clients/typescript) - [Deployment page at /docs/guides/deployment](https://deploy-preview-1836--electric-next.netlify.app/docs/guides/deployment) - Individual integration pages in the "Integrations" section of the docs nav, e.g.: [AWS](https://deploy-preview-1836--electric-next.netlify.app/docs/integrations/aws), [React](https://deploy-preview-1836--electric-next.netlify.app/docs/integrations/react) and [Supabase](https://deploy-preview-1836--electric-next.netlify.app/docs/integrations/supabase) Note that: - Netlify has a one-click-deploy form that uses https://github.com/electric-sql/standalone-basic-example - [Render](https://deploy-preview-1836--electric-next.netlify.app/docs/integrations/supabase) has a [Blueprint repo](https://github.com/electric-sql/render-blueprint) that also uses the same standalone-basic-example As @KyleAMathews commented on Discord, these might be better to include in the monorepo and update using a GitHub action. Perhaps that can be a subsequent Issues / PR. The integrations also include a [Phoenix page](https://deploy-preview-1836--electric-next.netlify.app/docs/integrations/phoenix) which is based on merging #1833 and publishing an updated release for https://hexdocs.pm/electric_phoenix/0.1.0-dev-2/Electric.Phoenix.html Note that the deployment docs all assume a single `DATABASE_URL`, i.e.: this is pre multi-tenant. --------- Co-authored-by: Kyle Mathews <[email protected]>
Docs are live https://electric-sql.com/docs/api/clients/elixir |
otherwise the elixir is syntax-highlighted and it's hard to read
queryable version only takes a single param, no opts
5a58d51
to
4431d4f
Compare
Yey! |
No description provided.