New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Splitting frontend/backend?? #652

Closed
wants to merge 2 commits into
base: master
from

Conversation

Projects
None yet
5 participants
@marrus-sh
Contributor

marrus-sh commented Feb 25, 2017

Yea so this has been my working setup for about a week or so now and figured I'd submit a PR incase this is functionality desired upstream. Adds two environment variables (SKIN and FRONTEND) and packages the default masto skin/frontend into /app/assets/skins/rooty/ and /app/assets/frontends/tooty/ (feel free to change). See the file I added to docs for more info! The only tricky bit was splitting up the CSS files but I think I did alright.

@yiskah

This comment has been minimized.

Collaborator

yiskah commented Feb 28, 2017

Into This Idea

@ProgVal

This comment has been minimized.

Contributor

ProgVal commented Apr 3, 2017

merge conflict :/

@Gargron

This comment has been minimized.

Member

Gargron commented Apr 25, 2017

I'm sorry it took so long to actually come out with a response (a lot of stuff got in the way and this wasn't exactly high prio). Basically, I do not intend to bundle any alternative frontends in the main repo. My position on the web UI is that while it is using the API like an app, it is a default UI, and every software comes with one. Usually they're static, this one's React. Its using the API exclusively just to make sure it has no advantages over 3rd party apps.

The alternative frontends don't actually need to live on the server. Like TweetDeck for Twitter, you can just make a webapp that works with any instance you throw at it.

There is another argument against it, and it's the high rate of churn during development. We're changing a lot of stuff, and having to support multiple variations would add a lot of wasteful overhead.

Sorry, and thank you for your effort. I imagine you will keep this in a fork of yours.

@Gargron Gargron closed this Apr 25, 2017

abcang added a commit to ykzts/mastodon that referenced this pull request Sep 13, 2017

Merge pull request tootsuite#652 from pixiv/fix-unsubscribe-service
Fix errors preventing UnsubscribeService from working (tootsuite#4866)

abcang added a commit to pixiv/mastodon that referenced this pull request Nov 15, 2017

yipdw pushed a commit to yipdw/mastodon that referenced this pull request Aug 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment