Review the new DB Proposal

Right now we are not updating the image when the user is created, must add this line of code on the get_or_create user.

We should have a central server that serves makes requests to the intra. This is so we can better keep track of how we are using the tokens. With a module we can't keep track of all the requests made and therefore we can run into "To Many Requests" issues. Having a single server which makes the requests would remedy this issue.

Create a Home Page route for the website.

Welcome Page

Create the CronJob Table which will register on our database all the syncronizations with intra
The crontab is just for metadata an for data analysis

Create the Project Model according to the DB Demo Reference we agreed upon.
The DB Demo Reference is available on the home page wiki or in Notion.

Submit a PR with your Code, well commented, indicating any code which might be ambiguous or abstract.

• It's a good idea to implement the str method already so we can access Objects from this instance and the return is not garbage, but a well understood string.

It's painful to wait for all the relations to update.

We should implement for example a way to update only the user-project relations
Or cursus-project relations.

Implement the Abstract User that we discussed.

For this to work you should rollback all your migrations and drop (prune) your database.

Let's also add a field: is_admin, change the username to intra_username, and the USERNAME variable as well, let's also try to delete the username field from the migration, we don't want an unused field on the db

Remove from view the hard coded redirect

Check that we have correctly done the cascade deletion for our Projects, Skills, Cursus & Users

https://github.com/pulgamecanica/42Portfolio/blob/8dcb5e2bcd77cc03f611e413d11bc6ee1581f9b9/backend/portfolio42_api/views.py#LL78C8-L78C8

Implement a session host parameter for the session, to avoid session attacks with stolen sids.

We must allow a different port to be exposed for the PostgreSQL container.

Currently the image will decide which port to use, by default 5432.

Tackle this once the Models are compleated.

Add all the modules to the Django Admin Interface.

Update wiki with new envs

In the api we don't give the id for each project when making a request to /api/projects

Create the Skill Model according to the DB Demo Reference we agreed upon.
The DB Demo Reference is available on the home page wiki or in Notion.

Submit a PR with your Code, well commented, indicating any code which might be ambiguous or abstract.

• It's a good idea to implement the str method already so we can access Objects from this instance and the return is not garbage, but a well understood string.

Consume the Django API with axios standard configuration

I tried to create a PR, but I don't have access permissions to the wiki repo

Save the SVG with a n expiration date.
Consider Redis for session cache

Resolve username confilct,
the user still has a field username, I can't understand why, we should look into this.
The only username should be intra_username...

Its conflictive because it's also unique on the DB so the db will need to have different usernames foe each user, we don't even want usernames we are using intra_username for that

Implement Django rest framework

Finished at should be nullable:

default=None, blank=True, null=True

Add SEO Tags, For better link share experience

Analise the meta tags, and add all relevant tags to the application.

For instance, mobile scale, title, description, tags, og; etc.

Maybe we can also add the animate.css library as a package.

Define what date we will ask from the user and what we will save.

Define how we erase the User Data and the limit

New Django Application

The wiki should explain what the sub-commands are and what they update. It can also have a technical section which explains how it updates the DB.

Identify the oAuth import module which fits best with our application.
There should be a strategy available to implement for the 42Api and Django, also find about that.

Finally implement the oAuth module, for normal users.

Create the decorators to guard the endpoints which need authentication.

Create the privacy policy

Change the solo attribute from the project to the project users
Projects itself might be solo or not, the user is the one deciding if he takes the project solo or not (when he is given the option ofcs)

Learn about European law & cookies

Create the Relations according to the DB Demo Reference we agreed upon.
The DB Demo Reference is available on the home page wiki or in Notion.

Indicate correctly the Relations with the Django relations module [ManyToMany, OneToMany, OneToOne, ManyToOne]

Submit a PR with your Code, well commented, indicating any code which might be ambiguous or abstract.

If you have any questions about the relations let me know

• ProjectCursus
• ProjectUser
• ProjectUserCursus
• CursusUser
• CursusSkill
• CursusUserSkill

• It's a good idea to implement the str method already so we can access Objects from this instance and the return is not garbage, but a well understood string.

Integrate Axios with React

In order to submit the PR for this, we should have a working Singleton, and you should just be able to do:

axios.get(route) --> Returns a promise response
axios.post(route) --> Returns a promise response

Create the Cursus Model according to the DB Demo Reference we agreed upon.
The DB Demo Reference is available on the home page wiki or in Notion.

Submit a PR with your Code, well commented, indicating any code which might be ambiguous or abstract.

• It's a good idea to implement the str method already so we can access Objects from this instance and the return is not garbage, but a well understood string.

Discussion about REST API Settings, should it be 100% read only? I think so...

Create the Intra Settings table

This Table will contain the encrypted intra credentials, this will be used to sync our data with intra.

For now we are using the .env and will continue to do so until this is created.

Define an annonimization data and implement this logic.

Create the User Model according to the DB Demo Reference we agreed upon.
The DB Demo Reference is available on the home page wiki or in Notion.

Submit a PR with your Code, well commented, indicating any code which might be ambiguous or abstract.

• It's a good idea to implement the str method already so we can access Objects from this instance and the return is not garbage, but a well understood string.

• Also we can just use the username instead of intra_username, so it's not very redundant, it's your choice ;)

Create a testing units for each model

• User
• Skill
• Project
• Cursus

Define React Pages:

Landing Page.

Welcome.

Legal & Privacy.

CV Generated Public page

SVG Rendered Page

Configurations Page.

Create a Base Class to implement in our models.

Base class will help us implement the updated_at attribute.

We can also implement the was_updated_today method on this class.

Later we can implement actions to update the elements with fetch calls to intra.

We need Tests for the relations and the models.

We want to limit our REST API responses to a max limit of 100 just like intra. Responses can't take much time and should not return so much data.
Currently the projects endpoint had loaded the intra projects with the sync command, it's around ~1500 projects
The REST API is returning all the projects in one request and this produces a buggy REST API on the frontend and it's more data than what the browser can handle so it might ask the user to close the tab because the page is not responding.