If you are getting the:
PhaseScriptExecution [CP] Embed Pods Frameworks issue in
the workaround is to update the generated
*-frameworks.sh files
to add the -f flag to the call to readlink.
This is most likely needs to be done only for your main frameworks.sh file
replace
source="$(readlink "${source}")"
with
source="$(readlink -f "${source}")"
Valid strings are any single-character string, or any of the following strings:
f1, f2, f3, f4, f5, f6, f7, f8, f9, f10, f11, f12,
f13, f14, f15, f16, f17, f18, f19, f20,
pad., pad*, pad+, pad/, pad-, pad=,
pad0, pad1, pad2, pad3, pad4, pad5, pad6, pad7, pad8, pad9,
padclear, padenter
return, tab, space, delete, escape, help,
home, pageup, forwarddelete, end, pagedown,
left, right, down, up,
shift, rightshift, cmd, rightcmd, alt,
rightalt, ctrl, rightctrl, capslock, fn
If you like the vertical rulers showing the column limit of the 80, 100, 120, or whatever you like to have, it’s super easy to seetu pin VSCode, apparently – no extensions needed.
Just an easy setting:
"eslint.codeActionsOnSave.rules": null,
"editor.rulers": [
80,
120
],
"workbench.colorCustomizations": {
"editorRuler.foreground": "#ffffff11"
}
In this case, rulers will be drawn at column 80 and 120, which can be helpful when following specific coding conventions or when trying to prevent lines of code from becoming too long.
Here, the color of the ruler lines is being customized to be a semi-transparent white color (#ffffff) with an opacity of 0.11 (11%). This could be useful to make the ruler lines less distracting or to make them stand out more against a dark background.
doctlDoctl is a command-line interface (CLI) tool for managing and interacting with DigitalOcean resources. There are several benefits to using Doctl, such as its ability to automate complex tasks and streamline workflows. With Doctl, users can easily create, configure, and delete resources such as droplets, volumes, and load balancers. Additionally, Doctl offers a simple and intuitive interface for managing clusters, deploying applications, and monitoring resources. Other benefits of using Doctl include its ability to integrate with popular DevOps tools like Terraform and Ansible, as well as its support for multiple programming languages and platforms. Overall, Doctl provides developers and system administrators with a powerful and flexible tool for managing their DigitalOcean infrastructure.
resourceID='4851361'
function DO-create-snapshot() {
doctl compute droplet-action snapshot $resourceID --snapshot-name "subdomain.domain.com$(date +%Y-%m-%d-%H-%M-%S)"
}
function DO-delete-last-snapshot() {
snapshotID=$(doctl compute snapshot list -v --region nyc3 | awk 'NR>1' | sort -k4 | awk 'NR==1{print $1}')
doctl compute snapshot --interactive=false delete $snapshotID --force # non interactive variant suitable for automation
}
# first schedule the creation of the new snapshot and IF successful - delete oldest one
alias DO-rotate-NYC-snapshot="DO-create-snapshot-NYC_DO_COMITIC_COM && DO-delete-last-NYC3-snapshot"
of course, you can do that for many resources and name the methdos accordingly
Hope it helps!
The DerivedData folder is a directory used by Xcode to store intermediate build outputs, including compiled code, logs, and other temporary files. While it can be helpful in speeding up the build process, over time, the folder can accumulate a large amount of data, which can take up valuable disk space. Additionally, the contents of the DerivedData folder can sometimes become corrupted, leading to build errors and other issues. In such cases, deleting the DerivedData folder can help resolve these issues and free up disk space, allowing Xcode to recreate the necessary files the next time you build your project. Therefore, it may be necessary to delete the DerivedData folder periodically to ensure optimal performance and stability when working with Xcode.
DERIVED_DATA="~/Library/Developer/Xcode/DerivedData/"
alias goto-DerivedData="cd $DERIVED_DATA"
alias derivedData-Delete="XcodeDeleteDerivedData"
alias XcodeDeleteDerivedData="rm -rf $DERIVED_DATA"
This code is defining four aliases in a Bash shell environment that are related to the DerivedData folder used by Xcode.
The first line assigns the path of the DerivedData folder to the DERIVED_DATA variable. The ~ in the path is a shortcut for the user’s home directory.
The second line creates an alias named goto-DerivedData that changes the current working directory to the DerivedData folder. This alias saves the user from having to type the full path to the DerivedData folder every time they need to access it.
The third line creates an alias named derivedData-Delete that calls another alias named XcodeDeleteDerivedData.
The fourth line creates an alias named XcodeDeleteDerivedData that deletes the entire contents of the DerivedData folder using the rm -rf command. The -rf option stands for “recursive force” and tells the command to delete all files and subdirectories within the DerivedData folder, even if they are write-protected or hidden.
Overall, these aliases provide convenient shortcuts for navigating to and deleting the DerivedData folder used by Xcode, which can help free up disk space and resolve build errors.
#Useful Crontab CheatSheet
* * * * * command to be executed
– – – – –
| | | | |
| | | | +—– day of week (0 – 6) (Sunday=0)
| | | +——- month (1 – 12)
| | +——— day of month (1 – 31)
| +———– hour (0 – 23)
+————- min (0 – 59)
An example script for backing up a database
#!/bin/bash
backupfolder="/backup/mongo/`date +"%Y-%m-%d_%H.%M"`"
db="db_to_backup"
# do the dump
mongodump --uri="mongodb://user:pass@domain:27017/" --db=$db -v --gzip --out=$backupfolder
# repack with zip - 0 - just basically adding a password...
zip -0 -P alamoAlamo $backupfolder/backup.zip $backupfolder/$db/*.gz
# cleanup original *.gz files
rm -fR $backupfolder/$db
#
# 5 level deep nested directory creation - this is roughly 65.5 million folders
#
#!/bin/bash
for p in {0..9} {a..z}
do
cd ${p}
for m in {0..9} {a..z}
do
cd ${m}
for n in {0..9} {a..z}
do
mkdir $n
cd ${n}
for y in {0..9} {a..z}
do
mkdir $y
cd ${y}
for z in {0..9} {a..z}
do
mkdir $z
# pwd #you may want to avoid printint, or it will take foever even in a 3 level deep structure :)
done
cd ".."
done
cd ".."
done
cd ".."
done
cd ".."
done
I have not tested the following but it should work and is somewhat simpler
#!/bin/bash
for p in {0..9} {a..z}
do
for m in {0..9} {a..z}
do
for n in {0..9} {a..z}
do
for y in {0..9} {a..z}
do
for z in {0..9} {a..z}
do
mkdir -p "./${p}/${m}/${n}/${y}/${z}
done
done
done
done
done
another option for a flatter structure would be to use doubles i.e. 00 01 02 ….. 8b 8c …..zz
This gives you 36 * 36 = 1296 variations in the first level and then adding a second level would give you about a million combinations :) which if you think about it, even if each folder has 100 files - that 100 million files.
If you need to make sure your comouter doesn’t go to sleep, with the recent addition of wakelock to Chrome this is extremely easy to do.
Open Chrome on any page
Open the developer tools:
Ctrl+Shift+C on Windows/Linux
or
⌘ +⇧+C on Mac (Cmd+Shift+C)
will open the dev tools - then go to the “Console” tab and paste/type this into the console
let screenLock = await navigator.wakeLock.request('screen');
That’s it. Your computer won’t sleep.
Note that you will lose the lock if you clos or change the tab.