Skip to content

General

General

Categories

184 results found

  1. Support notifications via Flowdock Team Inbox https://www.flowdock.com

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Our server runs out of space, and we don't need 4 old releases present, particularly, on staging instances. Thanks!

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. It would be great to have the Postgres extensions pgcrypto.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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 work

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. A better tool to visualize memcached stats would be great. Maybe something like memcached-top or mctop, integrated on the web UI.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Useful for small vps (eg digitalocean 512-1024mb)

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. It would allow to install plugins in a Elasticsearch install. For example https://github.com/sonian/elasticsearch-jetty

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. It's very useful to keep this technical users aware of changes.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. At the moment you use (at least on digital ocean) key names like c66-uselesslonghashprobablybasedonthestackid, it would be much more useful having c66-nameoftheserver. That would make much easier to see which keys are from old servers and that can be safely deleted

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?