Just use whatever Linux deployment environment your tool is built on. We can do it with something I’ve already contributed a decent amount of time to dockerizing the GUI and adding some helper scripts to launch things. Let’s go ahead and do it with a simple application. Oracle Java vs OpenJDK or Eclipse development environments.ĭocker.io auto-builds of a pseudo-vm to distribute your application.Ĭheck references for further reading on that part. Use some library that clashes with everything in the universe and is a pain in the butt to install. Rapid deployment of a given tool-set with no pain to the end user.Ĭompile these 30 dependencies, install these unsigned packages, and/or run it all in a VM or chroot. SSH in and grab the single application it is designed to run with xvfb or some desktop parts.ĭistribute a given tool with frozen dependencies that doesn’t affect the base OS.Ī tool that was written for and not updated to newer libraries, as those libraries are deprecated, and the OS reaches EOL. “That LXC stuff is scary and hard to read.” – source unnamed.ĭeploy a Linux application to OS X without as many abstraction layers.ĭeploy an application to AWS or some other cloud provider.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |