brew services start colima. You can skip the following work-around.
- Create an executable script to run in foreground and manage colima:
cat <<-EOF | sudo tee /usr/local/bin/colima-start-fg
#!/bin/bashbrew services start colima. You can skip the following work-around.
cat <<-EOF | sudo tee /usr/local/bin/colima-start-fg
#!/bin/bash| #!/bin/bash | |
| # (c) 2020 [email protected] | |
| # SPDX-License-Identifier: Apache-2.0 OR MIT | |
| # | |
| # This script installs support for building multi-architecture docker images | |
| # with docker buildx on CI/CD pipelines like Github Actions or Travis. It is | |
| # assumed that you start of with a fresh VM every time you run this and have to | |
| # install everything necessary to support 'docker buildx build' from scratch. | |
| # | |
| # Example usage in Travis stage: |
| # Rclone mount on boot | |
| # Copy file to: /etc/systemd/system | |
| # You need to create a remote on RClone and a folder on your disk, both with same name <rclone-remote> | |
| # This example uses /cloud/ folder as origin to mount all remotes, change it to your needs | |
| # This example use a linux user named rclone. Create it or adapt it to your needs. Rclone will get config from that user's home folder | |
| # Register new service by typing: | |
| # sudo systemctl daemon-reload | |
| # Do the next one for every remote you want to load on boot | |
| # sudo systemctl enable rclone-mount@<rclone-remote>.service | |
| # systemctl start rclone-mount@<rclone-remote>.service |
| # 你可以从该 URL 下载这个配置文件: http://surge.run/config-example/ios.conf | |
| # 用编辑器编辑后,再通过 iTunes, URL, AirDrop 或者 iCloud Drive 复制回 iOS 设备 | |
| # Version 2.0 | |
| [General] | |
| # 日志等级: warning, notify, info, verbose (默认值: notify) | |
| loglevel = notify | |
| # 跳过某个域名或者 IP 段,这些目标主机将不会由 Surge Proxy 处理。(在 macOS | |
| # 版本中,如果启用了 Set as System Proxy, 那么这些值会被写入到系统网络代理 | |
| # 设置中.) |
| # How to use "acme.sh" to set up Lets Encrypt without root permissions | |
| # See https://github.com/Neilpang/acme.sh for more | |
| # This assumes that your website has a webroot at "/var/www/<domain>" | |
| # I'll use the domain "EXAMPLE.com" as an example | |
| # When this is done, there will be an "acme" user that handles issuing, | |
| # updating, and installing certificates. This account will have the following | |
| # (fairly minimal) permissions: | |
| # - Host files at http://EXAMPLE.com/.well-known/acme-challenge |
| # alias to edit commit messages without using rebase interactive | |
| # example: git reword commithash message | |
| reword = "!f() {\n GIT_SEQUENCE_EDITOR=\"sed -i 1s/^pick/reword/\" GIT_EDITOR=\"printf \\\"%s\\n\\\" \\\"$2\\\" >\" git rebase -i \"$1^\";\n git push -f;\n}; f" | |
| # completely wipe git history | |
| wipe-history = "!f() { git add . && git reset --soft $(git rev-list --max-parents=0 HEAD) && git commit --amend -m \"${1:-sup}\" && git push --force; }; f" | |
| # squash the last N commits | |
| squash = "!f(){ git reset --soft HEAD~${1} && git commit --edit -m\"$(git log --format=%B --reverse HEAD..HEAD@{1})\"; };f" |