*What*
The local development workflow for apbs explained in out documentation / \ [1 / \ ] expects you to build and push apb images to an external registry (docker hub) and pull them again from within your local minishift or openshift cluster. This is very time consuming and not a great development experience.
The apb tools themselves now allow for proper local development of apbs using a local cluster without the need of external registries / \ [2 / \ ]. We should update all our documentation to point developers of the mobile apbs to the correct way of setting up a local development environment for apbs.
We also need to remove references inside the Makefiles where we are forcing the current approach of running the tools inside the container / \ [3 / \ ] . This instead should be left up to the developer to install the apb command locally from one of the recommended choices / \ [4 / \ ].
*How*
* Update local APB development docs
* Update minishift addon docs,
* Update that Makefile template in the apb repo
/ \ [1 / \ ]https://github.com/aerogear/mobile-core/blob/master/docs/walkthroughs/developing-apbs-locally.adoc#installing-the-apb-cli
/ \ [2 / \ ] https://github.com/ansibleplaybookbundle/ansible-playbook-bundle
/ \ [3 / \ ] https://github.com/aerogearcatalog/unifiedpush-apb/blob/master/Makefile#L14
/ \ [4 / \ ] https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/blob/master/docs/apb_cli.md#installing-the-apb-tool |
|
