It took a little longer than I would have liked, but there was a lot of changes that needed to be made to get the posts to work from Jekyll. Most of it revolved around how Hexo handles images. I also had to clean up a lot of the tags and the categories on posts since they did not line up with what I wanted. Lastly I removed some old posts, and removed some links to things that don’t work anymore, mainly my X (The Old Twitter) account.
Jekyll is an awesome static site generator, don’t get me wrong. I loved using it, and over the years I have changed my site, and started from scratch more times that I can count. I moved to Jekyll after I gave up on Wordpress and the bloat that comes with it. I needed a simple solution on how I could type away and have a website that stays updated without the need for a complicated backend. It was also a plus that Jekyll could run on Github Pages, so it would cost me a whooping $0 a month. I needed a change, so I started looking into something else. I played around with Hugo for a bit, I thought about just making a simple website myself, and I Googled down the rabbit hole more than I care to admit.
I recently upgraded the Ender 3 Pro printer I have with a Creality Sprite Extruder Pro. I had to make a lot of changes to the firmware and compile it myself to get it all working correctly, so I thought I would share it with the world since not a lot of people had everything I needed in one place.
You can find the repo with the firmware Here
Please note this is a custom Marlin firewamre (Bugfix 2.1.x) that I made for my printer with parts listed below.
I have also included a precompiled version of the firmware based on Marlin Bugfix 2.1.X. Your milage may vary, install at your own risk. If you choose to use this firmware I am not responsible for anything that happens.
I had to make edit to the pins_BTT_SKR_MINI_E3_V3_0.h file in order to get the fans and BLTouch probe working as intended. I will outline all my changes below
It has been a while since I posted anything, or worked on anything at all. My real job and family life took over a large chunk of my time so I was unable to sit down and really concentrate on working on something. I had also been working with the GodotNuts on the firebase plugin. It is super cool and I highly suggest everyone checks it out. This Plugin allows you to connect a Godot game to Google Firebase using the REST APIs without the need to recompile the Godot Engine.
Last year I posted an article about making a godot server in docker, and while I was happy with it, I was not convinced that it was really done. I knew I could do more, but I just didn’t have the time or the skills to work on it. Cut to now, and I am working with an awesome team that is helping to implement Firestore natively into Godot (More on that later). You can check out all the awesome work for that here
I started to look back on the docker container I made, and I noticed a bunch of problems with it. The first being you needed to add CentOS to make the container to work. The idea is to keep these things small, and adding CentOS didn’t really play nice with that ideal. I also wanted to make it so you pointed the container at your game, and it would just export it for you and run it. How cool would that be right?
I don’t think it will come as a surprise to anyone. I am glad 2020 is almost over. This has been a year and a half, and I for one am looking forward to never recalling it. There will be no fond memories of it, there will be no talks of the good times. This year sucked, and no one can convince me otherwise.
Anthem was released to the world in January of 2019, where it was not met with the warmest of receptions. To most this was an overhyped game that failed to deliver on a lot of the promises, and fell short on a technical level. Bugs plauged the game to start, and with repeative missions and for lack of a better term, annoying gameplay, people quickly turned away from this title.
There is no good way to sugarcoat this one. 2020 sucked, and it sucked hard. The only silver lining I can see, is 2020 gave me the time I needed to work on my code. For a long time I used to program in a IDE called Atom It’s a great IDE and it fits the needs I had, but some people had been telling me to give VSCode a shot.
I installed it and liked it. I really fell in love with it after I started to get some extensions going that helped me in my daily grind. So without wasting more of your time, here are the top extensions I have been using in 2020. Also side note I am doing all of this in Windows 10.
Docker has been a life saver for me on my personal server at home, I can’t stress that point enough. Before I found and started to use Docker, I would install all the apps and things I wanted to test locally. It was a mess, and I would need to wipe the server a lot when things would really break. If I had two services that need apache or something else, I couldn’t always use it as my knowledge was limited.
I knew Docker was a thing, but I never really looked into it until I was so frustrated with how many times I destroyed my server, I finally decided to jump in. Let me tell you, the difference in my day to day for testing is crazy. I can easily spin up containers and tear them down when I need. I even wrote a post about it.
The first thing you will want to do if you tried this before is remove any old versions of docker. This will give you a clean system to work on.
Like most jobs today, mine requires me to automate as much of it as possible. One of the things that seemed like an easy goal was to auto the creation of a GCP Project using a tool. We used to use Google Deployment Manager, but soon found it was more of a pain than we wanted to keep up to date.
When creating this I laid out the files in easy to use sections. I also made sure to use the depends_on line a lot so I could ensue that everything was working in the order I wanted
Below I will break down each file and what iot is used for as well as the code inside of it
In this file I look for a few variables that help me create the project including the name, what folder it should live in, and a simple label to be applied to it. I also setup google as the provider since I will be using GCP. To make life easy I setup a service account ahead of time that has the ability to create projects and modify IAM throughout my environment. I then took the JSON key from it and I insert the path so the script knows what to use.