Skip to content

Instantly share code, notes, and snippets.

View codenamegary's full-sized avatar

Gary Saunders codenamegary

11 followers · 2 following
View GitHub Profile
@notxarb
notxarb / subnets.txt
Last active May 12, 2016 21:35
Pagodabox CIDR addresses
75.126.19.144/28
75.126.23.16/28
184.173.69.128/28
50.97.157.0/26
75.126.59.16/28
@zaherg
zaherg / install.md
Last active October 18, 2020 17:45
a small tips to install latest nginx , php 5.5 & laravel 4.1 since that Laravel 4.1 has been released, i have removed the line which explain how to install laravel from dev branch using composer.

Creating Your Laravel & nginx Server

We will install Larave 4.1 with PHP5.5 & Latest nginx on Ubuntu 12.04.3 x64.

updating your system

apt-get update && apt-get upgrade
adduser [username]
usermod -aG sudo [username]
apt-get -y install git
@codenamegary
codenamegary / dev-ops-resource-needed.md
Created September 8, 2014 19:19
Dev-ops Resource Needed

#SKILLED DEV-OPS RESOURCE NEEDED FOR TEMPORARY / PART-TIME CONTRACT

##BACKGROUND

We are a small development team focused on mostly LAMP (or LEMP) based application development. We have traditionally deployed to hosting solutions using a PaaS like PagodaBox or FortRabbit. Some of our internal and client projects are beginning to grow and we need to focus on moving our hosting out to a more robust solution using Amazon, SoftLayer, BlueMix (CloudFoundry) or some other provider of your choosing.

Applications are entirely custom and built on either Laravel or Symfony, there is no Wordpress or Joomla or any other CMS involved in any of the existing projects.

Currently, we are a small team of sales and developers. We are familiar with all of the technologies involved in deploying to Amazon through Elastic Beanstalk and other facilities but do not have the will nor manpower to automate and assemble the process as much as we'd like. We are looking to augment and fill the dev-ops gap in our skills with a person who

@swaminator
swaminator / intro.md
Last active November 2, 2022 06:32 — forked from gwryssekk/intro.md
AWS Amplify - Converting Existing Monorepos to the New Supported Model

It was recently announced that AWS Amplify now has built in support for monorepos. Customers who had previously used manual commands in their applications build settings are now able to trigger builds in various apps can now consolidate all of their app settings in a single file at the root of the repository.

Let's assume you have two Amplify apps - app1 and app2 that belong to your monorepo.

  1. If you have an amplify.yml file in your repo, rename it to amplify-old.yml to back it up.
  2. Go to the app1 in the Amplify console, App settings > build settings and update your buildspec to the new version. For example, a simple app with the following build spec:
version: 1
frontend: