Hi everyone! My name is Justin, and I am a software developer living in Australia. For my first weekly post, I want to give you a bit of background on who I am and what my goals are.

Beginnings

I've always had an interest in programming, but as a child, I found it overwhelming. Instead of pushing through, I gave up and tinkered with MS-DOS instead of trying to learn Pascal, C, or C++. My desire to program was set aside, and I focused on learning DOS and Windows thoroughly.

University Days

When it came time to choose a major, I was torn between IT and politics. I considered studying IT, but I was unsure about sitting in front of a PC all day. So, I opted for International Relations and History, which I loved. I even considered making it a career, but the life changes it required didn't align with my goals. After a brief stint working for a local bank, I entered the IT field. Despite avoiding it for so long, computing has always been something I’m naturally gifted at.

IT Operations

I once asked my first IT manager, who loved cars, why he didn’t work as a mechanic. He said it would make his hobby feel like work. That’s how I felt about IT operations. It's a thankless job where you mostly hear from people when things are broken. Despite transitioning to server admin, my enjoyment for it didn’t change.

During my time at a company with offices across the country, I was tasked with finding a video conferencing solution on a very small budget. In 2011, the options were limited, so I chose Microsoft Lync. Installing, configuring, and testing it made me realize that adding real value was more rewarding than fixing printers and reacting to problems.

A More Rewarding Career... For a Time

I eventually moved into SharePoint development and application support, working with various business units and adding value. However, it soon became apparent that this role was a dead end. Despite knowing the existing SharePoint deployment needed replacing, the company refused to allocate the necessary funds. After months of frustration, I left, which in hindsight, was a mistake. What followed was a series of positions and two redundancies.

Web Design

After the second redundancy, I turned my web design side hustle into my main job. While I don't love it or hate it, it feels superficial. Clients usually want to play it safe, resulting in websites that follow common themes. However, I still enjoy building something from nothing and adding value for my clients.

Back to Software Development

COVID hit my business hard, reducing my income significantly almost overnight. I needed something more secure with a higher ceiling. I decided to return to software development, revisiting the C# and ASP.NET skills I learned earlier in my career. However, I found that ASP.NET had evolved into ASP.NET Core, which felt like learning something completely new. The web had changed a lot between 2012 and 2022.

I bought a book on ASP.NET Core, highlighting how outdated my knowledge was. Even my HTML and CSS skills needed refreshing. While I’m pretty good with HTML, CSS has always been frustrating because I never properly learned it. I am proficient enough to get by, but that's about it.

The New Journey

Instead of pushing through with ASP.NET, I'm going back to basics and learning everything from the ground up. My goal is to become a full-stack developer, and for that, C# and ASP.NET alone are not enough. I need to fill the gaps in my knowledge.

I will continue with C# as the foundation but will also focus on JavaScript, a language I have resisted learning for years. JavaScript is crucial as it opens up many possibilities. Once I achieve a reasonable level of competence, I will explore frameworks like React and other relevant technologies.

I'll return to Microsoft technologies with TypeScript before diving fully into what .NET offers. My C# skills will improve, but I will also focus on becoming competent in other areas.

I have a list of books to help on this journey, but I might need more. While I can learn from books and self-teaching, I thrive in structured learning environments, which might lead me back to university.

Back to University?

There is a two-year Master's degree I could enrol in to enhance my skills and obtain a degree for future employers. However, I'm unsure if the time and money are worth it the opportunity cost.

The benefits include satisfying recruiters and filling gaps in my knowledge, such as data structures, security, and cryptography. While I could learn these independently, I would find it easier in a structured environment. The degree would also serve as valuable proof of my skills.

I'm still deciding what to do. I have a few months to decide, as the next intake for the course is in October.

Conclusion

That’s a bit about me and my plan. I will write regularly about my journey, challenges, and successes, and I hope you will follow along. Thank you for joining me on this adventure!

This happened again this week when I wanted to backup my Wiki.js config files. When you run the backup, you nominate a local folder. The challenge is then gaining access to those files. I spent an hour or two trawling Google search results trying to understand how I could access these files, but the results all too often assumed prior knowledge that I simply did not possess.

How do you find the right answer when you don't fully understand the question?

In the end, I managed to pick up enough pieces of information to come up with a solution that I will now share. This is mainly so I remember myself when I come to do this next time, but I hope that someone else in a similar position will stumble across it and hopefully spare themselves some pain. I am no pro at Docker or Linux having 'grown up' in the Windows world, so if anyone has any tips or suggestions that would make this easier, I am all ears!

What I did was use the docker cp command to copy the files from within the container into a directory I could then access via WinSCP. The base command is as follows.

docker cp <containerID>:/file/path/within/container/ /host/path/target/

Getting your container ID is easy if you use Portainer to manage your containers. Open the specific container and the ID is displayed at the top in the 'Container status' box. I assume any Docker management tool will prominently display the ID, but as I have never used anything other than the CLI and Portainer, I cannot say for sure.

If you use the CLI, getting the ID is also pretty easy. Use the below command, replacing containerName with the name of your container.

docker ps -aqf "name=<containerName>"

Now that you have the container ID, you can confirm that the files have been backed up by Wiki.js by going back into the container in Portainer and going into the console. For my install, backups are saved to '.data/backups', so browse into that directory to confirm that the files are present. Run the command pwd to get the full path, which you'll soon need.

You're now ready to copy the files from the Docker container to a location you can easily access. Going back to our base docker cp command, we have the container ID and the path to the files we wish to access. Now use mkdir to create a directory in your home directory to act as a save location. For me, I did cd ~ to make sure I was in my home directory and then mkdir wiki.js.

Now it is time to copy. Going back to the base command, input your container ID, Docker container backup save file path, and the location where you wish to copy the files.

docker cp <containerID>:/wiki/backups/ /home/user/wiki.js/

Make sure that the file copy worked as expected and then you're ready to use something like WinSCP or rsync to move the files wherever you want.