just call it by:
ssh -i your.pem ec2-user@yourserver ~/./yourfile.sh
just call it by:
ssh -i your.pem ec2-user@yourserver ~/./yourfile.sh
by just declaring the captor as :
@Captor private ArgumentCaptor<List<SomeObject>> captor; and verify'ing by verify(someService).someMethod(captor.capture());
you can captor a list.
sudo yum -y install telnet
rsync -rave “ssh -i /your.pem” some.file ec2-user@yourec2machine:~
just create some user if you want to access to an rabbitmq admin console
rabbitmqctl add_user user pass
rabbitmqctl set_user_tags user administrator
rabbitmqctl set_permissions -p / user “.” “.” “.*”
For Redis, I couldn’t access to Redis from outside AWS, but can access it from EC2 or other platforms. #ReminderForMyself
by the way :
Please note that IP-range based access control is currently not enabled for Cache Clusters. All clients to a Cache Cluster must be within the EC2 network, and authorized via security groups as described above.
My friends warned me ‘You don’t become a scala developer by deleting return’ , and they are right …. 😦
Global should be in root package or should be written in application.conf file with the package name 😉
I bumped into a meaningless error ( for me 🙂 ) when I try to build a project in xcode 6 with el capitan
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc failed with exit code 11
Just clean and build again, it disappears 🙂
Avoid using any app icon including transparency as it will result with icon having a black backgroud which is ugly. The documentation actually states this here https://developer.apple.com/library/ios/documentation/userexperience/conceptual/mobilehig/AppIcons.html
Avoid transparency. An app icon should be opaque. If the icon’s boundaries are smaller than the recommended sizes—or you use transparency to create “see-through” areas—the resulting icon can appear to float on a black background, which tends to look especially unattractive on the beautiful wallpapers that users choose.