Skip to content

Instantly share code, notes, and snippets.

View gabeklein's full-sized avatar

Gabe Klein gabeklein

  • Miami, FL
  • 07:46 (UTC -04:00)
View GitHub Profile

Sales reporting app questionare

Sales Reporting App: thoughts and opinions.

Naturally, when beginning to stub out any new project, we usually come from a place of familiarity. That being said, while I couldn’t say most other stacks would not fit this project, I’d go with Node.js on the backend, with React.js in the browser. Probably partiality on my part, but one of the larger advantages of any stack for a given developer, is how quickly they can get up and running with it.

For React though, it has a good thing going for it, in that it also works on native mobile. This certainly couldn't hurt, while opening the door on growth into other platforms. Because it’s a pretty straight forward transition, between React and React Native code, developers not even familiar with native could get things done with the same basic principles at hand. This means you have more room to up-sell and enhance the project in a meaningful way, with the same team.

As for the database. I would tempted to say a NOSQL, for instance

FROM mhart/alpine-node:10 as base
WORKDIR /usr/src
COPY . .
# copy all the source stuff, excepting everything in .dockerignore
RUN yarn
# creates node_modules/ populates with dependancies
RUN yarn build
#creates live/ populates with transpiled code
RUN yarn --production
#(I assume) recreates node_modules/ without or deletes build dependancies
04e1498c066197a229f28092c106bb40ade9006ee196f88e7c274d078b91bf5a0daf17f396d4eb49e4256c4725efd29bdae47a277e71f9063ca77c294dee9d13e4