[
https://issues.apache.org/jira/browse/S4-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183952#comment-13183952
]
Matthieu Morel commented on S4-38:
----------------------------------
Nice, plenty of good things there!
That will surely facilitate development of S4 applications.
And my understanding is that more advanced admin facilities would be a separate
set of scripts, right?
So a typical scenario would be:
# create an application:
{code}s4 new <app-dir>{code}
This creates a project skeleton in the specified directory, along with a gradle
build script for that project.
# optionally prepare for editing in an IDE:
{code}s4 eclipsify|idealize <app-dir> {code}
# the developer adds application code in this project (and possibly adds
dependencies in the gradle script if needed)
# build and package
{code} s4 s4r <app-dir> {code}
This creates an S4R archive
# start a cluster
{code} s4 start {code}
(we might add parameters such as the number of nodes).
This starts S4 nodes locally, a Zookeeper instance, and create a logical
cluster with the running S4 nodes (for instance by default a 2 nodes cluster)
# deploy to the cluster
{code} s4 deploy <path-to-s4r> {code} or {code} s4 deploy <app-dir> {code}
This deploys the application to the running local S4 cluster
> S4 command line utility
> -----------------------
>
> Key: S4-38
> URL: https://issues.apache.org/jira/browse/S4-38
> Project: Apache S4
> Issue Type: New Feature
> Affects Versions: 0.5
> Reporter: Leo Neumeyer
>
> I'd like to propose that we provide a command line utility similar to play in
> Play! Framework. The idea is to implement various common function using a
> single utility program. Examples:
> {code}
> > s4 build // builds an app
> > s4 load // loads an app to the cluster.
> > s4 unload // stops and unloads an app from the cluster
> > s4 stats // provide stats about a running cluster
> {code}
> We can start by modifying the Play script which is under Apache license.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
