Hi.
You can tell to BaasBox to start an ODB daemon in order to accept incoming connections from other clients (be aware that this can be a security issue).
Here are the parameters you can pass to the start command:
orient.listener.enable=false //enable/disable ODB process. Default false
orient.listener.ports="2424-2430" //ports on which the ODB has to listen. Default is 2424-2430 range (ODB default). It means that ODB will try to connect on the first free port between 2424 and 2430
orient.listener.address="127.0.0.1" //Default 127.0.0.1, it means that only connections from localhost will be accepted
For example:
./start -Dorient.listener.enable=true &
Then, in ODB 1.7.9 bin/ directory:
./console.sh
connect remote:localhost/baasbox admin <your_admin_pass>
Keep in mind that there are two private users that BaasBox uses to manage the database: "internal_admin", and "baasbox" that can be used by an attacker to try to access to the db, if you expose ODB to the internet, of course.
Also regular users, with their user/pass, can access directly to the db.
Finally, BaasBox uses its own schema and metadata, so be careful when manually change them, it could easily lead to data inconsistencies.