Skip to content
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

Meta-Issue: Multi-tenancy in Fedora #926

Open
dannylamb opened this issue Sep 18, 2018 · 1 comment
Open

Meta-Issue: Multi-tenancy in Fedora #926

dannylamb opened this issue Sep 18, 2018 · 1 comment
Labels
Subject: Drupal related specifically to Drupal, usually pointing somewhere on drupal.org Subject: Fedora Related specifically to Fedora, usually should point somewhere to the Fedora project. Subject: Multi-tenancy related to having content from multiple Drupal sites in one system Type: documentation provides documentation or asks for documentation. Type: enhancement Identifies work on an enhancement to the Islandora codebase Type: Meta-issue Identifies multiple related tickets for ease

Comments

@dannylamb
Copy link
Contributor

This is a meta-issue to track the development of multi-tenancy usage of Fedora in Islandora, that is multiple Drupal (multi)sites preserved in a single Fedora.

The general approach is to give each Drupal site its own subtree in the overall Fedora, and use WebAC policies to enforce restrictions limiting activity to each sites' users.

Please reference this issue in each subsequent issues so that they are linked.

@acoburn
Copy link
Contributor

acoburn commented Sep 20, 2018

@dannylamb while I recognize that this is definitely a feature that people want, I'd like to push on the underlying assumptions a little.

Once upon a time, people built really large application servers that ran lots of apps for lots of users from different realms, but with the way things are with containerization, that's kinda a thing of the past. These days, rather than running a single server to handle lots of "sites", you more typically have lots of small containerized applications, each of which handles only its own realm. This allows you isolate data, runtime and access control, which is almost always a big win. In a cloud-deployed context, it is an even bigger win, especially for hosting institutions that might want a coherent way to "charge-back" the users of the system.

So, for this issue, the question would really become: in a multi-site context, do you want multiple repository backends or only a single repository backend?

@kstapelfeldt kstapelfeldt added Type: documentation provides documentation or asks for documentation. Subject: Drupal related specifically to Drupal, usually pointing somewhere on drupal.org Type: enhancement Identifies work on an enhancement to the Islandora codebase Subject: Fedora Related specifically to Fedora, usually should point somewhere to the Fedora project. Type: Meta-issue Identifies multiple related tickets for ease Subject: Multi-tenancy related to having content from multiple Drupal sites in one system and removed documentation labels Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Subject: Drupal related specifically to Drupal, usually pointing somewhere on drupal.org Subject: Fedora Related specifically to Fedora, usually should point somewhere to the Fedora project. Subject: Multi-tenancy related to having content from multiple Drupal sites in one system Type: documentation provides documentation or asks for documentation. Type: enhancement Identifies work on an enhancement to the Islandora codebase Type: Meta-issue Identifies multiple related tickets for ease
Projects
Development

No branches or pull requests

4 participants