Backend delpoyed at api-omega.herokuapp.com
To get the server running locally:
- Clone this repo
- npm install to install all required dependencies
- npm start to start the node environment
- npm run server to start the local server
- npm run test to start server using testing environment
- Oauth 2.0 takes care of authentication, user management, and security, all in one. It offers simplicity, and accessibility allowing users to use their already created accounts from other major services.
- Node and Express are widely used, rich frameworks that works with many services, keep data in native JSON, are well documented with a supported community. Provide a clean way for us to implement CRUD actions to our database.
- Postgres with Knex gives us data persistence, uses relational data modeling, while providing a SQL-esque API.
- Jest, SuperTest will be used to test our database, and to weed out edge cases. Morgan will provide logging to make development easier in case bugs occur. Helmet for securing our headers.
🚫This is a placeholder, replace the endpoints, access controll, and descriptioin to match your project
Method | Endpoint | Access Control | Description |
---|---|---|---|
GET | /organizations/:orgId |
all users | Returns the information for an organization. |
PUT | /organizations/:orgId |
owners | Modify an existing organization. |
DELETE | /organizations/:orgId |
owners | Delete an organization. |
Method | Endpoint | Access Control | Description |
---|---|---|---|
GET | /users/current |
all users | Returns info for the logged in user. |
GET | /users/org/:userId |
owners, supervisors | Returns all users for an organization. |
GET | /users/:userId |
owners, supervisors | Returns info for a single user. |
POST | /users/register/owner |
none | Creates a new user as owner of a new organization. |
PUT | /users/:userId |
owners, supervisors | |
DELETE | /users/:userId |
owners, supervisors |
🚫This is just an example. Replace this with your data model
{
id: UUID
name: STRING
industry: STRING
paid: BOOLEAN
customer_id: STRING
subscription_id: STRING
}
{
id: UUID
organization_id: UUID foreign key in ORGANIZATIONS table
first_name: STRING
last_name: STRING
role: STRING [ 'owner', 'supervisor', 'employee' ]
email: STRING
phone: STRING
cal_visit: BOOLEAN
emp_visit: BOOLEAN
emailpref: BOOLEAN
phonepref: BOOLEAN
}
🚫 This is an example, replace this with the actions that pertain to your backend
getOrgs()
-> Returns all organizations
getOrg(orgId)
-> Returns a single organization by ID
addOrg(org)
-> Returns the created org
updateOrg(orgId)
-> Update an organization by ID
deleteOrg(orgId)
-> Delete an organization by ID
getUsers(orgId)
-> if no param all users
getUser(userId)
-> Returns a single user by user ID
addUser(user object)
--> Creates a new user and returns that user. Also creates 7 availabilities defaulted to hours of operation for their organization.
updateUser(userId, changes object)
-> Updates a single user by ID.
deleteUser(userId)
-> deletes everything dependent on the user
In order for the app to function correctly, the user must set up their own environment variables.
create a .env file that includes the following:
🚫 These are just examples, replace them with the specifics for your app
* STAGING_DB - optional development db for using functionality not available in SQLite
* NODE_ENV - set to "development" until ready for "production"
* JWT_SECRET - you can generate this by using a python shell and running import random''.join([random.SystemRandom().choice('abcdefghijklmnopqrstuvwxyz0123456789!@#\$%^&*(-*=+)') for i in range(50)])
* SENDGRID_API_KEY - this is generated in your Sendgrid account
* stripe_secret - this is generated in the Stripe dashboard
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.
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.
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.
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.
- 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.
These contribution guidelines have been adapted from this good-Contributing.md-template.
See Frontend Documentation for details on the fronend of our project.