I was very happy to have been interviewed on CoderRadio! We had a great discussion on how PiCluster started and programming in general. I like that I was able to talk about my life’s work in open source. We discussed how I started my first project MephistoBackup and how hard it is to get community involvement in an open source project. This blog was also featured and I explained what linux-toys.com is all about. Finally, I was able to talk about my other main Project Cloud Explorer and the exciting features that it has.
I embedded the interview in this post so you can watch it easily here or on YouTube.
Thank you JupiterBroadcasting for having me on CoderRadio. I was always a big fan of the network. Their wonderful content helped me get back into Linux in their early days with the Linux Action Show. Their shows are very inspirational and I hope that you will also learn a lot about the Linux ecosystem and become a fan.
PiCluster is a great platform to manage and orchestrate Docker containers. Although it started as a way to manage my Raspberry Pi’s, it can be run on any operating system that supports Node.js and Docker. PiCluster has been under heavy development lately and I like to share what is new in v1.9.
Web applications typically feed information back and forth from a database to process information for the user. Organizations need to build applications that can scale with their business. While it is easy to scale web applications with containers and cloud platforms, the last thing that an IT administrator would want is a bottleneck at the database because it would affect application performance and availability at scale. One way to address these concerns is by using a clustered database solution such as ScyllaDB. This blog post will demonstrate how to use Node.js and ScyllaDB running in Docker.
In my previous blog posts, I always talked about my setup but never showed a completed diagram. In the above image, you can see everything that I am running on my 6 node Raspberry Pi cluster. All of the applications above are running in Docker containers managed by PiCluster except for Gluster.
I am pleased to announce PiCluster v1.7. In this release, I wanted to make PiCluster easier to use by having the Web Console handle most of the common configuration file changes. Not everyone enjoys editing json files including myself. Now let’s go over what is new in this release.
I did some updating to Cloud Explorer recently to make it work with Minio. Minio is one of many open source S3 servers available today for people to use on-premises for their personal cloud storage needs. With the added support, Minio users can take advantage of Cloud Explorer’s unique features such as performance testing, note taking, playing music, viewing images, and search.
Cloud Explorer is a open-source Amazon S3 client that works on any operating system. The program features a graphical or command line interface. Today I just released version 7.2 and hope that you give it a test drive. Feedback and uses cases are always encouraged.
What’s new in this release?
To start, this release of Cloud Explorer was compiled with Java 1.8.0_72 and version 1.10.56 of the Amazon S3 Java Development Kit ( JDK). The major improvements in this release regard file synchronization. Basically, it was mostly rewritten. By putting forth the effort, it helped reduce technical debt and consistency between the command line and graphical version of Cloud Explorer.
How do I get it?
Cloud Explorer v7.2 is available under the “Downloads” section of the Release page on GitHub. Simply click on “cloudExplorer-7.2.zip” and the download will begin. When the download is finished, extract the zip file and double click on “CloudExplorer.jar”.
Where do we go from here?
I know it has been a while since Cloud Explorer has been touched. It is hard to handle a project all by yourself and keep innovating. I feel that with this release, Cloud Explorer reached a stable point. I am always looking for new ideas and help from the community. If you are interested in contributing, please contact me or open an issue on the GitHub page.
I have been a hardcore CentOS user for many years now. I enjoyed its minimal install to create a light environment, intuitive installation process, and it’s package manager. Docker is the most popular container format today and provides developers and enthusiasts with an easy way to run workloads in containerized environments. I started using Docker in production at home for about a year now for services such as Plex Media Server, Web Server for this blog, ZNC, MineCraft, and MySQL to name a few. A Dockerfile is a set of instructions used to create a Docker image. I invested many hours creating perfect Dockerfiles using CentOS and Fedora to make deployments simple on any operating system. However, a personal revolution was brewing.
I have been working hard on new features and GUI enhancements for Cloud Explorer 6.0. I think it is important for an application to improve over time and this project has seen it’s share of visual evolutions. If you look back at the 1.0 release, the changes are night and day. I enjoy the challenge of making this program look pretty for each major release and hope that the users find it to be good. This release uses many free-licenses images and GPL images found in the KDE Desktop Environment.
Getting Cloud Explorer
Cloud Explorer is available for download from here.
Upgrading to 6.0
Starting with Cloud Explorer 5.0 or later, you can upgrade by clicking on Help -> Check for updates. After the update is complete, restart Cloud Explorer.
1. Fixed a bug when switching accounts.
2. If no region is specified, it will default to “defaultAWS” to
avoid a null pointer exception. To resolve the issue, delete and
add your account back.
3. If no image is selected when the image button is pressed, nothing
4. If no music is selected when the play button is pressed, nothing
5. Support for line spaces in s3.config
6. Versioning display fix.
1. Snapshots and Migration are now located under the new menu
“Snapshots and Migration”.
2. New Icons for GUI.
3. Maximize Window.
4. For improved GUI responsiveness, many actions now avoid
1. Create Bucket snapshots.
2. Restore Bucket snapshots.