# Digitale Wettbewerb Automation Dokumentation * [FME Software](https://knowledge.safe.com/page/documentation/index.html) > FME ist eine ETL Software (Extract Transform Load). Das Ziel ist so viel von den mögliche schritte die im eine Standard Digitale Wettbewerb mit dem FME Software automatisieren zu lassen. ### Paketen Alle Arbeitspaketen sind auf dem Server gelistet: W:\4381_DWB_Halter_Worb_Sternen\4381_06_Arbeitsordner\FME ##### Paket 1 Raw Input für FME. Alle Raw Data wird zuerst gesammelt. Für das POC ist eine Google Formular erstellt. Mit den Daten werden die Umgebung Koordinaten + Projekt Spezifische Informationen abgespeichert. * [Google Formular](https://docs.google.com/forms/d/1GYl921SdRDNkzmo17Mtg_HdQbb3NAUCHDuegYEN7I3k/edit) - Input Datei * Server: W:\4381_DWB_Halter_Worb_Sternen\4381_06_Arbeitsordner\FME\Paket1_Input **Inputs**: 1. **RawData_RG.xlsx** - Diese Datei wird durch der Projektleiter gepflegt und dient als der Standard Pset Bezeichnungen für allen Digitale Wettbewerben. Es ist ganz wichtig das eine Koherente Namensbezeichnung sich nicht ändern, weil es macht die auswertungen von zukunftigen Projekten nicht möglich. 2. **RawData_PL.xls** - PL steht für Projektleiter. Von der Google Formular werden Projekt Spezifischen Daten erstellt. 3. **RawData_SchweizGrenze.xls** - Die Schweizer Grenze Max Werte sind wichtig zu Prüfen ob die Kegel Koordinaten in der Schweiz sind. Inputs im Beiden Dokumenten sind folgendes: - Einheit, Nordausrichtung, Roter Kegel, Blauer Kegel, Parzelle Name, Geschossebezeichnung, Modellgliederung, Teilnehmer Namen, Anzahl Teilnehmer, Varianten, Projekt-Pset-Name, Attribute, Email Addresse von Projektleiter ##### Paket 2 ##### Paket 3 ##### Paket 4 ##### Paket 5 ##### Paket 6 ##### Paket 7 ##### Paket 8 ##### Paket 9 ##### Paket 10 [![N|Solid](https://cldup.com/dTxpPi9lDf.thumb.png)](https://nodesource.com/products/nsolid) [![Build Status](https://travis-ci.org/joemccann/dillinger.svg?branch=master)](https://travis-ci.org/joemccann/dillinger) Dillinger is a cloud-enabled, mobile-ready, offline-storage, AngularJS powered HTML5 Markdown editor. - Type some Markdown on the left - See HTML in the right - Magic # New Features! - Import a HTML file and watch it magically convert to Markdown - Drag and drop images (requires your Dropbox account be linked) You can also: - Import and save files from GitHub, Dropbox, Google Drive and One Drive - Drag and drop markdown and HTML files into Dillinger - Export documents as Markdown, HTML and PDF Markdown is a lightweight markup language based on the formatting conventions that people naturally use in email. As [John Gruber] writes on the [Markdown site][df1] > The overriding design goal for Markdown's > formatting syntax is to make it as readable > as possible. The idea is that a > Markdown-formatted document should be > publishable as-is, as plain text, without > looking like it's been marked up with tags > or formatting instructions. This text you see here is *actually* written in Markdown! To get a feel for Markdown's syntax, type some text into the left window and watch the results in the right. ### Tech Dillinger uses a number of open source projects to work properly: * [AngularJS] - HTML enhanced for web apps! * [Ace Editor] - awesome web-based text editor * [markdown-it] - Markdown parser done right. Fast and easy to extend. * [Twitter Bootstrap] - great UI boilerplate for modern web apps * [node.js] - evented I/O for the backend * [Express] - fast node.js network app framework [@tjholowaychuk] * [Gulp] - the streaming build system * [Breakdance](https://breakdance.github.io/breakdance/) - HTML to Markdown converter * [jQuery] - duh And of course Dillinger itself is open source with a [public repository][dill] on GitHub. ### Installation Dillinger requires [Node.js](https://nodejs.org/) v4+ to run. Install the dependencies and devDependencies and start the server. ```sh $ cd dillinger $ npm install -d $ node app ``` For production environments... ```sh $ npm install --production $ NODE_ENV=production node app ``` ### Plugins Dillinger is currently extended with the following plugins. Instructions on how to use them in your own application are linked below. | Plugin | README | | ------ | ------ | | Dropbox | [plugins/dropbox/README.md][PlDb] | | GitHub | [plugins/github/README.md][PlGh] | | Google Drive | [plugins/googledrive/README.md][PlGd] | | OneDrive | [plugins/onedrive/README.md][PlOd] | | Medium | [plugins/medium/README.md][PlMe] | | Google Analytics | [plugins/googleanalytics/README.md][PlGa] | ### Development Want to contribute? Great! Dillinger uses Gulp + Webpack for fast developing. Make a change in your file and instantaneously see your updates! Open your favorite Terminal and run these commands. First Tab: ```sh $ node app ``` Second Tab: ```sh $ gulp watch ``` (optional) Third: ```sh $ karma test ``` #### Building for source For production release: ```sh $ gulp build --prod ``` Generating pre-built zip archives for distribution: ```sh $ gulp build dist --prod ``` ### Docker Dillinger is very easy to install and deploy in a Docker container. By default, the Docker will expose port 8080, so change this within the Dockerfile if necessary. When ready, simply use the Dockerfile to build the image. ```sh cd dillinger docker build -t joemccann/dillinger:${package.json.version} . ``` This will create the dillinger image and pull in the necessary dependencies. Be sure to swap out `${package.json.version}` with the actual version of Dillinger. Once done, run the Docker image and map the port to whatever you wish on your host. In this example, we simply map port 8000 of the host to port 8080 of the Docker (or whatever port was exposed in the Dockerfile): ```sh docker run -d -p 8000:8080 --restart="always" /dillinger:${package.json.version} ``` Verify the deployment by navigating to your server address in your preferred browser. ```sh 127.0.0.1:8000 ``` #### Kubernetes + Google Cloud See [KUBERNETES.md](https://github.com/joemccann/dillinger/blob/master/KUBERNETES.md) ### Todos - Write MORE Tests - Add Night Mode License ---- MIT **Free Software, Hell Yeah!** [//]: # (These are reference links used in the body of this note and get stripped out when the markdown processor does its job. There is no need to format nicely because it shouldn't be seen. Thanks SO - http://stackoverflow.com/questions/4823468/store-comments-in-markdown-syntax) [dill]: [git-repo-url]: [john gruber]: [df1]: [markdown-it]: [Ace Editor]: [node.js]: [Twitter Bootstrap]: [jQuery]: [@tjholowaychuk]: [express]: [AngularJS]: [Gulp]: [PlDb]: [PlGh]: [PlGd]: [PlOd]: [PlMe]: [PlGa]: