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

Manage Multiple Databases #363

benhaynes opened this Issue Sep 7, 2018 · 1 comment


None yet
2 participants

benhaynes commented Sep 7, 2018


Manage Multiple Databases

πŸ‘ = 53

Created 1 year ago by @benhaynes

@benhaynes – πŸ‘ (1 year ago)

This would be a global dropdown to change the DB you're connected to.

@hrwebasst: I'd suggest moving this further up the issue list. I have a use case that is probably pretty common. Installing automatically in my docker instance with my site download for development purposes. I have already easily bypassed the login and can add the schema in by default but it would be nice if Directus could be simply pointed at a database the user had perms for so that I can bake this for all of my users.

tl;dr Directus has own database points to one or multiple sub-databases on install would be awesome.

@nums – (1 year ago)

How can you identify the DB on which the user logs on to the API?

Maybe like that?
curl -d "email=user@directus.local&password=pass123&db=mydb"

@detj – πŸ‘ (7 months ago)


@diegogurpegui – (6 months ago)

Regarding the "How can you identify the DB on which the user logs on to the API" I think it would be better to make it part of the URL/path, instead of a query parameter. And leave those only for filtering and things related to the query you are doing. The URL represents the resource you are accessing, and the database instance is part of that resource in my opinion.

@ezanattatray – πŸ‘ (4 months ago)



This comment has been minimized.


rijkvanzanten commented Sep 7, 2018

We have this in the form of Projects!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment