Puma-dev wouldn't automatically start those services. It will just start the Rails app.

Is the JS in your view or in the assets?

Thanks for your work with the gem!

1. I tried omitting the URL Helpers on the --api version and ran into undefined method issues.  Also, the default_url_options also failed without the url helpers.

2. This definitely would be a very specific use case. It was more of an illustration that ASM does support rendering partials. 

3. Not sure I follow.

I do plan on covering an elasticsearch episode which is what I currently use on several apps. My only hesitation is requiring an extra dependency. I will also cover full text search on postgresql with something like pg_search. Thanks for the suggestion!

When you do something like

git flow feature start FEATURENAME

It will create a branch called feature/FEATURENAME and it will be copied from the develop branch.

From here, you can make your code changes as needed and then make your git commits as you normally would.

If you are wanting to move your work over to another computer, you can call git flow feature publish and it will create the branch on the remote repository. You can then checkout the feature on the other computer.

When all changes and commits are made, you call 

git flow feature finish #optionally passing -m 'COMMIT MESSAGE'

and this will merge your commit back into the develop branch. Alternatively, you can publish your commit again to the remote repository and then create a merge request.