方法一:
为 PowerShell 设置代理,命令如下:
$Env:http_proxy="http://127.0.0.1:7890";
$Env:https_proxy="http://127.0.0.1:7890";
这是临时命令,重新代理终端需要重新输入
如果想要永久设置代理,建议使用自定义配置,使每次代理 PowerShell 窗口时,运行如上命令:
在 PowerShell 窗口中运行如下指令:
方法一:
为 PowerShell 设置代理,命令如下:
$Env:http_proxy="http://127.0.0.1:7890";
$Env:https_proxy="http://127.0.0.1:7890";
这是临时命令,重新代理终端需要重新输入
如果想要永久设置代理,建议使用自定义配置,使每次代理 PowerShell 窗口时,运行如上命令:
在 PowerShell 窗口中运行如下指令:
Usage:
```
$ mkdir RHEL9Doc
$ cd RHEL9Doc
$ fetchdoc.sh https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9
```
Prerequirement: curl, GNU Parallel
2024-11-21: fix for docs.redhat.com update
## I just ran into this after initializing a Visual Studio project _before_ adding a .gitignore file (like an idiot). | |
## I felt real dumb commiting a bunch of files I didn't need to, so the commands below should do the trick. The first two commands | |
## came from the second answer on this post: http://stackoverflow.com/questions/7527982/applying-gitignore-to-committed-files | |
# See the unwanted files: | |
git ls-files -ci --exclude-standard | |
# Remove the unwanted files: | |
git ls-files -ci --exclude-standard -z | xargs -0 git rm --cached |
TL;DR Set up your sole node Proxmox VE install as any other server - with DHCP assigned IP address. Useful when IPs are managed as static reservations or dynamic environments. No pesky scripting involved.
ORIGINAL POST DHCP setup of a single node
In programming languages, literals are textual representations of values in the source code. This is a syntactical concept.
Some examples:
7 # integer literal
A brief example on how to use npx
to run gist based scripts.
Read the article here https://neutrondev.com/npm-vs-npx-whats-the-difference/ or watch it on YouTube https://www.youtube.com/watch?v=fSHWc8RTJug
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
Delete all unused repositories and forgotten forks in 6 (semi)-automatic steps!
Ugh. Github forces me to type my password for every fork and repository I want to delete. That’s smart and all, but what if one wants to mass-delete a bunch of old, unused, forgotten, dirty little repositories that make his repository list look like a mess? well, that person follows this short guide:
[1.] Open in a new tab all to-be-deleted github repositores (Use the mouse’s middle click)
https://github.com/wildeyes?tab=repositories