I just uploaded a new version of efaLive. I spend a lot of time to port the efaLive tools from Python 2 to Python 3. The support for Python 2 will end soon. The images are based on Debian Buster now and the efa version is 2.2.2_42. The image for the Raspberry Pi now support the new Raspberry Pi 4. For more information check the efaLive page.
Some content got lost on the way though. There is no gallery any more, no contact form, no sophisticated download area, no comments, no search and no login. But that’s fine. The more useful stuff is still there and has the same structure as before.
I thought about generating static pages some years before already. But it took some time to come to a proper solution. I really like the concept of Jekyll and the lightweight content it generates.
No need for security updates any more …
Finally there is a new release of efaLive. Some refactoring has been performed in the efaLive-Setup tool. And of course a new version of efa and Debian is included. For more information check the efaLive page.
There is a new version of efaLive available for download! As usual, you can find bug fixes and an updated version of efa in the images. The main news is that efaLive is available for the popular RaspberryPi now. You can find a SD card image in the download section. For more information, check the efaLive page.
Many bigger development projects require a more or less complex development environment. In this case I do not talk about the IDE, compiler etc., but all components that are required to run the project that is under development. Let’s take a big web application that requires Apache, Tomcat and MySQL. All of these applications are customized in one way or the other. Each time a new developer needs to be ramped up for the project, just setting up the PC might take a day or even more.
To simplify this and keep away the complexity of the setup from developers, I started to experiment with VirtualBox virtual machines (VM). After a while I started to use more tools to make the setup and configuration of a development VM as flexible as possible. The current result is a setup that uses Packer, Docker, Vagrant and VirtualBox. All a new developer has to do when he/she starts to work on the project is to check out a Vagrant file, make a few configurations and run ‘vagrant up’. This only takes a few minutes and after that a full setup for the development is in place.
Below, I will explain the tool chain a bit.Read more
subscribe via RSS