-
Copy the
generate.py
script to your machine. -
Update the
BUCKET_NAME
andKEY_NAME
values in the script as needed. -
Run
python generate.py
. It will spit some output like the following:
$ python3 generate.py
import { Injectable } from '@angular/core'; | |
import { Entity } from '../enums'; | |
import { FleetPosition, Player } from '../models'; | |
import { StorageService } from './storage.service'; | |
@Injectable({ | |
providedIn: 'root' | |
}) | |
export class ApiService { |
#!/usr/bin/env python3 | |
import json | |
import os | |
import sys | |
from configparser import ConfigParser | |
from datetime import datetime | |
from pathlib import Path | |
import boto3 |
""" | |
Usage: | |
Make sure that redis is running on localhost (or adjust the url) | |
Install uvicorn or some other asgi server https://asgi.readthedocs.io/en/latest/implementations.html | |
pip install -u uvicorn | |
Install dependencies |
#!/bin/sh | |
# This script will be executed after commit in placed in .git/hooks/post-commit | |
# Semantic Versioning 2.0.0 guideline | |
# | |
# Given a version number MAJOR.MINOR.PATCH, increment the: | |
# MAJOR version when you make incompatible API changes, | |
# MINOR version when you add functionality in a backwards-compatible manner, and | |
# PATCH version when you make backwards-compatible bug fixes. |
language: python | |
python: | |
- "2.7" | |
- "3.3" | |
- "3.4" | |
- "3.5" | |
- "pypy" | |
- "pypy3" |
#!/usr/bin/env bash | |
############################################################################### | |
# | |
# Automatically detects a merge on to master from a gitflow-style release | |
# branch, e.g. release-1.1.1-alpha. If the merged branch matches, the major, | |
# minor and patch versions are determined and a new release tag is created | |
# locally. If remote origin exists, this tag will automatically be pushed. | |
# | |
# In addition to creating a tag, the release branch will automatically be | |
# merged into the develop branch. If the branch has already been merged this |
// check version | |
node -v || node --version | |
// list locally installed versions of node | |
nvm ls | |
// list remove available versions of node | |
nvm ls-remote | |
// install specific version of node |
Typing vagrant
from the command line will display a list of all available commands.
Be sure that you are in the same directory as the Vagrantfile when running these commands!
vagrant init
-- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.vagrant init <boxpath>
-- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64
.vagrant up
-- starts vagrant environment (also provisions only on the FIRST vagrant up)