Book Image

The Software Developer's Guide to Linux

By : David Cohen, Christian Sturm
5 (2)
Book Image

The Software Developer's Guide to Linux

5 (2)
By: David Cohen, Christian Sturm

Overview of this book

Developers are always looking to raise their game to the next level, yet most are completely lost when it comes to the Linux command line. This book is the bridge that will take you to the next level in your software development career. Most of the skills in the book can be immediately put to work to make you a more efficient developer. It’s written specifically for software engineers, not Linux system administrators, so each chapter will equip you with just enough theory to understand what you’re doing before diving into practical commands that you can use in your day-to-day work as a software developer. As you work through the book, you’ll quickly absorb the basics of how Linux works while you get comfortable moving around the command line. Once you’ve got the core skills, you’ll see how to apply them in different contexts that you’ll come across as a software developer: building and working with Docker images, automating boring build tasks with shell scripts, and troubleshooting issues in production environments. By the end of the book, you’ll be able to use Linux and the command line comfortably and apply your newfound skills in your day-to-day work to save time, troubleshoot issues, and be the command-line wizard that your team turns to.
Table of Contents (20 chapters)
18
Other Books You May Enjoy
19
Index

Terms you might come across

It can be very helpful to get a basic understanding of Git’s vocabulary. Although it can be confusing when other software mixes these terms up, knowing what they mean in the Git world allows you to work a lot more confidently, for example, when troubleshooting and reading error messages.

Here is an overview of the most common terms and what they mean.

Repository

This is essentially a “project,” the root directory of the code that is being managed and tracked by version control – the one containing the .git directory. A repository holds your source code and its history and changes.

Bare repository

This has a similar meaning, only that the code is not checked out. It matches what the .git directory contains. On servers hosting the repositories, such as GitHub, GitLab, sourcehut, or your company’s Gogs or Gitea instances, these are usually in a directory named project-name.git containing only what you...