Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
https://facebook.github.io/react-native/docs/getting-started.html#content http://facebook.github.io/react-native/docs/android-setup.html
We're going to be use io.js because node has a lot of trouble with the react-native cli.
Download io.js - https://iojs.org/en/
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
| GFORCE => git add -A && git commit --amend -C HEAD && git push -f | |
| c => git_index | |
| cbg => git rev-parse --verify HEAD | simple_clipboard | |
| g => git | |
| ga => git_add_shortcuts | |
| gaa => git add -A | |
| gap => git add -p | |
| gash => git stash | |
| gasha => git stash apply | |
| gashl => git stash list |
| Select all and delete (actually move to buffer) | |
| :%d | |
| Select all and copy to buffer | |
| :%y | |
| Use p to paste the buffer. |