If you have read my another post about creating a ToDo app in react you are good to go; if not see this post.
You know that React App is a single page application containing only static assets. So, you only need to setup a mechanism to serve your static assets like CSS, JS, HTML, IMAGE, etc. files when clients ask for. Either you can use market leader HTTP servers like Apache, Nginx, etc or simple Express server that runs in Node.js.
It is a good practice to follow community standards while developing softwares. It has some major pros like
- Its easier to understand and debug/maintain software
- quicker to get help when needed from community
- It will lower development cost [Money and Time]
We will be taking the convention used by this project into consideration. react-slingshot
Make a dir called ‘todo‘ and initialize a node.js app. Continue reading
One has to be very careful for shipping new changes/features to the production server.
When feature is said to be done
Assumption: Proper development processes have been followed
SSHKit is an amazing tool to run any commands on your VPS or docker images as any user. Capistrano uses it to all the server related stuffs. In other words you can build your own deployer software or server maintenance tools using SSHKit.
$ gem install sshkit
Lets create a ruby script to create a file in my VPS’s home directory
on ['deployer@4X.79.XXX.XX1'], in: :sequence, wait: 1 do |host|
within '~' do # or '/home/deployer/'
as :deployer do
execute 'echo', 'My name is shiva > shiva.txt'
Go and check in your VPS, you see the file Continue reading
When you run
cap production deploy, it invokes the following tasks in sequence:
deploy:starting - start a deployment, make sure everything is ready
deploy:started - started hook (for custom tasks)
deploy:updating - update server(s) with a new release
deploy:updated - updated hook
deploy:publishing - publish the new release
deploy:published - published hook
deploy:finishing - finish the deployment, clean up everything
deploy:finished - finished hook
Notice there are several hook tasks e.g.
:updated for you to hook up custom tasks into the flow using
VPS/VPC deployment being at remote makes it cumbersome to know exactly what is happening under the hood during the deployment process. So, I think it would be great if we could know what is happening and what configuration the EY client sending to the VPS. Continue reading
Engineyard uses CHEF recipes to configure the server instances. You must enable the appropriate chef-recipes according to type of server environment you require.