The post Fermentation appeared first on Thrasos Website.

(Use the * and # keys as pauses)

Korobeiniki :

1 2 3 1 # 1 9 1 #

6 8 * 9 6 3 # 9 6 3 #

9 6 3 1 # 1 9 1# 6 8

Bach’s Menuet :

5 3 2 1 2 1 3 3 2 1 2 3 #

4 # 4 # 4 # 9 8 # 9

Kalinka:

3 2 1 1 2 3 8 9 8 #

9 # 9 8 # 9 # 9 3 2 1 1 2 3*

8 9 8 # 9 # 9 8 # 9 # 9

The post Music with the Phone’s Keypad – Tetris – Part 2 appeared first on Thrasos Website.

Ctrl+F and regex:

(?s)BEGIN:VCARD(?:(?!END:VCARD|\bTEL\b).)*END:VCARD

Save and upload them to your contacts on your phone.

Regex breakdown:

(?s)          # Allow the dot to match newlines.
BEGIN:VCARD   # Match "BEGIN:VCARD".
(?:           # Start non-capturing group.
 (?!          # Make sure we're not able to match either
  END:VCARD   # the text "END:VCARD" (we don't want to match beyond the end)
 |            # or
  \bTEL\b     # "TEL" (because we don't want them to be in the match).
 )            # End of lookahead.
 .            # Match any character (if the preceding condition is fulfilled),
)*            # repeat as needed.
END:VCARD     # Match "END:VCARD"

_source

The post Cleaning up VCARD contacts without a phone. appeared first on Thrasos Website.

To set up multiple websites on Docker Compose, you’ll need to create a docker-compose.yml file for each website. A docker-compose.yml file defines the services that make up your website, such as a web server and a database, and how they are connected.

Here’s an example docker-compose.yml file that defines a simple web service:

version: "3"
services:
web:
build: .
ports:
- "8000:8000"

This file defines a single service called web that is built from the current directory (.) and exposes port 8000 on the host machine.

To set up multiple websites, you’ll need to create a docker-compose.yml file for each website. Each file should define the services for the website, including any dependencies and connections between the services.

Once you have your docker-compose.yml files, you can use the docker-compose command to build and run your websites. For example, to build and run the web service defined above, you would run:

$ docker-compose build 

$ docker-compose up

This will build the web service and run it in a Docker container. You can then access the website at http://localhost:8000.

You can repeat these steps for each website you want to set up with Docker Compose. This will allow you to run multiple websites on the same machine using Docker.

How to set up multiple websites on docker-compose using the same ports

To set up multiple websites on Docker Compose using the same ports, you’ll need to use a reverse proxy to route incoming requests to the correct website. A reverse proxy is a server that receives incoming requests and forwards them to the appropriate service based on the hostname or other information in the request.

To set up a reverse proxy for your websites, you’ll need to do the following:

1. Create a docker-compose.yml file for each website, as described in the previous answer. Make sure that each website’s services are listening on different ports.
2. Create a new service in your docker-compose.yml file for the reverse proxy. This service should run a reverse proxy server, such as nginx or Apache, and be connected to all other services in your docker-compose.yml file.
3. Configure the reverse proxy to route incoming requests to the correct service based on the hostname or other information in the request. For example, if you have two websites, example.com and example.org, you would configure the reverse proxy to forward requests for example.com to the service for that website and requests for example.org to the service for that website.
4. Use the docker-compose command to build and run your services, including the reverse proxy.

With this setup, incoming requests to your websites will be routed by the reverse proxy to the correct service, allowing you to use the same ports for multiple websites.

The post Docker Compose Notes #2 appeared first on Thrasos Website.

To set up Docker for multiple projects, you’ll need to create a new Dockerfile for each project. A Dockerfile is a text file containing instructions for Docker on building and setting up your project’s environment.

To create a Dockerfile for your project, follow these steps:

1. Create a new directory for your project and navigate to it in your terminal.
2. Create a new file called Dockerfile in your project directory.
3. Open the Dockerfile in a text editor, and add instructions for building the environment for your project. These instructions can include commands to install dependencies, set environment variables, and more.
4. Save the Dockerfile and close it.
5. Use the docker build command to build a Docker image for your project based on the instructions in the Dockerfile.
6. Use the docker run command to run the Docker image and launch your project.

You can repeat these steps for each project you want to set up with Docker. This will allow you to run multiple projects on the same machine using Docker.

Where are docker files stored?

By default, Docker stores the files that make up an image in a directory called /var/lib/docker on the host machine. This directory contains all of the files for the Docker images installed on the host machine.

You can use the docker inspect command to see the exact location of the files for a specific Docker image. For example, to see the files for the ubuntu image, you would run:

$ docker inspect ubuntu

This will output a JSON object that contains information about the ubuntu image, including the location of its files on the host machine.

Note that you should not modify the files in the /var/lib/docker directory directly, as doing so can cause problems with your Docker installation. Instead, use the Docker command-line interface to manage your images and containers.

The post Docker Notes #1 appeared first on Thrasos Website.

The post A.I generated poem in Greek appeared first on Thrasos Website.

The post A.I. Generated Art appeared first on Thrasos Website.

The post A.I. generated art. appeared first on Thrasos Website.

 create a conf file in data/conf/nginx with the following content:

server {
ssl_certificate /etc/ssl/mail/cert.pem;
ssl_certificate_key /etc/ssl/mail/key.pem;
index index.html;
client_max_body_size 0;
root /web;
include /etc/nginx/conf.d/listen_plain.active;
include /etc/nginx/conf.d/listen_ssl.active;
server_name visum.pt;

location ^~ /.well-known/acme-challenge/ {
allow all;
default_type “text/plain”;
}

location / {
root /web;
}
}

~Then add the index.html to data/web
~Add your domain to ADDITIONAL_SAN (https://mailcow.github.io/mailcow-dockerized-docs/firststeps-ssl/) to have proper SSL

The post MailCow, simple html in maindomain appeared first on Thrasos Website.

The trees were hung up with ropes. This road sat 6 miles from the Russian border, so when looking down from observation airplanes, the road would be disguised.

It was intended to be viewed obliquely (slanted) not directly from above. The suspended trees would conceal enough of the road to make it difficult to identify visually when flying past, or from surveillance photos taken from aircraft. Camouflage is designed to break up the shape of something against the background, this would have been effective within certain limits.

The post Camouflage appeared first on Thrasos Website.