Now that I had the pipeline ready, it was time to decide what to test it with. This was pretty easy to settle on, I already had an idea of what i wanted to make prior to creating the pipeline and that was a Discord bot. I will go in detail later about the bot itself but, I had the ground work and I was ready to test. First, I opened up my VS Code and authenticated into my Github for easy cloning and pushing. ...
Now that I had Portainer up and my runner primed, I was ready to get started with what container repository I wanted to use. There are several out there and admittedly, I feel like I should have gone with Harbor but, I ended up using Docker Hub. The main reason for this was because I had an account already and used it in my Gitlab pipeline creation (might re-visit this journey later). All I had to do is login and create my public repository. Not bad at all. ...
So in my previous post, I talked a bit about Tailscale and the more I thought about it, the more I wanted to make a post talking more in-depth on what it is. Now, I’m not a networking guy by any stretch of the imagination but, I do love computers and making them talk and that’s where Tailscale has made my life way easier. Essentially, Tailscale is a free service that allows you to connect devices as if they were on a LAN together. I’m making it a lot less complicated and there are so many moving pieces but, that’s the gist of it. ...
As I mentioned before in an earlier part, there was a specific tool that was on my self-hosted runner that plays an important role in this next few steps. That being Tailscale. I’m not going to go into great detail about what Tailscale is but, just know, it allows me to talk to all my devices inside my Tailnet without exposing anything externally. Very nifty to have and makes connecting/hosting things really easy. ...
This is a continuation of the last part in the Pipelines Series. Now that I had my self-hosted runner ready to go and assigned to take workflows, I was ready to start with making my first pipeline. Github is really good about providing necessary steps and files that are needed for certain task and this is no different. After i went into actions, I was able to pick a .yaml template. I went ahead with the basic Simple Workflow yaml. ...
As discussed in my first post, I initially wanted to lay out a plan for a pipeline in Github that would automagically push changes to a development environment as I coded. The first problem with this is: developers (myself included) are trigger happy. They love to push changes because I mean why not. The second problem I had was that I wanted the app to run continuously. Keeping these two things in mind, I hopped over to Github and started learning about pipelines. Now I have messed a bit with Gitlab pipelines so I had a general idea of what to expect. ...