Hosted mode: run the frontend from its own site and pick an instance #3583
No reviewers
Labels
No labels
BE Request
Backlog
Better behavior
Blocked by deps
Bug
Code Review
Discussion
Doing
Feature Request / Enhancement
In the shining bright future maybe
It's complicated
MS Edge
Mememoon (or other niche browsers)
Missing API
Missing feature
Missing l10n/i18n
NL1
NL2
NL4
Need to verify on develop
RELEASE BLOCKER
Reassign or Close
Refactor
Regression
Safari
To Do
User story
Waiting on godot
accessibility
better documentation
chore
confirmed
easy ticket
incident
l10n update
mastoapi
mobile
needs design
needs-info
needs-review
stupid
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
pleroma/pleroma-fe!3583
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/hosted-mode"
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?
With
"hosted": trueinstatic/config.json, the frontend can be served from any static host. On first load it asks for an instance, then talks to it directly (CORS):src/api/api_base.js). An empty base means the page is the instance, so nothing changes for normal installs.Tested with a build served by
vite previewagainst lain.com and fediffusion.art (picker, boot, timeline, OAuth redirect, change instance), and without hosted mode through the dev proxy.Known gaps in hosted mode: the admin-fe link in settings points at the hosted site, and web push is off.
i'm gonna add some nginx snippets and improve config.json logic (or just make a build argument?) later to make deployment easier
For now it's deployed onto https://fe.pleroma.dev/ and I upload and modify build manually over SFTP