On Sun, Feb 18, 2018 at 5:47 PM, Waldek Kozaczuk <[email protected]> wrote:
> If I may also add my 2 cents. I think it might be also worth to think > about priorities meaning which apps we care and which not so much. And the > make sure that at least the most important ones have fixed build process, > are well documented (README) and tested. > > Here would be my high level breakdown of the apps with first category > being most important: > > 1. Runtimes - Java (openjdk* apps), NodeJS, Erlang, Python, Ruby, Free > Pascal, etc > > And Go, hopefully :-) > > 1. Stateless apps - redis, memchached, twemproxy, etc (other apps that > could be ZFS-less) - things that do not require writing to a file system > (ROFS) > 2. Everything else - even though one can run MySQL or ElasticSearch on > OSv - I do not think many people will do it for real > > Lastly it would be nice to provide a Docker-based build process for some > of these apps. I am not big fan of Docker as a runtime platform (because I > am fan of OSv) I think that Docker is an excellent platform to provide > consistent/repeatable process to build OSv apps. Look here for examples - > https://cloudrouter.org/cloudrouter/2015/04/27/build-osv-images.html and > https://github.com/mikelangelo-project/capstan-packages/ > > Finally (even though I used lastly above ;-)) please bear in mind that > many OSv users may not care about Java app makefiles as in JVM-land they > would use tools like Maven, Gradle or to build. > I'm not sure what you mean here... You can have a tiny Makefile which just calls an external build script. We actually do this in many of the packages, where "make module" just calls an external script "GET". This script (or the makefile Directly) can use maven/gradle/whatever, if it wants. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
