184 results found
-
Git Tags
It would be nice add tags, called releaes by github, to git when code is deployed with the environment and timestamp.
6 votes -
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 -
Support Backup for entire MongoDB database
The managed backup system not save the entire MongoDB database but only one specified in the configuration.
Applications using MongoDB can switch databases easily to split data (for locales, clients or other) so save only 1 database is not enough as it will save only part of data.
We must be able to specified which databases can be saved or the all server (full dump).
6 votes -
caching dependencies on scaling up new servers
We should be able to easily cache bundler/yarn/assets dependencies on our new scaled up servers (on new builds, as we do in our deployments using capistrano)
6 votes -
Access to stack from my IP when in maintenance mode
HTTP/HTTS temporary access from my IP(or informed IP) like we have today with SSH
6 votes -
Hide all version and powered by headers by default in nginx config
Disable passenger version: https://www.phusionpassenger.com/documentation/Users%20guide%20Nginx.html#_passenger_show_version_in_header_lt_on_off_gt
Remove X-powered-by headers:
http://wiki.nginx.org/HttpHeadersMoreModule#more_clear_headersAt a minimum, dont send version info, but ideally dont leak anything that limits/narrows an attack surface (telling people you use nginx/passenger, etc).
5 votes -
Create a maintenance mode backdoor
Maintenance mode is a handy feature but allowing a way to privately test load an application that is in maintenance mode would make it even handier.
5 votes -
Offsite backup of GlusterFS volumes
When using GlusterFS you need some offsite backup solution. An add-in for GlusterFS backups would be nice.
5 votes -
5 votes
-
Notifications on Server Performance Monitoring.
For example,
if CPU load is at 2 or greater for longer than 5 minutes;
if Memory is greater than 60%.
If disk space is greater than 80%.
ETC.
Since you have monitor this stuff already, it would be fantastic to just get notified under certain conditions and triggers.
Would save people a lot of money by not having to buy a third party Server Monitoring solution like New Relic or Scout.
5 votes -
Integrate with Papertrail
This shouldn't be especially hard to do (Cloud66 servers appear to use rsyslog by default, and Papertrail's pretty much just a remote syslog target), and would save folks a lot of trouble when attempting to centrally collect and organize logs.
5 votes -
Way of specifying the number of workers in your Procfile.
I would be cool to specify that a process server should have 4 processes of DelayedJob so that when I scale up it'll actually boot up 4 processes for new Process Servers.
Thanks
4 votes -
Add Softlayer as a cloud provider
Softlayer has an extremely robust network, and they also have a CloudLayer VPS solution. It would be great to implement C66 with Softlayer.
4 votes -
a overview or schedule rake tasks
We have quite a few schedule tasks. I would like to see some sort of graph when they are run over a 24 hour period. Just so I don't need to go into each of them and map it myself.
4 votes -
Display stack name in invoice comments
Please include the stack name in the Comments section of the billing charges (breakdown) page. Ideally, this should be carried through to the invoice PDF as well, but at minimum, we would like to be able to see which stacks map to which costs.
4 votes -
Instant and Full Rollbacks
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 -
Support for Chinese cloud providers
Preferably Aliyun
4 votes -
Allow reduced backup retention over time
I'd like a way to make managed backups automatically delete some copies so that it appears to reduce frequency over time.
I might have hourly backups where all but one per day get deleted after a month, all but one per week get deleted after 6 months, and all but one per month get deleted after a year. In other words I'd have:
- Hourly backups for the last month,
- Daily backups for the 5 months prior,
- Weekly backups for the 6 months before that,
- Monthly backups for all time before that.
4 votes -
Reboot cluster servers requiring reboot automatically
At least for load balanced servers it should be easy to handle automatic rebooting. Just remove them from the load balancer, reboot and then add them back.
For load balancer and other services that can't be rebooted without service downtime, it would be nice to be able to assign a maintenance window. During the window, the stack would be taken to maintenance mode, servers requiring reboot would rebooted and then the maintenance mode would be lifted.
4 votes -
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
- Don't see your idea?