> --
> You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
> To post to this group, send email to simple-b...@googlegroups.com.
> To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
>
In a very similar vein, one can use sbt-launcher as a deployment system.We've been using the sbt-launcher for application deployment for a long time and it has worked out really well.
--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/4_JYgFa3ByIJ.
--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/4_JYgFa3ByIJ.
--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/4_JYgFa3ByIJ.
> Sigh .. to plant one more seed ...
Although I vaguely knew what you were up to, it is always interesting to hear the details. Thanks!
-Mark
Sigh .. to plant one more seed ... one more cool thing that people may not know is that both Service Wrapper and sbt-launcher can do a self bootstrap. i.e. They can download new versions of themselves and then reboot into their new versions. Which means you can do this at the app level. This was a cool and and key feature we leveraged. Self bootstrapping turtles all the way down....So roughly, all app nodes open an HTTP admin port.NaivelyPUT - curl http://myapp.com/admin/deploy/version/1.2.3POST - curl htpp://myapp.com/admin/restart
- App cluster updates the sbt-launch version config with the first PUT after a cluster paxos consensus agreement. You can PUT the new version to any node, if and only if the version was consensus agreed to by the cluster as a whole does a node "learn" the new version to record in the config file.
- The second POST causes the app to do a shutdown and then uses sbt's "reboot" api call to reboot itself and come up on the new version.