|shpuld 9c2c00992d Remove files I accidentally pushed in||1 day ago|
|build||1 week ago|
|config||1 week ago|
|src||1 day ago|
|static||1 day ago|
|test||1 week ago|
|.babelrc||10 months ago|
|.editorconfig||2 years ago|
|.eslintignore||2 years ago|
|.eslintrc.js||1 week ago|
|.gitignore||7 months ago|
|.gitlab-ci.yml||2 months ago|
|.node-version||2 years ago|
|BREAKING_CHANGES.md||1 month ago|
|CHANGELOG||2 years ago|
|COFE_OF_CONDUCT.md||2 years ago|
|CONTRIBUTORS.md||1 year ago|
|LICENSE||2 years ago|
|README.md||3 months ago|
|index.html||2 months ago|
|package.json||4 days ago|
|yarn.lock||4 days ago|
A single column frontend for both Pleroma and GS servers.
To translate Pleroma-FE, add your language to src/i18n/messages.js. Pleroma-FE will set your language by your browser locale, but you can temporarily force it in the code by changing the locale in main.js.
You don't need to build Pleroma-FE yourself. Those using the Pleroma backend will be able to use it out of the box. For the GNU social backend, check out https://git.pleroma.social/pleroma/pleroma-fe/wikis/dual-boot-with-qvitter to see how to run Pleroma-FE and Qvitter at the same time.
# install dependencies npm install -g yarn yarn # serve with hot reload at localhost:8080 npm run dev # build for production with minification npm run build # run unit tests npm run unit
You can create file
/config/local.json (see example) to enable some convenience dev options:
target: makes local dev server redirect to some existing instance's BE instead of local BE, useful for testing things in near-production environment and searching for real-life use-cases.
staticConfigPreference: makes FE's
/static/config.jsontake preference of BE-served
/api/statusnet/config.json. Only works in dev mode.
FE Build process also leaves current commit hash in global variable
___pleromafe_commit_hash so that you can easily see which pleroma-fe commit instance is running, also helps pinpointing which commit was used when FE was bundled into BE.
Edit config.json for configuration.
loginMethod can be set to either
password (the default) or
token, which will use the full oauth redirection flow, which is useful for SSO situations.