mimcomp / mcp-standalone

Standalone version of the mobile-control-panel.

REPOSITORY ARCHIVED: See fork https://github.com/aerogear/mobile-core for continuation of this work

Mobile Control Panel (MCP)

The Mobile Control Panel is PoC for a `per namespace' service that helps developers discover, create and integrate Mobile Apps and Services on OpenShift.

• Mobile SDKs are developed and maintained in their respective repos

• The Backend is a Golang server in this repo

• The Frontend is a set of AngularJS services, controllers, views etc… in this repo that extend the OpenShift Web Console UI (via extensions)

• Services are developeed and maintained in their respective repos. They leverage the Service Catalog and various brokers to help provision them

The MCP brings all of these componments together to create a unified Mobile developer experience on top of OpenShift.

Contributing

You can develop locally on your host. Please include as much info as possible in Issues and Pull Requests. Merging to master requires approval from a reviewer and a passing CI build.

Communication

Daily communication happens on #feedhenry on freenode IRC. The [email protected] mailing list is also used for team-wide & community comms. Issues are tracked in both Jira and Github Issues. Where issues are duplicates, they should be linked so that only 1 source of info exists (automation would be nice here). Typically the core Red Hat team will create and work from Jira Issues.

Onboarding Resources

• Mobile SDKs

  • Android Sync SDK

  • Cordova/Browser Sync SDK

  • Push SDKs

  • Keycloak JS Adapter

• Backend Resources

  • Tour of Go

• Frontend Resources

  • UI src

  • AngularJS PhoneCat Tutorial

  • AngularJS API Docs

  • Patternfly

  • OpenShift Web Console

  • Customising the OpenShift Web Console (Extensions

  • Service Catalog/OpenShift Mall UI

• Catalog/Mall, Brokers & Services

  • Service Catalog

  • Ansible Service Broker (ASB) & Ansbile Playbook Bundles (APB)

  • Template Service Broker

  • fh-sync-server

  • fh-sync-server Template

  • Keycloak

  • Keycloak APB

Walkthroughs

• Local Setup

• Developing APBs Locally

• Data Sync & Keycloak Walkthough

• Keycloak Walkthrough

• Mobile CI/CD Walkthough

• 3scale Walkthrough

Videos

• FeedHenry Youtube Channel

Development Release

Release

Installing from a development release

Effectively all you need to do is add the dockerhub_tag to your install command. An example is show below. Note it is important that the image version exists in dockerhub.

make clean
ansible-playbook playbook.yml -e "dockerhub_username=$DOCKERHUB_USERNAME" -e "dockerhub_tag=${TAG}" -e "dockerhub_password=$DOCKERHUB_PASSWORD" -e "dockerhub_org=$DOCKERHUB_APBS_ORG" -e "skip_apb=keycloak-apb" --ask-become-pass

By default an admin user will be created with cluster edit permissions. To skip creating this user use --tags=local with the installer. For example:

ansible-playbook playbook.yml -e "dockerhub_username=$DOCKERHUB_USERNAME" -e "dockerhub_tag=${TAG}" -e "dockerhub_password=$DOCKERHUB_PASSWORD" -e "dockerhub_org=$DOCKERHUB_APBS_ORG" --tags=local --ask-become-pass