cpursley

PostgreSQL is Enough

• Simplify: move code into database functions
• Just Use Postgres for Everything
• Just use Postgres
• PostgreSQL is the worlds’ best database
• Postgres is eating the database world
• Hacker News discussion

Background and Cron Jobs

RajChowdhury240

Extract [Decompile]

*Jadx - decompiler gui
jadx-gui

* Jadx - decomp cli (with deobf)
jadx -d path/to/extract/ --deobf app_name.apk

* Apkx decompiler
apkx example.apk 

jeremyben

# https://www.freedesktop.org/software/systemd/man/systemd.unit.html
[Unit]
Description=My App
After=network.target

# https://www.freedesktop.org/software/systemd/man/systemd.exec.html
[Service]
Type=simple
# https://www.freedesktop.org/software/systemd/man/systemd.exec.html#WorkingDirectory=
WorkingDirectory=-/srv/app/

m-radzikowski

#!/usr/bin/env bash

set -Eeuo pipefail
trap cleanup SIGINT SIGTERM ERR EXIT

script_dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd -P)

usage() {
  cat <<EOF
Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-v] [-f] -p param_value arg1 [arg2...]

Th3Whit3Wolf

What's Cool

• Encrypted root partition
  • AES-256 bit cipher
  • Argon2id variant for PBKDF
  • Sha3-512 bit hash
• rEFInd bootloader
  • With dreary theme
  • Optimal Settings (optimized for aesthetics, and boot time)
• Boot into backups thanks to refind-btrfs

gushmazuko

Proxmox VE Installation on Hetzner Server via Rescue System

Follow these steps to install Proxmox VE on a Hetzner server via the Rescue System. The Rescue System is a Linux-based environment that can be booted into to perform system recovery tasks. We'll be using it to install Proxmox VE.

In order to complete the process, it is indeed necessary to first boot into the Rescue System and then connect to it via SSH. This will allow you to run the commands for installing Proxmox VE. Here are the steps:

Starting the Rescue System

1. Log into the Hetzner Robot.
2. Under "Main Functions; Server" select the desired server and then open the tab "Rescue".

EmranAhmed

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

• Stable version NGINX (deb/rpm)

yasenn

### Nginx main config: Tweaks & SSL settings (without the FastCGI-cache config parts)

## http {} block:

http {

# [...]

	server_tokens off;
	reset_timedout_connection on;

miketheman

CURRENT_DIRECTORY := $(shell pwd)

TESTSCOPE = apps
TESTFLAGS = --with-timer --timer-top-n 10 --keepdb

help:
	@echo "Docker Compose Help"
	@echo "-----------------------"
	@echo ""
	@echo "Run tests to ensure current state is good:"

floudet

# Chroot Jail for SSH Access 
# Tested on Ubuntu 14.04.2 LTS and Debian GNU/Linux 8 (jessie)

# Reference : http://allanfeid.com/content/creating-chroot-jail-ssh-access
# 
# Had to add/change several things to make it work, including:
# - create lib64 folder
# - copy whoami dependencies that ldd doesn't show to fix 'I have no name!'
#   in the customized prompt + create passwd file 
#