184 results found
-
Allow to set optional ipv4 on Hetzner
Hetzner announced the ability to disable ipv4 on cloud instances, which would save an extra 50 cents on instances. It'd be nice to be able to disable them on internal only instances (eg. database, workers, etc)
3 votes -
Allow database groups to be renamed and allow dashes/underscores in group names
We can currently rename stacks but cannot rename database groups! Also for some reason dash and underscore are not acceptable characters in a database group name.
3 votes -
Support for debian!
Please!
2 votes -
It would be great if it was possible to change some settings from the iPhone app. The git branch is the one i'm most concerned with.
It would be great if it was possible to change some settings from the iPhone app. The git branch is the one i'm most concerned with.
2 votes -
Allow me to allocate components individually
I don't want you to handle my web servers, but for instance to work like a hosted DB for redis and mysql on DigitalOcean. They don't offer that and you'll provide me with good configs and constant improvements. I can also have backups handled by you automagically. I loved you UI and your service in general but I dislike the notion of a stack attached to rails. We have our largest app in rails, but some smaller service components in minimal rack up with DynamoDB. Plus, we would prefer to push with Git heroku style. For minimal extremely fair priced…
2 votes -
Play with PayPal
It would be great to be able to pay the bill with PayPal
2 votes -
Feature parity between toolbelt CLI and GUI
Develop feature parity between the command line interface (cx) and the cloud66 backend interface. That is, if we can do something in the backend, we should also be able to do it in cx (perhaps with some minor exceptions like editing billing information or other rarely used paths that have nothing to do with deployments).
2 votes -
let us control the # of releases in your capistrano script
Our server runs out of space, and we don't need 4 old releases present, particularly, on staging instances. Thanks!
2 votes -
2 votes
-
2 votes
-
Provide support for Rails 3.2 via https://railslts.com/
Rails 3.2 is going to end its official maintenance cycle.
If Cloud66 bought a enterprise version of https://railslts.com/ they could then offer it as a addon to their Rails customers. Thus ensuring that the rails 3.2 stacks can have support. going forward
2 votes -
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 -
Have a way to copy jobs when cloning
Whenever we clone a cloud machine, we should have a way to copy the jobs as well. Or export the job and reimport it. It'd save us alot of time when we are trying to replicate the production's site.
2 votes -
Basic analytics for servers
I think it would be great to install a few basic analytics for our server to track main KPI so that we know we we should scale or down scale servers.
- CPU Load
- CPU%
- Memory%
- Disk space on Postgres2 votes -
Do not source Cloud 66 environment globally
Cloud 66 uploads a file /etc/profile.d/cloud66_profile.sh which loads environment globally, for all users. This means that when I log in to my server, I am greeted with this:
-bash: /var/.cloud66_env: Permission denied
I think it would make more sense to only load this environment for the given user, and not globally for all shells.
1 vote -
use YAML formats for setting Environment Variables
Right now the current form for upload is stripping out trailing "=" from environment variables.
1 vote -
Add the ability execute a single command across the stack
The ability to run a command against your entire stack, or selected servers would be ideal.
1 vote -
1 vote
-
Allow integration with Ubiquity servers
Ubiquity servers (https://www.ubiquityservers.com/cloud) are cheap and good quality. Integration with them would be amazing.
1 vote -
Check the status of deployment location prior to building stack
For example, on Digital Ocean, New York 1 is full. If you try and deploy here, then C66 will try and fail. If there was something in the API between C66 and DO to let C66 know the current available deployment status, then the full locations could be greyed out and not selectable.
If I try to deploy a server directly on DO, it tells me it is unavailable. So the information is in their system. They just need to send it to C66.
1 vote
- Don't see your idea?