Angular Components

ITEC 3870 Software Development II,
Roberto Salas Montoya

(License: CC BY-SA 4.0)

Prev - Angular Beginner, Next - Angular Routing

What are Angular Components?

Angular Components can be describe as a the most basic building blocks of an Angular application. In simple technical terms a component is just controller for the user interface.

Let’s create an Angular Project

In order to create Angular project we must first have Node installed in our system. You can download Node from here.

Once Node is installed the next step is to open the terminal and run the next commands to install and create our Angular application.

$ npm install -g @angular/cli

The previous command installed Angular the next command is to create a Project and give it a name.

$ ng new ComponentsDemo

The next command is to run and open our application

$ cd ComponentsDemo
ng serve --open

Accessing our Project

In order to edit and modify our Angular components application we are going to use Visual Studio Code. Download and install Visual Studio Code.

We can open our project in Visual code using the following command in the Terminal.

$ code .

Creating our Components

There are two ways to create components in Angular manually and using the Angular CLI

$ ng generate component <component name>

First Container

First we’ll create and run an Ubuntu container:

$ docker run -it --rm ubuntu bash

where

• -it is short for --interactive --tty which starts the container in interactive mode and lets you enter text via the terminal
• --rm deletes the container after it exits (but not the image)
• ubuntu is the name of the image
• bash is the command executed when the container starts
  (technically bash is already the default entrypoint for the Ubuntu image and is only used here to showcase the [COMMAND] argument)

First Container

If this is your first time using the Ubuntu image Docker will first download it from Docker Hub. If everything has gone according to plan, you should see a new prompt similar to

root@a5d9a7a5232c:/#

where

• root is the current user
• a5d9a7a5232c is the hostname (randomly generated by Docker)
• / is your current working directory (root directory in this case)
• # is another indication that you’re logged in as root (non root users have a $)

Note: In documentation, it is common to use a single dollar sign $ prompt (instead of something like root@a5d9a7a5232c:/#) for simplicity, especially when the information conveyed in a longer prompt isn’t relevant to the concepts at hand.

First Container

You can try running commands like ls to list files and folders:

$ ls
bin  boot  dev  etc  home  lib  ...  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var

or ps aux to list running processes:

$ ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  1.0  0.1   4112  3492 pts/0    Ss   17:13   0:00 /bin/bash
root        10  0.0  0.1   5900  3024 pts/0    R+   17:13   0:00 ps aux

Note: If this were a virtual machine, you would see tens, possibly hundreds of running processes instead of a small list of isolated ones.

First Container

You can also try factoring very large numbers:

$ factor 12345678901010101010101010987654321
12345678901010101010101010987654321: 19 853 32069 398053 465067 128312953569637

or:

$ yes Dr. Gunay is awesome
Dr. Gunay is awesome
Dr. Gunay is awesome
Dr. Gunay is awesome
Dr. Gunay is awesome
...

First Container

To quit, run the command exit. Since bash (PID 1) was the initial process used to start the container, once it exits, the container stops.

Because we used the --rm option, Docker should delete the container once it exits which you can verify by typing

$ docker container ls -a

however the Ubuntu image should still be saved locally:

$ docker image ls
REPOSITORY        TAG           IMAGE ID       CREATED       SIZE
ubuntu            latest        f63181f19b2f   12 days ago   72.9MB

Running Python

As another example, you can also try running Python instead of bash:

$ docker run -it --rm python:slim

Python 3.9.1 (default, Jan 12 2021, 16:56:42)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

>>> a = 5
>>> print(a + 2)
7

>>> exit()

Running Python 2.7

You can also create containers for different versions of Python:

$ docker run -it --rm python:2.7-slim

Python 2.7.18 (default, Jan 12 2021, 16:56:42)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

>>> a = 5
>>> print a+2
7

>>> exit()

Dockerfiles

Say you’d like to slightly customize an image available on Docker Hub. If you’re trying to run a Python application you could start off with the image python:slim, add your application and install any dependencies to create an image specific to your app. This is done using a Dockerfile.

Common Dockerfile Commands

• COPY <src> <dest>
  Copies files on the host at <src> to the container at the path <dest>

• RUN <command>
  Executes the command once inside the image

• ENV <key>=<value>
  Sets the environment variable <key> to <value>

• ENTRYPOINT <command>
  Executes <command> whenever the container starts

You can read more about all the different commands here.

Python Dockerfile

Create the file hello.py somewhere on your computer with the following lines:

import os

name = input('What is your name? ')
print(f'Hello {name}!')

print(os.environ.get('GOODBYE'))

Python Dockerfile

In the same folder as hello.py, create the file Dockerfile and add:

FROM python:3.9-slim

ENV GOODBYE=adios

# You can also add comments :0
COPY hello.py .

ENTRYPOINT python hello.py

$ docker build -t hello .

$ docker image ls
REPOSITORY        TAG           IMAGE ID       CREATED          SIZE
hello             latest        50b4f80bd32a   13 seconds ago   114MB

Running Your Image

Use the following command to run your image:

$ docker run -it --rm hello
What is your name? bob
Hello bob!
adios

After entering your name, the container should print a greeting, a closing, and then exit. Because of the --rm option, the container should be deleted.