are declared in JSON 2. App design repo with UI and API access 3. Provides a hierarchical model for defining apps on a per-org basis 12 Application Model Services declare extension points Apps are containers for extensions Extensions implement extension points Overview Service App Ext1 Ext2 Ap p Ext # NCUG
IBM 2. IBM forks your repo under github.com/ibmcnxdev and syncs with ICC 3. To update your app, modify the code in the repo and issue a Pull Request 4. Your PR will either merge automatically or need to be reviewed by IBM manually 5. Upon merge, updates are synched to ICC 6. Repeat Steps 3-5 as needed 18 End to End Roundtrip Customizer GitHub ibmcnxdev repositories Code Synch via webhook IBM Connections Cloud # NCUG
have your content on github.ibm.com it needs migrating to github.com • There is a procedure • Migration Process • Make sure to have a local fork or archive of the existing repository you wish to preserve and use. • Create an account at https://github.com if you do not already have one. • Create a new repository at github.com into which you can migrate the existing customization files, taking note of the guidance below: • iYou cannot re-use the exact same repository name because Customizer builds an aggregated store of all customizations from both github.ibm.com and github.com and repository names must be unique. • There is no need to continue using the organization ID as the repository name. • Use a meaningful name for your repository. Please avoid using 'customizer' or 'customization' in the name if possible. Adhere to the github naming convention by using all lowercase letters with hyphens as separators (e.g bluemix-weather-widget, uniqueName-samples). You can rename your repository in the repository Settings tab - see Settings - Option - Repository Name - Rename. • Please include a readme file explaining the repository contents and its intended purpose, even if this is very brief and high level. • You can optionally include a licence. Ideally we hope your project will graduate to something that others would like to consume or maybe even help extend. If you add a license to your project we recommend the Apache License 2.0. • 4. Copy the files from the existing fork or archive into the new repository. • 5. Invite the email@example.com account into the new repository so that it can fork and merge from your new repository into the organization from which Customizer builds the customizations. • 6. Notify the Customizer Development Team via email at firstname.lastname@example.org when ready for content to be pulled into the Customizer organization in GitHub. • 7. Once the changes have been merged from the new repository, update the application definition JSON to reference the new repository name. • 8. Test that the customizations are functioning correctly.
the Connections Developer GitHub site: https://github.com/ibmcnxdev/ https://github.com/ibmcnxdev/global-samples https://github.com/ibmcnxdev/customizer/ https://github.com/ibmcnxdev/customizer/blob/master/README.md https://github.com/ibmcnxdev/customizer/blob/master/docs/IBMConnectionsCustomizer.md Be part of the community : https://opencode4connections.org Watch some short enablement videos on the OpenNTF YouTube channel http://bit.ly/2xmUuj5 Follow Martin’s blog: http://martindonnellyblog.wordpress.com/ 22 Summary # NCUG