After a bunch of experimenting I figured out how to streamline the process of deploying OpenBD on Heroku.
If you would prefer to manage the OpenBD engine in revision control along with your code, you can use the fat buildpack. This will let you use whatever version of OpenBD you want, add/remove plugins and jars, etc. https://github.com/heathprovost/heroku-buildpack-openbd-fat Some developers might want to keep the engine out of revision control and only manage their actual source code. If that's you and you don't need to do a lot of customization then you will want to use the thin buildpack. https://github.com/heathprovost/heroku-buildpack-openbd-2.0.2-thin I have tested both of these options fairly well and so far it works like a charm. You don't have to mess with Maven or any complicated dependency management, and deployment is very quick with either buildpack. Slug size is small (around 50MB) and performance is pretty good. The only real requirement is that you must manage your code in git. Heath -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" 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/groups/opt_out.
