Skip to content

General

General

Categories

(thinking…)

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

184 results found

  1. Temporarily disable some rake tasks

    It would be convenient if a scheduled rake task could have an "enabled" flag.

    In the event of a primary stack failure, a failover stack could have all the rake tasks already entered (but disabled), and it would just be a matter of disabling the primary stack's tasks and enabling the failover stack's tasks. Right now, you have to manually add and delete them.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  2. Bahnhof Cloud provider support

    http://www.bahnhof.net

    Bahnhof is known for their security measures and would be a welcome Scandinavian provider. For those who take security and privacy into the equation (next to performance and price) Bahnhof would be a great option.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  3. Disable asset pre compilation on servers not serving web content

    We have separate process server which is not used to serve any web pages at all. However, I've noticed that during deployment it performs assets pre compilation which slows down deployment and is not necessary for this server. I'd like to be able to disable asset compilation through server settings.
    Something like cx server-set MY_STACK asset_pipeline_precompile false

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  4. It would be great if Cloud66 would support Mercurial source control system other than Git.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  5. Restart workers on stack restart

    When calling cx restart on a stack, the workers aren't restarted.

    This is surprising when the "cx restart --help" docs state " This will send a restart method to all stack components. This means different things for different components."

    My scenario is as follows. Deployed, but needed to run migrations. Ran migrations. Ran cx restart. Web picked up migration changes, but workers did not because they weren't restarted.

    Currently the only ways I've found to restart a worker is through the web interface or via ssh.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  6. If there is no heartbeat on a server, it would be nice if it tried to reboot it.

    If there is no heartbeat on a server, it would be nice if it tried to reboot it (using the cloud provider's API). Suggested by Jevin Maltais.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  7. create a global gemrc

    Create a file called /etc/gemrc with this in it:

    gem: --no-document

    this will skip the useless gem docs and speed up gem installation time by 300%.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  8. Ability to see cost (maybe even per stack) before invoice

    With multiple stacks and servers it can take a little time to count and estimate size of next invoice. Would be nice if account showed size of next invoice - broken down pr. stack.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  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)
    Close
    Close

  9. Don't automatically enable processes

    When a Rails app is deployed for the first time with a Procfile (and I think also when a processing server is added), 1 process is automatically booted for each entry in the Procfile.

    This is bad for at least two reasons:

    1. Testing - processing may begin before you can verify deployment was configured correctly (e.g all correct environment variables have been set, connecting to correct DB, etc)

    2. Resource exhaustion - deployments with many Procfile entries could lead to lots of unnecessary connections being made to databases, and preventing other applications from accessing these resources.

    We have about 3 dozen…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  10. Allow per-stack (adn per stage) keys

    Allow to generate a set of deploy keys per stack and stage so these can be added as deploy keys in GitHub.

    Organizations / Admins have issues with adding a single key to their user account, as a compromise of that key would result in a massive leak.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  11. Set the nginx http to https regex in the manifest file

    I would be awesome to be able to set you're own rewrite regex in the manifest file. Especially in conjunction with setting redhttpto_https to true.

    That would enable you to use something like ^((?!assets).)*$ to redirect everything except assets. It would make it a lot easier to have everything preconfigured for cloudfront.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  12. set http to https redirect in manifest file

    It would be helpful to be able to set redhttpto_https from the manifest file so a new stack could load with that setting.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  13. Freeze/Suspend a stack

    We have a BETA stack which we bring up every now and then when we need to test new features before deploying to production.

    It would be great if it was possible to freeze/suspend a stack.

    I imagine hitting freeze on the stack, it takes a full backup of my database, save the current git repos id, cancel my servers (or ask me to do it). On a later time I can hit the unfreeze button, it will then setup new cloud servers, install software, use the specific git repos id, restore the backup, and setup the elastic address to…

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  14. allow deploy hooks on haproxy instances

    I'd like to automate things such as installing newrelic monitoring when spinning up haproxy load balancer instances. Currently, I do this using deploy hooks on application servers and it works great. If I could do the same on haproxy servers, I'd be thrilled.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  15. Support for MariaDB

    It should be pretty straight forward as it is a drop-in replacement for MySQL. MariaDB is often performing better than MySQL and community improvements from Facebook, Twitter, Google, and Percona all roll into MariaDB sooner than they appear in MySQL.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  16. Support for Galera Cluster for MySQL

    It would be great to have the option for using Galera Cluster to create a true Mysql cluster instead of using master/slave replication.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  17. Support Postgres SSL or SSH tunnel connections from app servers

    Support the application servers connecting to Postgres over SSL (preferred) or even over a SSH tunnel.

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  18. Automatically follow postgres.log when adding the logentries addin

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 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)
    Close
    Close

  19. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  20. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close
1 2 … 5 7 9 10
  • Don't see your idea?