Atadzhan Dzhan85

Install PostgreSQL 17 on Ubuntu 24.04

1. Import the repository signing key:

$ sudo apt install curl ca-certificates
$ sudo install -d /usr/share/postgresql-common/pgdg
$ sudo curl -o /usr/share/postgresql-common/pgdg/apt.postgresql.org.asc --fail https://www.postgresql.org/media/keys/ACCC4CF8.asc

2. Create the repository configuration file:

Simple WireGuard configuration

1 server, 2 clients

Getting started

Install Wireguard on all machines.

Generate all keys

Prerequirements:

Have Elasticseach + Kibana installed
Have server.basePath: "/kibana" option configured in your kibana.yml file

i. Install NGINX apt install nginx

ii. Modify nginx.conf

In /etc/nginx/nginx.conf you should have a similar setup:

ELK (Elasticsearch Logstash Kibana)

Though we're focused more on server setup procedure in this document, I will still give a very brief explanation in laymen terms for ELK. To those who are starting new in this stack, must have already heard of MVC (Model View Controller), so take it like this:

Model => Elasticsearch (for Storage, Indexing & Search)
View => Kibana (for DataViz & G-Man, yeah the one in half life 😏)
Controller => Logstash (For Logs & Filtering)

Deploying a Production ready React-Express app on AWS

In this tutorial, I will be going over to how to deploy a Javascript app from start to finish using AWS and EC2. Recently, my partner Tu and I launched our app AlgoAcademy (a resource for reviewing algorithms and data structures) and we wanted to share with other developers some of the lessons we learned along the way.

Following this tutorial, you will have an application that has:

A React frontend, Express backend
An AWS EC2 server configured to host your application
SSL-certification with Certbot
A custom domain name

Handling Multiple Github Accounts on MacOS

The only way I've succeeded so far is to employ SSH.

Assuming you are new to this like me, first I'd like to share with you that your Mac has a SSH config file in a .ssh directory. The config file is where you draw relations of your SSH keys to each GitHub (or Bitbucket) account, and all your SSH keys generated are saved into .ssh directory by default. You can navigate to it by running cd ~/.ssh within your terminal, open the config file with any editor, and it should look something like this:

Host *
 AddKeysToAgent yes

> UseKeyChain yes

	version: '4.5'
	services:

	# GITLAB
	gitlab-web:
	image: 'gitlab/gitlab-ce:latest'
	restart: always
	container_name: gitlab-web
	hostname: '192.168.0.14'
	environment:

	# See docs/examples
	# http://doc.gitlab.com/ce/ci/quick_start/README.html
	# http://doc.gitlab.com/ce/ci/yaml/README.html

	# GitLab CI template for Go tests. Note this installs
	# a new working copy of Go in a non-standard path such
	# that sudo/root is not needed for the install stage.

	# note that this particular install-environment stage
	# is overly verbose in order to debug anything tricky

	workflow "Demo workflow" {
	on = "push"
	resolves = ["SNS Notification"]
	}

	action "Build Image" {
	uses = "actions/docker/cli@c08a5fc9e0286844156fefff2c141072048141f6"
	runs = ["/bin/sh", "-c", "docker build -t $IMAGE_URI ."]
	env = {
	IMAGE_URI = "xxxxxxxx.dkr.ecr.ap-northeast-1.amazonaws.com/github-action-demo:latest"

	#!/bin/bash
	# Install docker
	apt-get update
	apt-get install -y cloud-utils apt-transport-https ca-certificates curl software-properties-common
	curl -fsSL https://download.docker.com/linux/ubuntu/gpg \| sudo apt-key add -
	add-apt-repository \
	"deb [arch=amd64] https://download.docker.com/linux/ubuntu \
	$(lsb_release -cs) \
	stable"
	apt-get update