| .husky | ||
| app/javascript | ||
| bin | ||
| config | ||
| lib/assets | ||
| public | ||
| streaming | ||
| .browserslistrc | ||
| .buildpacks | ||
| .dockerignore | ||
| .env.test | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .foreman | ||
| .gitattributes | ||
| .gitignore | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc.js | ||
| .profile | ||
| .rspec | ||
| .slugignore | ||
| .yarnclean | ||
| app.json | ||
| AUTHORS.md | ||
| babel.config.js | ||
| CHANGELOG.md | ||
| Dockerfile | ||
| ide-helper.js | ||
| jest.config.js | ||
| jsconfig.json | ||
| LICENSE | ||
| nginx.conf | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| stylelint.config.js | ||
| tsconfig.json | ||
| yarn.lock | ||
Masto-FE (🦥 flavour)
This is a fork of Iceshrimp's Masto-FE Standalone repository, which is itself a fork of Mastodon Glitch Edition, which in turn forks Mastodon. Phew!
The goal of this repository is to make it possible to smoothly and intuitively use the Mastodon frontend with a GoToSocial instance as the backend.
This mostly means making changes to the frontend to allow it to work with GoToSocial-specific features, making it slightly less Mastodon-y by changing some of the branding, wording, iconography, etc, and fixing other small issues.
There's a version running here that you can try:
https://masto-fe.superseriousbusiness.org
The application doesn't gather or store any information that you give it, including access tokens or passwords, everything just happens in your browser's local storage.
Building
Not Docker (must have Node + Yarn installed)
You can build the whole thingy by running:
yarn && yarn build:production
Docker (don't need to have Node or Yarn installed)
You can build a docker container for the whole thingy by running (for example):
docker build -t superseriousbusiness/masto-fe-standalone:0.1.0 .
Deploying
Not Docker
Serve all the stuff in public behind an nginx or whatever you want! See the included nginx.conf for one example of how to do this, it's not too bad.
Docker (definitely the easiest way)
The Docker container is based on Nginx, and serves over port 3000. Just deploy it and listen on that port, preferably with a reverse proxy at some point (Traefik? Caddy? Another Nginx perhaps?) handling https.