184 results found
-
Allow resync to be scheduled
I would like to schedule a resync during low-traffic - I don't see a way to do that today.
1 vote -
Link to where changes can be made to address StackStore concerns
Currently, it appears that you just link to the FAQs here - link to where I can make the changes you're suggesting so I can actually address these easily.
1 vote -
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 -
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 -
9 votes
-
Support AWS spot instances
The idea is to take advantage of AWS spot instances for some periods when heavy background processing is going on — i.e. temporarily scale up using spot instances.
23 votes -
Integrate with Stride
Atlassian is discontinuing support for Hipchat, and moving customers to their new product Stride. Integration would be much appreciated.
10 votes -
Redeploy Stack(s) to Different Cluster
Clusters are a fantastic new feature providing flexibility between host and stack management. As a result, I'm now using fewer server instances for the same number of stacks. However, when I have an issue with my cluster, I now have more complexity to "migrate" to a new cluster, i.e. create a new cluster and then clone/deploy for each of my stacks, which is not an insignificant amount of configuration. Ideally, I would like to be able to create a new cluster and then redeploy my stacks to the new cluster (sans clone, setup, deploy, etc.).
1 vote -
Deploy Failure after rebase
Hi Team
I have noticed that the first deploy after a git rebase on my branch fails all the time. Deploy seems to pick a non-existant commit. This probably happens because the commits gets squashed and the old commit ids are lost and maybe Cloud66 seems to remember or fetch not the latest is.
This fails, goes to an error page. And if i come back to project again and deploy it works fine.
1 vote -
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 -
3 votes
-
Fixe bad link on stacks/55555/settings bad help link
Clicking on the link to tell me more about server deletion setting on this page takes me to a help page about IP address management.
1 vote -
Prevent help documents from having bad or empty links
Example page: http://blog.cloud66.com/tail-your-logs-straight-from-cx/
All of the referenced help links are broken.
1 vote -
Per server metadata configurations
Currently, when you want to add more servers to a stack, you can choose how many you want to add. The advance section let you choose in which AWS region. All new servers will be added to the selected region.
However, for fault tolerance, we often want to have multiple servers in multiple regions. Would be nice to have access to a more user friendly interface where we can add as many servers as we want and for each one, be able to specify its metadata, such as the region where it should be created on.
8 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 -
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 -
cloud9
cloud9 online ide plugin to setup a cloud9 remote ssh workspace in a few clicks. Useful in c66 development stacks.
1 vote -
Add Cloud 66 to the start of the page titles
I usually have lots and lots of tabs open, and I can never find the cloud 66 tabs easily, so if you were to append cloud66 to your page titles it would make it easier to find open tabs.
2 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 -
Publish a vagrant box (or boxes) that mimic your stacks.
Testing app changes on Cloud66 can be time consuming, esp. when iteratively trying to resolve an production issues in a realistic environment since I have to redeploy again and again.
I'd love if you published a Vagrant box that mimics the c66 Rails stack (in this case) so I can iterate quickly before deploying to c66.
1 vote
- Don't see your idea?