Hello Vito,
-
I am suprised that the q2 commands are not working. Since you have attached the container I would have expected in that window that opening terminal and running "q2 -h" would have resulted in showing a list of available q2 commands. If this is still the case, make a comment here and I will reach out to you directly and we can setup a call and figure out why what is happening is happening.
-
The URL for "Total Access" will be the same as in the welcome email as well as on q2developer.com after signing in on your dashboard. The environment is not hosted locally. The only thing hosted locally is the SDK extension. All the traffic is going through the container to our servers and then posted to Total Access. This is also how it works in the data center so that the environment will stay up even if there are issues with the SDK extension.
-
As the same with 2. There is no local database. The database is on a server which is also closer to what would be in the Data Center. To access the db, it may be easiest to use the Shared Dev server and connect to the database there via the Shared Dev setup documentation. You can connect to the db locally to run sql scripts and such, however it is a bit of work.
Some additional information. Local development is still going to only running the SDK webserver locally. This is not running the entire environment or database, rather just connecting to those two via a websocket and Caliper Api respectively.
Thank you,
Trey Teter