[Feature Request]: Subdomain for shelves #2488

Closed
opened 2026-02-05 04:18:43 +03:00 by OVERLORD · 6 comments
Owner

Originally created by @Tealk on GitHub (Nov 13, 2021).

Describe the feature you'd like

Make a shelf accessible via a subdomain, so that it looks like there is only this theme.

Describe the benefits this feature would bring to BookStack users

It would be possible to divide areas better and to access them directly. The clarity and handling would improve for the user.

Additional context

No response

Originally created by @Tealk on GitHub (Nov 13, 2021). ### Describe the feature you'd like Make a shelf accessible via a subdomain, so that it looks like there is only this theme. ### Describe the benefits this feature would bring to BookStack users It would be possible to divide areas better and to access them directly. The clarity and handling would improve for the user. ### Additional context _No response_
OVERLORD added the 🌔 Out of scope🔨 Feature Request labels 2026-02-05 04:18:43 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Nov 13, 2021):

Hi @Tealk,

I don't really understand this request.

  • Is this in relation subdomains as in the URL bar (Like https://subdomain.example.com)?
    • If so, Are you asking for subdomain-specific shelves?
    • Otherwise, What is meant by "Make a shelf accessible via a subdomain"?
  • By "theme" are you talking about a category or are you reference design/styling?
@ssddanbrown commented on GitHub (Nov 13, 2021): Hi @Tealk, I don't really understand this request. - Is this in relation subdomains as in the URL bar (Like https://subdomain.example.com)? - If so, Are you asking for subdomain-specific shelves? - Otherwise, What is meant by "Make a shelf accessible via a subdomain"? - By "theme" are you talking about a category or are you reference design/styling?
Author
Owner

@Tealk commented on GitHub (Nov 13, 2021):

If so, Are you asking for subdomain-specific shelves?

yes, your example would then navigate to the shelf subdomain

By "theme" are you talking about a category or are you reference design/styling?

yes i mean categories, subdivision of topics

@Tealk commented on GitHub (Nov 13, 2021): > If so, Are you asking for subdomain-specific shelves? yes, your example would then navigate to the shelf subdomain > By "theme" are you talking about a category or are you reference design/styling? yes i mean categories, subdivision of topics
Author
Owner

@ssddanbrown commented on GitHub (Nov 13, 2021):

@Tealk Okay, Thanks for confirming.

BookStack doesn't support being served via multiple host-names/sub-domains at all.
It's not really something I'd look to support at this time due the impact and further requirements it would likely generate.

For this kind of situation I'd advise the use of multiple BookStack instances.

@ssddanbrown commented on GitHub (Nov 13, 2021): @Tealk Okay, Thanks for confirming. BookStack doesn't support being served via multiple host-names/sub-domains at all. It's not really something I'd look to support at this time due the impact and further requirements it would likely generate. For this kind of situation I'd advise the use of multiple BookStack instances.
Author
Owner

@Tealk commented on GitHub (Nov 13, 2021):

yes that would be possible but it increases the support effort; you need a central login service and have to take care of each instance individually

@Tealk commented on GitHub (Nov 13, 2021): yes that would be possible but it increases the support effort; you need a central login service and have to take care of each instance individually
Author
Owner

@ssddanbrown commented on GitHub (Nov 13, 2021):

yes that would be possible but it increases the support effort; you need a central login service and have to take care of each instance individually

Sure, but the alternative puts an implementation and maintenance burden upon this project (and myself) at a level I can't foresee being viable at this time.

@ssddanbrown commented on GitHub (Nov 13, 2021): > yes that would be possible but it increases the support effort; you need a central login service and have to take care of each instance individually Sure, but the alternative puts an implementation and maintenance burden upon this project (and myself) at a level I can't foresee being viable at this time.
Author
Owner

@ssddanbrown commented on GitHub (Nov 14, 2021):

Will therefore close this off as out of scope.

@ssddanbrown commented on GitHub (Nov 14, 2021): Will therefore close this off as out of scope.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#2488