184 results found
-
Update Hipchat Integration (Hipchat API v1 is deprecated)
Hipchat API v1 is deprecated. New users of Hipchat can't create v1 keys, so notifications aren't showing up.
Here's some background from a similar request of New Relic:
https://discuss.newrelic.com/t/hipchat-v1-api-is-deprecated-please-use-v2-oauth-room-tokens/259433 votes -
Allow re-naming the git repos in CustomConfigs
While it's great that we now have the ability to interact with customConfigs using git, their naming conventions are... obtuse. In fact, they don't seem to correlate to the name of the stack in any way, like, "platium-plated-penguin-9001". A workaround is to have users locally softlink with a more meaningful name.
What I'm looking for is the ability to re-name the git repo to be more inline with the stack name.
3 votes -
3 votes
-
Integrate with Spotinst
Spotinst (https://www.spotinst.com) is a a sophisticated cluster software and prediction purchasing algorithm for EC2 and GCE resources. By leverage spotinst you can bring the cost down of EC2 and GCE resources and still have enough power to run your applications.
3 votes -
Import a database from another stack via API
Ability to import a database from another Stack via API - accessible
from the interface.
3 votes -
add support for rollbar
I need to be able to see, monitor and record errors that are happening on a live production server.
3 votes -
Support Multi-Master Databases
When deploying globally, it'd be nice if db writes could take place using the local db shard rather than a single master half way around the world. Scaling is incredibly limited without this.
3 votes -
Automatic Let's Encrypt certificate renewal for failover groups
At the moment LetsEncrypt and failover groups don't really work well together, and you basically have to renew certificates on both servers manually. Some kind of automatic redirect to the failover server, or sharing the certificate to both servers would work great.
3 votes -
accept deploy hooks when the stack is in deployment lockdown
I put my stack in deployment lockdown mode to prevent deploys of new docker images. What happens is that all CI deploys (which build the docker images and trigger the deploy hook on git push) fail as the deploy hook returns:
{"ok":false,"message":"stack requires authorization to deploy and can therefore not use redeployment hooks"}I'd rather have it return an non-error message with the hint to pending deploy authorization, like:
{"ok":true,"lockdown":true,"message":"stack requires authorization to deploy, your deployment request has been issued"}With deployment lockdown, I want to turn off automatic deploys, but I'd love to have them scheduled for review so…
3 votes -
3 votes
-
allow load balancer to take into account weights
This to have the possiblity to have a mix of differently sized servers.
An easy solution would be to next to intipv4 and extipv4 in the CustomConfig servers list also have a servers.numberofcpus or servers.sumofcpu_speed.
This would not be perfect, but probably is relatively easy to implement and would allow for some differentiation in most cases.
3 votes -
CX tunnel with remote host option
Because CX tunnel does not allow for providing the remote address in the tunnel specification local-port:remote-host:remote-port
We have to maintain a bastion host for this purpose which is a pain especially because we really like the security cloud66 uses for access to servers!
Would love to see cx tunnel support specifying a remote host as well as remote port.
3 votes -
Support for secure database replication (in MySQL)
Make sure database replication occurs over SSL as currently it does not.
If it did then it would be possible yo set
require_secure_transport=ONon the database server to force all connections to use SSL where currently you can only specify the requirement on individual users.3 votes -
Enable secondary backup location for managed backup
In addition to the primary, default location where backups are stored (in same region as the server), allow us to configure an optional second location so that in case of certain types of disasters or outages, the backup is effectively 'offsite', so it can still be accessed for the purpose of eg bare bones recovery.
3 votes -
Add the possibility to increase shared memory size
The option to specify shm_size in service.yml or anywhere else.
3 votes -
Better visibility into build
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 -
cx tunnel: add option to open a ssh tunnel into an existing container
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 -
Deploy Elixir/Phoenix as easily as Ruby/Rails
It would be great if deploying an Elixir/Phoenix app were as easy on C66 as deploying a classic Ruby/Rails app.
3 votes -
Add headers to deployment health checks
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
curloptions.3 votes -
Share support tickets among team
When a support ticket is created, we would like it to be able to be tracked by multiple developers, not just the user that created it. That means having the tickets show up on the UI (with a way to read them, preferably), and emails being sent to everyone on the support list.
3 votes
- Don't see your idea?