let's use pipenv for uniformity across all our python projects

Originally posted by @aibunny in #153 (comment)

I recently tried setting up the project for local development and upon following the steps and running the backend I met issues with missing env variables.

I would suggest adding a .env.example file to the project for easier setup by contributors. The example env file can contain values only used on the development machine.
The documentation could be modified to ask whoever's locally setting up the project to rename .env.example to .env.
Since the file is in .gitignore, it'll only affect the one setting up the project on their machine.

Phone number is not showing on the admin side. If you want to update phone number, the phone number field isn't there. @hellen-22 can check it

User Attributes
Unique ID(UUID)
From the mvp the user id and most transaction ids needed to be unique

It's hard to make a first-time contribution because there are no directions on how to create a virtual environment

I'm going to write the step-by-step directions

I added the directions to set up the env but I've realized there's a spacing error after the issue has been closed

I'll add space to make the file more legible

API throttling is the process of limiting the number of API requests a user can make in a certain period. An application programming interface (API) functions as a gateway between a user and a software application.

While there are various algorithms for API throttling, here are the basic steps in any API throttling algorithm:

A client/user calls an API that interfaces with a web service or application.
The API throttling logic checks if the current request exceeds the allowed number of API calls.
If the request is within limits, the API performs as usual and completes the user’s task.
If the request exceeds the limit, the API returns an error response to the user.
The user will have to wait for a pre-agreed time period, or pay to make any more API calls.

          I would recommend using Pipenv

Originally posted by @JimmyTron in #153 (review)

using non-native auth services to authenticate users to the application.

The authentication service makes sure that information is accessed only by users who have the access permission or right. The SpaceYaTech OpenSource CMS implements two forms of Authentication - JWT Authentication and Oauth 2.0 for Authentication and Authorization of Users within the Application. Here is a detailed look into the potential implementation of both forms of Authentication forms:
Read more here

Tracking daily user data by selecting some basic information about people who visit the app including those who successfully logged in, logged out or who logged in failed. or simply get the overall statistics of those who visited.

To use the Djoser library to handle the user, accounts, and authentication
Djoser is a popular Django package that provides a set of ready-to-use REST API endpoints for user authentication and registration.

Add a .gitignore file
The pycache folder contains compiled binaries that should be ignored

Originally posted by @nyandika in #19 (review)

These are the environment settings for the project.
To help set a standard for transferability of the project.

The environ file for the project's SECRET KEY is missing. Running migrations would throw an error of missing SECRET KEY.

Filter the draft posts from appearing on the post list
I created some posts and had most of them as drafts but when i checked the post listing they all appeared which should not be the case

To Reproduce
Steps to reproduce the behavior:

1. login and create a new post
2. mark the post as Draft
3. Query the posts list
4. See the issue?

Expected behavior
A draft post should not display on the posts listing
Screenshots

Hi there,

^{@sangkips once the environment settings issue is resoled by @wanjirumurira and @mamu234}

pull the changes and create an empty project.

Create a new branch and push it upstream.

• Don't forget to open a pull request 😉

Having all secrets saved in .env file
These should include database username and password and any other key that isn't supposed to be visible
`Can this be put in an env file instead of in code?

_Originally posted by @nyandika in https://github.com/SpaceyaTech/Team-Rio-Django/pull/48#discussion_r1030619058_`

Writing tests for the models. Setting precedence for future models.

Describe the bug
Sending a POST request on the 'categories' endpoint with a category name creates a new category. This happens even on an anonymous session without having provided login credentials or a valid token.

To Reproduce
Steps to reproduce the behavior:

1. Go to the 'categories' URL. If running locally, go to 'http://localhost:8000/categories'
2. Create a POST request with an input called 'name' and a value of any category name
3. Submit the request

Expected behavior
The endpoint should reject the request and prompt for authentication credentials before creating the new category.

Screenshots

The screenshot shows that the category is successfully created in an unauthorized environment.

Desktop (please complete the following information):

• OS: Linux
• Browser [Brave]
• Version 1.56.14 Chromium: 115.0.5790.114 (Official Build) (64-bit)]

Looking at this action and this one it seems to me they are running essentially the same steps.
Wondering if there is a reason why we have two of them

Pillow is an image library that we shall use to manipulate our images.
We need to tell Django which URL to use for serving the media files and also specify the root directory where our images will be stored.

Describe the bug
Running 'python manage.py makemigrations' results in a duplicate migration being generated every time for the user model in the accounts app.

To Reproduce
Steps to reproduce the behavior:

1. Run 'python manage.py makemigrations'
2. A new migration for the user model in the accounts application is created.
3. Run 'python manage.py makemigrations'.
4. A similar migration with a different verification ID is created.

Expected behavior
Only one migration for each specific change should be created.

Screenshots

Desktop:

• OS: Linux Mint
• Browser: Chrome
• Version: 117

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Being a core service required for this CMS project the blog app is a timely implement.
BlogService (Fetch blogs, create blogs, update blogs, delete blogs)(posts/1)

Creation of the blog app
some of the highlighted features from modeling the blog app that were agreed upon are as follows:

• Blog Posts -
  • Unique Id(PK),
  • Post title
  • Description (small section which highlights the blog post)
  • Content (main content of the post)
  • UserId(FK)
  • Status
  • Date_Created
  • Date_updated
  • Date_Published
  • CategoryID (FK)
  • Images Urls (Post can have multiple multimedia files)
  • Number of Views
• Reactions (Set of ReactionsLike or upvote or a downvote)
• Comments

Here is a sample blog from the labs
credits: @Fredrick-Waihenya

    Since the pychache files are already in a commit adding gitignore here is not enough, you have to clean the branch up so the files are ignored

Do the following:

git rm -r --cached .
git add .
git commit -m "<commit_message_addressing_cleanup>"

Originally posted by @nyandika in #19 (comment)

**The blog comments should have the following fields : **

• id( unique id)
• body -the content of the comment
• user id (FK) -links the comment to a specific user who created/ commented
• post id (FK) -link the comment to a specific post
• date created
• date flagged
• List of Reactions

Additional context
Add any other Functionality that seems necessary
this is a screenshot of Medium

Discussed in #12

creating a model for the blog post

Choosing a database for the project

          We'll need to include permisions that only allow account owners to list their accounts

• Restrict only acount owners and admins to list accounts

Originally posted by @JimmyTron in #123 (comment)

Drafts Page
A page where the blog owner get to view their draft posts

Custom permission IsBlogOwner
Make a custom permission class to only allow for the blog owner to view their draft posts.
This should restrict other users from viewing their drafts.

Find a better way to have phone numbers handle international phone number formats such as +1 777777. This way it will be better to handle users' phone numbers globally.

Featured Stori

Add a featured field to make it easy to flag Stories that should be featured on the website

Featured Field:

Checkbox or boolean input to designate if the Stori should be listed as featured on the website.

The pre-dev branch to contribute to as directed by the contributions.md is missing.
The contribution guide suggests:
git checkout -b <issue-number-title> pre-dev

What happens after running:
$ git checkout -b issue-x-do-something pre-dev fatal: 'pre-dev' is not a commit and a branch 'issue-x-do-something' cannot be created from it

This leaves contributors to branch from the main branch which ideally should only be used for releases.

What if we had all our tests in one place insteadvof having them on idividual apps?
What would be the merits of demerits of doing so?

Originally posted by @JimmyTron in #40 (comment)

  Substituting a custom User model - it gives the chance to use the Django User Attributes(email, username, firstname, lastname, email), considering our model requires the Django user attributes. We will just need to add our extra fields(gender, account status, phone number e.t.c)

Originally posted by @hellen-22 in #26 (comment)

Description:
The current method of listing application dependencies in a text file is proving to be challenging to track and manage effectively. I suggest implementing a more managed approach to handle dependencies, such as utilizing a package manager or dependency management tool.

Reactions

• id(unique id)
• type -( up vote/down vote or like/dislike)- enumerated value
• user_id (FK) - links the reaction to a specific user who created it
• post_id
• comment_id
• date created,updated

The reactions are in a way used to communicate emmotions without having to acctually reply to the blog or comment

auto populate the slugfield from title in the blog model

creation of post model