Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ FEATURE ] Latest API endpoint #259

Open
FlavioAdamo opened this issue Sep 13, 2023 · 11 comments
Open

[ FEATURE ] Latest API endpoint #259

FlavioAdamo opened this issue Sep 13, 2023 · 11 comments
Assignees
Labels
backend enhancement New feature or request good first issue Good for newcomers

Comments

@FlavioAdamo
Copy link
Member

FlavioAdamo commented Sep 13, 2023

Is your feature request related to a problem? Please describe

I have noticed that our current API system lacks the capability to retrieve the latest APIs that have been added to our platform. This presents a significant challenge for users who want to stay up-to-date with the latest additions.

Describe the solution you'd like

I would like to request the implementation of a new endpoint in our API system that allows users to retrieve the latest APIs added to our platform. This endpoint should return a list of APIs sorted by their addition date, with the most recent ones appearing first. To facilitate this, we will also need to modify our API model to include a 'date' field that tracks when each API was added to the platform.

Additional context

Adding this feature will greatly enhance the user experience and make it easier for developers and other users to discover and integrate the latest APIs into their projects. It will also improve the overall usability of our platform by providing a clear and concise way to access up-to-date API information.

https://github.com/Exifly/ApiVault/tree/feat_feedback_panel

@FlavioAdamo FlavioAdamo added enhancement New feature or request good first issue Good for newcomers backend labels Sep 13, 2023
@gdjohn4s
Copy link
Member

Linked feature branch to the issue

@zackhamr
Copy link

Hey, i am gonna take a crack at this unless someone has already start on it.

This is my first time contributing to an open source project so any pointers will be greatly appreciated.

@FlavioAdamo
Copy link
Member Author

FlavioAdamo commented Sep 14, 2023

@zackhamr Sure, Issue assigned!
If you need any help feel free to reach me :)

@gdjohn4s
Copy link
Member

@zackhamr Hi, any news about the issue?

@zackhamr
Copy link

@gdjohn4s not much haven't had a ton of time, and had some issues getting the docker containers going

@zackhamr
Copy link

gonna spend some time on it later today after I finish a couple applications

@gdjohn4s
Copy link
Member

no problem 😄

@zackhamr
Copy link

So im having issues with docker (my first time using it), the error I get when I run compose is

Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:9001 -> 0.0.0.0:0: listen tcp 0.0.0.0:9001: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

and looking online I found that tends to mean that port is being used.

So I tried changing the port and began getting issue with changing postrges permissions
changing permissions of '/var/lib/postgresql/data/pgdata/': Operation not permitted

which I believe is the cause of some other warnings am i getting
django.db.utils.OperationalError: could not translate host name "database" to address: Temporary failure in name resolution

has anyone else dealt with this or know how to fix this?
any other docker tips would also be helpful. Been going through some youtube tutorials which are helpful but not really for my situation .

@gdjohn4s
Copy link
Member

It's strange how your docker is trying to expose port 0 on the right side:
0.0.0.0:9001 -> 0.0.0.0:0

Have you launched the compose inside the root project?

Can you provide us some system information like what OS are you using?

@zackhamr
Copy link

Yeah using the one in ApiVault, I am using windows 10 and using wsl ubuntu terminal.

@gdjohn4s
Copy link
Member

Mhh have you tried removing the data-db directory before restarting your docker-compose?

@gdjohn4s gdjohn4s self-assigned this Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants