Skip to content

Instantly share code, notes, and snippets.

View artificialarea's full-sized avatar

Sacha Sedriks artificialarea

View GitHub Profile
@artificialarea
artificialarea / Node-pg-and-heroku-ssl.md
Created March 22, 2021 19:38 — forked from bookcasey/Node-pg-and-heroku-ssl.md
How to fix Node/pg version compatibility issues, and set the correct SSL options for heroku

How to fix common Node/pg compatability issues locally and on Heroku

Certain versions of the pg library do not play nice with certain versions of node.

The following combinations are known to work:

  • Node v12 and pg@7
  • Node >=v14 and pg@8

Additionally, different versions of pg on heroku requires certain ssl options to be set certain ways.

Checkpoint Assignments for Thinkful Capstone II

Team: Michaela Bateman, Jerrad Moon, Jonathan Cochran, Sacha Sedriks


1. Product Proposal

per assignment

Artsy

Capstone Project Title (to do now)

One line description of what this app is doing and who is it for

1. Working Prototype (to do later)

(Example) You can access a working prototype of the React app here: https://your-app-client.herokuapp.com/ and Node app here: https://your-app-server.herokuapp.com/

2. User Stories (to do now)

This app is for two types of users: a visitor and a logged-in user

src: https://github.com/sparkrnyc/sparkr_general_docs/wiki/What-are-Prototype,-POC,-Alpha,-Beta-and-MVP

Agile is an iterative way to develop and release very quickly many small versions and grow your application by adding new features in each new version or release. As your application grow bigger and more mature, your business also grows and keeps pace with the development of the application. In other words, business processes and application grow parallel and dependent on each other.

Releases are named or referred to often by using so-called [[Semantic Versioning|http://semver.org/]], which looks like v0.1.2. You see 3 numbers that represent versions for MAJOR.MINOR.PATCH updates:

  • The first number refers to MAJOR releases, in this example '0'. Major refers to releases from 0 (Prototype to Beta) to Release (1 to n), and incrementally to versions that change the User Experience or the application drastically.
  • The second number refers to MINOR releases, in this example '1'. Every scrum is in principle

https://html-108.vercel.app ... https://github.com/artificialarea/html-108-app

I have some concerns that although the changes to state and subsequent re-renders are as I intended, I suspect I may be erroneously mutating state in the process. I discovered only by accident that if I commented out the entire block of code within setState() and just left it as an empty setState({ }) shell, the state still changed and re-rendered as intended... what the fuck?!? I've committed and deployed it in that state for discussion. Also left a console.log(this.state) in the render() to reflect change in state.


  • Re: handleBeatChange (permalink)
  • if you click on the 'beat-pads' it does what it should, re-rendering beats toggle on/off based on new state. (btw, no audio yet)

HTML-108: virtual drum machine

v1.o MVP

Inspired by electronic/techno/house music and the instruments of that era, the HTML-108 virtual drum machine emulates aspects of the seminal Roland TR-808 by offering a (considerably scaled down) web-based version of this rhythm instrument.

The HTML-108 enables people to:

  1. create 4 measure / 16 beat loops with a select group of sounds
  2. save and store their rhythm loops into a collection (if a registered user)
  3. download their loops as audio files.