If you enable s3 enpoint in your route table, it's kind of tricky to know if the endpoint is really working. Two things to validate:
1) traceroute tcp before and after (traceroute -T s3-us-west-1.amazonaws.com 443)
You will see more hope when endpoint not activated
2) try an s3 sync cross region with enpoint activated : it should failed since it's not supported (yet @ 2017-05-02)
:Glog
:clist
:cprev
:cnext
:cfirst
:clast
Pratique quand on doit jongler entre différents comptes AWS
et l'équivalent pour s3cmd : http://mikesisk.tumblr.com/post/8703449578/s3cmd-and-multiple-accounts
about:config
punycode
|jq -r '.ApplicationVersions|sort_by(.DateCreated)|.[]|.VersionLabel'|tail -1
C'est pas le 1er Twitter like décentralisé, est ce que ça va prendre ?
Via Skunnyk
diff -r folder1 folder2 | grep -P '(^diff|^Only)'
diff -r folder1 folder2 | grep -P '(^diff|^Only)' | sed -r 's/^diff -r /vimdiff /'
I may have to use this one, but issue number is freaking me out