3 ms·
Do you think there would be demand for `serveo` but instead of running your project locally, you point to a Dockerfile and the entire container + all of its dep
by MuffinFlavored 7y ago
Do you think there would be demand for `serveo` but instead of running your project locally, you point to a Dockerfile and the entire container + all of its dependencies are ran remotely (with wildcard subdomain SSL included)?
I was going to test the waters with https://www.dollardeploys.com/ https://www.dollardeploys.com/ (not functional yet), wasn't sure how to differentiate it between ngrok/serveo.
- benologist 7y agoI think at that point you're really into Heroku's territory rather than ngrok/serveo. Their free dynos might be hard to compete with, you can push a git commit or docker image or automatically deploy upon repo changes: https://devcenter.heroku.com/categories/deploying-with-docker https://devcenter.heroku.com/categories/deploying-with-docke...
- MuffinFlavored 7y agoI 100% agree which is why I decided not to pursue the idea. Thank you very much for taking the time to provide feedback!