A practical cheat sheet for designing robust, testable, future-proof agent workflows.
This is optimized for:
- single main agent ownership
- explicit skill usage
- sequential, deterministic execution
- “good enough” optimization
Let say you want to host example1.com, example2.com, and example3.com on your machine, respectively to localhost:8080, localhost:8181, and localhost:8282.
Note: Since you don't have access to a DNS server, you should add domain name entries to your /etc/hosts (you can't do this on CDF machines):
... 127.0.0.1 example1.com example2.com example3.com ... To proxy eaxmple1.com we can't use the location part of the default server. Instead we need to add another server section with a server_name set to our virtual host (e.g., example1.com, ...), and then a simple location section that tells nginx how to proxy the requests:
Making vagrant and ansible work together with virtualbox as a provider is not well documented across the documentations. Ansible's control node doesn't work on Windows. However, it works on WSL which make the installation of ansible and vagrant on WSL necessary and the access from WSL to virtualbox which is still running under the Windows host.
| var gulp = require('gulp'), | |
| gutil = require('gulp-util'), | |
| sass = require('gulp-ruby-sass'), | |
| minifyCSS = require('gulp-minify-css'), | |
| concat = require('gulp-concat'), | |
| webserver = require('gulp-webserver'), | |
| uglify = require('gulp-uglify'), | |
| rename = require('gulp-rename'), | |
| minifyHTML = require('gulp-minify-html'), | |
| imagemin = require('gulp-imagemin'), |
| { | |
| "Version": "2012-10-17", | |
| "Statement": [ | |
| { | |
| "Effect": "Deny", | |
| "Action": [ | |
| "organizations:LeaveOrganization", | |
| "guardduty:DeleteDetector", | |
| "guardduty:DisassociateFromMasterAccount", | |
| "guardduty:UpdateDetector", |
Bypassing USB Debugging off and FRP Google Account lock enabled on a Samsung XCover4.
Model: Samsung XCover4
Unity3D scenes and prefabs cannot not be merged automatically by default. Working on one scene / prefab at the same time can cause issues when a merge conflict happens. Usually that means that one version needs to be discarded or the files need to be merged manually (which isn't easy).
However, Unity provides the UnityYAMLMerge tool with each Unity installation to merge scenes and prefabs semantically for manual setup. This is also called Smart Merge. The tool can be accessed from the command line and is also available to third-party version control software like Git, etc. To setup the smart merge for Git, follow the following steps.
The default file size limit for Outlook data file (.ost) is 50GB. To change file size limit to 100 GB, add following keys to the registry usind cmd or regedit.
REG ADD HKCU\Software\Microsoft\Office\16.0\Outlook\PST /v WarnLargeFileSize /t REG_DWORD /d 102400 /f
REG ADD HKCU\Software\Microsoft\Office\16.0\Outlook\PST /v MaxLargeFileSize /t REG_DWORD /d 107520 /f
| stages: | |
| - publish | |
| - deploy | |
| variables: | |
| TAG_LATEST: $CI_REGISTRY_IMAGE/$CI_COMMIT_REF_NAME:latest | |
| TAG_COMMIT: $CI_REGISTRY_IMAGE/$CI_COMMIT_REF_NAME:$CI_COMMIT_SHORT_SHA | |
| publish: | |
| image: docker:latest |