joshjohanning

#!/bin/bash
GITLAB_URL="https://example.gitlab.com/"
PROJECT_ID="2" # get this id via the repo/project's overview page
ACCESS_TOKEN="glpat-abc"

# Create a new merge request
curl --header "Private-Token: $ACCESS_TOKEN" \
  "$GITLAB_URL/api/v4/projects/$PROJECT_ID/merge_requests" \
  --data "source_branch=my-branch" \
  --data "target_branch=main" \

teito-dev

pyTelegramBotAPI

starter code

import telebot

# I just import the part down below seperately just for convinience
from telebot import types 

niklaskeerl

How to install pwndbg and gdb on arch linux

sudo pacman -S gdb
sudo pacman -S pwndbg
echo 'source /usr/share/pwndbg/gdbinit.py' >> ~/.gdbinit

If you are getting the following error "Cannot find Pwndbg virtualenv directory: /usr/share/pwndbg/.venv: please re-run setup.sh", do the following steps, otherwise ignore:

blackknight36

[Unit]
Description=Setup Systemd script for Artifactory in Tomcat Servlet Engine
After=network.target

[Service]
Type=forking
GuessMainPID=yes
Restart=always
RestartSec=5
PIDFile=/var/opt/jfrog/run/artifactory.pid

enricofoltran

package main

import (
	"context"
	"flag"
	"fmt"
	"log"
	"net/http"
	"os"
	"os/signal"

jeffjohnson9046

# This is something that I always forget and had a surprisingly hard time finding (or better yet, understanding).  Here's the
# scenario: a colleague creates a new kubernetes cluster, named" cluster-foo.example.com".  You want to look at it (for 
# troubleshooting, updating the deployment, whatever).  To get your kubectl installation to "see" the new cluster, take the 
# following steps:

# ASSUMPTION:  You have pointed kops to some location where the cluster configurations are stored 
# (I have this in my ~/.bash_profile):
export KOPS_STATE_STORE=s3://example-state-store

# Use kops to get the list of clusters

defHLT

# Solution found here: http://stackoverflow.com/questions/134882/undoing-a-git-rebase

# The easiest way would be to find the head commit of the branch as it was immediately before the rebase started in the reflog...
git reflog
# and to reset the current branch to it (with the usual caveats about being absolutely sure before reseting with the --hard option).

# Suppose the old commit was HEAD@{5} in the ref log
git reset --hard HEAD@{5}

vachanda

server {
  listen *:80;
  server_name www.icinga2.com;

  root /usr/share/icingaweb2/public; #Path of icinga2 web directory
  index index.php;
  access_log /var/log/nginx/access.log; 
  error_log /var/log/nginx/error.log;

  location = /favicon.ico {