You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pinterest's API v5 has significantly reduced functionality, only allowing
users to manage their own content without access to public data. This
makes it not good candidate for the intent of hackathon-starter.
Changes:
- Remove Pinterest OAuth2 authentication
- Remove Pinterest API example endpoints and views
- Remove related configuration and documentation
Copy file name to clipboardExpand all lines: README.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,7 @@ I also tried to make it as **generic** and **reusable** as possible to cover mos
85
85
- Contact Form (powered by SMTP via Sendgrid, Mailgun, AWS SES, etc.)
86
86
- File upload
87
87
-**API Examples**
88
-
- Facebook, Foursquare, Tumblr (OAuth 1.0a example), Pinterest, Github, Steam, Quickbooks, Paypal, Stripe, Twilio (text messaging), Lob (USPS Mail), HERE Maps, Google Maps, Google Drive, Google Sheets, Alpha Vantage (stocks and finance info) with ChartJS, Last.fm, New York Times, Web Scraping
88
+
- Facebook, Foursquare, Tumblr (OAuth 1.0a example), Github, Steam, Quickbooks, Paypal, Stripe, Twilio (text messaging), Lob (USPS Mail), HERE Maps, Google Maps, Google Drive, Google Sheets, Alpha Vantage (stocks and finance info) with ChartJS, Last.fm, New York Times, Web Scraping
89
89
- Flash notifications
90
90
- reCaPTCHA and rate limit protection
91
91
- CSRF protection
@@ -162,7 +162,7 @@ _What to get and configure:_
162
162
- Set TRANSACTION_EMAIL as the "From" address for emails sent to users thru the lost password or email verification emails to users. You may set this to the same address as SITE_CONTACT_EMAIL.
163
163
164
164
- ngrok and HTTPS
165
-
If you want to use some API that needs HTTPS to work (for example Pinterest or Facebook),
165
+
If you want to use some API that needs HTTPS to work (for example Github or Facebook),
166
166
you will need to download [ngrok](https://ngrok.com/). Start ngrok, set your BASE_URL to the forwarding address (i.e `https://3ccb-1234-abcd.ngrok-free.app` ), and use the forwarding address to access your application. If you are using a proxy like ngrok, you may get a CSRF mismatch error if you try to access the app at `http://localhost:8080` instead of the https://...ngrok-free.app address.
167
167
168
168
After installing or downloading the standalone ngrok client you can start ngrok to intercept the data exchanged on port 8080 with `./ngrok http 8080` in Linux or `ngrok http 8080` in Windows.
@@ -243,11 +243,11 @@ Obtain SMTP credentials from a provider for transactional emails. Set the SMTP_U
- Enter _Project Name_, then click on **Create** button
246
-
- Then click on _APIs & auth_ in the sidebar and select _API_ tab
247
-
- Click on **Google+ API** under _Social APIs_, then click **Enable API**
248
-
- Click on **Google Drive API** under _G Suite_, then click **Enable API**
249
-
- Click on **Google Sheets API** under _G Suite_, then click **Enable API**
250
-
- Next, under _APIs & auth_ in the sidebar click on _Credentials_ tab
246
+
- Then click on _APIs & auth_ in the sidebar and select _API_ tab and based on your usage add:
247
+
- Login by Google: Click on **Google+ API** under _Social APIs_, then click **Enable API**
248
+
- Google Drive: Click on **Google Drive API** under _G Suite_, then click **Enable API**
249
+
- Google Sheets: Click on **Google Sheets API** under _G Suite_, then click **Enable API**
250
+
- Next, under _APIs & auth_ in the sidebar click on the _Credentials_ tab
251
251
- Click on **Create new Client ID** button
252
252
- Select _Web Application_ and click on **Configure Consent Screen**
253
253
- Fill out the required fields then click on **Save**
@@ -258,6 +258,10 @@ Obtain SMTP credentials from a provider for transactional emails. Set the SMTP_U
258
258
- Click on **Create Client ID** button
259
259
- Copy and paste _Client ID_ and _Client secret_ keys into `.env`
260
260
261
+
**Warning:** Restrict your **Google Maps API key** to the "Maps JavaScript API" and the specific domain name you are using (for example, your ngrok development domain). Avoid using "localhost" or leaving the key unrestricted, because your Maps API key will be publicly exposed through the web application. This exposure could allow unauthorized users to misuse your key, potentially resulting in charges to your GCP account and credit card.
262
+
263
+
- Google Maps API Key: To use the "Maps JavaScript API," you must activate your Google Cloud Platform account with a valid credit card. If your account hasn't been activated yet, this process will also trigger the countdown for the expiration of your free credits if any. If you'd prefer to avoid this, consider using **HERE Maps** as an alternative. To get a key add the Search for "Maps Platform API Key" in your GCP Console and select the appropriate option. Then get your key and add your domain as the Website restriction for it.
0 commit comments