160 results found
-
Avoid recompile existing and unchanged assets
Please tweak your deploy to avoid compile all the assets at each deploy, but just compile the ones that changed since the last deploy. Exactly like heroku does. This will speed up a lot the deploy process
48 votesThis is supported through Turbo Sprockets gem. You need to be running Rails 3.2 or above.
-
Managed backups for Redis database
There is currently option to do managed backups of PostgreSQL that are hosted by Cloud66. I miss this functionality for Redis database - I prefer to have them done automatically instead of hosting them on S3.
2 votes -
Ability to run rake task manually through interface
Right now the rake task setup requires a schedule. Its also super useful to be able to just use the cloud66 interface to do 1 click manual rake tasks without ssh'ing in. So I'd love to have an option to not schedule rake tasks just have the link in the interface (I currently use a cron schedule for feb 31st so it never runs automatically). Also an easy way to run rake tasks on deploy would be neat too. I know it can be done via deploy hooks but would be prefer if I just had an 'after_deploy' option when…
44 votesThis is available through Toolbelt: http://help.cloud66.com/toolbelt/toolbelt-command
-
change environment variables without full redeploy.
Allow updating of environment variables without doing a full redeploy!
All it would have to do is upload the new variables and reload the web servers and worker processes. This would make the environment variables more useful.
15 votesRestart feature is now available as part of the toolbelt
-
Manage instance sizes individually
When deploying stack I can choose what size of server I want to use. The problem is that currently all parts of system will use the same size - i.e. for DigitalOcean if I will choose instance size of 1 GB then both my Rails server, PostgreSQL server and Redis server will use the same setting. This is serious problem for applications that need different params - like fast-cpu for Rails and big RAM for Databases. Because of that it would be useful to be able to set each component individually inside of stack.
0 votes -
Manage to which server databases are deployed
Currently during creation of stack I have two choices for each database present:
- Locally - Same as the web server
- On a Dedicated Server
But in some cases I would like have one server (or servers) for Rails and another for all databases. This will be especially useful with requested support for Elasticsearch.
0 votes -
Restore database to new server from backup
Most of the time I restore a backup I'm doing it to a new stack either because I'm switching servers. cloning servers or just rebuilding the stack to do updates. Its a shame there isn't a way of doing this through the dashboard as you control the backup and the new stack/server. The whole download upload, unzip and restore on the command line is a bit of a pain.
37 votes -
Support database server clustering/replication/scaling
Postgresql 9.3 has new replication features, as does MySQL, Maria DB etc.
19 votesMySQL, PostgreSQL, MongoDB and Redis replications are now supported
-
Rackspace Performance Servers
I t would be nice to choose the Rackspace Performance Servers over standard.
pricing within this tier is also currently cheaper!
2 votes -
Support for ElasticSearch
ElasticSearch is a great addition to a stack as a search server. Also, I hear some people use it as an app's sole data store.
91 votesauto-detected, deployed and configured by the availability of the gem
-
Support the ability to serve fonts from other domains (CORS)
You should add in nginx the setting for Access-Control-Allow-Origin on fonts assets. Otherwise fonts served by an assets domain wouldn't be loaded by firefox
https://github.com/h5bp/server-configs-nginx/blob/master/conf/cross-domain-fonts.conf
https://developer.mozilla.org/en-US/docs/HTTP/Access_control_CORS33 votes -
Upload file to stack
Right now I have a settings file saved in my home folder containing passwords and other sensitive information (~/.secret/passwords.yml) it would be great if I could upload a file to all (or one of) my stacks..
3 votes -
Change env variables through c66 toolbelt
It would be great to be able to change the environment variables through the command line!
8 votes -
Maintenance mode API
Ability to quickly switch the site to maintenance mode from the API
7 votes -
sqlite support for development environment
There is no reason to change my gemfile and database configuration to addapt my app to cloud66, I understand this should be the other way.
It's nice to have a check for production but alowing this in development doesn't make any harm.3 votes -
Redirect http -> https for load balancer
If you use a load balancer and ssl certificates on the application servers, a request to the http://kdvnet-production.c66.me is returning a 503 response, instead of redirecting to https://kdvnet-production.c66.me
20 votesHAProxy now support CustomConfig http://help.cloud66.com/how-to/haproxy-customconfig.html
-
Have multi organisation support (similar to GitHub)
Not being able to share an account with multiple organisations means that I need to maintain multiple accounts with separate email addresses.
There should be a method similar to GitHub's organisations where a single user account can belong to multiple organisations.
5 votes -
Support for private network at DigitalOcean
DigitalOcean is allowing creation of private networks since recently (only for NYC2 for now, bot more will be rolling soon). It would be nice to enable support for it at Cloud66, as it will reduce inter-network bandwidth costs (currently transfer between servers is treated as communication with outer network).
Relevant link: http://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/3020028-private-back-end-network-support
3 votesWe do support private networks on NY2 already! I’m sorry about the lack of clarity around documentation, we are working hard to improve that
-
Fix environment uploader to allow comments
Please have the environment file uploader ignore files beginning with a #. Right now this line:
KEY=value
is interpreted with a name of "# KEY".
1 vote -
clone staging from production stack
I would love to clone a production stack and make it the current staging stack that uses the production database as well.
Might need to add warnings about production data being present, emails etc so you're not emailing production users when testing on staging.
This on-demand staging would rock!
14 votes
- Don't see your idea?