Skip to content

Instantly share code, notes, and snippets.

View fqjony's full-sized avatar
🎯

Dmytro Smirnov fqjony

🎯
View GitHub Profile
@fqjony
fqjony / gist:cc4ac4f8ff4a556a165cb50db473ed92
Created June 24, 2025 12:33
From Integration to Orchestration: Advanced GitHub Workflows
# From Integration to Orchestration: Advanced GitHub Workflows
Modern engineering teams need more than just faster tests or automated builds—they need delivery pipelines that coordinate complex environments, validate infrastructure, and enforce safety at every stage. While GitHub Actions began as a CI platform focused on build and test automation, its real power emerges when used to orchestrate secure, reliable workflows across the entire software delivery lifecycle.
## Why Deeper Workflow Design Matters
Modern software systems span application code, cloud infrastructure, and environment-specific configurations. Delivering such systems reliably—especially to production—requires orchestrating multiple components in a secure, consistent, and controlled way. GitHub workflows, when intentionally designed, can operate as orchestration layers—connecting logic across applications, environments, teams, and repositories.
Workflows become intelligent automation gateways—evaluating branch context, repository metadat
$FilePath = "C:\Windows\Temp\WindowsAzureVmAgent.msi"
Retry-WebRequest -Params @{
Uri='https://github.com/Azure/WindowsVMAgent/releases/download/2.7.41491.1071/WindowsAzureVmAgent.amd64_2.7.41491.1071_2209271071.fre.msi';
OutFile = $FilePath
}
$DataStamp = get-date -Format yyyyMMddTHHmmss
$logFile = '{0}-{1}.log' -f $FilePath,$DataStamp
$MSIArguments = @(
function getDrinks(numberOfGuests) {
let sum = 0;
for (let i = 1; i <= numberOfGuests; i++) {
sum = sum + i;
}
return sum;
}
### RAW
QUERY='{"query":{"bool":{"must":[{"term":{"_mls":"crmls"}},{"terms": {"ListingId":["315004795","218002386","218006981","218007251","218010956","218011911","218012340","219000169","219000990","219000991","219000999","219001002","219001005","219001007","219001009","219001053","219001810","219003414","219003582","219003974","219004628","219005122","219005208","219005467","219005987","219006699","219006947","219007451","219007560","219008059","219008609","219008751","219008801","219008924","219009426","219009816","219009868","219010054","219010082","219010226","219010229","219010341","219010379","219010390","219010471","219010712","219010743","219010742","219010785","219010816","219010909","219010988","219011040","219011098","219011182","219011198","219011320","219011372","219011471","219011475","219011485","219011551","219011556","219011706","219011728","219011734","219011773","219011874","219011886","219011896","219011903","219012031","219012057","219012058","219012067","219012070","219012091","2190120
"5.172.196.188",
"5.178.78.77",
"37.252.231.50",
"46.165.195.139",
"46.20.45.18",
"52.209.186.226",
"52.209.34.226",
"52.210.232.124",
"52.48.244.35",
"52.57.132.90",
@fqjony
fqjony / rest-controller-extend.php
Created March 30, 2018 13:47 — forked from sagarkbhatt/rest-controller-extend.php
Sample class that extends WP rest controller
<?php
/**
* Add rest api endpoint for category listing
*/
/**
* Class Category_List_Rest
*/
class Category_List_Rest extends WP_REST_Controller {
/**

It helps to identify the type of content we will have.

  1. Content Pages - change often, most likely will have different content based on host
  2. Static Assets - scripts, styles and images. always same, even if host changes. See example #1
  3. Administrative Areas - require login and special cookies to be allowed.
  4. API and RPC - dont require cookies but should not be cached

For most dynamic pages that following headers should be allowed: