- Clearly state your task or question at the beginning of your message.
- Provide context and details to help Claude understand your needs.
- Break complex tasks into smaller, manageable steps.
Bad prompt:
| $remoteport = bash.exe -c "ifconfig eth0 | grep 'inet '" | |
| $found = $remoteport -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}'; | |
| if( $found ){ | |
| $remoteport = $matches[0]; | |
| } else{ | |
| echo "The Script Exited, the ip address of WSL 2 cannot be found"; | |
| exit; | |
| } |
Some random notes on trying (and failing) to get Proxmox as host with 5700G APU GPU PCI Passthrough to Ubuntu guest VM working:
References:
| #cloud-config | |
| package_upgrade: true | |
| ssh_authorized_keys: | |
| - <your key> | |
| packages: | |
| - apt-transport-https | |
| - ca-certificates | |
| - curl |
| ######################################## | |
| ## Import of DrugBank Annotation Data ## | |
| ######################################## | |
| ## Function to import DrugBank XML to data.frame | |
| ## Last step gives error. To debug, the following function may help. | |
| ## Note, this functions needs some major speed improvements. Ideally, | |
| ## it should be replaced with a standard XML import method. | |
| ## (1) Download | |
| ## - download DrugBank XML (https://www.drugbank.ca/releases/latest) | |
| ## - name uncompressed file 'drugbank.xml' |
| ############################################################################################################ | |
| ################## ############################# | |
| ################## ############################# | |
| This Gist collection contains all localstack related examples | |
| ################## ############################# | |
| ################## ############################# | |
| ############################################################################################################ |
This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.
While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)
The instructions here were tested with F