-
Notifications
You must be signed in to change notification settings - Fork 139
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
Auto-deploy imageflow_server to Docker Cloud / DO #92
Comments
It would be awesome to get a docker image with an entry point set so that one can simply Any chance of getting this? |
If you want a HTTP2 nginx-proxied (but not output-cached) setup, this stackfile for Docker Cloud should work: For imageflow alone, |
Fixed. @alexisvincent - please open another issue for any questions related to the Docker image(s). Happy to help, but this task is done. 🎉 Each commit to Imageflow triggers a rebuild of imazen/imageflow_base_os immediately. When all tests pass, a second Docker image is built - imazen/imageflow_server_unsecured. When this is updated, the demo server reloads the new code. For the moment, this demo server is reachable at https://imageflow-demo-a.imazen.io/proxied_demo/index.html Folks... yeah, I recycled the ImageResizer 2007-era demo page. Sue me. Or, help me update it and get free promotion for your web agency. The ImageResizer demo page was downloaded over a million times.... |
Endpoint is down :) |
Thanks! I got it back up Saturday, but I definitely need to add a monitoring solution. |
No worries. Just noticed :) |
As part of Travis CI build,
Using a new docker image will reduce footprint from 1GB to 200mb.
Phase 2:
Use Docker Compose; use Redis for caching.
The text was updated successfully, but these errors were encountered: