Best practice development workflow
- This topic has 0 replies, 1 voice, and was last updated 4 years, 4 months ago by .
Viewing 1 post (of 1 total)
Viewing 1 post (of 1 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: AEP Model › Best practice development workflow
Tagged: AEP, developer workflow, ide, MTCAP, Node-RED
Hi,
At a certain point the JS code in node-red on the MTCAP-AEP becomes too unwieldy to maintain using the node-red editor.
Looking for input from community about workflow to:
1. initial d/l of custom node-red app to developer workstation
2. make local edits on developer workstation in some editor
3. checkin to remote repo (github/bitbucket).
4. checkout from remote repo to dev workstation
5. handle “hot” deploy for emergency break fix
Want to hear from you guys about best-practice for developer to manage the workflow. pros/cons and what does/doesnt work. What are you guys using for:
1. IDE editor, which one is best to work with node-red JS code? advantages? ( we use vi mostly, now)
2. techniques/tools best most efficient way to download/upload code to/from IDE Editor/Conduit
3. how to get the JS code on conduit checked-in directly to remote repository (bitbucket/github)
We are using deviceHQ to deploy to the conduit(s) now. it seems to work pretty well , but also interested in other alternatives.