Skip to content

labs14-lambda-app-store/FE2

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

804 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Lambda App Store

logo

Contributors:

Jeff Lapp Chris Petito James Starks Victor Ngyuen Joshua Disney Kayla Crow


MIT React Redux auth0 Material UI

Project Overview

Trello Board

Vision Doc

UX Design files

Feature Canvases App Gallery Admin Dashboard Student Dashboard Landing Page Subscription

"Lambda App Store" is a Lambda Labs project built for Lambda School to create a central place to view and use the apps that our awesome students create.

5️⃣ Key Features

  • Students can create a profile to submit their completed/deployed apps
  • Admins can approve or deny student app submissions
  • Visitors can browse Lambda apps by featured/category/trending/new/key word
  • Visitors can access free student apps/free versions of student apps
  • Visitors can purchase a subscription for full access to premium apps

Tech Stack

Front end built using:

  • React
  • React Hooks
  • Redux

Front end deployed to netlify

Back end built using:

  • Node.JS
  • PostgreSQL
  • Express

Back end deployed to heroku

APIs

1️⃣ Authentication API here

All accounts use Auth0 for authentication. Auth0 provides us with authentication & authorization services and help keeps our app secured.

2️⃣ Payment API here

Stripe API We intend to implement Stripe into our app in a future product cycle. This will allow us to include the ability to subscribe and pay for access to premium apps.

3️⃣ Environment Variables

In order for the app to function correctly, the user must set up their own environment variables. There should be a .env file containing the following:

* REACT_APP_CLOUDINARY_URL - Our personal URL that we upload the images to.
* REACT_APP_CLOUDINARY_UPLOAD_ PRESET - Consists of upload parameters centrally managed using the Admin API.
* REACT_APP_OAUTH_CLIENT_ID - Is assigned to you by Auth0 upon account creation.
* REACT_APP_OAUTH_DOMAIN - Is assigned to you by Auth0 upon account creation.

4️⃣ Content Licenses

Image Filename Source / Creator License
Lambda_Avatar_Red.jpg Lambda School UNCERTAIN
Lambda_Avatar_White.jpg Lambda School UNCERTAIN
Lambda_Logo_white.png Lambda School UNCERTAIN
Lambda_Logo.png Lambda School UNCERTAIN
lambda-student.png Lambda School UNCERTAIN
LambdaLandingUX-Original.png Lambda School UNCERTAIN
LambdaLandingUX.png Lambda School UNCERTAIN

5️⃣ Testing

For testing, we are using Cypress.io. Cypress.io responds and reloads in real time, automatically waits for the DOM to load before testing, the errors are easy to debug, and the documentation is clear.

6️⃣ Installation Instructions

Run yarn install after cloning.

Other Scripts

* build - creates a build of the application
* start - starts the production server after a build is created
* test - runs tests in **tests** directory \* eject - copy the configuration files and dependencies into the project so you have full control over them
* eject - moves create-react-app’s config files and start/build/test scripts into the app directory.

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct. Please follow it in all your interactions with the project.

Issue/Bug Request

If you are having an issue with the existing project code, please submit a bug report under the following guidelines:

  • Check first to see if your issue has already been reported.
  • Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
  • Create a live example of the problem.
  • Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.

Feature Requests

We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.

Pull Requests

If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.

Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.

Pull Request Guidelines

  • Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  • Update the README.md with details of changes to the interface, including new plist variables, exposed ports, useful file locations and container parameters.
  • Ensure that your code conforms to our existing code conventions and test coverage.
  • Include the relevant issue number, if applicable.
  • You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.

Attribution

These contribution guidelines have been adapted from this good-Contributing.md-template.

Documentation

See Backend Documentation for details on the backend of our project.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors