General

General

Categories

  1. When configuring preview deployments based on pull requests, filter by label(s).

    E.g. if a PR is opened (or labels are added or removed from an existing PR), if it contains certain labels, deploy a preview.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  2. Currently you can only filter on the target branch, but it'd be nice to be able to filter on the source branch name within the PR config.

    E.g. have a PR config with:
    - source branch pattern (the new option I'm suggesting)
    - target branch pattern (currently the only option)

    Then I could open a PR against the stack branch (e.g. staging), but only have it spin up a preview environment if my source branch is e.g. feature-123 and my source pattern is feature*.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  3. Instead of running a full rebuild which can take a very long time when things are broken, use the last build. Capistrano stores the builds and it completely defeats the purpose of their existence if we never use them. It would take a few seconds at most to rollback a problem vs waiting for an entire new build. For our stack that's over 10 minutes of downtime.

    My proposed solution based on some chats in Slack is to have both an Instant and Full Rollback option since I was told some stacks have deploy hooks that need to be rerun.…

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  4. This would save time so as not to have to go to the AWS UI to configure these separately. On the same note "Redirect HTTP to HTTPS" option should include an expected response option. Meaning if my server is expected to send anything other than a 200 response to the check, the server will return as healthy. For example, a 301 or 302.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  5. Increasing the number of groups in a rolling deployment would be more feasible for certain deployments. It would also allow us to run better than half capacity.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  6. Whenever we clone a cloud machine, we should have a way to copy the jobs as well. Or export the job and reimport it. It'd save us alot of time when we are trying to replicate the production's site.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  7. We have a lot of sidekiq queues that would benefit from this.

    For example, we have 6 pods running for sidekiq which are only used between 00:00-06:00 and we could scale up other parts of our app after these jobs have completed but right now I would have to manually do this.

    https://github.com/kedacore/keda

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  8. The API is very handy when you need to automate stuff but the documentation is not up to date. I would rather not have to bother the support with questions regarding missing things in the docs.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add an option to automate firewall rules installation through manifest.yml file
    e.g.
    staging:
    firewall_rules:
    from: 127.0.0.1/16
    to: 123.123.123.123
    protocol: tcp
    port: 22

    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  ·  Flag idea as inappropriate…  ·  Admin →
  10. As per the Ruby on Rails guide for a multi db setup;

    the username for the writers and replicas should be different, and the replica user's permissions should be set to only read and not write.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow deployment to Ubuntu 20.04

    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  ·  Flag idea as inappropriate…  ·  Admin →
  12. I want to deploy to UpCloud and not have to create registered servers.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  13. With deployment health checks, it would be useful to be able to specify HTTP headers such as authorization or "Host". It may be beneficial to accept arbitrary curl 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  ·  Flag idea as inappropriate…  ·  Admin →
  14. It would be great if deploying an Elixir/Phoenix app were as easy on C66 as deploying a classic Ruby/Rails app.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  15. In many stacks, I use dockerized databases such as Redis, Solr or even Postgresql.

    With "cx run -s mystack --container web-123 -I 'bash'" the cx toolchain allows me to directly get a bash in an already running container, e.g. to perform checks or development changes.

    It would be much more convenient however, if I had the possibility to open as ssh tunnel into these containers so I can access their (mapped) port locally and use all the great database tools out there. :) Just like with "cx tunnel".

    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  ·  Flag idea as inappropriate…  ·  Admin →
  16. The import database feature can be used to test staging environment against production data. Having a way to specify the exact backup ID to import (rather than only having the very last one available) in the UI - with a dropdown or text field entry for the backup ID will be useful to cover more testing scenarios.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  17. Deploying a new Maestro stack builds a "master" server, but C66 does not have good enough status about what's going on as it builds. The last update received is "Kubernetes: Service deployments complete", but it's been spinning doing something for almost 40 minutes since, without having any idea what's going on.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  18. With a lot of stacks, it is impossible to know what stack I'm currently looking at without repeatedly scrolling up to the header and the back down to what I was looking at. With multiple tabs open in order to try to copy settings, for instance, it makes it incredibly difficult to know what I'm looking at.

    The name of the stack being viewed should always be visible in the top fixed header.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  19. The option to specify shm_size in service.yml or anywhere else.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  20. Hey,

    I am using c66 now for quite some time and projects, and recently stumbled on this: when deleting a project, it removes the main EC2 instance on AWS, but leaves behind:

    • volumes
    • load balancers
    • security groups
    • key pairs

    Not sure about the RDS instance, for that short-lived project, I opted to just have the db run on the one EC2 instance as well..

    I would actually expect, that every additional service added for a project is cleaned up on AWS when deleting the project. At least a little warning would be nice, or a checkbox asking, if you want…

    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  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 9 10
  • Don't see your idea?