ashishkapoor / ecommerce-blog-api Goto Github PK

We've a config.json which has fields for all of the database credentials. We should push this via Environment or Secret Manager like Vault.

Tables for:

• User
• Product
• Order
• Cart
• Blog

We should also add containerisation support via Dockerfile and docker-compose.yml for Docker for respective alternatives for Kubernetes.

We can then build a CI/CD pipeline around this. What is you suggestion on this?

Api should be able to:-

Pseudo:

• Register: Post /api/users,

• Login: Post /api/logins,

• Hashed password

• Using JWT while hashing passwords in the password field.

• Getting current user.

Hi!

I just checked out the code, and it seems that while we do have a routes folder, we use a separate structure inside app for the api routes. This seems a bit inconsistent.

Furthermore, we should also separate logic, if complex, from routes, hence perhaps you can have general router for the api, pointing to the individual views for the CRUD for each model.

Let me know about your thoughts.

Api should be able to:-

• Forgot Password: (optional),
• Storing secrets in environment variables (optional)
• Protect Routes with authentication middleware.
• Logging out users.
• Role based authentication.

Hi! Great work on the API btw.

I was just curious of what the application is about and maybe the documentation itself wasn't making it obvious to me. While there are certainly a lot of keywords, I think mostly they lack the context in the Readme.md.

I think Readme should contain a generic section, focusing on following sections:

1. What is E-Commerce Blog API?
2. Getting started.
3. How to contribute?

1. Products ✅
2. Shopping Cart ✅
3. Users ✅
4. Authors ✅
5. Posts ✅