Following this video ---> https://www.youtube.com/watch?v=T3X7hfltr8c
https://ethereum.github.io/go-ethereum/downloads/
descomprimir y copiar a /usr/local/bin/geth
! ojo que lo tengas en el path
Following this video ---> https://www.youtube.com/watch?v=T3X7hfltr8c
https://ethereum.github.io/go-ethereum/downloads/
descomprimir y copiar a /usr/local/bin/geth
! ojo que lo tengas en el path
This is my response to an email asking about Domain-Driven Design in golang project.
Thank you for getting in touch. Below you will find my thoughts on how golang works with DDD, changing it. This is merely a perception of how things worked out for us in a single project.
That project has a relatively well-known domain. My colleagues on this project are very knowledgeable, thoughtful and invested in quality design. The story spelled out below is a result of countless hours spent discussing and refining the approach.
Conclusions could be very different, if there was a different project, team or a story-teller.
Refactoring view general checkpints
in the header of the file, in this way the flowtype binary will not ignore the file, and will statically analise it.
Proptypes is deprecated in react-native, the way Facebook team is going forward is using flowtype. To specify the types of properties
I hereby claim:
To claim this, I am signing this object:
curl -L https://packages.gitlab.com/install/repositories/runner/gitlab-ci-multi-runner/script.rpm.sh | sudo bash
sudo yum install gitlab-ci-multi-runner
sudo gitlab-ci-multi-runner install
sudo gitlab-ci-multi-runner register --url "https://gitlab.com/" --registration-token "pR5HPnsDd6c5z2arvWZR" --description "docker"
docker pull google/cloud-sdk
sudo wget https://dl.yarnpkg.com/rpm/yarn.repo -O /etc/yum.repos.d/yarn.repo
sudo yum install yarn
mkdir -p /srv/api
sudo pecl install xdebug
sudo touch /etc/php5/mods-available/xdebug.ini
edit /etc/php5/mods-available/xdebug.ini
and paste this content in to the file:
zend_extension=/usr/lib/php5/20100525/xdebug.so
xdebug.remote_enable=1
xdebug.remote_connect_back=1
xdebug.remote_port=9000
xdebug.show_local_vars=0
Gandi.net ssl certificate working with haproxy | |
In one file concatenate the certifcate with the private key (domain.pem in the example) | |
In other file just the intermediate ceritificate (gandi.ca.pem in the example) then in your haproxy.cfg | |
bind *:443 ssl crt /home/.ssh/domain.pem ca-file /home/.ssh/gandi.ca.pem | |
frontend https-in | |
bind *:443 ssl crt /home/.ssh/domain.pem ca-file /home/.ssh/gandi.ca.pem | |
timeout client 1h |
#!/bin/bash | |
MOCHA=node_modules/.bin/mocha | |
ISTANBUL=node_modules/.bin/istanbul | |
COVERALLS=node_modules/coveralls/bin/coveralls.js | |
# test files must start with "test*.js" | |
TESTS=$(shell find test/ -name "test*.js" -not -path "*service/*") | |
SERVICETEST=$(shell find test/service/ -name "test*.js" ) | |
test: | |
$(MOCHA) -R spec $(TESTS) | |
test-service: |
body { | |
padding-top: 120px; | |
padding-bottom: 40px; | |
background-color: #eee; | |
} | |
.container { | |
width: 50%; | |
} | |
.btn | |
{ |