Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Multi tenancy #77

Closed
badlanguage opened this issue Jul 26, 2021 · 4 comments
Closed

Multi tenancy #77

badlanguage opened this issue Jul 26, 2021 · 4 comments

Comments

@badlanguage
Copy link

Background
The current platform allows for one single "namespace" / "project"; however this should be extended to allow for multiple projects with their own collection of apps / services (see - #75). Additionally the concept of Organisations could be introduced (teams, if you will) - allowing for multiple users to view and manage these resources, with a roles system.

Use case
There are multiple use cases, but one that stands out the most is allowing for the orchestration of multiple projects from one Coolify instance, such as in an enterprise environment where multiple teams need access to different resources or perhaps a "production/staging" environment separate.

Notes

  • Please consider how this would work with the proposed API feature request (API #74) as this would mean additional endpoints would have to be implemented.
  • Please consider how this would work with (Kubernetes integration #45) as a project could be the equivalent of a "namespace" on kubernetes; a single service mesh tool like Istio could be used for scaling across multiple clusters via Kubernetes, among other overlaps i.e. roles, where necessary - impacting the implementation of this feature.
@badlanguage badlanguage changed the title [Feature request] Multi tenenacy [Feature request] Multi tenancy Jul 28, 2021
@andrasbacsai andrasbacsai mentioned this issue Aug 10, 2021
@andrasbacsai andrasbacsai added this to the v2 milestone Aug 10, 2021
@andrasbacsai andrasbacsai self-assigned this Aug 10, 2021
@andrasbacsai
Copy link
Member

It's partly - if not entirely - implemented in v2.

You could have separation by teams on the UI and docker network on the docker/server levels.

Environments like prod/staging would be implemented later, but it needs to be figured out how. 😄

@andrasbacsai andrasbacsai removed this from the v2 milestone Feb 21, 2022
@andrasbacsai andrasbacsai changed the title [Feature request] Multi tenancy Multi tenancy Feb 21, 2022
@robertorubioguardia
Copy link

Hi @andrasbacsai Loving Coolify.

One detail: If I have registration closed, I cannot invite new members to teams. From a management point of view, I would like to create my teams (as I am the server admin) and then invite people to specific teams.

Is that possible?

@andrasbacsai
Copy link
Member

Hi @andrasbacsai Loving Coolify.

One detail: If I have registration closed, I cannot invite new members to teams. From a management point of view, I would like to create my teams (as I am the server admin) and then invite people to specific teams.

Is that possible?

Thanks! Yes, it will be possible if I add SMTP integration.

@andrasbacsai andrasbacsai removed their assignment Apr 18, 2023
@andrasbacsai
Copy link
Member

I'm closing this issue, because tracking features will be moved to GitHub discussions. Github issues will be only for bugs.

Version 4 is in full focus. v3 related issues will be closed, if it is not a critical bug.

Thanks for your understanding.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 17, 2024
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants