Marcin Cieślak is a user on mastodon.social. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Installed backend, now contemplating the frontend, if any.

@saper

both the Pleroma FE and Mastodon FE are available (go to /web after creating an account for the Mastodon FE)

@kaniini I am just contemplating. I think patches to keep Mastodon FE ruby free should be upstreamed.

@saper

Mastodon FE is already ruby free. The patches that aren't upstreamed are the ones that remove the Mastodon branding, which we cannot re-use, as it would be misrepresenting the product and such.
@kaniini @saper No, that's actually incorrect. I'm sure running webpacker is actually useful if you run the entire Mastodon application, as it integrates smoothly hot reloading to RoR. But for us, since we only care about the frontend, I just changed package.json to remove json.

So this is why I don't think I can do an upstream patch for this.
Marcin Cieślak @saper

@howl @kaniini I don't need webpacker if I build resources once for production? Also a couple of JS dependencies go away this way (including my favourite -sass)

· Web · 0 · 0
@saper @kaniini That is actually correct. Might actually do so then one day

@howl @kaniini I proposed to build a separate port only to build webpack resources. This way folk who do not need to fiddle with scss will get way less run time dependencies (in case of JS, I think - none?)