Need help streamlining automation or configuration management?
Need to green field or “lift and shift” applications into the cloud?
If you are trying to do any of these, and running into issues please contact me. I am now open to consulting directly. Fixing even a few small inefficiencies can have a huge impact on the bottom line. Not only that, if the DevOps philosophies are really taken up, its likely that the employee base will also be happier, and proud of their accomplishments as a team.
As far as technologies I support, please take a look at my Technologies page. (Updated often) I am also happy to take on new ones for a project if needed.
Creating an efficient pipeline is what I do; and a fully functional system that is working well can be an amazing thing.
First, I would like to say thank you to the community members for helping out. I have gotten a lot of input on the new image. This has also given me better feel for what the community wanted in an image. Which leads me to the next bit of news.
Some of you are undoubtedly wondering why I have not released my Jasper v1.6 image as of yet. Well, I can assure you there are very good reasons.
Firstly, I have had some severe family/health issues come up as of late which take priority. I am also in the middle of moving a family of 5. Combine that with the other reasons below, and I feel that most will feel the wait to be worth it.
This leads me to the next bit of news, however shocking it may be.
There will be no version 1.6 image.
There will be no image at all…
Instead, there will be a full installer.
This is one of the reasons for the delay.
The installer will work with a full GUI, and on the desktop.
Full ubuntu Install.
Fresh RPI install with GUI.
The installer will be iterated on by feature going forward.
We can add community approved features one at a time.
A component of software configuration management (aka SCM), version control, also known as revision control or source control, is the management of changes to files and source. Changes are usually identified by a number or letter code, termed the “revision number”, “revision level”, or simply “revision”. For example, an initial set of files is “revision 1”. When the first change is made, the resulting set is “revision 2”, and so on. Each revision is associated with a timestamp and the person making the change. Revisions can be compared, restored, and with some types of files, merged.
Revision control can be very confusing to someone new, as you can see there are many ways to say the exact same thing. This can make it difficult to pick up the concepts. There are also many different kinds as you can see here. However, the major one I would hope everyone would be familiar with is GIT, and SVN for the older folks. JJ… 😛
Git, invented by Linus Torvalds as mentioned here is the most prolific and widely used one out currently. I also have a links under my Learning Resources page that are great for learning GIT. Please keep in mind that GIT, and GitHub or two differnt things. One is the software/method, and the other is a service that simply sells said software as a service.
Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time.It aims at building, testing, and releasing software faster and more frequently. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.
Continuous Integration is a software development practice where members of a team integrate their work frequently; usually they integrate at least daily – leading to multiple per day. Each integration is verified by an automated build/test to detect integration errors as quickly as possible. This usually leads to significantly reduced integration problems and allows a team to develop software more rapidly.
Everyone has seen these “Top 50 commands” blah blah blah….. #clickbait….
I am writing this just to make BASH a much more pleasant experience for people new and old to Linux. It is also for any sysadmin that has simply not been introduced to some of them.
I could list tons of them, but that’s going to get a simple TL;DR for most people. Then they will move on. So I will list a few and lets let those digest. Keep in mind all commands are in Linux, and may vary by distribution.
First BASH tips (Simple, but time savers):
Type ‘cd’ and you will go to your home directory for the user you are logged into.
Similar to “cd” ~, however ~ can sometimes rely on the environment.
To return to the previous directory you can type ” cd -“.
This will return you to your previous location, not home.
Type “tailf”, instead of “tail f” for the same results.
Also, “tail -200” can be used instead of “tail -n 200”
Use a custom “PS1” for root, and regular users.
A “PS1” is the text in the login prompt. See Example to the right:
Notice it is yellow
Do the same but in red for root.
Debian PS1 for a normal user (as seen to the right)
I have seen much FUD around this, and I wanted to clarify so people are aware what Google’s Intentions are for Hangouts. As I am a heavy user of the product, I was very surprised to see this. It appears that Google will still keep Hangouts around, but for the ‘normal’ user demographic only. They will be disabling their API on April 25. This however, should not be a complete surprise. Google has made it clear that with the arrival of their new products Allo and Duo that they are switching to an enterprise vision for many of their products. However, they will NOT BE REMOVING IT COMPLETELY, as mentioned in the linked engadget.com article.
What does this mean for you? The ‘End User’, if just using the services at face value may not even see a difference. However, services and sites that use the integration features will likely be affected. They (google) have allowed for an exception, and that is if they site/service qualifies as an “Enterprise Communication Tool”, slack for example. There won’t be many of those I expect.
Basically it comes down to this, they are ending the Hangouts API integration (publicly) on April 25th.
There are already several improvements to the image, and I have put out feelers for any fixes/updates/etc that I can do to make the user experience better. I already have a few of the obvious ones, however please feel free to report them in the new slack room “image-v1-6”, or in the Forums at the following LINK.
I am already working on it being pre-installed in the future with a REST api on it. Making it easy to integrate with anything!
I will be posting the release notes with the new updates with the new image, and here as a post. So please keep an eye out.
First, I want to thank everyone that has been patient with me so far in getting these things done one at a time…
I know it is not easy to get some of these things completed without good documentation. So, with the help of a few community members, I have started what is a very rough draft of our documentation. It is neither complete, or ready…. However, we are adding information as we go, so keep a close eye. Even feel free to clone it, and contribute. There will be documentation on how to do both of those coming as well. Feel free to watch here, the repository, or the Support Forums/Slack for updates. I update them all.
If you have items you would like to see added to the documentation, I would run it by myself, or d34dman first. If we have not already written it (there are some not committed yet); then we will just let you know to put in a PR (aka Pull Request). Once we have both reviewed it and give it a thumbs up. We will merge it.
Alright, all that said… Here is the link to the documentation!