184 results found
-
Navigation structure is quite confusing
The nested nature of a lot of the config screens, along with what appears on each is quite confusing.
I managed to totally miss how to add a Redis server after initial deployment despite seeing I could create it as an Addin - I couldnt find the Addins page, and then couldnt find the "+" icon after I cound the section
I also managed to totally miss the Redis Servers page "Configure Redis" button as it is a de-highlighted blue button far to the right - it really should be in the main flow of the page
3 votes -
on Mobile, most of your site works ok and is responsive - but none fo your modals are responsive
on Mobile, most of your site works ok and is responsive - but none fo your modals are responsive and viewport width is fixed meaning you cant use mobile properly (at least not a phone)
1 vote -
let us control the # of releases in your capistrano script
Our server runs out of space, and we don't need 4 old releases present, particularly, on staging instances. Thanks!
2 votes -
add notes for backups
Hey guys,
I just thought It would be great to have the ability to add notes before running a backup processes. For example, I have scheduled backup on every day. But when I want to make some changes in project that would affect DB I always make additional backup. It would have been much simpler to understand why that backup was created if I can see a small note on it. Hope you'll find this usefull.
Thanks
1 vote -
add support for Nginx listening on IPv6 addresses
The version of Nginx installed doesn't have IPv6 enabled. If this was enabled, we could offer IPv6 connections to our clients.
Some useful info on IPv6 and Nginx is available here:
http://www.lowendguide.com/3/networking/enabling-ipv6-support-in-nginx/
11 votes -
Use AWS IAM roles instead of access keys
I believe it would be possible for cloud66 to have one AWS account with it's own keys (managed by cloud66) and we the customers would have to add a trust relationship in our IAM roles for that account. Then when a new stack is launched cloud66 code would assume the role specified by the user to do it's work instead of using API keys. This is also how future deploys and edits would work.
This is following the AWS best practices. The goal being that we don't need to give out AWS keys.
1 vote -
Support Backup for entire MongoDB database
The managed backup system not save the entire MongoDB database but only one specified in the configuration.
Applications using MongoDB can switch databases easily to split data (for locales, clients or other) so save only 1 database is not enough as it will save only part of data.
We must be able to specified which databases can be saved or the all server (full dump).
6 votes -
Save stacks settings when re-analyzing
Steps:
1. Edit a stack
2. Modify the cloud provider, db or redis settings.
3. Push a code change and re-analyze the stack.What happens:
My cloud provider, db and redis settings are forgotten.What I would like to happen:
My cloud provider, db and redis settings to persist while re-analyzing.1 vote -
Change DNS settings
if have a suggestion. I got a performance problem with the Twitter gem. Got a lot of timeouts.
After investigating the problem. I found out that the DNS servers Digital Ocean is using (/etc/resolv.conf) are the public Google ones. Those DNS services are rate limeted and slow down performance if you are using outbound traffic, like trying to access the api.twitter.com service. My suggestion is to use other DNS services that 4.4.4.4 and 8.8.8.8 or make it editable.
3 votes -
Add a validator for configuration files
As a user, it would be helpful to me if you had a validator for the .cloud66 configuration files. While it's easy enough to test that the files are valid YAML currently, I would also like to see specific validation of the configuration options.
3 votes -
cx: required parameters shouldnt be shown as optional
Required command-line-parameters shouldn't be displayed as optional (with square brackets around):
f.e. cx restart
Usage: cx restart [-s <stack>]
you might - in addition to that - also consider implementing a unified syntax for addressing stacks/hosts and omit the "-s"-option in general.
1 vote -
Provide invoice breakdowns by stack
Currently, my invoice just shows one rate combined for all my stacks. A breakdown by stack would be nice so that I can pass the costs on to each client.
1 vote -
Add memcached monitoring
A better tool to visualize memcached stats would be great. Maybe something like memcached-top or mctop, integrated on the web UI.
7 votes -
pgcrypto PG extension
It would be great to have the Postgres extensions pgcrypto.
3 votes -
Support for Elasticsearch plugins autoinstall
It would allow to install plugins in a Elasticsearch install. For example https://github.com/sonian/elasticsearch-jetty
3 votes -
http://help.cloud66.com/web-server/nginx-auth.html misses ref to ftp-ports
The help-article about basic-auth misses a note about firewall-exceptions for the use of
apt-get
, which uses FTP to fetch packages.I has to add TCP 20 & 21 to make
apt-get
proper work1 vote -
Play with PayPal
It would be great to be able to pay the bill with PayPal
2 votes -
Feature parity between toolbelt CLI and GUI
Develop feature parity between the command line interface (cx) and the cloud66 backend interface. That is, if we can do something in the backend, we should also be able to do it in cx (perhaps with some minor exceptions like editing billing information or other rarely used paths that have nothing to do with deployments).
2 votes -
Show in the deployment history how long the deploy took
It would be nice to see how long each single deploy took, in order to compare and [hopefully] see improvements over time
The same information could also be added to the email/chat notification
9 votes -
Git Tags
It would be nice add tags, called releaes by github, to git when code is deployed with the environment and timestamp.
6 votes
- Don't see your idea?