prisma-care / api Goto Github PK

Set up a LEMP stack on a VPS, configure the following:

• PHP
• MySQL
• Nginx
• Application environment
• TLS (LetsEncrypt) -> Domain name needed

• POST /patient/{id}/story
• GET /patient/{patientId}/story/{storyId}
• PATCH /patient/{patientId}/story/{storyId}
• DELETE /patient/{patientId}/story/{storyId}
• POST /patient/{patientId}/story/{storyId}/asset

Document PHP versions & prerequisites needed and how to develop locally.

Protect everything except for user signup by implementing the new jwt.auth middleware from #37

This is blocking everything else, too many things are breaking because of untested deploys. No refactors/features until Travis is running API tests

• User signin
• User signup
• User signout
• Patient
• Album
• Story
• Story Assets -> BLOCKED
• Connect & Disconnect users from patients

• POST /user
• GET /user/{id}

Asset names will be changed to be unique

We'll need a value for MAIL_FROM_ADDRESS in the .env file on the server.

See https://laravel.com/docs/5.4/mail#configuring-the-sender

Initialize the repo as a new empty laravel project, with https://github.com/barryvdh/laravel-cors set up.

Look into Swagger automated API docs by adding comments

See #7 for the API specification

When adding an asset to a story

• GET /patient/{id}/album
• POST /patient/{id}/album
• GET /patient/{patientId}/album/{albumId}
• PATCH /patient/{patientId}/album/{albumId}
• DELETE /patient/{patientId}/album/{albumId}

To prevent people from creating a profile for the same patient, suggest that a profile already exists, based on:

• Full name
• Date of birth
• Gender

I will write the migrations for all database tables.

Currently any user can request stuff for any patient.
Only allow requests to patients a user is connected to.

A new patient should have some content in their albums by default

Validate requests to the following resources

• Patient
• Album
• Story

Username/Password based API authentication

Demoable frontend/backend communication - A static user creates a story with a picture as a media type

To be implemented:

• POST /patient/{patientId}/story
• POST /patient/{patientId}/story/{storyId}/asset

http://www.php-fig.org/psr/psr-2/

Should be ready for next release @siimonco

Create the needed laravel controllers and fill them with the required queries for the api

The production application should always reflect the master branch.
Continuous integration (#5) should deploy to the server (#14) on merge.

Add some improvements to help them debug

They're just in the public folder. Store these somewhere else and serve based on access rights, once we have authentication.

"Patient" serves as a container for albums and stories

• POST /patient
• GET /patient/{id}