rcdelacruz

Default

Powerlevel10k

rcdelacruz

# Taps
tap 'homebrew/cask-fonts'
tap 'homebrew/cask-versions'
tap 'heroku/brew' 

# Install CLI Tools
## Shell Utilities
brew 'coreutils'
brew 'findutils'
brew 'autojump'

rcdelacruz

Overview: running crc on a remote server

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

rcdelacruz

############################################################################################################
##################                                                             #############################
##################                                                             #############################

                  This Gist collection contains all localstack related examples
                    
##################                                                             #############################
##################                                                             #############################
############################################################################################################

rcdelacruz

Address:
  type: object
  description: |
    Representation of an address.

    As addresses are only used for delivery, we require a phone number.
  required:
    - name
    - streetAddress
    - city

rcdelacruz

#!/bin/sh

SOURCE_TABLE=xxx-mydata-accp
TARGET_TABLE=xxx-mydata-prod
AWS_PROFILE=default
AWS_REGION=ap-southeast-2

# Step 1 - export and transform

aws --profile=$AWS_PROFILE \

rcdelacruz

1. Development environment

• How would you rate the development environment in team? (Use the [1-5] scale)
• How would you rate the project Settings needed to start to work? (Use the [1-5] scale)
• How would you rate documentation of the necessary tools? (Use the [1-5] scale)
• How do you rate the team’s current onboarding process? (Use the [1-5] scale)
• Do you think we have enough tools to work with? (Use the [1-5] scale)
• What tools are you missing in order to be more productive at work?

2. Code

• What is the level of satisfaction with the current codebase? (Use the [1-5] scale)

rcdelacruz

# Brownbag Notes

This brownbag is a showcase of the toolkits that has been gaining popularity amongst software development community, DevOps community, and open source community.

This is not meant to be a workshop for beginners, but to give you an idea on what is going on around the different communities in the IT world.

But don’t fret, I’ll be giving you some introductions and basic concepts along the way. And at the end of this sessions, you will gain understanding and awareness of the different tools that may help you leverage or accelerate development by running your projects on  your local machine. And hoping that this might help you eliminate or minimize bugs in production environment.

<aside>
💡 The `docker compose` (with a space) is a newer project to migrate compose to Go with the rest of the docker project. This is the `v2` branch of the [docker/compose](https://github.com/docker/compose/tree/v2) repo. It's been first introduced to Docker Desktop users, so docker users on Linux didn't see the com

rcdelacruz

Proxmox GPU Passthrough

Config :

• Motherboard : ASUS PRIME B450M-A
• CPU : AMD Ryzen 7 2700x
• GPU : EVGA AMD RADEON R9 380 Series
• Ram : DDR4 2133 MHz

Setting it all up

Update packages

rcdelacruz

# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
lerna-debug.log*

# Diagnostic reports (https://nodejs.org/api/report.html)
report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json