dnakov/proxly

Proxly

An experiment evolved into a web dev tool

• Redirects web requests to local files
• Redirects web requests to wherever else you want
• Enables CORS
• Runs a web server
• Watches files for changes
• Livereloads your stuff
• All of this using just Chrome, no command line tools or anything else
• Exists on the chrome store

Install

Get the Proxly App and Proxly Extension from the Chrome Store

Build

npm install
npm run build

Then in chrome://extensions, add unpackaged directories app/src and extension/src

proxly's Issues

Implement livereload

automatically close the options tab when the app has been opened

remove the badge when the tab has been closed

Extension popup list doesn't update when existing rules are edited

Steps:
Add new rule.
Edit rule
change to main window and click the extension's icon.
Popup lists the new rule with the same name as before.

To fix I need to add another rule or delete one.

Https

It appears that the server doesn't support https - so working with sites on https won't work (because it would be unsecured content)

I'm able to get around it using a local https server
(https://www.npmjs.com/package/http-server with a self signed certificate)

Seems less likely that TLS support might be a possibility
(https://code.google.com/p/chromium/issues/detail?id=132896)

However, some docs/inline help on how to get this setup might be really helpful.

Can't enable more than one rule

Clicking enable inside the extension's popup will switch all other "checkboxes" reverting the other rule from enabled to disabled.

The extension page seems to be down.

Searching for proxly in the chrome webstore returns no results, also when navigating to the pages directly it returns a 404.

Thanks much for the work on proxly!

automate chrome store publishing

Publish Instructions

Here https://developer.chrome.com/webstore/using_webstore_api
Get Ids from here: https://console.developers.google.com

Get the token:

curl "https://accounts.google.com/o/oauth2/token" -d \
"client_id=$CLIENT_ID&client_secret=$CLIENT_SECRET&code=$CODE&grant_type=authorization_code&redirect_uri=urn:ietf:wg:oauth:2.0:oob"

token is good for 40 min

Upload a new app:

curl \
-H "Authorization: Bearer $TOKEN"  \
-H "x-goog-api-version: 2" \
-X POST \
-T $FILE_NAME \
-v \
https://www.googleapis.com/upload/chromewebstore/v1.1/items

Update the app:

curl \
-H "Authorization: Bearer $TOKEN"  \
-H "x-goog-api-version: 2" \
-X PUT \
-T $FILE_NAME \
-v \
https://www.googleapis.com/upload/chromewebstore/v1.1/items/$APP_ID

Publish to public

curl \
-H "Authorization: Bearer $TOKEN"  \
-H "x-goog-api-version: 2" \
-H "Content-Length: 0" \
-X POST \
-v \
https://www.googleapis.com/chromewebstore/v1.1/items/$APP_ID/publish

Get Status

curl \
-H "Authorization: Bearer $TOKEN"  \
-H "x-goog-api-version: 2" \
-H "Content-Length: 0" \
-H "Expect:" \
-X GET \
-v \
https://www.googleapis.com/chromewebstore/v1.1/items/$APP_ID?projection=draft

1. Auto-increment the manifest file (follow semver somehow)
2. run all this shit after zip
3. print some status
4. make this into a gulp plugin
5. make this whole fucking thing into a chrome-app/extension generator using gulp