4 ms·

There's currently no paid option. Obviously one should assume such a free service can't be sustainable so you'd be correct to think we should have one. Current

There's currently no paid option. Obviously one should assume such a free service can't be sustainable so you'd be correct to think we should have one. Currently we rely on Github sponsors as well as our own additional funding

justinclift 3y ago
With the server, is it primarily a gateway to the hosted SQLite databases? eg receives incoming shell history to store in the backend, and maybe do some searches/retrievals of shell history to pass back? eg for shell completion, etc If that's the case, then I'm wondering if it could work in with online data stores (eg https://api.dbhub.io https://api.dbhub.io <-- my project) that do remote SQLite storage, remote querying, etc.
- conradludgate 3y ago
  We currently use postgres. The server is very dumb, verifies user authentication and allows paging through the encrypted entries. There's a PoC that allows it to work with SQLite too for single user setups - and we are thinking of switching to a distributed object store for our public server since we don't need any relational behaviour.
  - justinclift 3y ago
    Interesting. Yeah, we use PostgreSQL as our main data store too. The SQLite databases are just objects that get stored / opened / updated / queried (etc) as their own individual things. :) One of our developer members mentioned they're learning Rust. I'll point them at your project and see if they want to have a go at trying to integrate stuff. At the very least, it might result in a Rust based library for our API getting created. :D
  - justinclift 3y ago
    > we are thinking of switching to a distributed object store for our public server As a data point, we're using Minio (https://github.com/minio/minio https://github.com/minio/minio) for the object store on our backend. It's been very reliable, though we're not at a point where we're pushing things very hard. :)

justinclift 3y ago

With the server, is it primarily a gateway to the hosted SQLite databases? eg receives incoming shell history to store in the backend, and maybe do some searches/retrievals of shell history to pass back? eg for shell completion, etc If that's the case, then I'm wondering if it could work in with online data stores (eg https://api.dbhub.io https://api.dbhub.io <-- my project) that do remote SQLite storage, remote querying, etc.

conradludgate 3y ago
We currently use postgres. The server is very dumb, verifies user authentication and allows paging through the encrypted entries. There's a PoC that allows it to work with SQLite too for single user setups - and we are thinking of switching to a distributed object store for our public server since we don't need any relational behaviour.
- justinclift 3y ago
  Interesting. Yeah, we use PostgreSQL as our main data store too. The SQLite databases are just objects that get stored / opened / updated / queried (etc) as their own individual things. :) One of our developer members mentioned they're learning Rust. I'll point them at your project and see if they want to have a go at trying to integrate stuff. At the very least, it might result in a Rust based library for our API getting created. :D
- justinclift 3y ago
  > we are thinking of switching to a distributed object store for our public server As a data point, we're using Minio (https://github.com/minio/minio https://github.com/minio/minio) for the object store on our backend. It's been very reliable, though we're not at a point where we're pushing things very hard. :)