patchwork compat

[christianbundy]

What's the problem you want solved?

Issues like #432 / #535 make me wonder if we should even be connecting to Patchwork.

Is there a solution you'd like to recommend?

Maybe Oasis should be an independent app that doesn't aim for compat with other SSB servers (Patchwork, SSB-Server, etc). Maybe Oasis should just be its own SSB-Server + UI + SSB-CLI instead?

[inoas]

Gave oasis a tiny go:

npm -g install fraction/oasis#semver

EDIT: I did run globally installed oasis via

oasis

... it showed some output on the terminal and opened the host with the port.

EDIT END

Patchwork was installed but did not run.

Result:

1. opens localhost:3000 in browser, shows nginx 404 default error page
2. npm spinning to 300% cpu, fans starting up
3. I quit it and restarted Patchwork, it started to index database again

oasis #patchwork

... would have preferred if it imported my credentials from .ssb but used its own subfolder for database/indexing, ... and showed so that it indexes on the browser instead of a 404 (if the fans wouldn't have started up, I'd have had no idea that it actually ran, but thought it was defect/buggy)

[christianbundy]

Did you run Oasis, or just install it? You should've had to do npm -g install fraction/oasis#semver and then later run oasis.

Since Oasis doesn't use Nginx, my guess is that you have some other Nginx server running on port 3000 and Oasis was never started.

[christianbundy]

Also, if you think this is a bug would you mind creating a new issue? This issue is specifically for whether Oasis should try to use Patchwork as a server.

[christianbundy]

(Assuming you Nginx running on port 3000, Oasis should've output this error. Maybe try oasis --port 4000?)

[inoas]

My fault for the port. I am running docker and multiple webservers and projects on different ports from 3000 to 9000