This repository is not longer active and has been moved to https://github.com/syndesisio/syndesis (code & issues)
The front end application or UI for Syndesis - a flexible, customizable, cloud-hosted platform that provides core integration capabilities as a service. It leverages open source technologies like Apache Camel and OpenShift to provide a rock-solid user experience.
For the middle tier API that this client communicates with, please see the syndesis-rest repo.
- Quick Start
- Day-to-Day Workflow
- Technology Stack
- File Structure
- Getting Started
- Contributing
- Resources
- Data Mapper Updates
You can follow these steps if it's your first time setting up Syndesis, or if you want a fresh local installation to replace an existing one.
-
Make sure you have installed node version >= 6.x.x and Yarn version >= 0.18.1.
-
Get a developer deployment of Syndesis running in a Minishift environment as described in the Syndesis Quickstart. Most are specific to your environment, so follow the links below for a quick setup:
- Install a hypervisor for Minishift. For macOS, we recommend using the Docker xhyve plugin here, which can be installed using Homebrew.
- Install Minishift. For macOS, we recommend you use the Homebrew method.
- Get a local developer UI with hot reloading, using the Syndesis backend running on Minishift:
# Clone our repo:
$ git clone https://github.com/syndesisio/syndesis-ui.git
# Change directory to Syndesis:
$ cd syndesis-ui
# Start up Minishift
$ minishift start
# Make sure Minishift is running:
$ minishift status
# Which should look like:
Minishift: Running
Profile: minishift
OpenShift: Running (openshift v3.6.0+c4dd4cf)
DiskUsage: 11% of 17.9G
# Log into OpenShift with developer account
# Password: whatever you like
$ oc login -u developer
# Set environment variables to point to Minishift resources:
$ eval $(minishift oc-env)
$ eval $(minishift docker-env)
# For a fresh install of Syndesis:
$ ./scripts/syndesis-install --clean --pull
# Install the dependencies:
$ yarn install
# Start the UI server:
$ yarn start:minishiftThe yarn start:minishift command works when it can properly detect your local development machine's IP address. A proxy server inside the minishift deployment will use that IP address to connect back to the development server being run by the yarn command. If detection of the IP is failing for you, then set the SYNDESIS_DEV_LOCAL_IP env variable to your local machine's IP address before running the yarn yarn start:minishift command.
Open the Syndesis UI in your browser from the command line by running:
# To connect with Syndesis backend you don't have to use http://localhost:4200 url.
# The url has a structure similar to http://syndesis-ui-default.192.168.42.205.nip.io
# You can try to obtain it directly from Minishift configuration with one of the following commands.
# on macOS
$ open https://$(oc get routes syndesis --template "{{.spec.host}}")
# on linux
$ xdg-open https://$(oc get routes syndesis --template "{{.spec.host}}")
# on windows
$ start https://$(oc get routes syndesis --template "{{.spec.host}}")A smoke test to verify you are ready to work is to add any content at the beginning of src/app/app.component.html and verify you see the modification in the main page of the application.
If you are having issues with Minishift, you can also use https://0.0.0.0:4200/ to access the UI for quick development, but it will not use Minishift resources, so the app will not work properly.
In a separate tab, you might want to run unit tests and lint checks as you code. See below for more information on how to do that.
# Start up Minishift
$ minishift start
# Log into OpenShift with developer account
# Password: whatever you like
$ oc login -u developer
# Set environment variables to point to Minishift resources:
$ eval $(minishift oc-env)
$ eval $(minishift docker-env)
# Start the UI server:
$ yarn start:minishiftFollow the instructions above for opening the Syndesis UI in your browser.
At the end of the day you might want to stop Minishift:
$ minishift stop
Included in this stack are the following technologies:
- Language: TypeScript (JavaScript with @Types)
- Framework: Angular
- Module Bundler: Angular CLI
- Design Patterns: PatternFly Angular (Design Consistency)
- Testing: Cucumber.js (BDD Unit Test Framework), Karma (Unit Test Runner), Istanbul (Code Coverage)
- Linting: TsLint (Linting for TypeScript)
- Logging: typescript-logging (TypeScript Logging)
- Code Analysis: Codelyzer (TsLint rules for static code analysis of Angular 2 TypeScript projects)
We use the component approach in our starter. This is the new standard for developing Angular apps and a great way to ensure maintainable code by encapsulation of our behavior logic. A component is basically a self contained app, usually in a single file or a folder with each concern as a file: style, template, specs, and component class.
syndesis-ui/
│
├──docs/ * our documentation
| ├──commands.md * additional cli commands available to us
| ├──contributing.md * contribution guidelines
| ├──entities.md * entities/models and their relationships for reference
│ ├──faq.md * frequently asked questions about using syndesis
│ ├──overview.md * a technical overview for understanding the project
│ └──typescript.md * some typescript tips and resources
│
├──src/ * our source files that will be compiled to javascript
│ │
│ ├──app/ * our Angular 2 application
│ │ │
│ │ ├──user/ * an example 'user' component, based on an entity/model. can be nested further.
│ │ │ ├──user.component.ts * the primary Angular component file; essentially a controller + directive combined
│ │ │ ├──user.html * our HTML user template for the user component
│ │ │ └──user.spec.ts * our unit test for the user component
│ │ │
│ │ ├──app.component.ts * a simple version of our App component components
│ │ └──app.spec.ts * a simple test of components in app.ts
│ │
│ ├──assets/ * static assets are served here
│ │ ├──robots.txt * for search engines to crawl your website
│ │ └──service-worker.js * ignore this. Web App service worker that's not complete yet
│ │
│ ├──polyfills.ts * our polyfills file
│ └--index.html * our primary layout that contains subviews
│
├──.gitignore * let git know which files to ignore and not stage for commit
├──karma.conf.js * karma, our test runner, config file
├──LICENSE * Syndesis is available for use under the Apache 2.0 license
├──npm-shrinkwrap.json * npm's way of allowing us to control exact versions of dependencies
├──package.json * what npm uses to manage it's dependencies
├──README.md * this exact file :)
├──tsconfig.json * typescript compiler config
├──tslint.json * typescript lint config
What you need to run this app:
node(brew install nodefor OS X users)yarn(see https://yarnpkg.com/en/docs/install)angular-cli(optional, but useful for development. see here)- Ensure you're running the latest versions Node
v6.x.x+ and Yarn
You do not need to install Angular CLI globally, but we recommend it if you'd like to use the convenient commands it provides, or any of the ng commands we reference below.
To make sure your code is formatted consistently with the rest of the team's, you can run the following command to prettify it:
yarn format
The repo is commitizen friendly, after making some changes:
yarn commit
to commit them. yarn commit is the same as running git cz in this case. So, you can use all the git commit options,
for example: yarn commit -am 'Blah blah blah''.
Don't forget to add your files to staging first with git add -A. This is a git commit tool, not a total git replacement.
We use Compodoc for documentation, or here to see how to format comments. Files get generated automatically in the /documentation directory. Read the documentation here to see how to properly document features. You can automatically generate and run docs using Yarn:
yarn compodoc
Or manually with compodoc -s, or compodoc if you want it to simply generate the files in the default /documentation directory and run it with an HTTP server.
Requires having angular-cli installed globally.
ng serve --prod -aot
ng test or yarn test
ng test --watch=false
To run the linter: yarn lint
Configuration files live in /config. Configuration files are currently available for Webpack, Karma, and Protractor.
Pull requests are always welcome. Please read through our Contribution guidelines for submitting improvements.
New feature development should generally follow these guidelines.
To update the data mapper, change the commit SHA in package.json to pick up the desired code revision, then run yarn install. Verify that the projects still builds by running yarn start:prod and adjust the code as necessary based on the data mapper example usage in the README.
When updating the SHA you should also run yarn copy:assets to bring over any assets the data mapper component needs, this tasks copies them all to src/assets/dm
![pure-bot[bot] avatar](https://avatars.githubusercontent.com/u/23079786?v=4 "pure-bot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent