Settings and activity
15 results found
-
1 vote
AdminCloud 66
(Admin, Cloud 66)
shared this idea
·
-
3 votes
An error occurred while saving the comment -
2 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Hi Mark,
Thanks for the suggestion. Wouldn't it make more sense to have the stack name appear first in the text of the title element? The advantage of this approach is that if you have multiple stacks in different tabs you would probably want to see what stack you are working with first? We can certainly append cloud 66 to the end of the text if that helps you navigate via the window menu?
-
2 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Hi Zach,
Can you clarify this a bit please? Thank you
-
2 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Thanks for your suggestion! We're going to add MySQL and MongoDB logs to this list, but PSQL doesn't enable logging by default (for performance reasons).
-
5 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Thanks for your suggestion! Are you aware that we already integrate with Logentries? They provide a similar service.
-
14 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Thanks for your suggestion! In my view, there are two suggestions here:
1) Supply your own SSH keys instead of generating them
2) Improve notifications around downloading of SSH keysI'll pass on this feedback to our team, but just for your information, you can switch off the notification for the download of SSH keys on your stack notification page.
AdminCloud 66
(Admin, Cloud 66)
shared this idea
·
-
8 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Hi Kenny,
Stack based notifications are available now under Stack detail page. Would that work for you?
-
1 vote
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Thanks Florian. Stack name is optional since it is not needed if you are on the same directory as with the git repository/branch of one of your deployed stacks.
-
3 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
I made a deploy hook that'll install this for you automagically: https://github.com/cloud66/deploy_hooks/blob/master/elasticsearch_plugins.txt
The plugin command generally only needs the install (and optionally URL) parameter, so it's easy to adapt this. Also, most plugins don't need anything beyond running this command, so it can get quite simple.
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Hi Michel, we're looking into supporting this. Please note however that the Sonian plugin is discontinued and doesn't support the latest versions of ElasticSearch - see the pmusa version, which is supported (http://www.emergi.net/elasticsearch/plugins.html).
-
3 votes
I’m going to close this tomorrow to release your votes unless you have a comment on my last note.
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
It seems using the Environment Variables should be enough to achieve this. Is it not?
-
2 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
The API now supports this.
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Branch and repository can only be changed through the Command Line Toolbelt. We are opening the API for those as well soon.
-
9 votes
An error occurred while saving the comment AdminCloud 66
(Admin, Cloud 66)
commented
Good point. There are some points to note:
- Updating our images on the cloud vendors that support shared images (like AWS). This usually speed things up and is done regularly. We just performed one on AWS.
- Not all cloud vendors support taking images - public or private (like Telefonica or Joyent).
- Most cloud vendors (AWS included) will have shut the box down to take an image if you require data consistency. This would either make the first build much slower (shutdown, cut the image, start and adjust the new IPs), or will require a shutdown of a server sometime during its life (most likely the first server in a cluster, which would result in a downtime).
To achieve the ultimate goal of speeding up deployments and scaling we are working on a solution that is based on spending little time on the VM and more on the containers that are pre-built. That way we will be decoupled from the vendor limitations and restart requirement.
Hope this makes sense. We are improving the system constantly at a high speed. I hope it will be satisfactory when it's ready!
-
4 votesAdminCloud 66
(Admin, Cloud 66)
supported this idea
·
-
8 votesAdminCloud 66
(Admin, Cloud 66)
shared this idea
·
Hi Max,
Are you trying to use cx to tunnel to ANY server or is it one of the servers you have running as part of a Cloud 66 Stack?