Saul Salazar

Repositories git-access-control (users and teams) git-repositories (repos and groups) Why separate repos Separation of concerns principle. Least Privilege principle. Terraform works faster. A few rules/scenarios: An user can be a member of more than one team GitLab Permissions and Roles Reference: https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions I recommend giving the developer access because otherwise the next role would be maintainer and they can delete things, manage users, edit project settings, edit branch protection and manage gitlab pages (domains and certificates) GitLab Modules Example # repo: git-access-control module "team_example" { source = ".

I realized moments before publishing that this article sounds like Documentation / Docs as Code but you can call it whatever you want :D Problems How to write technical documents? (at large scale company) How to find information faster? (to increase productivity) How to separate different information? (security purposes) Solution Use the same workflow developers already know and love (Git) and write documentation using plain text (Markdown), let the docs be easily written on the favorite editor of anyone.

Make employee onboarding easier providing a tool with a single command to install all required applications and plugins. The tool is Make so you just need to write a single file (the Makefile). Depending the case, this can be implemented for the entire tech area, the development division, multiple teams, or even big projects. Plus you can add ASCII art What you can automate Create default folders (notes, projects, documentation, temp).

Dear Linux user, does your touchpad annoys you? Maybe your laptop keyboard shortcuts dont work and you cant disable it. Anyway, take this bash script with you. We will be using xinput to get device information from the touchpad, which in my case is a Synaptics Touchpad Bash Script #!/bin/bash # script to toggle state of synaptics touchpad tpid=`xinput list | grep SynPS | sed 's/.*id\=\([0-9]\+\).*/\1/g'` declare -i status status=`xinput list-props ${tpid} | grep Device\ Enabled | sed -e 's/.

Scripts that I hope will help you, you can add them as an alias or copypaste directly when you need them. Doge git commands I will start with some funny aliases to convert git into “doge language”. # add to your .bashrc or .zshrc alias such=git alias very=git alias wow='git status' # reload your terminal and be doge $ wow $ very add some_files $ such commit -m 'Commit Message' $ very push How to create website backups (Apache Web Server) It also downloads the backup directly to your workstation thanks to SSH (be sure to configure it before trying to connect) and compress the result file using GZIP.

A simple javascript function to generate policy strings for AWS S3 Buckets that can run on your browser. You can customize it to your needs :D Lets start by saying you have A LOT of buckets var buckets = ['bucketName1', 'bucketName2'] Then you have to iterate/loop through them buckets.forEach((bucket) => { var policy = getPolicyString(bucket) console.log(policy) }) And finally the function, I named it getPolicyString XD function getPolicyString (bucketName) { return `{ "Statement": [ { "Effect": "Allow", "Action": "s3:ListAllMyBuckets", "Resource": "arn:aws:s3:::*" }, { "Effect": "Allow", "Action": "s3:*", "Resource": [ "arn:aws:s3:::${bucketName}", "arn:aws:s3:::${bucketName}/*" ] } ] }` }