danielkanangila / labspt12-express_groomer-teamc-be

express-groomer-be

For steps on how to work with this repository please see here

Project

You can find the deployed project Here.

Contributors

Ryan Barnhill	Lydie Cherilus	Daniel Kanangila	Ken Ridenour

Key Features

Connect groomers with pet owners

Release 1

• FE and BE: completed
  • Account creation and login
    • Users should be able to create an account based on their persona. Account type for the groomer and a seperate account type for the client.
  • Search Groomer Database
    • Groomers should be able to set up profile. Based on the groomer profile, users will be able to search groomers.

Release 2

• FE: in progress
  • Appointments/Scheduling: in progress
    • Groomers should be able to manage the request from users, schedule appointments, and have a way to manage their appointments
  • Enhanced Groomer Search: in progress
    • Using the mapbox API, provide a way for users to search within an area: completed
    • The user should be able to enter an address, provide a search radius, and the output will be a list of groomers based on the criteria entered: in progress
    • The user should also be able to pin the groomers or save for later: not started
• BE: completed
  • Appointments/Scheduling
  • Enhanced Groomer Search

Release 3

• FE: in progress
  • Payment Services: not started
    • Payment integration with Stripe.
  • Groomer Rating System: in progress
    • Users will be able to rate groomers based on the experience they had. This rating should be 1-4 stars and an option for the user to provide comments based on thier experience.
• BE: completed
  • Payment Services
  • Groomer Rating System

Back end deployed to Heroku

Back end built using:

• Node
• Express
• Nodemon
• Knex
• Dotenv
• Helmet
• Cors
• Morgan
• Okta/jwt-verifier
• Axios
• Swagger-jsdoc / Swagger-ui-express
• Cookie-parser
• Faker
• Eslint
• Jest
• Supertest

APIs

Authentication API here

Swagger Documentation

Payment API here

Stripe

Getting Started

Enviornment Variables

• PORT - API port (optional, but helpful with FE running as well)
  • The following ports are whitelisted for use with okta
    • 3000
    • 8000
    • 8080
• DATABASE_URL - connection string for postgres database
• OKTA_URL_ISSUER - The complete issuer URL for verifying okta access tokens. https://example.okta.com/oauth2/default
• OKTA_CLIENT_ID - the okta client ID.

See .env file for example values

Setup postgres

There are 3 options to get postgresql installed locally [Choose one]:

1. Use docker. Install for your platform
   • run: docker-compose up -d to start up the postgresql database and pgadmin.
   • Open a browser to pgadmin and you should see the Dev server already defined.
   • If you need to start over you will need to delete the folder $ rm -rf ./data/pg as this is where all of the server data is stored.
     • if the database api-dev was not created then start over.
2. Download and install postgresql directly from the main site
   • make note of the port, username and password you use to setup the database.
   • Connect your client to the server manually using the values previously mentioned
   • You will need to create a database manually using a client.
   • Make sure to update the DATABASE_URL connection string with the values for username/password, databasename and server port (if not 5432).
3. Setup a free account at ElephantSQL
   • Sign up for a free Tiney Turtle plan
   • copy the URL to the DATABASE_URL .env variable
   • make sure to add ?ssl=true to the end of this url

Setup the application

• create your project repo by forking or using this as a template.
• run: npm install to download all dependencies.
• confirm correct env variables in your .env file.
• run: npm run knex migrate:latest to create the starting schema.
• run: npm run knex seed:run to populate your db with some data.
• run: npm run tests to confirm all is setup and tests pass.
• run: npm run watch:dev to start nodemon in local dev enviornment.

Make sure to update the details of the app name, description and version in the package.json and config/jsdoc.js files.

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

• 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.

Documentation

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