184 results found
-
1 vote
-
Take Rails LTS into account when calculating the Code Stack Score
We run several applications which use the Rails LTS - railslts.com - this is a supported version of Rails and it would be useful for the code stack score to recognise this and not report the Rails version as being outdated. We have to ignore the code score on these because it's inaccurate.
1 vote -
Add an activity indicator when backing up
There is currently no indicator to show when a backup is in progress. It would be nice to have some way of finding out whether a backup is running, and even better: to be able to see the % complete.
1 vote -
Allow lower case environment variables with toggle switch
Currently all env vars are upcased in the UI. I have many apps using lower case env vars. Despite various dogma some frameworks or tools use lower case for avoiding collisions with system env vars.
It would be great to have a checkbox to turn off the forced upcasing of env vars.
At the moment I can't use cloud 66 without this feature.
1 vote -
Add support for Microsoft SQL server Linux
Microsoft announced SQL server for Linux and would be great using it as a database when available.
1 vote -
1 vote
-
Add support for an atomic update to the service.yml in one single API
Add support for an atomic update to the service.yml in one single API
1 vote -
load balancer
Determine which subnet to deploy load balancer into (aws)
1 vote -
Deploy/scale hooks for Docker
Deploy hooks don't run when scaling services, so it'd be nice to have a new hook point that covers all circumstances in which a Docker container is created or destroyed, on scale or deploy.
1 vote -
Send a notification when deployment fails to start
We get notifications when deployment starts successfully but not when it doesn't (for example if a server cannot be reached via SSH).
1 vote -
1 vote
-
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 -
cloud9
cloud9 online ide plugin to setup a cloud9 remote ssh workspace in a few clicks. Useful in c66 development stacks.
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 -
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 -
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 -
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 -
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 -
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 -
For Jobs, have extra info so it'll help us debug easier
I think what will be useful if we can get what's schedule when the cron job is being run (eg "every 5 minutes", "daily at 1 AM" etc.) on the Jobs overview table.
When trying to figure out what a performance issues, this data is valuable if it's in the Job's overview table
Thanks
1 vote
- Don't see your idea?