vertx start
vertx deploy
Usage: vertx [run|deploy|undeploy|start|stop] [main] [-options]
vertx run <main> [-options]
runs a verticle called <main> in its own instance of vert.x.
<main> can be a JavaScript script, a Ruby script, A Groovy script, or a
Java class.
valid options are:
-conf <config_file> Specifies configuration that should be provided
to the verticle. <config_file> should reference
a text file containing a valid JSON object
which represents the configuration.
-cp <path> specifies the path on which to search for <main>
and any referenced resources.
Defaults to '.' (current directory).
-instances <instances> specifies how many instances of the verticle will
be deployed. Defaults to 1
-worker if specified then the verticle is a worker
verticle.
-cluster if specified then the vert.x instance will form a
cluster with any other vert.x instances on the
network.
-cluster-port port to use for cluster communication.
Default is 25500.
-cluster-host host to bind to for cluster communication.
If this is not specified vert.x will attempt
to choose one from the available interfaces.
vertx version
displays the version
You can use vertx runI think this was discussed in another thread recently
在 2012年6月26日星期二UTC+8下午4时16分28秒,Tim Fox写道:You can use vertx run
I think this was discussed in another thread recently
So you mean that vertx start is deprecated, right ?
No wonder why I can not find docs for vertx start just now :)
OK, I'll read the new doc :)
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/vertx/-/hkKnz-J1rpgJ.
To post to this group, send an email to ve...@googlegroups.com.
To unsubscribe from this group, send email to vertx+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/vertx?hl=en-GB.
It's not deprecated, it's been removed.So you mean that vertx start is deprecated, right ?
The doc is actually old. The behaviour of vertx run hasn't changed, it's just that vertx start is redundant
On 26/06/2012 09:20, 赵普明 wrote:It's not deprecated, it's been removed.
在 2012年6月26日星期二UTC+8下午4时16分28秒,Tim Fox写道:You can use vertx run
I think this was discussed in another thread recently
So you mean that vertx start is deprecated, right ?
No wonder why I can not find docs for vertx start just now :)
OK, I'll read the new doc :)
The doc is actually old. The behaviour of vertx run hasn't changed, it's just that vertx start is redundant
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/vertx/-/hkKnz-J1rpgJ.
To post to this group, send an email to ve...@googlegroups.com.
To unsubscribe from this group, send email to vertx+unsubscribe@googlegroups.com.
It's not deprecated, it's been removed.
Is vertx deploy and vertx undeploy also removed?
yes
>
> If that is the case, how can I replace a verticle when they're running?
One solution would be to run your verticles clustered
> And it would be even better if vert.x can detect code change and
> redeploy automatically. just like what Play!framework does. I've seem
> it talked somewhere, but forgot the details.
Yes there is a github issue for this (well... if there isn't please add
one :) )
> vertx+unsubscribe@googlegroups.com.
Is there something planned to allow remote deployment of verticles now the deploy command has gone? Even though you couldnt do it from the command line client, the code let you specify a host as well as port for deploying.
To view this discussion on the web, visit https://groups.google.com/d/msg/vertx/-/97GpZeJ0k5sJ.
To post to this group, send an email to ve...@googlegroups.com.
To unsubscribe from this group, send email to vertx+un...@googlegroups.com.