Шпаргалка с командами Docker
Discover gists
# Usage: export_volume volume_name | |
# export_volume volume_name > file.tar | |
# | |
# prints to STDOUT a volume in .tar format | |
export_volume() { | |
# Quit if volume name is not specified | |
vol=${1:?} | |
# If there is no such container, a new container will be created, we don't need that | |
docker volume inspect $vol > /dev/null || (echo "Container specified for export doesn't exist" && return 1) |
version: "3.5" | |
services: | |
mongo: | |
image: mongo:latest | |
container_name: mongo | |
environment: | |
MONGO_INITDB_ROOT_USERNAME: admin | |
MONGO_INITDB_ROOT_PASSWORD: admin | |
ports: |
TOP: checkvm getcountermeasure getgui get_local_subnets gettelnet hostsedit killav remotewinenum scraper winenum | |
clearev | |
use incognito | |
run autoroute -s 10.0.0.0/24 | |
irb log.clear | |
run autoroute -h | |
getsystem |
Here's what you do! | |
1. Terminal: Unzip the ipa (it's just a zip file after all) | |
unzip -q App.ipa | |
1a, You will need to have the entitlements file, this information is needed during signing. | |
codesign -d --entitlements :- "Payload/App.app" | |
2. Terminal: This will produce a `Payload/` directory. Remove the existing code signature. | |
rm -rf Payload/App.app/_CodeSignature |
The merge tool that ships with JetBrain's IntelliJ IDEA or WebStorm is really awesome and way better than FileMerge
. It is quite simple to configure SourceTree to use it as the default mergetool:
- Open the SourceTree preferences and select the
Diff
tab - Choose
Custom
both asVisual Diff Tool
and asMerge Tool
- Paste the following commands into the textfields:
- Diff Command:
/Applications/IntelliJ\ IDEA.app/Contents/MacOS/idea diff
This cheatsheet assumes the user is knowledgeable about bare installations of virtual private servers on cloud providers and is looking for quick but comprehensive instructions.
Some trivial commands might be missed or skipped.
However, this document can also work as quick tutorial for newcomers to the RHEL eco-system.
This reference guide shows how to configure a TypeScript Node.js project to work and compile to to native ESM.
CommonJS module system was introduced by the Node.js developers due to the lack of the notion of "modules" in the original JavaScript (ECMAScript) language specification at that time. However, nowadays, ECMAScript has a standard module system called ESM — ECMAScript Modules, which is a part of the accepted standard. This way CommonJS could be considered vendor-specific and obsolete/legacy. Hopefully, TypeScript ecosystem now supports the "new" standard.
So the key benefits are:
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions and generate verion and changelogs