DEV Community: Orestis Pantazos

iOS App Review on iPhone: Resume Builder - Professionals on App Store Connect

Orestis Pantazos — Mon, 19 Jul 2021 17:05:33 +0000

App Store Connect:
https://apps.apple.com/gr/app/resume-builder-professionals/id1569380836

YouTube Video:
https://youtu.be/089SGaIYFOw

iOS App Review on #iPhone: Resume Builder - Professionals on App Store Connect

The Resume Builder for #LinkedIn users is an iOS mobile application that offers a great user experience for building your ideal template to earn your job of your preference.

LinkedIn has a lot of jobs worldwide, but it is needed to upload a great material including in your #CV with no time.

Your job-hunting is already started on LinkedIn. Good luck!

Resume Builder - Professionals is the next social network for professionals that like LinkedIn networks and groups. Build your professional network based on Resume Builder, connect with anyone, and use your professional profile as an online resume with Apple Sign-In, Google Sign-In, Microsoft Sign-In and GitHub for developer professionals.

JOB SEARCH

• Search and apply to millions of job openings including your responsive resume
• Upload and easily submit your resume to jobs that fit on LinkedIn jobs
• Save searches and create alerts to be the first to know about new job openings and worldwide events

The Resume Builder - Professionals app has a low cost to use and download.

There are no additional subscriptions or premium plans. Find a job, create your business, find and hire the new talented persons worldwide with a really low cost on 4.99 $ all over the world.

Create a resume in a minute

Orestis Pantazos — Sun, 06 Jun 2021 15:21:00 +0000

Resume Builder for Professionals is available on App Store: https://apps.apple.com/gr/app/resume-builder-professionals/id1569380836

The iOS mobile app is already built with SwiftUI

🖇 Linux Server Commands

Orestis Pantazos — Wed, 21 Apr 2021 07:23:01 +0000

Shutdown:

sudo poweroff

Restart:

sudo reboot

Check on 80 port number if something is listening via netstat:

sudo netstat -plnt | grep ':80'

JBoss bind offset port number:

...\bin\standalone.bat -Djboss.socket.binding.port-offset=100

nginx - nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)

sudo pkill -f nginx & wait $!

sudo systemctl start nginx

☸ Install and Configure WildFly (JBoss) on Ubuntu 20.04 LTS

Orestis Pantazos — Wed, 21 Apr 2021 07:21:41 +0000

Step 1: Open the Terminal

Step 2: Update repository index

sudo apt-get update

Step 3: Install the OpenJDK package from APT

sudo apt-get install default-jdk

Step 4: Create a user and group for WildFly

sudo groupadd -r wildfly

sudo useradd -r -g wildfly -d /opt/wildfly -s /sbin/nologin wildfly

Step 5: Download the WildFly Installation file

Version_Number=22.0.1.Final

wget https://download.jboss.org/wildfly/$Version_Number/wildfly-$Version_Number.tar.gz -P /tmp

Step 6: Extract the WildFly tar.gz file to /opt folder

sudo tar xf /tmp/wildfly-$Version_Number.tar.gz -C /opt/

Step 7: Create a symbolic link to point to the WildFly installation directory

sudo ln -s /opt/wildfly-$Version_Number /opt/wildfly

Step 8: Give access to WildFly group and user

sudo chown -RH wildfly: /opt/wildfly

Step 9: Configure Wildfly to be run as a service

sudo mkdir -p /etc/wildfly

sudo cp /opt/wildfly/docs/contrib/scripts/systemd/wildfly.conf /etc/wildfly/

sudo nano /etc/wildfly/wildfly.conf

**WILDFLY_BIND=0.0.0.0**

sudo cp /opt/wildfly/docs/contrib/scripts/systemd/launch.sh /opt/wildfly/bin/

sudo sh -c 'chmod +x /opt/wildfly/bin/*.sh'

sudo cp /opt/wildfly/docs/contrib/scripts/systemd/wildfly.service /etc/systemd/system/

sudo systemctl daemon-reload

Step 10: Start the WildFly service

sudo systemctl start wildfly

sudo systemctl status wildfly

sudo systemctl enable wildfly

Configure WildFly

Step 1: Allow traffic on port 8080

sudo ufw allow 8080/tcp

Step 2: Create a WildFly Administrator

sudo /opt/wildfly/bin/add-user.sh

Step 3: Access and verify the successful setup of WildFly

IP address: **http://192.168.1.8:8080**

Managing the Administrative console remotely

sudo nano /etc/wildfly/wildfly.conf

WILDFLY_CONSOLE_BIND=0.0.0.0

sudo nano /opt/wildfly/bin/launch.sh

$WILDFLY_HOME/bin/domain.sh -c $2 -b $3 -bmanagement $4

else

$WILDFLY_HOME/bin/standalone.sh -c $2 -b $3 -bmanagement $4

sudo systemctl restart wildfly

sudo nano /etc/systemd/system/wildfly.service

ExecStart=/opt/wildfly/bin/launch.sh $WILDFLY_MODE $WILDFLY_CONFIG $WILDFLY_BIND $WILDFLY_CONSOLE_BIND

sudo systemctl daemon-reload

sudo systemctl restart wildfly

Open the Administrative Console CLI

cd /opt/wildfly/bin/

./jboss-cli.sh --connect

DevOps Community: Android mobile app

Orestis Pantazos — Mon, 23 Nov 2020 09:03:55 +0000

DevOps Community is Android mobile application as an open community for software developers and DevOps engineers. The users can navigate and write an article like in their blog for AWS (Amazon Web Services), GCP (Google Cloud Platform), and Azure for cloud technologies, Docker, Kubernetes, Firebase and Java.

The Android mobile application provides categories as shown below:

☕ Java
🔥 Firebase
🌊 Docker
⚓ Kubernetes
☁ Cloud technologies

Please provide your best article and it will published on https://opendevops.dev/ website.

Thank you everyone for your support.

https://play.google.com/store/apps/details?id=com.apps.tech.software.devops

Open DevOps - JBoss Explained in 3 minutes

Orestis Pantazos — Mon, 23 Nov 2020 08:16:10 +0000

YouTube:

🔧 Git: The Story Book

Orestis Pantazos — Wed, 30 Sep 2020 07:11:31 +0000

Git Cheat Sheet

Introduction

Git is a distributed version control system that supports collaboration through teams in the corporation. Teams of developers and open-source software maintainers basically handle and manage their projects through Git. It is very useful as open-source software toolkit for developers and DevOps engineers.

Git is ready to download it from the official website and is available for Linux, MacOS and Windows.

Setup Git

Check your Git version with the following command.

git --version

Initialize the current working directory as a Git repository with the following command.

git init

Clone your projects from hosted remotely Git repositories with specified repo's URL or server location on GitHub or GitLab instances.

git clone https://www.github.com/username/repo-name

Show your current Git directory's remote repository.

git remote

Staging

Check the status of your Git repo including files added that are not staged and the files that are staged also.

git status

Include all the available files in the current working directory.

git add .

Remove a file from staging within your working directory.

git reset CDI.java

Committing

Commit the staged files with meaningful commit message that you can track your commits later on.

git commit -m "Added new files"

Branches

Show all available current branches with the following command.

git branch

Create a new branch on your working directory.

git branch new-branch

Switch to another existing branch and checkout to your current working directory.

git checkout another-branch

Create the branch and switch to the new one to your current working directory.

git checkout -b new-branch

Merge the specific branch's history into the current one's.

git merge branch-name

Collaborate and Update

Fetch and merge any commits from the tracking remote branch.

git pull

Push your local branch commits to the remote repository branch.

git push origin main

Inspecting

Display the commit history for the currently active branch.

git log

🛠 DevOps Developer Ecosystem by JetBrains

Orestis Pantazos — Wed, 30 Sep 2020 07:10:33 +0000

What configuration management tools do you or your organization use?

26% Ansible
22% Custom solution
8% Chef
7% Puppet
4% Salt
3% Other
43% None

What server templating tools do you or your organization regularly use?

60% Docker
8% Vagrant
4% Packer
1% CoreOS rkt
2% Other
36% None

What infrastructure provisioning tools do you or your organization use?

21% Terraform
19% AWS CloudFormation
7% AWS CDK
6% OpenStack Heat
1% TOSCA/Cloudify
5% Other
55% None

What container orchestration services do you use in production, if any?

40% Kubernetes (self-managed or fully managed)
14% Amazon ECS / Fargate
14% Docker Swarm
7% Amazon EKS
2% Mesos or DC / OS
1% CoreOS Tectonic
1% Hashicorp Nomad
3% Other
40% None

How do you deploy your Docker images to the docker repository, if you do?

44% I deploy from CI / CD
34% I use only the command line
25% I do not deploy
9% I deploy with custom / in-house tools
9% I use a configuration management tool (Chef, Puppet, Ansible, etc.)
1% Other

Which cloud services do you use?

62% Amazon Web Services
30% Google Cloud Platform
25% Microsoft Azure
14% Heroku
3% RedHat OpenShift
2% Cloud Foundry
1% IBM SoftLayer
1% Rackspace
18% Other

🌊 How To Secure Nginx with Let's Encrypt on Ubuntu 18.04 in DigitalOcean

Orestis Pantazos — Wed, 30 Sep 2020 07:09:11 +0000

Step 1

Installing Certbot

sudo add-apt-repository ppa:certbot/certbot

sudo apt install python-certbot-nginx

Step 2

Confirming Nginx’s Configuration

sudo nano /etc/nginx/sites-available/example.com

/etc/nginx/sites-available/example.com

...
server_name example.com www.example.com;
...

sudo nginx -t

sudo systemctl reload nginx

Step 3

Allowing HTTPS Through the Firewall

sudo ufw status

Output
Status: active

To                         Action      From
--                         ------      ----
OpenSSH                    ALLOW       Anywhere                  
Nginx HTTP                 ALLOW       Anywhere                  
OpenSSH (v6)               ALLOW       Anywhere (v6)             
Nginx HTTP (v6)            ALLOW       Anywhere (v6)

sudo ufw allow 'Nginx Full'
sudo ufw delete allow 'Nginx HTTP'

sudo ufw status

Output
Status: active

To                         Action      From
--                         ------      ----
OpenSSH                    ALLOW       Anywhere
Nginx Full                 ALLOW       Anywhere
OpenSSH (v6)               ALLOW       Anywhere (v6)
Nginx Full (v6)            ALLOW       Anywhere (v6)

Step 4

Obtaining an SSL Certificate

sudo certbot --nginx -d example.com -d www.example.com

Output
Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
-------------------------------------------------------------------------------
1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you're confident your site works on HTTPS. You can undo this
change by editing your web server's configuration.
-------------------------------------------------------------------------------
Select the appropriate number [1-2] then [enter] (press 'c' to cancel):

Output
IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/example.com/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/example.com/privkey.pem
   Your cert will expire on 2018-07-23. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot again
   with the "certonly" option. To non-interactively renew *all* of
   your certificates, run "certbot renew"
 - Your account credentials have been saved in your Certbot
   configuration directory at /etc/letsencrypt. You should make a
   secure backup of this folder now. This configuration directory will
   also contain certificates and private keys obtained by Certbot so
   making regular backups of this folder is ideal.
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

Step 5

Verifying Certbot Auto-Renewal

sudo certbot renew --dry-run

🛡 Install Let's Encrypt Certificate on JBoss WildFly in Linux

Orestis Pantazos — Wed, 30 Sep 2020 07:07:43 +0000

Please make sure that you have the following PEM-encoded files:

cert.pem: Server certificate only
chain.pem: Root and intermediate certificates only, Let’s Encrypt chain
fullchain.pem: Previous cert.pem and chain.pem combined
privkey.pem: Your certificate's private key

Download the certbot-auto script

Change directory to your home directory

cd /home/orestis

Download certbot-auto from the internet as a superuser

sudo wget https://dl.eff.org/certbot-auto

Change mode for full-write access to this directory

sudo chmod a+x certbot-auto

The certbot is hopefully installed now, and we need to ask it to renew or create the certificate.

Stop all background services that are already running on port 80.

certbot-auto renew

EXAMPLE:

certbot-auto certonly --standalone --standalone-supported-challenges http-01 --agree-tos --rsa-key-size 4096 --renew-by-default --email admin@example.com -d example.com -d www.example.com

REAL EXAMPLE:

certbot-auto certonly --standalone --standalone-supported-challenges http-01 --agree-tos --rsa-key-size 4096 --renew-by-default --email opantazos@gmail.com -d opendevops.dev -d www.opendevops.dev

The command line argument shows something like this in the end:

IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at
/etc/letsencrypt/live/*/fullchain.pem. Your cert will
expire on *. To obtain a new or tweaked version of this
certificate in the future, simply run certbot-auto again. To
non-interactively renew *all of your certificates, run
"certbot-auto renew"*
- If you like Certbot, please consider supporting our work by:
Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
Donating to EFF: https://eff.org/donate-le

NOTE:

If you are working in Java environment, then the Java key store is the official place to store your private keys. Java desktop or web applications typically expect to get the keys that they need from JKS, and it is easy to access from your own Java applications. JKS is not accessible from outside Java environment.

PKCS#12 files (PFX) are the file format that is often called .p12 or .pfx where you can store a private key and certificates.

We nede to get the public and private keys into JBoss WildFly application server. For example, Apache, Nginx servers that were setup with the public and private keys pointed to separately, instead of, generally in Java, WildFly works off of a keystore (.jks). We need to convert the PEM file into a P12 file that is readable format by Java keytool.

Use OpenSSL security toolkit:

Example:

openssl pkcs12 -export -in /etc/letsencrypt/live/YOURDOMAIN/fullchain.pem -inkey /etc/letsencrypt/live/YOURDOMAIN/privkey.pem -out KEYSTORENAME.p12 -name KEYSTOREALIAS

Real Example:

YOURDOMAIN replacement is the folder corresponding to the domain object that you are generating the key for, and was present in the listed console output from the previous step.

KEYSTORENAME will become part of the generated file name (.p12), and will be used in the JBoss WildFly XML part of the configuration, as the KEYSTOREALIAS.

When you have pressed ENTER shortcut, you will be prompted and verified for a new password credential. This new password will be used in a moment, when we generate the keystore.

Generating Java keystore (.jks)

Example:

/usr/lib/jvm/jdk1.7.0_80/bin/keytool -importkeystore -deststorepass WILDFLY_NEW_STORE_PASS -destkeypass WILDFLY_NEW_KEY_PASS -destkeystore NEW_KEYSTORE_FILE.jks -srckeystore KEYSTORENAME.p12 -srcstoretype PKCS12 -srcstorepass PREVIOUSPASSWORD -alias KEYSTOREALIAS

Real Example:

/usr/lib/jvm/jdk1.8.0_80/bin/keytool -importkeystore -deststorepass athens -destkeypass athens -destkeystore mycert.jks -srckeystore mycert.p12 -srcstoretype PKCS12 -srcstorepass athens -alias mycert

Go to JBoss WildFly server config directory as superuser and copy the file mycert.jks:

sudo cp mycert.jks /opt/wildfly/standalone/configuration/

WILDFLY_NEW_STORE_PASS: It is keystore password credential
WILDFLY_NEW_KEY_PASS: It is the destination keystore password
NEW_KEYSTORE_FILE: It is the final .jks file name

Go to standalone.xml configuration file, follow and transfer the rule cases:

Example:

<server-identities>
   <ssl>
      <keystore path="NEW_KEYSTORE_FILE.jks" 
                relative-to="jboss.server.config.dir" 
                keystore-password="WILDFLY_NEW_STORE_PASS" 
                alias="KEYSTOREALIAS" 
                key-password="WILDFLY_NEW_KEY_PASS"/>
   </ssl>
</server-identities>

Real Example:

<server-identities>
   <ssl>
      <keystore path="mycert.jks" 
                relative-to="jboss.server.config.dir" 
                keystore-password="athens" 
                alias="mycert" 
                key-password="athens"/>
   </ssl>
</server-identities>

Last but not least, start the WildFly application server on run mode.

.\standalone.sh -b 0.0.0.0

🔥 Firebase Android Release Notes

Orestis Pantazos — Wed, 30 Sep 2020 06:57:06 +0000

To review release notes for the Firebase console and for other Firebase platforms and related SDKs, refer to the Firebase Release Notes.

Learn how to install these SDKs in your app: Add Firebase to your Android Project.

Latest SDK versions

build.gradle

buildscript {

  repositories {
    // Check that you have the following line (if not, add it):
    google()  // Google's Maven repository
  }

  dependencies {
    // ...

    // Add the following line:
    classpath 'com.google.gms:google-services:4.3.3'  // Google Services plugin
  }
}

allprojects {
  // ...

  repositories {
    // Check that you have the following line (if not, add it):
    google()  // Google's Maven repository
    // ...
  }
}

app/build.gradle

apply plugin: 'com.android.application'
// Add the following line:
apply plugin: 'com.google.gms.google-services'  // Google Services plugin

android {
  // ...
}

app/build.gradle

Analytics enabled

dependencies {
  // ...

  // Add the Firebase SDK for Google Analytics
  implementation 'com.google.firebase:firebase-analytics:17.4.0'

  // Add the dependencies for any other Firebase products you want to use in your app
  // For example, to also use Firebase Authentication
  implementation 'com.google.firebase:firebase-auth:19.3.1'

  // Getting a "Could not find" error? Make sure that you've added
  // Google's Maven repository to your root-level build.gradle file
}

Analytics not enabled

dependencies {
  // ...

  // Add the dependencies for the Firebase products you want to use in your app
  // For example, to use Firebase Authentication
  implementation 'com.google.firebase:firebase-auth:19.3.1'

  // Getting a "Could not find" error? Make sure that you've added
  // Google's Maven repository to your root-level build.gradle file
}

Java Android

Service or Product

AdMob

com.google.android.gms:play-services-ads:19.1.0

Analytics

com.google.firebase:firebase-analytics:17.4.0

App Indexing

com.google.firebase:firebase-appindexing:19.1.0

Authentication

com.google.firebase:firebase-auth:19.3.1

Cloud Firestore

com.google.firebase:firebase-firestore:21.4.3

Cloud Functions for Firebase Client SDK

com.google.firebase:firebase-functions:19.0.2

Cloud Messaging

com.google.firebase:firebase-messaging:20.1.6

Cloud Storage

com.google.firebase:firebase-storage:19.1.1

Crashlytics

com.crashlytics.sdk.android:crashlytics:2.10.1

Alternatively, to use the Firebase Crashlytics SDK (beta):

com.google.firebase:firebase-crashlytics:17.0.0

Dynamic Links

com.google.firebase:firebase-dynamic-links:19.1.0

In-App Messaging

com.google.firebase:firebase-inappmessaging:19.0.6

In-App Messaging Display

com.google.firebase:firebase-inappmessaging-display:19.0.6

Performance Monitoring

com.google.firebase:firebase-perf:19.0.7

Realtime Database

com.google.firebase:firebase-database:19.3.0

Remote Config

com.google.firebase:firebase-config:19.1.4

Firebase Bill of Materials (BoM)

com.google.firebase:firebase-bom:25.3.0

The latest Firebase BoM version contains the latest versions of each Firebase Android library available at the BoM's release. For the library versions mapped to previous BoM versions, review the release notes for that version.

Google Play services plugin

com.google.gms:google-services:4.3.3

⚓ Kubernetes: The Story Book

Orestis Pantazos — Sun, 22 Mar 2020 11:37:25 +0000