The following instructions are only meant for development and testing environments, not for production! Although it will lead us somewhere with Packages and Appstore apps? Maybe, let’s see about that in 2016 □ Can’t be that hard, no?įor gods sake there’s homebrew and additional repositories allowing you to add your own development stack getting to work on your terminal. While I still could go for Docker or Vagrant, I just want to natively run my development stack on OSX even. There’s Xcode but nothing I would need to compile Icinga 2 or run a web application. Shiny little thing with plenty of stuff already pre-installed. Long story short – my new notebook at NETWAYS is now a Macbook Pro. Hey, there’s even MS Office which won’t screw up your Powerpoint presentations (Libreoffice does…) you share with other Icinga team members. At last years Icinga Camp in SFO it was pretty obvious – everyone uses Macbooks these days to get their stuff done. I want a stack to work with, not hacking wrong kernel modules or other broken stuff while trying to get my stuff fixed. Apart from that we, the developers at NETWAYS, do have our own Windows VM to develop and test Icinga 2 on Windows as well (check this blog post I wrote a while ago). My preferred platform to develop Icinga 2 was still Fedora including Vagrant boxes and Docker containers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |