I needed a local mercurial hosting option. The following is what I came up with. Hopefully, you will find it useful or the post at least gives you some ideas. My requirements were basic. Web browsable repositories Minimal and maintenance-free Support for pushing new changesets Accessible through a URL to easily pull dependencies Needed access from a single computer (which let me omit authentication) I didn’t need bug tracking, code review, or anything fancy.
Starting with microservice design, it’s easy to follow your old habits of designing each microservice as if it was a normal application. One aspect of this, that I fell into when first moving to microservice applications, was adding authentication to my microservices that were only accessible from internal systems. The level in which you secure your microservices is dependent on your infrastructure, who will be using the microservices, and the availability of the microservice.
With Docker, it’s easy to end up with images many times larger than they need to be. Even if you remove unnecessary files and packages, you’ll still see your image size be much larger than expected. The size of the image may not seem too important to some, but there are many benefits to having smaller docker images. A smaller image will allow you to upload and download the images faster.
Even with a markup language as simple as Markdown, it is nice to have an editor that complements the language. I use Markdown frequently to write posts on my websites along with writing documentation when developing software. I’ve used many of these following editors and I am sure we will have a different opinion on which one is the best. I’ve also tried many other editors that I couldn’t care enough about to even mention here.
This post is going to cover how to take a USB device and write software that can interact with the device without having publicly available documentation. I came about writing this post when I found an old AverMedia RECental USB button in a box of electronics. I wanted to repurpose the button and this is the result of that process. The device used while writing this tutorial was a very simple in that it only sent two different interrupts (pressed / released) along with a method to create LED animations.