Open andriusj opened 10 years ago
So, we're still tweaking the sbt-server bits, but pretty soon this will be a lot easier. @skyluc is consuming this on the IDE side right now, so he might have a pointer to some code you can actually use.
Sorry for the long delay in response :)
Alright, the integration tests are starting to be filled out. Those are you best bet at usage examples for now. e.g. see:
We should be rapidly stabilizing over the next few weeks. So by the first milestone release, I think you'll have the docs you need.
I've been using FileProvidedSbtProcessLauncher previously to run sbt for play apps remotely, but it seems that this approach is obsolete now. What would be the proper way to use the new server/client API?
I have a java based play app (a kind of cms) which is used to create other apps (somewhat similar to Activator, except that it integrates with mercurial repos, allows branching, etc), which multiple users can use to access, modify, preview, and deploy the builds to remote servers. It pretty much work(-ed), except that the remote sbt management was far from clean (you'd need to start an sbt instance, then if the preview was being ~run, it'd have to be terminated before the app can be packaged before deployment, etc). If you could point me in the right direction on how to implement this with the new remote sbt API, I would be glad to update the wiki in return.
Essentially, I would like to be able to preview (~run) and package (dist) a play application on a local filesystem through a remotely controlled sbt. If it's easy to do it from java, would be best, but I'm cool with scala too.
Any pointers would be much appreciated.