11–20 of 27 posts
Also, not great UI design. I kept wanting to manage my monitors, but to do so, I had to hit Status, and then hit Manage Monitors. I'd rather have had it on the sidebar, like Add Monitor was.
Why would anyone want this in the cloud? Self hosted, absolutely. I wouldn't want any service to store credentials that can remotely bounce my VMs or login and restart services. edit: If I wanted to run my own instance what things are missing? That doesn't seem very clear.
Thats a good point, right now we work solely off of API's and don't offer any way for us to store usersnames/passwords. The thought is that API credentials can be revoked easier. In general we are looking to meet the market of folks who are 100% in cloud environments, where the adoption of a SaaS solution is not as much of a concern. But in the future there are some ideas on how to handle self hosting and not sending…
In theory you could meet this need via a prebuilt AWS image or something. Then people can still get up and running with one click but within their own cloud environments.
Kind of didn't work. I signed up, and i was trying to set something up on my staging to scale it out if a dyno was idle, but it didn't appear to work. I had it at zero dynos, so you'd expect it to scale up immediately. Also, not great UI design. I kept wanting to manage my monitors, but to do so, I had to hit Status, and then hit Manage Monitors. I'd rather have had it on the sidebar, like Add Monitor was.
The UI is also something that we are working on, in fact it is our next big project. We are a growing app so some things aren't exactly perfect but were working towards it.
Earlier quoted context omitted.
Thats a good point, right now we work solely off of API's and don't offer any way for us to store usersnames/passwords. The thought is that API credentials can be revoked easier. In general we are looking to meet the market of folks who are 100% in cloud environments, where the adoption of a SaaS solution is not as much of a concern. But in the future there are some ideas on how to handle self hosting and not sending…
> In general we are looking to meet the market of folks who are 100% in cloud environments, where the adoption of a SaaS solution is not as much of a concern In theory you could meet this need via a prebuilt AWS image or something. Then people can still get up and running with one click but within their own cloud environments.
Kind of didn't work. I signed up, and i was trying to set something up on my staging to scale it out if a dyno was idle, but it didn't appear to work. I had it at zero dynos, so you'd expect it to scale up immediately. Also, not great UI design. I kept wanting to manage my monitors, but to do so, I had to hit Status, and then hit Manage Monitors. I'd rather have had it on the sidebar, like Add Monitor was.
Hey jprince, I'd have to look at the "Not Idle" monitors for dynos that don't exist. The way that monitor works is it looks at the monitor status to see if any are idle, if there are no dynos then there would be none idle. The UI is also something that we are working on, in fact it is our next big project. We are a growing app so some things aren't exactly perfect but were working towards it.
I think one or more images overflow the main content container, causing the site to look broken on my iPhone 6 plus. I don't know how much cross platform testing your done, but it's a data point. I wasn't too excited to read the marketing copy as a result.
I don't love your logo. It's a book on a cloud with some kind of diagonal line for some reason.
Looks interesting, whatever the case.
Few more options for "IFTTT for DevOps": http://docs.factor.io/ http://stackstorm.com/ http://www.airstack.io/ https://www.cloudmunch.com/
Few more options for "IFTTT for DevOps": http://docs.factor.io/ http://stackstorm.com/ http://www.airstack.io/ https://www.cloudmunch.com/
Another similar tool is http://www.rundeck.org this one is open source and self-hosted.