New user - ? on 'console', 'attach', 'detach', 'q().'

[Bob Gustafson]

Hi

I have cloudi running on my Macbook. I disabled the tests at configure time - this seems to be helpful at this point.

In poking at the running cloudi, the 'console' command doesn't seem to work, because there is already a console user - 'net..'

To get into console mode, 'attach' seems to be useful. From there 'help().' is a gateway to other actions.

However, if I engage the console mode at one terminal by using 'attach., it doesn't seem possible to 'attach' from a different terminal.

Also, the console command 'q().' brings down the whole cloudi.

I don't seem to find a 'detach' command.

----

Just some inconsistencies.

A fun project though.

Bob G

[Michael Truog]

Normally, you would just use 'start' and 'stop' and utilize CloudI services that have entries within the CloudI configuration file.  However, you can use 'console' to start CloudI in console-mode which keeps the Erlang shell running (stopping CloudI when you exit the Erlang shell).  The 'console' usage might help for quick testing of Erlang code but is not used often.  The 'attach' usage is more common, to attach to a running CloudI node and utilize the Erlang shell on the node.  To detach after using 'attach' you use the Control-D key combination (shown in the output).

When you have the Erlang shell available, you can use the cloudi_service_api module for the CloudI Service API (http://cloudi.org/api.html#CloudI) and the cloudi module to send to CloudI services (the cloudi module has a subset of the CloudI API to allow sending to a CloudI service from any Erlang process).  If you need to know more about Erlang CloudI integration, there are a series of examples for different ways of using CloudI with Erlang source code at https://github.com/CloudI/CloudI/tree/develop/examples#readme .

However, it is possible to use CloudI without needing to use Erlang source code for your services due to the other supported programming languages.  The CloudI Service API doesn't need to be accessed through the cloudi_service_api Erlang module because it is exposed through the cloudi_service_api_requests CloudI service (which is often used through the cloudi_service_http_cowboy service).

Best Regards,
Michael

----

Just some inconsistencies.

A fun project though.

Bob G

--
You received this message because you are subscribed to the Google Groups "CloudI Questions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cloudi-questio...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.