Create an empty git repo or reinitialize an existing one
git init
Create an empty git repo or reinitialize an existing one
git init
Computational complexity is a field from computer science that analyzes algorithms based on the amount of resources required for running it. The amount of required resources varies based on the input size, so the complexity is generally expressed as a function of n, where n is the size of the input.
The space complexity is the amount of memory space required to solve a problem concerning the input size.
The time complexity is the computational complexity that describes the amount of time it takes to run an algorithm. Time complexity is commonly estimated by counting the number of elementary operations performed by the algorithm, supposing that each elementary operation takes a fixed amount of time to perform.
In this article, I share some shortcuts that I believe are useful to the broadest range of the sysadmin community. They are a vital part of my life and allow me to save time and focus better on what I enjoy doing. I also provide a quick tip at the end to help you master any Linux shortcuts.
Shortcuts are a key or combination of keys that provide quick access to a specific task or command. Almost everyone uses computer shortcuts in some form or fashion, but they are particularly critical for Linux sysadmins.
Note, most of these tricks assume you are using a Bash shell. They may be similar in other shells, but be aware there could be subtle differences.
Let's have a look at some basic and most useful commands:
Key | Description |
---|
This is a snippet that will create a new user in jenkins and if security has been disabled , it will enable it :)
import jenkins.model.*
import hudson.security.*
def instance = Jenkins.getInstance()
def hudsonRealm = new HudsonPrivateSecurityRealm(false)
hudsonRealm.createAccount("MyUSERNAME","MyPASSWORD")
instance.setSecurityRealm(hudsonRealm)
# Navigated to /etc/apt/sources.list.d/ | |
cd /etc/apt/sources.list.d/ | |
# Edited google.list by invoking | |
eg: sudo nano google.list | |
# Commented out the source with a '#' | |
# Save and run | |
sudo apt-get update |
variable regions_as_objects { | |
type = list(object({ | |
zone = string | |
region = string | |
})) | |
default = [ | |
{ | |
zone = "us-east1-c" | |
region = "us-east1" |
A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.
Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.