- or
No existing idea results
- ~ No ideas found ~
184 results found
-
Fix downloading an ssh key on mobile
Specifically iOS
0 votes -
1 vote
-
Allow servers from different regions/data centers during scale up
During scaling up, you allow us to pick the size and how many, but it would be nice if we could pick the region/AZ/data center to put the server in. For example, I'd like to have application servers in the IAD and DFW Rackspace datacenters within the same stack. One might argue this doesn't matter if my IAD load balancer fails, but I could change DNS from the IAD load balancer to the DFW application server. It's easier and cheaper than having a failover group on standby.
6 votes -
1 vote
-
Display stack name in invoice comments
Please include the stack name in the Comments section of the billing charges (breakdown) page. Ideally, this should be carried through to the invoice PDF as well, but at minimum, we would like to be able to see which stacks map to which costs.
4 votes -
Set request start time in default nginx.conf
This way we can get request queue reporting (at least w/ newrelic) out of the box. https://docs.newrelic.com/docs/apm/other-features/request-queueing/request-queue-server-configuration-examples
3 votes -
Don't "protip" DB backup in case of external DB
The protip to keep your data safe is nice enough, but when my database is external the protip doesn't make sense. My DB is in fact backed up, as it's managed externally.
I know I can ignore it, but it'll keep popping up and for an external DB this protip does not make sense.
1 vote -
3 votes
-
Hide all version and powered by headers by default in nginx config
Disable passenger version: https://www.phusionpassenger.com/documentation/Users%20guide%20Nginx.html#_passenger_show_version_in_header_lt_on_off_gt
Remove X-powered-by headers:
http://wiki.nginx.org/HttpHeadersMoreModule#more_clear_headersAt a minimum, dont send version info, but ideally dont leak anything that limits/narrows an attack surface (telling people you use nginx/passenger, etc).
5 votes -
a overview or schedule rake tasks
We have quite a few schedule tasks. I would like to see some sort of graph when they are run over a 24 hour period. Just so I don't need to go into each of them and map it myself.
4 votes -
An option for owners to permit administrators to specify cloud keys
A way for the owner to permit full access to the administrator, including specifying the cloud keys. This is very useful for clients who own their cloud66 account, but are not technical.
1 vote -
Accept Docker Push Commands
Allow for us to build the docker image on another server and push to cloud66 docker repo
3 votes -
Be able to specify bash aliases at account level
It would be nice if I was able to specify a set of always used bash aliases on my user account preferences.
1 vote -
MongoDB 3.0
Enable deploys with mongodb 3.0 version
4 votes -
Deny Wheel (sudo) Access to Team Members
Some team members need to have shell access to my servers (especially for tunneling to MySQL with Sequel Pro), but not root/sudo access. When adding team members with shell access, could you add a checkbox to deny wheel group/sudo?
1 vote -
Trigger deploy from DockerHub webhook
I'd like to be able to build my docker image on my CI tool, together with running tests, and when the image is ready then cloud66 will pull it from the repository and deploy it to the needed containers.
This will enable:
* Creation of smaller docker images (build from source will happen on CI, and only the artifacts will be copied to my docker image)
* Fail deployment if the tests don't passHere's a nice description of how it should work:
http://blog.tutum.co/2015/06/10/node-js-and-continuous-deployment-with-circleci-docker-hub-and-tutum3 votes -
Add firewall rule for entire stack of servers
Add ability to select a stack so that every server ip associated with the stack obtains a firewall rule. This would automatically get applied to new scaled up servers.
1 vote -
Way of specifying the number of workers in your Procfile.
I would be cool to specify that a process server should have 4 processes of DelayedJob so that when I scale up it'll actually boot up 4 processes for new Process Servers.
Thanks
4 votes -
Allow mapping to a elastic IP when creating new node
There is a need to use elastic IP when creating node in AWS. At the moment there is no way to do assign that as part of the config
6 votes -
Customize the startup grace time for worker processes
For instance, give Resque workers more time to start before they are considered "not running" - avoids getting spammed with alerts on each deploy
3 votes
- Don't see your idea?