-
Build two boxes and install ubuntu18.04
- box1: master -> Ubuntu 18.04 with PG 12
- static ip: 192.168.33.33
- hostname: master
- box2: slave -> Ubuntu 18.04 with PG 12
- static ip: 192.168.33.44
- hostname: slave
- box1: master -> Ubuntu 18.04 with PG 12
#!/bin/bash | |
## This gist contains step by step instructions to install cuda v10.1 and cudnn 7.6 in CentOS 7 | |
### steps #### | |
# verify the system has a cuda-capable gpu | |
# download and install the nvidia cuda toolkit and cudnn | |
# setup environmental variables | |
# verify the installation | |
### | |
### to verify your gpu is cuda enable check |
#!/bin/bash | |
## This gist contains instructions about cuda v11.2 and cudnn8.1 installation in Ubuntu 20.04 for Pytorch 1.8 & Tensorflow 2.7.0 | |
### steps #### | |
# verify the system has a cuda-capable gpu | |
# download and install the nvidia cuda toolkit and cudnn | |
# setup environmental variables | |
# verify the installation | |
### |
def applications = env.APPLICATIONS.split(",").findAll { it }.collect { it.trim() } | |
def environment = env.ENVIRONMENT | |
def version = env.VERSION | |
def jobs = [:] | |
if (applications.size() < 1) { | |
error("ERROR: APPLICATIONS must be a comma-delimited list of applications to build") | |
} | |
for (int i = 0; i < applications.size(); i++) { |
## | |
# WHOIS servers for new TLDs (http://www.iana.org/domains/root/db) | |
# Current as of 2017-12-10 UTC | |
## | |
\.aarp$ whois.nic.aarp | |
\.abarth$ whois.afilias-srs.net | |
\.abbott$ whois.afilias-srs.net | |
\.abbvie$ whois.afilias-srs.net | |
\.abc$ whois.nic.abc |
External Resources
- linuxacademy.com (Training)
- Acloud.guru (training)
- Read the top-level Documentation and FAQs for all the major AWS resources (EC2, S3, RDS, Auto Scaling, etc). The answers to the "nit-picky" questions can be found here. It's also helpful to go deeper on VPCs and networking-related concepts.
- Everyone says read the white papers. The ones I read were:
- Security Best Practices https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Best_Practices.pdf
- Cloud Best Practices https://d0.awsstatic.com/whitepapers/AWS_Cloud_Best_Practices.pdf
What this guide will cover: the code you will need in order to include Redis and Resque in your Rails app, and the process of creating a background job with Resque.
What this guide will not cover: installing Ruby, Rails, or Redis.
Note: As of this writing I am still using Ruby 1.9.3p374, Rails 3.2.13, Redis 2.6.11, and Resque 1.24.1. I use SQLite in development and Postgres in production.
Background jobs are frustrating if you've never dealt with them before. Over the past few weeks I've had to incorporate Redis and Resque into my projects in various ways and every bit of progress I made was very painful. There are many 'gotchas' when it comes to background workers, and documentation tends to be outdated or scattered at best.
Settting up a Container Registry with docker-gitlab
This should be used for new users to getting started with the container registry feature on docker-gitlab.
-
Docker Distribution >= 2.4
-
Docker GitLab >= 8.8.4 ( #708 must be merged)
-
TLS certificates because it should be run with https it's not designed to use it without https
#!/bin/bash | |
# Setup | |
# | |
# - Create a new Jenkins Job | |
# - Mark "None" for Source Control Management | |
# - Select the "Build Periodically" build trigger | |
# - configure to run as frequently as you like | |
# - Add a new "Execute Shell" build step | |
# - Paste the contents of this file as the command |