Anna Anks Nowak matisnape

Setting up flask app in heroku with a database

The below article will cover the intricacies of setting up databases and heroku in respect to a flask app. This is more like a memo and will have out of sequence instructions or solutions to errors so read thoroughly.

Setting up a database

You'll need the packages

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

Clone some repo (you've probably already done this step)
```
git clone [email protected]
```

Free O'Reilly books and convenient script to just download them.

Thanks /u/FallenAege/ and /u/ShPavel/ from this Reddit post

How to use:

Take the download.sh file and put it into a directory where you want the files to be saved.
cd into the directory and make sure that it has executable permissions (chmod +x download.sh should do it)
Run ./download.sh and wee there it goes. Also if you do not want all the files, just simply comment the ones you do not want.

	#!/bin/bash

	echo "Setting up and running e2e tests!"

	# Create database and seed (since we might want to include some data needed for our app to work properly like oauth clients
	rails db:setup

	# Start puma server in e2e environment on meta-address host on port 5001 in detached mode
	RAILS_ENV=e2e puma -b tcp://0.0.0.0:5001 -d

	class FBGroupMemberRemover {
	constructor() {
	this.adminText = 'Admin';
	this.removeMemberModalHeadingText = 'Remove Member';

	this.memberElementSelector = '[data-name="GroupProfileGridItem"]';
	this.memberContextMenuSelector = 'button[aria-label="Member Settings"]';
	this.removeMemberButtonSelector = 'a[data-testid="leave_group"]'

	this.removalOptions = {

	version: '2' # Version of composer
	services:
	backend: # Backend container
	build:
	context: ~/backend # Backend should be pulled by git to this location
	dockerfile: docker/Dockerfile.e2e # The location of Dockerfile, relative to context above
	depends_on: # The containers below will be resolved and loaded before backed
	- redis
	- postgres
	- frontend

	## Real app image
	FROM nginx:alpine # Remove 'as app'

	COPY nginx.conf /etc/nginx/nginx.conf

	EXPOSE 3000

	## specify node version
	FROM quay.io/netguru/ng-node:6 as builder # First 'FROM', as builder is used as reference below

	## add necessary environments
	ENV NODE_ENV staging # Set env var

	## add code & build app
	ADD . $APP_HOME # Copy / add external source to image's filesystem
	RUN yarn install # Install all dependencies for frontend app
	RUN yarn build # Compile frontend build

	{
	"workbench.colorCustomizations": {
	"terminal.foreground": "#839496",
	"terminal.background": "#002833",
	"terminal.ansiBlack": "#003541",
	"terminal.ansiBlue": "#268bd2",
	"terminal.ansiCyan": "#2aa198",
	"terminal.ansiGreen": "#859901",
	"terminal.ansiMagenta": "#d33682",
	"terminal.ansiRed": "#dc322f",

	This builds off the excellent work of @lmarkus.

	The scripts below can be used in conjunction with the Slack Emoji Tools Google Chrome extension to export emojis from
	one Slack team and import into another team.

	Original work here: https://gist.github.com/lmarkus/8722f56baf8c47045621