According to the official website of Spack,

Spack is a package manager for supercomputers, Linux, and macOS. It makes installing scientific software easy. Spack isn’t tied to a particular language; you can build a software stack in Python or R, link to libraries written in C, C++, or Fortran, and easily swap compilers or target specific microarchitectures.

This makes it a tool for a very specific sector but also for users who need a similar tool. With Spack, you can build a package with multiple versions, configurations, platforms, and compilers, and all of these builds can coexist on the same machine.

For such a professional tool, it’s very easy to install on Ubuntu 20.04

Install Spack on Ubuntu 20.04

Before you start, update all the operating system packages by running the following commands in the terminal:

sudo apt update
sudo apt upgrade

After that, install git and the Ubuntu package building tools.

sudo apt install git build-essential

Once the installation is finished, it’s time to install Spack.

To do this, you can use git and specify a directory where you want to save the archive.

git clone https://github.com/spack/spack ~/.apps/spack/Spack

In my case, I have chosen ~/.apps/spack/Spack but you can choose another path.

Now, to use Spack from any location at the prompt, you have to add this folder to the PATH.

echo '. ~/.apps/spack/Spack/Spack/share/spack/setup-env.sh' >> ~/.bash_profile

Then, apply the changes by running

source ~/.bash_profile

And we can start using it, for example, it shows the installed version:

spack -V
0.16.0-1053-f28026c040

Using Spack on Ubuntu 20.04

The tool is quite simple to use, to install a program you just need to run

spack install [program_name]

Also, you can install the specific version of a program with the help of the @ sign.

spack install [program_name]@version

Now to know the version list of a program, you can use versions

spack versions [program_name]

If you want to know which packages or programs are available, you can do so with the list command

spack list

You can even filter them using a wildcard

spack list 'py-*'

In this case, all packages starting with py- will be shown.

To uninstall packages we can use the same syntax as install but with the uninstall command

spack uninstall [program_name]

Or for a specific version:

spack uninstall [program_name]@version

Also, it is useful to remove its dependencies with the -R option.

spack uninstall -R [program_name]

So, enjoy it.

Conclusion

Thanks to this post, you now know how to install Spack on Ubuntu 20.04 which is a tool used at a scientific level. It is quite easy to use and to install for all it does.

The post Install Spack on Ubuntu 20.04 appeared first on Linux Windows and android Tutorials.

Lighttpd is a “secure, fast, compatible and very flexible” web server optimized for high-performance environments. It consumes very few resources compared to other web servers and especially fast for running AJAX applications. It is also open source and uses a BSD license and works on UNIX-like systems, such as Linux or BSD.

Generally, Lighttpd is used in servers where maximum performance is needed even at the sacrifice of some features. Despite this, Lighttpd is always a good alternative to the popular Apache and Nginx.

Install Lighttpd on FreeBSD 12

For this tutorial, you need to have sudo enabled. For this, I recommend you to read our post about it:

How to enable sudo on FreeBSD 12?

Before starting with the tutorial, it is recommended to update the system completely, to do it, open a terminal emulator or connect to your server using SSH and write:

:~$ sudo pkg update

Now we can really get started with the tutorial.

1.- Install Lighttpd

Lighttpd is available from the official FreeBSD repositories. Therefore, the installation will not result in problems. So to install it, use the following command:

:~$ sudo pkg install lighttpd
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01    
Fetching packagesite.txz: 100%    6 MiB  53.0kB/s    02:02    
Processing entries: 100%
FreeBSD repository update completed. 31558 packages processed.
All repositories are up to date.
The following 4 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
lighttpd: 1.4.54
lua52: 5.2.4
libedit: 3.1.20191211,1
pcre: 8.43_2

Number of packages to be installed: 4

The process will require 10 MiB more space.
2 MiB to be downloaded.

Proceed with this action? [y/N]:

After entering the password, the download will start.

For now, we won’t start the Lighttpd service because there are some settings we have to make first.

2.- Install PHP on FreeBSD 12

Of course, if we install only Lighttpd we won’t be able to run any web application made with PHP. This brings a consequence that the functionality would decay. So let’s install it:

:~$ sudo pkg install php74 mod_php74 php74-mbstring php74-zlib php74-curl php74-gd php74-json

I took the opportunity to install some extra modules.

Now we have to make some modifications to PHP so that it can work without problems with Lighttpd.

First open the file /usr/local/etc/php-fpm.d/www.conf and make these changes.

Find the line:

listen = 127.0.0.1:9000

And exchange it for this one:

listen = /var/run/php-fpm.sock

Then, locate the following lines and decomment them:

;listen.owner = www
;listen.group = www
;listen.mode = 0660

Looking like this in the picture:

So, save the changes and close the file.

Now it is necessary to create a new php.ini file. During the installation, two example files are created that we have to use depending on the function of our computer. These files are php.ini-production and php.ini-development.

So we have to choose one, in my case, I will assume that FreeBSD 12 is for production, so that will be my choice.

Note: it is likely that if you choose the other one this tutorial will work as well.

So, we copy the example file as php.ini:

:~$ sudo cp /usr/local/etc/php.ini-production /usr/local/etc/php.ini

And we edited the file in question:

:~$ sudo nano /usr/local/etc/php.ini

And locate the line:

;cgi.fix_pathinfo=1

And exchange it for this one:

cgi.fix_pathinfo=0

Again, save the changes and close the file.

Now we can start and enable the PHP-fpm service.

:~$ sudo sysrc php_fpm_enable=yes
php_fpm_enable: -> yes
:~$ sudo service php-fpm start
Performing sanity check on php-fpm configuration:
[20-Feb-2020 14:50:21] NOTICE: configuration file /usr/local/etc/php-fpm.conf test is successful
Starting php_fpm.

3.- Configuring Lighttpd on FreeBSD 12

In this section of the tutorial, we have to make some configurations to Lighttpd so that it can work with PHP.

So, open the file /usr/local/etc/lighttpd/modules.conf

:~$ sudo nano /usr/local/etc/lighttpd/modules.conf

And uncomment the line:

include "conf.d/fastcgi.conf"

What this does is to include the fastcgi module which is the one we will use for Lighttpd to process PHP.

At the end of that same file, add the following:

fastcgi.server += ( ".php" =>
        ((
                "socket" => "/var/run/php-fpm.sock",
                "broken-scriptfilename" => "enable"
        ))
)

Save the changes and close the editor.

Before starting the service, edit the main Lighttpd configuration file and uncomment the line:

:~$ sudo nano /usr/local/etc/lighttpd/lighttpd.conf

server.bind = "localhost"

So, you can save the changes and close the file.

If your server uses IPv6, you have to locate this line as well and leave it as it is:

server.use-ipv6 = "enable"

And at the end of the file comment on this line:

$SERVER["socket"] == "0.0.0.0:80" { }

Remember, this is only if your server uses IPv6, if not omit this.

Now, enable and start the Lighttpd service:

:~$ sudo sysrc lighttpd_enable=yes
lighttpd_enable: -> yes

:~$ sudo service lighttpd start

So, we are going to test it.

4.- Testing Lighttpd and PHP on FreeBSD 12

Now we’re going to try everything we’ve done. The best way is to create a PHP file for the server to run.

First, create the folder where Lighttpd will look for the web files. In other words, the root directory.

:~$ sudo mkdir -p /usr/local/www/data

And now create a PHP file called test.php and add the following:

:~$ sudo nano /usr/local/www/data/test.php
<?php
phpinfo();
?>

Save the changes and close the file.

Now open your favorite web browser and go to http://server-ip/test.php and you will see the following:

So, that is it. If you want to use a database management program in FreeBSD 12, you can check these posts:

How to install PostgreSQL on FreeBSD 12?

How to install SQLite on FreeBSD 12?

So, enjoy it.

Conclusion

Lighttpd is less popular than Apache and Nginx, that’s for sure, but it’s quite useful on small servers or when we want maximum performance in a web application. Today thanks to this post, you have learned how to install it on FreeBSD 12.

Please share this post and join our Telegram channel.

The post How to install lighttpd on FreeBSD 12? appeared first on Linux Windows and android Tutorials.

PostgreSQL

PostgreSQL is one of the most advanced and modern relational database managers out there. It is always shown as the immediate competitor of MySQL and MariaDB in the segment of open source and community database managers.

One of the main advantages of using PostgreSQL is that it has extensive documentation and supports powerful features. All this in an open-source and free application.

And recently version 12 has been released. If you want to know more about it read our post about it.

PostgreSQL 12.0 is available

This new version includes security improvements and interesting new features so it’s a good idea to install it.

So, let us start.

Install PostgreSQL on FreeBSD 12

In this guide, we will use commands that require you to be root. In this case, we will choose a user with privileges to use sudo. In case your user can’t do it, you can read our post.

How to enable sudo on FreeBSD 12.

If you are already the root user, you can simply remove the word sudo from the following commands.

The first step is to upgrade the system completely. To do this, open your FreeBSD terminal and run the following command:

:~$ sudo pkg update

After this, the system will be ready for work.

The goal of this post is to install PostgreSQL 12 on FreeBSD but in the official repositories, we have several versions of PostgeSQL.

:~$ sudo pkg search ^postgresql |grep -i server
postgresql10-server-10.11      PostgreSQL is the most advanced open-source database available anywhere
postgresql11-server-11.6       PostgreSQL is the most advanced open-source database available anywhere
postgresql12-server-12.1       PostgreSQL is the most advanced open-source database available anywhere
postgresql94-server-9.4.25     PostgreSQL is the most advanced open-source database available anywhere
postgresql95-server-9.5.20     PostgreSQL is the most advanced open-source database available anywhere
postgresql96-server-9.6.16     PostgreSQL is the most advanced open-source database available anywhere

The above command performs a search of the PostgreSQL package repositories but refines the search to server.

As you can see, versions 9.4, 9.5, 9.6,10,11 and 12 are available. Let’s install the version 12. To do so, run the following:

:~$ sudo pkg install postgresql12-server
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 5 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	postgresql12-server: 12.1
	icu: 65.1,1
	postgresql12-client: 12.1
	perl5: 5.30.1
	readline: 8.0.1

Number of packages to be installed: 5

The process will require 141 MiB more space.
31 MiB to be downloaded.

Proceed with this action? [y/N]:

Then, the installation will start normally.

Once the installation is complete, the first thing to do is to get PostgreSQL started with the system. This is not mandatory but it is convenient in many cases.

So to do this, edit the /etc/rc.conf file

:~$ sudo nano /etc/rc.conf

Now add the following:

postgresql_enable="YES"

Save the changes and close the file. In case you don’t have nano installed, you can do it with the following command:

:~$ sudo pkg install nano

Before starting the PostgreSQL service the default database must be initialized. To do this, run the following command:

:~$ sudo service postgresql initdb
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "C".
The default text search configuration will be set to "english".

Data page checksums are disabled.

creating directory /var/db/postgres/data12 ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... America/Caracas
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    /usr/local/bin/pg_ctl -D /var/db/postgres/data12 -l logfile start

And now you can start the PostgreSQL service with the following command:

:~$ sudo service postgresql start
2020-02-05 14:52:37.731 -04 [869] LOG:  starting PostgreSQL 12.1 on amd64-portbld-freebsd12.0, compiled by FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1), 64-bit
2020-02-05 14:52:37.732 -04 [869] LOG:  listening on IPv6 address "::1", port 5432
2020-02-05 14:52:37.732 -04 [869] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2020-02-05 14:52:37.735 -04 [869] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2020-02-05 14:52:37.749 -04 [869] LOG:  ending log output to stderr
2020-02-05 14:52:37.749 -04 [869] HINT:  Future log output will go to log destination "syslog".

Finally, access the PostgreSQL console with the following command:

:~$ sudo -u postgres psql

As you can see you can already use PostgreSQL 12 on FreeBSD without problems.

Conclusion

PostgreSQL is perhaps the best open source database manager and this consideration has not been given away. It has been earned with many jobs and above all with extraordinary performance. Now you know how to install it on FreeBSD 12.

Share this post and join our Telegram channel.

The post Install PostgreSQL on FreeBSD 12 appeared first on Linux Windows and android Tutorials.

FFmpeg is an open source software (also a command line tool) used for transcoding multimedia files. FFmpeg consists of shared libraries like libswresample, libavcodec, libavformat, libavutil & programs for handling video, audio & other multimedia files & streams. It provides you the facility of converting various video & audio formats. With FFmpeg you can also capture & encode in real-time from hardware such as TV capture card. Just follow the guide to easily Install FFmpeg on your Ubuntu 18.04.

Step 1: Add ppa:jonathonf/ffmpeg-4.2

Add jonathonf repo & press Enter when prompt to continue

sabi@sabi:~$ sudo add-apt-repository ppa:jonathonf/ffmpeg-4
  Backport of FFmpeg 4 and associated libraries. Now includes AOM/AV1 support!
 FDK AAC is not compatible with GPL and FFmpeg can't be redistributed with it included. Please don't ask for it to be added to this public PPA.
 
 PPA supporters:
 BigBlueButton (https://bigbluebutton.org)
 
 Donate to FFMPEG: https://ffmpeg.org/donations.html
 Donate to Debian: https://www.debian.org/donations
 Donate to this PPA: https://ko-fi.com/jonathonf
  More info: https://launchpad.net/~jonathonf/+archive/ubuntu/ffmpeg-4
 Press [ENTER] to continue or Ctrl-c to cancel adding it.

Step 2: Update the Repository index

sudo apt-get udpate

After adding PPA , Install the FFmpeg package by running

sudo apt -y  install ffmpeg

Step 3: Verifying FFmpeg Installation

Confirm the installation by verifying version of FFmpeg

sabi@sabi:~$ ffmpeg -version
 ffmpeg version 4.2.1-2~18.04.york2 Copyright (c) 2000-2019 the FFmpeg developers
 built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
 configuration: --prefix=/usr --extra-version='2~18.04.york2' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
 libavutil      56. 31.100 / 56. 31.100
 libavcodec     58. 54.100 / 58. 54.100
 libavformat    58. 29.100 / 58. 29.100
 libavdevice    58.  8.100 / 58.  8.100
 libavfilter     7. 57.100 /  7. 57.100
 libavresample   4.  0.  0 /  4.  0.  0
 libswscale      5.  5.100 /  5.  5.100
 libswresample   3.  5.100 /  3.  5.100
 libpostproc    55.  5.100 / 55.  5.100

Install Additional packages by typing

ffmpeg -encoders
ffmpeg -decoders

You have successfully installed FFmpeg on your system. It’s time to test and run the FFmpeg on your Ubuntu 18.04

Step 4: How To Use FFmpeg

Let’s take some examples to cover basic things to use FFmpeg on Ubuntu 18.04

Basic Conversion

In basic conversion you don’t have to specify the conversion formats. FFmpeg automatically detects the formats and covert them based on the file extension of an output file.

Covert a video from mp4 to WebM

ffmpeg -i video.mp4 video.webm

Advanced Conversion

In advance conversion, you can specify the codecs using -c option. Specify the name of any encoder/decoder which is supported by ffmpeg for copying the input stream along with -c.

For example, here we will covert the audio (-c:a copy) from input.webm & convert the video to a VP9 codec (-c:v vp9) with a bit rate of 1M/s (-b:v), all bundled up in a Matroska container (output.mkv)

ffmpeg -i input.webm -c:a copy -c:v vp9 -b:v 1M output.mkv

The post How To Install FFmpeg on Ubuntu 18.04 appeared first on Linux Windows and android Tutorials.

Podman is used to develop, manage and run OCI Containers on our Linux System. It runs without starting daemon every time. In today tutorial, we will cover the installation of Podman on our Debian System.

Step 1: Updating your system

Update your system by running

sudo apt -y update && sudo apt -y upgrade

Step 2: Installing pre-requisites

In our case we are going to build the packages from source code. Install the required dependencies you want to use

sudo apt -y install \

gcc \

  make \

  cmake \

  git \

  btrfs-progs \

  golang-go \

  go-md2man \

  iptables \

  libassuan-dev \

  libc6-dev \

  libdevmapper-dev \

  libglib2.0-dev \

  libgpgme-dev \

  libgpg-error-dev \

  libostree-dev \

  libprotobuf-dev \

  libprotobuf-c-dev \

  libseccomp-dev \

  libselinux1-dev \

  libsystemd-dev \

  pkg-config \

  runc \

  uidmap \

  libapparmor-dev

Step 3: Installing common

Common is used to monitor OCI run times on your Linux System. Install the latest version of common on Debian by cloning.

git clone https://github.com/containers/common
cd common
sudo make podman
sudo cp /usr/local/libexec/podman/common /usr/local/bin/

Step 4: Installing CNI Plugins

Make sure that the CNI Plugins are installed on your system. If they are not installed yet, Install them by typing

git clone https://github.com/containernetworking/plugins.git $GOPATH/src/github.com/containernetworking/plugins
cd $GOPATH/src/github.com/containernetworking/plugins
./build_linux.sh
sudo mkdir -p /usr/libexec/cni
sudo cp bin/* /usr/libexec/cni

Step 5: Setting Up CNI Networking

Now, add the configuration files by

sudo mkdir -p /etc/cni/net.d
curl -qsSL https://raw.githubusercontent.com/containers/libpod/master/cni/87-podman-bridge.conflist | sudo tee /etc/cni/net.d/99-loopback.conf

Step 6: Populate Config files

You have to manually add configuration files like registry and policy files.

sudo mkdir -p /etc/containers
sudo curl https://raw.githubusercontent.com/projectatomic/registries/master/registries.fedora -o /etc/containers/registries.conf
sudo curl https://raw.githubusercontent.com/containers/skopeo/master/default-policy.json -o /etc/containers/policy.json

Step 7: Installing Podman

After doing all the above requirements, its time to download and Install Podman on your system.

git clone https://github.com/containers/libpod/ $GOPATH/src/github.com/containers/libpod
cd $GOPATH/src/github.com/containers/libpod
make
sudo make install

You can run the command podman version to check the installed version of podman

$ podman info
 host:
   BuildahVersion: 1.9.2
   Conmon:
     package: Unknown
     path: /usr/local/bin/conmon
     version: 'conmon version 1.0.1-dev, commit: 8392df88fba944510b51c7d5b92aa745a15863f8'
   Distribution:
     distribution: debian
     version: "10"
   MemFree: 6179495936
   MemTotal: 8167223296
   OCIRuntime:
     package: 'runc: /usr/sbin/runc'
     path: /usr/sbin/runc
     version: |-
       runc version 1.0.0~rc6+dfsg1
       commit: 1.0.0~rc6+dfsg1-3
       spec: 1.0.1
   SwapFree: 0
   SwapTotal: 0
   arch: amd64
   cpus: 2
   eventlogger: journald
   hostname: debian10
   kernel: 4.19.0-5-amd64
   os: linux
   rootless: false
   uptime: 13m 44.64s
 registries:
   blocked: null
   insecure: null
   search:
 docker.io
 registry.fedoraproject.org
 registry.access.redhat.com
 store:
 ConfigFile: /etc/containers/storage.conf
 ContainerStore:
 number: 0
 GraphDriverName: overlay
 GraphOptions: null
 GraphRoot: /var/lib/containers/storage
 GraphStatus:
 Backing Filesystem: extfs
 Native Overlay Diff: "true"
 Supports d_type: "true"
 Using metacopy: "false"
 ImageStore:
 number: 0
 RunRoot: /var/run/containers/storage
 VolumePath: /var/lib/containers/storage/volumes 

Here are the main configuration files.

• /etc/containers/regestries.conf : We use this file to store the registries of domain or new container images.
• /etc/containers/mounts.conf: Keeps the record of mounted directories.

Step 8: Testing Podman Installation on Debian

Download the Alpine image by running

$ podman pull alpine
Trying to pull docker.io/library/alpine…
Getting image source signatures
Copying blob 050382585609 done
Copying config b7b28af77f done
Writing manifest to image destination
Storing signatures
b7b28af77ffec6054d13378df4fdf02725830086c7444d9c278af25312aa39b9

Run Docker Container

[root@localhost sabi]# podman images
 REPOSITORY                 TAG      IMAGE ID       CREATED       SIZE
 docker.io/library/alpine   latest   b7b28af77ffe   3 weeks ago   5.85 MB
 $ podman run -ti b7b28af77ffe /bin/sh
 / # cat /etc/os-release 
 NAME="Alpine Linux"
 ID=alpine
 VERSION_ID=3.10.1
 PRETTY_NAME="Alpine Linux v3.10"
 HOME_URL="https://alpinelinux.org/"
 BUG_REPORT_URL="https://bugs.alpinelinux.org/
 /# exit

You can remove the container by running the below command

[root@localhost sabi]# podman rm -f podman ps -aq
d16db8f39c82f50f3a2bbf4834d948b660525a5c2b98979e433c3428f613c18d

And that is it.

The post How To Install Podman on Debian on 10 / 9 appeared first on Linux Windows and android Tutorials.

Step 1: Adding PowerShell Repository

As PowerShell is not available on CentOS 7 / 8 operating system, we have to add it from Microsoft repositories by running

curl https://packages.microsoft.com/config/rhel/7/prod.repo | sudo tee /etc/yum.repos.d/microsoft.repo

Now, move towards the installation of PowerShell

Step 2: Installing PowerShell on CentOS 7 / 8

Fire the given command to get install PowerShell on RHEL / CentOS 7 / 8.

[sabi@localhost ~]$ sudo yum -y install powershell
 packages-microsoft-com-prod                            297 kB/s | 3.9 MB     00:13    
 Last metadata expiration check: 0:00:09 ago on Fri 27 Dec 2019 01:48:08 PM PKT.
 Dependencies resolved.
  Package        Arch       Version               Repository                       Size
 Installing:
  powershell     x86_64     6.2.3-1.rhel.7        packages-microsoft-com-prod      54 M
 Transaction Summary
 Install  1 Package
 Total download size: 54 M
 Installed size: 54 M
 Downloading Packages:
 powershell-6.2.3-1.rhel.7.x86_64.rpm                   1.1 MB/s |  54 MB     00:47    
 Total                                                  1.1 MB/s |  54 MB     00:47     
 warning: /var/cache/dnf/packages-microsoft-com-prod-687ce8c973efa9d3/packages/powershell-6.2.3-1.rhel.7.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID be1229cf: NOKEY
 packages-microsoft-com-prod                            358  B/s | 983  B     00:02    
 Importing GPG key 0xBE1229CF:
  Userid     : "Microsoft (Release signing) gpgsecurity@microsoft.com"
  Fingerprint: BC52 8686 B50D 79E3 39D3 721C EB3E 94AD BE12 29CF
  From       : https://packages.microsoft.com/keys/microsoft.asc
 Key imported successfully
 Running transaction check
 Transaction check succeeded.
 Running transaction test
 Transaction test succeeded.
 Running transaction
   Preparing        :                                                               1/1 
   Installing       : powershell-6.2.3-1.rhel.7.x86_64                              1/1 
   Running scriptlet: powershell-6.2.3-1.rhel.7.x86_64                              1/1 
   Verifying        : powershell-6.2.3-1.rhel.7.x86_64                              1/1 
 Installed:
   powershell-6.2.3-1.rhel.7.x86_64                                                     
 Complete!
 [sabi@localhost ~]$ 

Use the following command to get more information about powershell package.

[sabi@localhost ~]$ rpm -qi powershell
 Name        : powershell
 Version     : 6.2.3
 Release     : 1.rhel.7
 Architecture: x86_64
 Install Date: Fri 27 Dec 2019 01:49:13 PM PKT
 Group       : shells
 Size        : 156967268
 License     : MIT License
 Signature   : RSA/SHA256, Wed 11 Sep 2019 03:16:07 AM PKT, Key ID eb3e94adbe1229cf
 Source RPM  : powershell-6.2.3-1.rhel.7.src.rpm
 Build Date  : Wed 11 Sep 2019 03:11:50 AM PKT
 Build Host  : e7b300f89b4a
 Relocations : / 
 Packager    : PowerShell Team PowerShellTeam@hotmail.com
 Vendor      : Microsoft Corporation
 URL         : https://microsoft.com/powershell
 Summary     : PowerShell is an automation and configuration management platform.
 Description :
 PowerShell is an automation and configuration management platform.
 It consists of a cross-platform command-line shell and associated scripting language.

Step 3: Start and Use PowerShell on CentOS / RHEL 7 / 8

[sabi@localhost ~]$ pwsh
 PowerShell 6.2.3
 Copyright (c) Microsoft Corporation. All rights reserved.
 https://aka.ms/pscore6-docs
 Type 'help' to get help.
 PS /home/sabi> 

Now, try to run few commands to verify our Installation.

PS /home/sabi> pwd
 Path
 /home/sabi
 PS /home/sabi> mkdir /tmp/test
 PS /home/sabi> cd /tmp/test
 PS /tmp/test> pwd
 Path
 /tmp/test
 PS /tmp/test> get-process | more
 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
  ------    -----      -----     ------      --  -- -----------
       0     0.00       0.04       0.00    1213 …85 (sd-pam)
       0     0.00       0.04       0.00    2540 …32 (sd-pam)
       0     0.00       0.96       0.15     974 974 accounts-daemon
       0     0.00       0.00       0.00     122   0 acpi_thermal_pm
       0     0.00       0.41       0.00     854 854 alsactl
       0     0.00       0.97       0.02    1993 …93 at-spi-bus-laun
       0     0.00       0.96       0.01    2672 …72 at-spi-bus-laun
       0     0.00       0.00       0.01    2001 …93 at-spi2-registr
       0     0.00       0.44       0.03    2680 …72 at-spi2-registr
       0     0.00       0.00       0.00     407   0 ata_sff
       0     0.00       0.41       0.01    1077 …77 atd
       0     0.00       0.30       0.06     815 815 auditd
       0     0.00       0.75       0.11     850 850 avahi-daemon
       0     0.00       0.03       0.00     950 850 avahi-daemon
       0     0.00       3.57       0.06    4196 …96 bash
       0     0.00       1.38       0.03    2045 …45 boltd
       0     0.00       0.29       0.06     874 873 chronyd
       0     0.00       0.97       0.13    2145 …45 colord
       0     0.00       0.00       0.00      13   0 cpuhp/0
       0     0.00       0.48       0.20    1091 …91 crond
       0     0.00       0.00       0.00      24   0 crypto
       0     0.00       0.79       0.05    1063 …63 cupsd
       0     0.00       3.22       1.81     855 855 dbus-daemon
       0     0.00       0.88       0.20    1602 …02 dbus-daemon
 --More--

That is enough to substantiate our PowerShell functioning on CentOS / RHEL 8. Now you can make use of PowerShell to perform various functions & scripts.

The post How To Install PowerShell on CentOS 8 / RHEL 8 appeared first on Linux Windows and android Tutorials.

• code
• runtime
• system tools
• system libraries

And much more you can Install on a Linux server. The main specification of Docker is that it can work in any Environment.

Lets proceed with the Installation process.

Step 1: Update your System

Make sure that your system is up-to date.

sudo apt -y update

Step 2: Install Basic Dependencies

We need few dependencies for our actual Installation of Docker, so we will configure these. Install them by running the given command in your Terminal.

sudo apt -y install apt-transport-https ca-certificates curl gnupg-agent software-properties-common

Step 3: Installing Docker CE on Ubuntu 16.04 / 18.04 / 19.04

If you’re using any previous version of Docker remove them.

sudo apt remove docker docker-engine docker.io containerd runc

Now, import GPG key.

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

After it, add Docker CE repository to Ubuntu.

sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"

Final step is to Install Docker CE on Ubuntu 16.04 / 18.04 /19.04

sudo apt update
sudo apt -y install docker-ce docker-ce-cli containerd.io

Now, add your user account to docker group

sudo usermod -aG docker $user
newgrp docker

Check Docker Version to Verify your Installation.

$ docker version
 Client: Docker Engine - Community
  Version:           19.03.2
  API version:       1.40
  Go version:        go1.12.8
  Git commit:        6a30dfc
  Built:             Sun Nov 30 05:29:11 2019
  OS/Arch:           linux/amd64
  Experimental:      false

Server: Docker Engine - Community
  Engine:
   Version:          19.03.2
   API version:      1.40 (minimum version 1.12)
   Go version:       go1.12.8
   Git commit:       6a30dfc
   Built:            Sun Nov 30 05:27:45 2019
   OS/Arch:          linux/amd64
   Experimental:     false
  containerd:
   Version:          1.2.6
   GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
  runc:
   Version:          1.0.0-rc8
   GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
  docker-init:
   Version:          0.18.0
   GitCommit:        fec3683

Step 4: Install Docker Compose on Ubuntu

Congratulations! You’re all done.

Follow the below link to read :

How To Install Latest Docker Compose on Linux.

The post How To Install Docker on Ubuntu 16.04 18.04 / 19.04 appeared first on Linux Windows and android Tutorials.

Step 1: Update the system

First of all update your system by running the given command.

sudo apt -y update && sudo apt -y upgrade

Step 2: Install Node.js 13 on Ubuntu / Debian / Linux Mint

You can install node.js 13 after updating the system and then installing the required repository.

curl -sL https://deb.nodesource.com/setup_13.x | sudo bash -

After creating directory, you can move forward to Install Node.js 13 on Ubuntu / Debian / Linux Mint.

sudo apt-get install -y nodejs

You can check your installed version by following this command.

node -V

For Installing Development tools, run the following command as a root or with sudo privileges.

sudo apt-get install gcc g++ make

For yarn package Installation follow the below step

curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -

echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list

sudo apt-get update && sudo apt-get install yarn

The post How To Install latest node.js 13 on Ubuntu 19.04 / Debian / Linux appeared first on Linux Windows and android Tutorials.

What is Docker Compose?

Docker Compose is a tool that provides us the facility to define and run multi-container Docker application. A YAML file is the configuration file used to configure your application’s services.
So, we are going to Install Docker Compose in as much details as possible so you can easily understand and Install it. For this Installation we’ll check Github API releases page for our project. After it we’ll pull out the latest binary file for our Installation process. So, follow the below steps to move further.

Step 1: Installing Latest Docker Compose on Linux

Requirements:

You must have installed Curl on your system for this operation.
Access to the root or user with root privileges.

---- CentOS / RHEL -----
 $ sudo yum -y install curl
 ---- Debian / Ubuntu ----
 $ sudo apt install -y curl 
 ----- Fedora -----
 $ sudo dnf -y install curl 

After Installing curl move to the next point which is Downloading the latest Compose on your Linux Machine.

curl -s https://api.github.com/repos/docker/compose/releases/latest \
   | grep browser_download_url \
   | grep docker-compose-Linux-x86_64 \
   | cut -d '"' -f 4 \
   | wget -qi -

Make sure to make binary file executable.

chmod +x docker-compose-Linux-x86_64

Now, move the file to your PATH.

sudo mv docker-compose-Linux-x86_64 /usr/local/bin/docker-compose

Check the version you’ve installed.

docker-compose version

Step 2: Configure Compose Command-line completion.

Compose has command completion for the bash & zsh shell.

Bash users.

Place the completion script in /etc/bash_completion.d/

sudo curl -L https://raw.githubusercontent.com/docker/compose/master/contrib/completion/bash/docker-compose -o /etc/bash_completion.d/docker-compose

Source the file or re-login to enjoy completion features.

source /etc/bash_completion.d/docker-compose

Zsh users

Download the completion script in your ~/.zsh/completion/

mkdir -p ~/.zsh/completion

curl -L https://raw.githubusercontent.com/docker/compose/master/contrib/completion/zsh/_docker-compose > ~/.zsh/completion/_docker-compose

Include the directory in your $fpath by adding in ~/.zshrc

fpath=(~/.zsh/completion $fpath)

Double check that compinit is loaded or load it by adding in ~/.zshrc.

autoload -Uz compinit && compinit -i

After-it reload your shell.

exec $SHELL -l

Step 3: Test Docker Compose Installation

Make a file for testing docker compose.

vim docker-compose.yml

Copy & paste the below data in the file.

version: '3'  

services:

  web:

    image: nginx:latest

    ports:

     - "8080:80"

    links:

     - php

  php:

    image: php:7-fpm

Start the containers services.

$ docker-compose up -d
Starting root_php_1 … done
Starting root_web_1 … done

Output:

Show running Containers

$ docker-compose ps
    Name                 Command              State          Ports        
 root_php_1   docker-php-entrypoint php-fpm   Up      9000/tcp            
 root_web_1   nginx -g daemon off;            Up      0.0.0.0:8080->80/tcp

Destroy Containers.

 $ docker-compose stop
 Stopping root_web_1 … done
 Stopping root_php_1 … done 

$ docker-compose rm -f
 Going to remove root_web_1, root_php_1
 Removing root_web_1 … done
 Removing root_php_1 … done

For detailed description or learning more about Docker documentation & Docker Compose documentation visit their official page .

The post How To Install Latest Docker Compose on Ubuntu 19.04 / CentOS 8 / Debian 10 / Fedora 30 appeared first on Linux Windows and android Tutorials.

All of these steps can be performed on the host you want to register.

Step 1: Add EPEL & Foreman repositories

sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
sudo yum install -y https://yum.theforeman.org/client/2.0/el8/x86_64/foreman-client-release-2.0.0-1.el8.noarch.rpm

Step 2: Install subscription manager

sudo yum -y install subscription-manager

Now, download and install ca-consumer package to get a copy of the CA certificates from your Katello/Foreman Server.

export katello_fqdn="katello.example.com"

sudo rpm -Uvh http://$[katello_fqdn]/pub/katello-ca-consumer-latest.noarch.rpm

You should be able to resolve katello.example.com host-name in order to work for above command.

Step 3: Register CentOS Server on Katello Server.

You can register your CentOS server by running following command

sudo subscription-manager register --org="YOURORG" \

--activationkey="ACTIVATION-KEY-NAME"

Note: Replace the inverted commas text to your organization & key details.

Activation key must be created on foreman before running above command.

Step 4: Install katello agent tools

Install the katello-host-tools and katello-agent package which reports errata & package profile info, it does not allow to remotely control clients.

sudo yum -y install katello-host-tools  katello-agent katello-host-tools-tracer

Step 5: Start & enable the katello agent Services.

systemctl start goferd

systemctl enable goferd

Step 6: Update CentOS repositories

Remove or move all of your repositories except redhatrepo which are present in /etc/yum.repos.d/.

cd /etc/yum.repos.d/

sudo mkdir old

sudo mv CentOS-* epel* katello* old/

Use Katello Dashboard to verify that katello-agent is installed.

Hosts->Content Hosts->

For installing a package navigate to Hosts->Content Hosts->Select Host->Packages

Choose package action as “Package Remove” to perform action to delete.

The post How To Subscribe CentOS Server to Katello/Foreman appeared first on Linux Windows and android Tutorials.