[frontends] allow for arbitrary frontend settings #12
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
currently akkoma supports only
:primary
and:admin
settings for the frontend - this means you can have only one user-facing frontend at a timethis should be expanded to allow any number of frontends mounted at a given path - in the style of masto-fe being hosted at
/web
this will need some consideration given that most frontends assume they are running at
/
- do we need a specific build that does not assume that? i wouldn't be keen on rewriting anything dynamicallyi had the solution to this revealed to me in a dream last night
subdomains
SUBDOMAINS
how could i not have seen it
everything wants to run on
/
, so let's... let itreverse proxies can have n domains, and we can probably use phoenix to route based on it
close?
close as in "should we close this?" or "are you close?"
i got it working but i'm yet to find a satisfying flow to get it to work
How close is this to getting made a feature?