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

Submission: Trail Blazers #27

Open
ShreyamMaity opened this issue Aug 21, 2022 · 0 comments
Open

Submission: Trail Blazers #27

ShreyamMaity opened this issue Aug 21, 2022 · 0 comments

Comments

@ShreyamMaity
Copy link

ShreyamMaity commented Aug 21, 2022

Team Name

Trail Blazers

Team members

Member # 1
Name: Shreyam Maity
Email: [email protected]
Twitter handle (hyperlinked): ShreyamMaity

Member # 2
Name: Kallyan Singha
Twitter handle (hyperlinked): KallyanSingha

Project Name

Apiffer

Contact Details (Leader)

[email protected]

Project Track

https://apiffer.ml

Open Innovation

Link to project GitHub public repo

https://github.com/apiffer-apis/apiffer

Link to the roject website

https://apiffer.ml

Link to demo video

https://drive.google.com/file/d/1KPOQ6dejP-1HytNHSNPzT3HWCQo9dfeg/view?usp=sharing

Inspiration

I've seen many of my frontend friends try to make dynamic web apps without knowing any backend or API knowledge. What they do is they try to use the APIs mentioned in the tutorial they're following but most of them don't work or have rate limitations. So we tried to create a platform where you can quickly create APIs without any backend knowledge.

What it does

we tried to create a platform where you can quickly create APIs without any backend knowledge.

Challenges you ran into

  • time : this is a large project so faced the 40hr time issue
  • our app is better on local networks. for production we have to open multiple ports or create a lot of reverse proxy configs. Instead of a web app, we could have made a vs code extension but due to limited time and knowledge of making an extension, we failed.
  • we haven't added the authentication and authorization. If we want to allow multiple users then for each user we have to create a new reverse proxy but that's not a good solution. We think the optimised solution will be like if we create a new server which will hold all new proxies and we'll create pm2 nodes for each proxy but that would require a lot of experiments. Or we can make this a local area-based application like we mentioned in the vs code extension or windows application.

Anything else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant