projectoperations projectoperations

Note: This originates from: https://forum.synology.com/enu/viewtopic.php?f=258&t=107508&sid=78d911737c5ecea1f9087bdab13612bf&start=15#p478281

Here are steps that I have modified to work for me. This assumes you have a shared folder named "docker" in volume1.

We need to Symlink /var/run/docker.sock to /volume1/docker/docker.sock, because Synology Docker GUI will not be able to run it when it's pointed directly to /var/run/docker.sock. Also the symlink needs to persist after reboot. To make it do so, you will need to create an automated task in your Synology DSM via "Task Scheduler".

Go to "Control Panel" > "Task Scheduler".
Click "Create" > "Scheduled Task" > "User-defined Script".
On the "Create Task: Window, make sure "User:" is selected as "root" and rename the "Task:" to whatever you like.
Click "Schedule" tab. Under "Date - Run on the following days", select "Daily". Under "Time - Frequency", select "Every 1 hour(s)" (just to be on the safe side).

Simple automated GIT Deployment using GIT Hooks

Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.

How it works

You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.

~ Command List :

Install chumaky/postgres_mysql_fdw

$ sudo docker pull chumaky/postgres_mysql_fdw

Install toleg/postgres_mysql_fdw

$ sudo docker pull toleg/postgres_mysql_fdw

Demystifying Docker Volumes for Mac and PC Users

Docker runs on a Linux kernel

Docker can be confusing to PC and Windows users because many tutorials on that topic assume you're using a Linux machine.

As a Linux user, you learn that Volumes are stored in a part of the host filesystem managed by Docker, and that is /var/lib/docker/volumes. When you're running Docker on a Windows or Mac OS machine, you will read the same documentation and instructions but feel frustrated as that path don't exist on your system. This simple note is my answer to that.

When you use Docker on a Windows PC, you're typically doing one of these two things:

Run Linux containers in a full Linux VM (what Docker typically does today)

Installing logstash

Server install

Install

Install the Java prerequisite:

Enable TCP port 2375 for external connection to Docker

See this issue.
Docker best practise to Control and configure Docker with systemd.

Create daemon.json file in /etc/docker:

 {"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]}

	#Setup NextJS on Ubuntu server (Digital Ocean, EC2,...) Terminal Commands
	#based on my YouTube video
	#Recommended: An ubuntu server with at least 2 GB memory to handle npm run build

	#login to server
	ssh root@ip_address

	#Upgrade Server - may take a few minutes
	sudo apt update
	sudo apt upgrade

	import subprocess

	def get_docker_containers():
	try:
	# Run the docker ps command with the specified format
	result = subprocess.run(['docker', 'ps', '--no-trunc', '--format', '{{.ID}}\|{{.Image}}\|{{.Command}}\|{{.RunningFor}}\|{{.Status}}\|{{.Ports}}\|{{.Names}}'],
	stdout=subprocess.PIPE, text=True, check=True)
	output = result.stdout
	except subprocess.CalledProcessError as e:
	print(f"Error executing command: {e}")

	version: '3'

	volumes:
	local-dbt-env-shell-history: # This basically let's docker auto-manage this volume.

	services:
	local-dbt-env:
	profiles:
	- development
	platform: linux/amd64 # We force the platform for consistency.

	# -- mode: ruby --

	# vi: set ft=ruby :

	boxes = [
	{
	:name => "server1",
	:eth1 => "192.168.205.10",
	:mem => "1024",
	:cpu => "1"