What's the point of this self-hosted project?

[felixsanz]

First of all thanks for releasing it open source, but what's the point in doing it this way? The repos don't even have a README.

Example: https://hub.docker.com/r/standardnotes/web

There is no documentation and everything seems just so complicated so that people give up and pay the official version.

[eric-pierce]

Documentation is found on the standardnotes site: https://docs.standardnotes.com/self-hosting/getting-started/

[felixsanz]

Documentation is found on the standardnotes site: https://docs.standardnotes.com/self-hosting/getting-started/

Yes, and you scroll down to the Web application and the only link redirects you to https://github.com/standardnotes/app/tree/main/packages/web

which is just a repo with a bunch of files, no readme and no instructions

[eric-pierce]

@felixsanz The web-app and sync server are separate projects - https://github.com/standardnotes/app is the web app, and includes some docker instructions and a sample .env file. Agreed that documentation could be better, but at least the information needed to get something live is there. Here's how I have set up the web-app with docker-compose in case it's helpful: https://github.com/eric-pierce/Personal-Cloud/blob/main/docker-compose.yml#L834

[felixsanz]

@felixsanz The web-app and sync server are separate projects - https://github.com/standardnotes/app is the web app, and includes some docker instructions and a sample .env file. Agreed that documentation could be better, but at least the information needed to get something live is there. Here's how I have set up the web-app with docker-compose in case it's helpful: https://github.com/eric-pierce/Personal-Cloud/blob/main/docker-compose.yml#L834

Thanks for your personal docker-compose.yml, that's helpful! But that also proves that official docs are (hard? inexistent?).

So to able to run standard notes completely self-hosted I do need the web app, the sync server, the many workers stuff, the auth stuff, etc etc, right? Or it's only the web app and i'm doing it wrong?

[eric-pierce]

@felixsanz you can self-host the web app, the syncing server, or both. The web app is just one container, and is really just the interface you'd work with in a browser that talks to whatever backend you point it at.

Here are a few possible ways of working with StandardNotes:

• If you only use the mobile apps and never the web-interface, you could just host the syncing server and not bother with the web interface.
• You can use Standardnotes' hosted instance of the web-app and point it to your syncing server backend
• You can also just host the web-app and point it to your server backend (this is what I do)

The backend syncing server is definitely more complex than the web app, and it has increasingly been more focused on enterprise level installs with a lot of users vs single user installs as mine is. I'm hopeful that a third party like linuxserver.io will take up re-packaging a single docker container backend (excluding the database). There are a few threads on their discourse about that:
https://discourse.linuxserver.io/t/request-standards-new-sync-service/3109/
https://discourse.linuxserver.io/t/request-standardnotes-web-sync/1955/

[BobWs]

I'm hopeful that a third party like linuxserver.io will take up re-packaging a single docker container

Take a look at this standardfile
I’m testing it and I must say it works well with the standardnotes clients. The only thing that is not working at the moment is file, but I’m hopeful that it will resolve soon.