Remove WebUI and just use bepasty as engine

[NotANormalNerd]

We could follow the same path as letusorder it.

Create and work on the server as an engine and move the ui to another project.
Like bepasty-client-cli, bepasty-client-android/io

-> bepasty-client-web

[ThomasWaldmann]

doesn't make sense (esp. for bigger files), you would need to handle them twice, which is quite expensive.

[NotANormalNerd]

Can you Plesse Fürther explain that? I dont understand why we need to handle files twice with a separate web ui.

[ThomasWaldmann]

maybe let's first think about how letusorderit is intended to work:
a) core part with models, controllers, only interface to outer world is a REST/JSON web api (no userinterface, no direct communication with user)
b) separate part that has a user interface that talks to the core part via REST api. web UI or IRC or OS specific clients. User deals with UI part, UI part's code talks to core part via REST.

So, with a strict separation, the UI part would need to accept the uploaded file and then feed it via REST calls to the core part, which is inefficient for everything else than small files. If you optimize that so the user directly talks to the core part for up/downloading files, it's not really separate any more...