This command will print out each folder and also show how much space the folder is occupying.
find . -name "node_modules" -type d -prune -print | xargs du -chsfind . -name 'node_modules' -type d -prune -print -exec rm -rf '{}' \;| const MyDiagram = () => { | |
| // create diagrams schema | |
| const [schema, setSchema] = useState(initialSchema); | |
| const addNode = () => { | |
| var new_node = { | |
| //new node data | |
| } | |
| var new_schema = Object.assign({},schema) | |
| new_schema.nodes.push(new_node) |
| #!/usr/bin/env bash | |
| # Install mesa drivers | |
| sudo apt update -y && sudo apt install -y mesa-*=22.0.* | |
| # Avoid updating mesa drivers | |
| dpkg-query --showformat='${Package}\n' --show | grep mesa | while read -r line; do | |
| sudo apt-mark hold $line | |
| done |
This READMEexplains the whole process, from start to finish, on how to setup a custom Security Pipeline using GitLab.
The starting point is a an already vulnerable application, for this example https://github.com/appsecco/dvna will be used.
The repo is cloned and pushed as-is in a new GitLab Project (empty). The first thing to do is enable a runner for our pipeline, this can be done in the Settings -> CI/CD section of the project