| | |
|---|
| | | 4. [VueJS](https://vuejs.org/) - Vue (pronounced /vjuː/, like view) is a progressive framework for building user interfaces. It is designed from the ground up to be incrementally adoptable, and can easily scale between a library and a framework depending on different use cases. It consists of an approachable core library that focuses on the view layer only, and an ecosystem of supporting libraries that helps you tackle complexity in large Single-Page Applications. |
|---|
| | | |
|---|
| | | ## Big Picture |
|---|
| | | > From the previous exercise; we created some supporting tooling needed by our app. Now we will introduce our Sample App and create a pipeline for it |
|---|
| | | > From the previous exercise; we created some supporting tooling needed by our app. Now we will introduce our sample application and create a pipeline for it |
|---|
| | | |
|---|
| | |  |
|---|
| | | |
|---|
| | |
|---|
| | | |
|---|
| | | 2. Open up Gitlab and login. Create a new project (internal) in GitLab called `todolist-fe` to host your clone of the project and copy its remote address.  |
|---|
| | | |
|---|
| | | 3. In your local clone of the `todolist-fe`, remove the origin and add the GitLab origin by replacing `<YOUR_GIT_LAB_PROJECT>`. Push your app to GitLab |
|---|
| | | 3. In your local clone of the `todolist-fe`, remove the origin and add the GitLab origin by replacing `<YOUR_GIT_LAB_PROJECT>`. Push your app to GitLab. (As before, we will bypass SSL key verification in this repo since we are using self-signed certificates on the GitLab sever.) |
|---|
| | | ```bash |
|---|
| | | git config http.sslVerify false |
|---|
| | | git remote set-url origin <YOUR_GIT_LAB_PROJECT> |
|---|
| | | # verify the origin has been updated |
|---|
| | | git remote -v |
|---|
| | |
|---|
| | | 9. To prepare Nexus to host the binaries created by the frontend and backend builds we need to run a prepare-nexus script. Before we do this we need to export some variables and change `<YOUR_NAME>` accordingly in the below commands. |
|---|
| | | |
|---|
| | | <p class="tip" > |
|---|
| | | NOTE: Microsoft Windows users, run the following commands in the *do500-toolbox* container. Linux and MacOS users should skip this tep and continue from the *oc login* step. |
|---|
| | | NOTE: Microsoft Windows users, run the following commands in the *do500-toolbox* container. Linux and MacOS users should skip this step and continue from the *oc login* step. |
|---|
| | | </p> |
|---|
| | | |
|---|
| | | ```bash |
|---|
| | | docker run -it -v C:/do500-workspace:/home/tool-box/workarea:Z quay.io/jrigsbee/do500-toolbox /bin/bash |
|---|
| | | docker run -it -v C:/do500-workspace:/home/tool-box/workarea:Z quay.io/redhat/do500-toolbox /bin/bash |
|---|
| | | ``` |
|---|
| | | |
|---|
| | | ```bash |
|---|
| | |
|---|
| | | |
|---|
| | | 2. On GitLab; create a new project (internal) called `todolist-api` to host your clone of the project and copy its remote address as you did for the previous repositories. |
|---|
| | | |
|---|
| | | 3. In your local clone of the `todolist-api`, remove the origin and add the GitLab origin by replacing `<YOUR_GIT_LAB_PROJECT>`. Push your app to GitLab |
|---|
| | | 3. In your local clone of the `todolist-api`, remove the origin and add the GitLab origin by replacing `<YOUR_GIT_LAB_PROJECT>`. Push your app to GitLab. (As before, we will bypass SSL key verification in this repo since we are using self-signed certificates on the GitLab sever.) |
|---|
| | | ```bash |
|---|
| | | git config http.sslVerify false |
|---|
| | | git remote set-url origin <YOUR_GIT_LAB_PROJECT> |
|---|
| | | ``` |
|---|
| | | ```bash |
|---|
