vogellacompany/tutorials.technology

Tutorials from vogella.com in the category technology

Technology tutorials from vogella.com

Contributions

We gladly and thankfully accept pull requests to improve the content of our tutorials. See Contributing to this repo for the legal details.

How to build

In the root directory the following commands can be used to build different outputs.

// create HTML 5
./gradlew cH

// create PDF
./gradlew cP

// create EPub 3
./gradlew cE

// create All (HTML 5, PDF, EPub 3)
./gradlew cA

Alternativly the command can be changed to:

/gradlew -t xx

this will triger an automatical run of the command once a change is saved in the adoc files.

If these commands are run in the root directory all subprojects will be build.

Tip	Single subprojects can be build when navigating into a subproject and for example run ../gradlew cH

Note	On Windows OS ./gradlew.bat must be used See CSS tutorial

Create a new tutorial

1. Create a new project(a sub-directory) in the root directory

2. Add the new project to the settings.gradle file (include '{newProjectName}')

3. Open new project in terminal and run ../gradlew cT to run the createTemplate task

Publish HTML task for Jenkins

Currently the jenkins build server is used to copy the HTML tutorials from an '/output' folder to the actual webserver, therefore the publishHtml task can be used to create the HTML Tutorials and copy the HTML tutorials to a '/asciidocOutput' folder.

tutorials.technology's Issues

Add more infos to Git Submodule article

• fix reference in Git/332_merge.adoc#L71
• git submodule add https://github.com/chaconinc/DbConnector
• initial setup & update:
  git submodule init
  git submodule update
  options:
  --remote: checkout latest commit instead of commit specified by superproject
  --recursive: init/update all subsubprojects recursively
  -j $number: update/download $number submodules at once
• pull/fetch new commits of submodules too:
  git fetch --recurse-submodules
  git pull --recurse-submodules
• git submodule foreach

How can we generalize the Gradle tutorial creation code?

I'm very impressed with your Gradle skills @SimonScholz

For example great to see that you have separated the code to create a template. As we plan to move all vogella tutorials to Asccidoc, how can this code be made reusable? Could we move it to a "real" Gradle plug-in and publish it on Maven Central / Bintray?