kelvinst
Triplex - a complete solution to multi-tenancy with PG schemas
Hey everyone!
Well, we made this lib a while ago and now we decided to finally go out and public with it! It’s a tool for creating and managing multi-tenancy applications using postgres schemas.
https://github.com/ateliware/triplex/
We’ve recently released version 1.1.2 with support for ecto 2.2.0-rc. ![]()
I know there are some other options of libraries for the same purpose, like GitHub - Dania02525/apartmentex: SaaS support for Phoenix + Ecto · GitHub and GitHub - tweag/tenantex: Multi-tenant support for Ecto (Elixir) · GitHub. At the time we wrote this lib, the other libraries were a little bit out of date with their pull requests, didn’t have everything we wanted and, the worst for us, were a little bit intrusive (I’ll talk about it later).
So we decided to write a simple one, and now here we are, another option for you. Here is a list of features we missed on the other libraries:
- Mix tasks for migrating and rollbacking all schemas
- Plugs to load and ensure if the tenant is loaded from a param, session value or subdomain
- A way to infer the name of the tenant from a given struct which represents the tenant on your application
- Smarter configuration like:
- Set the default
Repowhere to execute the tenant management tasks - Tenant names that must be reserved, like
apiorwwwif you’re using subdomains to load your tenant
- Set the default
There are also some differences in the way the libs handle the queries and commands with the prefix. While tenantex and apartmentex are a little bit intrusive to your Repo or the use of it, on triplex we tried to stay the least intrusive we could.
For example, here is how to make a query applying a prefix from an tenant struct called org on raw ecto:
Repo.all(User, prefix: org.subdomain)
Now the same query using a properly configured triplex:
Repo.all(User, prefix: Triplex.to_prefix(org))
The same with tenantex:
# first you need to change your repo to use their repo not ecto's
defmodule Repo do
use Tenantex.Repo, otp_app: :your_app
end
Repo.all(User, prefix: org)
Finally, with apartmentex:
Apartmentex.all(Repo, User, org)
The reason behind this decision is simple: being less intrusive makes triplex a lot easier to upgrade for future versions of ecto.
And one last thing: we got our docs a little bit further! That’s a bonus for anyone who wants to use it! ![]()
Feel free to try it and send feedbacks for us!
Most Liked
kelvinst
Heeey! Long time no see, but I’m here to announce 1.3.0 (not rc, the official one) is out! You can check the list of stuff on the release notice, but for those that have no time, the big thing on this release was the support to Ecto 3.
Hope that the lib is still useful for all of you and we are always open to contributions, but please do not be sad if we take some time to answer, there are not too many people on the core team for it and we are very busy lately.
Thanks!
kelvinst
1.2.0-rc is out!
Hey guys! Quick update: we got a new release!
Despite not having huge changes or new features, we have incremented the minor version for some reasons. You can check these reasons as well as the changelog here: Release 1.2.0-rc.0 · ateliware/triplex · GitHub
But for those who don’t have time do get there, the biggest things that are coming out with this release are:
- Plug as an optional dependency, so if you don’t use any plug on your app, triplex will not add this dependency on your project.
- The support for using triplex on OTP releases, which I really didn’t know we had a problem with, but now, thanks to @dustinfarris, we do not have it anymore! PS: if anyone does need this correction on a
1.1patch release, please let me know. - Docs and README improved.
- Refactors on plug configs and method return values.
Hope you’re liking to use it.
kelvinst
I’m here to announce the long awaited new version for Triplex!
Actually, it’s an RC for the new version. You know, we need to test it well before releasing it out in the wild.
Anyways, this version will come with the support for two new things: Ecto 3 and MySQL!
The details are here in the release notice: Release 1.3.0-rc.0 · ateliware/triplex · GitHub
Also, refer to the release notice for how to upgrade, since there are some breaking changes on Ecto 3 migrations that affected Triplex.create inside Repo.transactions.
With no further ado, we would be very grateful if you could test it out on your projects and let us know with github issues if any problem occurs!
Thank you all!
Popular in Announcing
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









