acepsaepudin

   List all Google Compute Engine instance resources:

        $ gcloud compute instances list

    List Compute Engine instance resources that have machineType f1-micro:

        $ gcloud compute instances list --filter="machineType:f1-micro"

    List Compute Engine instance resources with zone prefix us and not
    MachineType f1-micro:

acepsaepudin

GitHub Copilot Resources

Learning

• Introduction to GitHub Copilot

Videos

• Series of GitHub Copilot videos use cases from VSCode team
• Series of GitHub Copilot videos use cases from GitHub SE team
• GitHub Copilot: Custom Coding Standards with Copilot
• GitHub Copilot: AI Pair Programmer

acepsaepudin

• 0.1. References
• 0.2. Other cheatsheets
• 0.3. Manage multiple gcloud config configurations
  • 0.3.1. Switch gcloud context with gcloud config
• 0.4. Credentials
• 0.5. info
• 0.6. projects
• 0.7. zones & regions
• 0.8. Organization
• 0.9. billing

acepsaepudin

@Grab(group='org.yaml', module='snakeyaml', version='1.18')
import jenkins.model.*
import hudson.model.*
import hudson.triggers.*
import hudson.tasks.LogRotator
import hudson.plugins.git.*
import hudson.plugins.git.extensions.*
import hudson.plugins.git.extensions.impl.*
import org.jenkinsci.plugins.workflow.job.WorkflowJob
import org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition

acepsaepudin

MacOS X + oh my zsh + powerline fonts + visual studio code (vscode) terminal settings

Thank you everybody, Your comments makes it better

Install oh my zsh

http://ohmyz.sh/

sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

acepsaepudin

Background

While I'm learning how to use Nginx, I was instructed to update the server_names_hash_bucket_size (/etc/nginx/nginx.conf) value from 32 to 64, but I don't understand why should I increase the value to 64.

References

References that have been read so far:

• See the Server names, Optimization section.
• See setting up hashes

acepsaepudin

---
- hosts: all
  tasks:
  - name: Install prerequisites
    apt:
      name: ['python3-pip', 'python3-setuptools', 'virtualenv']
      update_cache: yes

  - name: Install docker-compose
    pip:

acepsaepudin

// ***********************
//
// Build and deploy different environments with jenkins pipeline
//
// Merge to develop -> triggers development release
// Merge to master without tag -> triggers staging release
// Merge to master with tag -> triggers staging and production release
// Production release requires manual approval on the jenkins job
// 
// Configure jenkins pipeline project to pull tags! By default, tags are not pulled!

acepsaepudin

Mistakes to Avoid: Docker Antipatterns

Whichever route you take to implementing containers, you’ll want to steer clear of common pitfalls that can undermine the efficiency of your Docker stack.

Don’t run too many processes inside a single container

The beauty of containers—and an advantage of containers over virtual machines—is that it is easy to make multiple containers interact with one another in order to compose a complete application. There is no need to run a full application inside a single container. Instead, break your application down as much as possible into discrete services, and distribute services across multiple containers. This maximizes flexibility and reliability.

Don’t install operating systems inside Docker containers

It is possible to install a complete Linux operating system inside a container. In most cases, however, this is not necessary. If your goal is to host just a single application or part of an application in the container, you need to install only the essential

acepsaepudin

Some Jenkinsfile examples