Skip to content

Instantly share code, notes, and snippets.

Remote employee forever!

Theodoros Ploumis theodorosploumis

Remote employee forever!
Block or report user

Report or block theodorosploumis

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

Κανόνες παιχνιδιού κεντρικού παίκτη (midfielder)

  1. Πρέπει ανά πάσα στιγμή να ελέγχει όλο το γήπεδο (γρήγορες ματιές) και να ξέρει που είναι όλοι οι συμπαίκτες και οι αντίπαλοι.
  2. Είναι υπεύθυνος για τον ρυθμό του παιχνιδιού και την συμμετοχή όλων των παικτών στο παιχνίδι (αλλαγές παιχνιδιού, δημιουργα υπεραριθμίας κτλ).
  3. Απλό παιχνίδι (μέγιστο 2 κοντρόλ).
  4. Καλές τοποθετήσεις στον κατάλληλο (κενό) χώρο.
  5. Οι πάσεις του πρέπει να έχουν όσο το δυνατόν καλύτερη ακρίβεια.
  6. Όταν παίρνει την μπάλα με την πλάτη να την επιστρέφει σχεδόν πάντα πίσω.
  7. Οι πάσες προς τα πίσω να είναι 100% σωστές.
  8. Όταν έχει κοντά αντίπαλο δίνει άμεσα πάσα.
View composer_commands.txt
composer outdated -Dm
composer prohibits vendor/package version
composer show vendor/package
composer show vendor/package -a
composer depends vendor/package -t
composer outdated -m
composer outdated
composer update vendor/package --with-dependencies --dry-run
composer require vendor/package:constraint --no-update
composer update vendor/package vendor/package vendor/package
  • Dev/Stage/Live environment
  • Software for issues (eg Jira, GitHub etc)
  • Security monitoring
  • Git precommit hooks
  • Git hosting (eg Gitlab, GitHub, Bitbucket)
  • CI (eg CircleCI)
  • Development tools (eg performance, build etc)
  • Collaboration tools (eg Slack)
  • Drupal specific hosting (Acquia, Pantheon, Amazee etc)
  • Drush custom commands
theodorosploumis /
Last active Feb 15, 2019
How to move a Drupal site from Server A to Server B

How to move a Drupal site from Server A to Server B.

  1. Create the Domain on Server B
  2. Create the Emails on Server B
  3. Create the Database on Server B
  4. Download the database from Server A using backup_migrate
  5. Rsync files from Server A to Server B using ssh. Be careful to also transfer the dotfiles (or use git if is set)
  6. Install drush on Server B (see drush-installer)
  7. Install Drupal on Server B with a clean Database
  8. Enable module backup_migrate on the new site on Server B
### Keybase proof
I hereby claim:
* I am theodorosploumis on github.
* I am theodorosploumis ( on keybase.
* I have a public key whose fingerprint is 12F8 43E2 FE78 653C 6C93 B925 6F21 831E 78DB 885B
To claim this, I am signing this object:
theodorosploumis /
Last active Apr 13, 2019
Get lists of software etc used on a Drupal 8.x site (modules, themes, 3rd party libraries, drupal libraries)
// Get lists of software etc used on a Drupal 8.x site
// Get drupal projects
drush pml --status="enabled"
// Get non core Drupal projects installed
drush pml --status="enabled" --no-core --format="table"
// Get php party libraries
composer show -i
theodorosploumis / gist:32c1592659b23812837af2c9344e72c0
Created Aug 19, 2016 — forked from prairiehippo/gist:3238902
Drupal API settings for Chrome Search Engine
View gist:32c1592659b23812837af2c9344e72c0

Want to search the Drupal API directly using the Chrome Omnibox?

Right click on the omnibox in chrome (URL box) and select "Edit Search Engines".

You very likely already have a Drupal API search engine entry in the table, but if not, scroll to the bottom and add a new entry with the following items.

theodorosploumis /
Last active Feb 15, 2019
Drupal 8.x with Composer, example of step commands
theodorosploumis /
Created Jun 8, 2016 — forked from mohamed-el-habib/
drupal fpm with nginx and mysql


git clone git:// docker-drupal-fpm
cd docker-drupal-fpm
mkdir -p /usr/local/share/dockervolumes/drupal # if you change this folder please update the
chmod +x && ./ up
theodorosploumis /
Last active Apr 10, 2019
The Gizra way pricing method

Basic rules

A simple pricing estimation method to avoid cost and time pitfalls. See more at

  • Everyone should understand the "pricing" table (simple naming etc)
  • Split the project to undestandable taks
  • Set max of 12hr for a task (more hr cannot be accurate)
  • Setup a human language for the tasks
  • Create group of tasks with a visible result (eg a webpage, a complete functionality etc)
  • Write zero prices for almost zero time tasks (eg a Drupal login)
  • With Drupal we can split tasks and estimate time is easier because of the architecture of the CMS (menu, entities, fields etc)
You can’t perform that action at this time.