Closed srebling closed 1 year ago
I doubt AceBase supports having /
in the database name when using the server or client.
If you are trying to have the server store the database in a specific path, there is a configuration option path
for that (might be missing from the documentation).
I added a path: "../../"
property to the server settings and removed it from the dbnames. It is working now. Thanks for pointing that out. The main acebase engine docs do mention the path
property, I overlooked it while trying out the server/client packages.
Getting this message when trying a simple client connection. 'Could not get server info, update your acebase server version' I am using the latest version. Also receive a 'not found' error when issuing a db.ref().get() on a paths that I know exist. No authentication or signin needed for this use case. This is all on the same localhost (OSX 10.15.7, node v16.14.2). The database was generated with a node.js app using just the acebase engine, which works very well and as expected for reading and writing to the database. The code below is running in two separate terminal instances. What am I missing? Thanks.
Server code:
Client code:
package.json: