For the Image Search Abstraction, does anyone have any tips for setting up the image search functionality? I've been struggling with using the google custom search api for the last day or so. I can get it to respond with search result data, but I can't seem to figure out how to limit that to results from google images, which seems to be what the example project is doing. Perhaps I'm barking up the wrong tree?
Hmmm, I'll have to look into that. It's a little disappointing that I can't seem to figure it out though. It seems rather simple, like I'm just missing a certain query param in my request. And I can't seem to find the right google search term to get to the answer I'm looking for.
Thanks @darrylpargeter
:star: 744 | @darrylpargeter | http://www.freecodecamp.com/darrylpargeter
here is the link to the pertinent function I'm using to call the api:
https://github.com/jonslucas/fcc-imgsearchabstraction/blob/master/app/controllers/imgSearch.server.js
https://github.com/jonslucas/fcc-imgsearchabstraction/blob/master/app/controllers/imgSearch.server.js
but, I guess it's not too much trouble to just scrap it and start with the bing API
@Rafase282 Flow:
- register user, save user with hashed password (I used bcrypt)
- login: compare hashed passwords and if ok, create JWT, (I used "jsonwebtoken" npm mod) send back in res to client
- client send JWT in req, >> I did a simple middleware mod, that checks the JWT validity before routing to the protected route!
To logout user, you can simple delete token on the client side, but there are a way to revoke the token from server as well.
- Protect your secret string, I put in .env
- When you create token, don't forget to mask password in user object as the token is not encrypted only encoded, anyone can easily read a token
OBS to stream. I'm trying to fill a gap, the streams are either bonfires or FCC bug fixes or Musare, so I'm tryign to add API Backend and related front end dev while working on my project because I doubt people will sit to watch me write articles for the wiki. But the idea was to show you my api and then we can come up with a decent way to provide security, so far mine works but I'm still a noob. @anders462
skypeid andben462
my login page works well on xampp
but when i take it online, it doesn't login again
But, I am also interested in figuring out what I was missing in the cse api
I spent yesterday figuring it out. You need to start https://cse.google.com and add a search engine. For now, type in anything in the sites to search (e.g. www.google.com). Give it a name you'll recognize later. If you search engine is successful, you'll be on a page with an option to Modify your search engine. Click on the Control Panel button. Under the Basic tab, under Site to Search change the drop down to Search the entire web but emphasize included site. Now you can delete the sites to search that you set when you created the search engine. Toggle allow image search to ON. Save your changes. Now you've basically recreated google search with image search enabled - it will search the entire web and allow you to search images through the api url. On this same page you can get your search engine ID - which you will need for your api url. Copy and paste that to your .env file. Now go to console.developers.google.com and create a new project. In your new project dashboard, click the hamburger menu button and select API Manager. Start by creating credentials. Create an API Key - Browser Key. Copy and paste the key to your .env file because you will need it in your api url. Now for the final step! From the API manager click Overview. Search for the Custom Search Engine API and click enable. That is it. Now you should be able to access your custom search engine using the url https://www.googleapis.com/customsearch/v1?key=GOOGLE_API_KEY&cx=GOOGLE_CSE_ID&q=SEARCH_STRING&searchType=image
I hope I am not leaving any steps out! It is definitely complicated. I was hung up on the final step, enabling the custom search api for hours yesterday.
:star: 333 | @anders462 | http://www.freecodecamp.com/anders462
How did you discover that part of it?
I found the docs to be rather unhelpful personally
But perhaps I was looking in the wrong area