-
-
Notifications
You must be signed in to change notification settings - Fork 608
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
Add Description of imgproxy-form repo and local-install #12
Comments
This issue seems to be more appropriate for the imgproxy-form repository. Can we move it there and close this one? |
It looked like the imgproxy-form repo was owned by some other project. It looks like these two belong together, and imgproxy-form might fight as an example UI in this project. |
Yes they are definitely related, but the change to the Readme seems like it should be done on the imgproxy-form project. |
imgproxy-form is a kind of easy-test thing. Its goal is to give an ability to try your fresh deployment to Heroku without writing any code. Like press the button, fill the form, wow, it works! You totally shouldn't use it in production in any way. It's related only to the article, and I don't think we should mention it itself in the Readme. |
Folks with creds won't want to push their creds to the imgproxy-form out on the net. Add a section to the Readme describing how to clone that thing locally and use it. Or maybe just mention it so folks can easily swipe that code to put up their own url generators.
For ref:
https://github.com/progapandist/imgproxy-form
Easy task for the eager!
The text was updated successfully, but these errors were encountered: