LibreOffice is Dropping 32-bit Support After Version 6.2

LibreOffice is my favorite office suite as a free and powerful alternative to Microsoft Office tools on Linux. Even when I use my Windows machine – I prefer to have LibreOffice installed instead of Microsoft Office tools any day.

Now, with the recent LibreOffice 6.2 update, there’s a lot of good stuff to talk about along with a bad news.

What’s New in LibreOffice 6.2?

Let’s have a quick look at the major new features in the latest release of LibreOffice.

The new NotebookBar

libreoffice tabbed

A new addition to the interface that is optional and not enabled by default. In order to enable it, go to View -> User Interface -> Tabbed.

You can either set it as a tabbed layout or a grouped compact layout.

While it is not something that is mind blowing – but it still counts as a significant user interface update considering a variety of user preferences.

Icon Theme

libreoffice icons

A new set of icons is now available to choose from. I will definitely utilize the new set of icons – they look good!

Platform Compatibility

With the new update, the compatibility has been improved across all the platforms (Mac, Windows, and Linux).

Performance Improvements

This shouldn’t concern you if you didn’t have any issues. But, still, the better they work on this – it is a win-win for all.

They have removed unnecessary animations, worked on latency reduction, avoided repeated re-layout, and more such things to improve the performance.

More fixes and improvements

A lot of bugs have been fixed in this new update along with little tweaks here and there for all the tools (Writer, Calc, Draw, Impress).

To get to know all the technical details, you should check out their release notes.

The Sad News: Dropping the support for 32-bit

Of course, this is not a feature. But, this was bound to happen – because it was anticipated a few months ago. LibreOffice will no more provide 32-bit binary releases.

This is inevitable. Ubuntu has dropped 32-bit support. Many other Linux distributions have also stopped supporting 32-bit processors. The number of Linux distributions still supporting a 32-bit architecture is fast dwindling.

Installing LibreOffice 6.2

Libre Office 6.2 Release

Your Linux distribution should be providing this update sooner or later.

Arch-based Linux users should be getting it already while Ubuntu and Debian users would have to wait a bit longer.

If you cannot wait, you can either download the deb file or use this official PPA:

sudo add-apt-repository ppa:libreoffice/ppa
sudo apt update
sudo apt install libreoffice

Wrapping Up

LibreOffice 6.2 is definitely a major step up to keep it as a better alternative to Microsoft Office for Linux users.

Do you happen to use LibreOffice? Do these updates matter to you? Let us know in the comments below.

Source

Weekend Reading: Containers | Linux Journal

The software enabling this technology comes in many forms, with Docker as the most popular. The recent rise in popularity of container technology within the data center is a direct result of its portability and ability to isolate working environments, thus limiting its impact and overall footprint to the underlying computing system. To understand the technology completely, you first need to understand the many pieces that make it all possible. Join us this weekend as we learn about Containers.

Everything You Need to Know about Linux Containers, Part I: Linux Control Groups and Process Isolation

Truth be told, certain software applications in the wild may need to be controlled or limited—at least for the sake of stability and, to some degree, security. Far too often, a bug or just bad code can disrupt an entire machine and potentially cripple an entire ecosystem. Fortunately, a way exists to keep those same applications in check. Control groups (cgroups) is a kernel feature that limits, accounts for and isolates the CPU, memory, disk I/O and network’s usage of one or more processes.

Everything You Need to Know about Linux Containers, Part II: Working with Linux Containers (LXC)

Part I of this Deep Dive on containers introduces the idea of kernel control groups, or cgroups, and the way you can isolate, limit and monitor selected userspace applications. Here, I dive a bit deeper and focus on the next step of process isolation—that is, through containers, and more specifically, the Linux Containers (LXC) framework.

AWS Quickstart for Kubernetes

Kubernetes is an open-source cluster manager that makes it easy to run Docker and other containers in production environments of all types (on-premises or in the public cloud). What is now an open community project came from development and operations patterns pioneered at Google to manage complex systems at internet scale.

An Interview with Heptio, the Kubernetes Pioneers

Editor Petros Koutoupis spent some time chatting with Craig McLuckie, CEO of the leading Kubernetes solutions provider Heptio. Centered around both developers and system administrators, Heptio’s products and services simplify and scale the Kubernetes ecosystem.

The Search for a GUI Docker

Docker is everything but pretty; let’s try to fix that. Here’s a rundown of some GUI options available for Docker.

Managing Docker Instances with Puppet

This article focuses on how to manage Docker images and containers with Puppet.

Concerning Containers’ Connections: on Docker Networking

In this article, Frederico Kereki goes over some details of setting up a system based on several independent containers, each providing a distinct, separate role, and he explains some aspects of the underlying network configuration. You can’t think about production deployment without being aware of how connections are made, how ports are used and how bridges and routing are set up, so I examine those points as well, while putting a simple Web database query application in place

Source

Scaling up Azure Service Fabric Linux Clusters using Ubuntu Xenial? Not so fast, friend

Workaround needed if you suddenly run into trouble with latest Linux OS update

While the Redmond executioner was bringing the axe down on the neck of Azure Party Clusters, an Ubuntu security update has done the same to the Azure cloud’s Service Fabric Linux Clusters.

Problems began with a security update made on February 6 to Ubuntu Xenial (the 16.04 LTS) which arrived via the usual public Ubuntu package sources. According to Microsoft, something in that package made Service Fabric’s Image Builder process very poorly.

Image Builder is used to provision applications in Service Fabric. Thanks to the glitch, Ubuntu-based Service Fabric nodes cannot perform management operations unless users downgrade that package to the previous version.

The issue hits any new Azure-based Service Fabric clusters, any new nodes added to an existing cluster, or any nodes that have been had the upgraded package. Existing clusters that haven’t been scaled up or re-imaged should be fine, and the Fabric Service Team advised that if you’re currently unaffected, for goodness sake don’t do any scaling.

saint bernard in a party hat

Party pooper Microsoft pulls plug on Party Cluster

READ MORE

Ubuntu 16.04 LTS is, right now, the only properly supported OS for Linux Service Fabric Clusters on Azure. Red Hat Enterprise 7.4 is in preview, but you really shouldn’t be putting production workloads through it because, well, it’s a preview.

Windows operating systems, however, still enjoy greater support on the clustering platform, with Penguistas lacking some of the features their Windows brethren enjoy. The Service Fabric gang have, however, promised parity eventually. Just hopefully not in the borked management states.

In the meantime, the Azure Service Fabric team on Thursday emitted a workaround to mitigate the problem consisting of a Python script to apply as Custom Script Extension to the Azure Resource Manager (ARM) and some JSON to shovel into the ARM template for the deployment configuration.

Once done, the template can then be deployed using a helpfully provided Azure CLI or PowerShell command, and everything should be gravy for existing as well new clusters.

The gang is working to “fix the issue on our end.” but no estimate has been given as to when that fix will arrive. The Register has also contacted Ubuntu-maker Canonical to get its take on things.

Microsoft pointed to 2.3.4-4+deb8u1build0.16.04.1 of the rssh package in its original posting, but we note version 2.3.4-4+deb8u2build0.16.04.1 of rssh cropped up this morning, so a fix could well be incoming. The urgency of the rssh update is listed as medium.” ®

Source

How to Enable/Disable Edge Scrolling in Ubuntu 18.04 LTS

What is Edge Scrolling?

While working on your laptop, there is an option to scroll up and down b using the extreme right edge of your touchpad. This is exactly how you would use the middle wheel of your mouse. This edge scroll function helps you in scrolling through lengthy web pages, documents, and about everywhere where there is an option for scrolling.

While this two edge scrolling works fine for some, a few of you might find it a real nuisance as it might mess up with your current view if you accidentally touch or swipe up and down the right hand side of the touchpad. Keeping the personal preferences of all users in mind, Ubuntu has kept this option customizable. You can enable/disable this feature both through the graphical user interface and through the Ubuntu command line.

In this article, we will explain how to enable/disable touchpad edge scrolling for your Ubuntu system. We have run the commands and procedures mentioned in this article on a Ubuntu 18.04 LTS system.

Enable/Disable Edge Scrolling through the UI

If you prefer using the GUI for performing simple administrative tasks, you can make use of the graphical Settings utility.

You can access the Settings either through the system Dash or by accessing it as follows:

Click on the downward arrow located at the top-right corner of your Ubuntu desktop and then click the settings icon from the following view:

Options

The Settings utility opens in the Wi-Fi tab by default. You need to click on the Devices tab, and then the Mouse & Touchpad in order to make the required configurations.

This is how the Mouse & Touchpad view looks like:

Mouse and Touchpad settings

Alternatively, you can directly launch this view by entering relevant mouse and touchpad keywords in the Ubuntu Dash search, as follows:

Mouse and Touchpad

In the Mouse & Touchpad settings view, try to locate the Edge Scrolling button under the Touchpad section. By default, this button is switched on in Ubuntu 18.04 which means that the Edge Scrolling is enabled on your touchpad. Simply turn the button off in order to disable edge scrolling or turn it on in order to enable it. As soon as you do it, your new settings with take effect immediately.

You can now close the Settings utility.

Enable/Disable Edge Scrolling through the Command Line

For a more Terminal savvy person, we have an alternative to the UI approach of enabling/disabling edge scrolling on your Touchpad.

Open your Terminal application either through the system Dash or the Ctrl+Alt+T shortcut.

For Ubuntu 18.04, you might first need to remove the libinput Touchpad driver, if your system is currently running it. Run the following command as sudo in order to remove the mentioned driver:

$ sudo apt-get remove xserver-xorg-input-libinput libinput-tools

Remove libinput package

Please note that only an authorized user can add, remove and configure software on Ubuntu.

Then install the synaptics driver for Touchpad, that will let you make numerous configurations through it. Run the following command to install the new driver:

$ sudo apt-get install xserver-xorg-input-all xserver-xorg-input-evdev xserver-xorg-input-synaptics

Install Synaptics driver

The system might prompt you with a Y/n confirmation option in order to continue installation. Please enter Y to continue, after which the new driver will be installed on your system.

You might then need to restart your system for the new driver to be configured.

In order to view what all you can do with the synclient tool after you have installed the new driver, enter the following command:

$ synclient

Run synclient command

You will also be able to spot the VertEdgeScroll variable in the list. This is the one we will be configuring in order to enable/disable touchpad edge scrolling.

The value 1 indicates that edge scrolling is currently enabled on your system. If you want to disable edge scrolling, you can do so by running the following synclient command:

$ synclient VertEdgeScroll=0

Disable edge scrolling

Or, run the following command in order to enable it:

$ synclient VertEdgeScroll=0

As soon as you do it, your new settings with take effect immediately.

You can now close the Terminal by using the exit command:

$ exit

So whatever your preference is about edge scrolling, you can enable or disable it easily by following either of the two ways we have described in this article.

Source

Linux Today – How To Install Apache Hadoop on Ubuntu 18.04 LTS

In this tutorial we will show you how to install Apache Hadoop on Ubuntu 18.04 LTS. For those of you who didn’t know, Apache Hadoop is an open source framework used for distributed storage as well as distributed processing of big data on clusters of computers which runs on commodity hardwares. Hadoop stores data in Hadoop Distributed File System (HDFS) and the processing of these data is done using MapReduce. YARN provides an API for requesting and allocating resources in the Hadoop cluster.

This article assumes you have at least basic knowledge of Linux, know how to use the shell, and most importantly, you host your site on your own VPS. The installation is quite simple and assumes you are running in the root account, if not you may need to add ‘sudo’ to the commands to get root privileges. I will show you through the step by step installation Apache Hadoop on an Ubuntu 18.04 Bionic Beaver server.

Install Apache Hadoop on Ubuntu 18.04 LTS Bionic Beaver

Step 1. First, make sure that all your system packages are up-to-date by running these following apt-get commands in the terminal.

Step 2. Installing Java (OpenJDK).

Since hadoop is based on java, make sure you have java jdk installed on the system. If you don’t have Java installed on your system, use following link to install it first.

Step 3. Installing Apache Hadoop on Ubuntu 18.04.

To avoid security issues, we recommend to setup new Hadoop user group and user account to deal with all Hadoop related activities, following command:

After creating the user, it also required to set up key based ssh on its own account. To do this use execute following commands:

Download the latest stable version of Apache Hadoop, At the moment of writing this article it is version 2.8.1:

Step 4. Configure Apache Hadoop.

Setting up the environment variables. Edit ~/.bashrc file and append following values at end of file:

Apply environmental variables to current running session:

Now edit $HADOOP_HOME/etc/hadoop/hadoop-env.sh file and set JAVA_HOME environment variable:

Hadoop has many of configuration files, which need to configure as per requirements of your hadoop infrastructure. Let’s start with the configuration with basic Hadoop single node cluster setup:

Edit core-site.xml:

Edit hdfs-site.xml:

Edit mapred-site.xml:

Edit yarn-site.xml:

Now format namenode using the following command, do not forget to check the storage directory:

Start all hadoop services use the following command:

You should observe the output to ascertain that it tries to start datanode on slave nodes one by one. To check if all services are started well using ‘jps‘ command:

Step 5. Accessing Apache Hadoop.

Apache Hadoop will be available on HTTP port 8088 and port 50070 by default. Open your favorite browser and navigate to http://yourdomain.com:50070 or http://server-ip:50070. If you are using a firewall, please open port 8088 and 50070 to enable access to the control panel.

Congratulation’s! You have successfully installed Hadoop. Thanks for using this tutorial for installing Apache Hadoop on Ubuntu 18.04 LTS system. For additional help or useful information, we recommend you to check the official Apache Hadoop web site.

Source

Linux Today – How to Install NodeBB Forum on Fedora 29

NodeBB is a Node.js based forum software built for the modern web. It’s built on either a MongoDB or Redis database. It utilizes web sockets for instant interactions and real-time notifications. NodeBB has many modern features out of the box such as social network integration and streaming discussions. Additional functionality is enabled through the use of third-party plugins. NodeBB is an open source project which can be found on Github. In this guide, we will walk you through the step-by-step NodeBB installation process on the Fedora 29 operating system by using Nginx as a reverse proxy, MongoDB as the database and acme.sh and Let’s Encrypt for HTTPS.

Requirements

NodeBB requires the following software to be installed:

  • Node.js version 6 or greater
  • MongoDB version 2.6 or greater or Redis version 2.8.9 or greater
  • Nginx version 1.3.13 or greater
  • Git

NOTE: Installing NodeBB’s dependencies may require more than 512 megabytes of system memory. It is recommended to enable a swap partition to compensate if your Linux system has insufficient memory.

Prerequisites

  • A running Fedora 29 system with at least 1GB or RAM.
  • Domain name with A/AAAA records set up.
  • A non-root user with sudo privileges.

Initial steps

Check your Fedora version:

cat /etc/fedora-release
# Fedora release 29 (Twenty Nine)

Set up the timezone:

timedatectl list-timezones
sudo timedatectl set-timezone 'Region/City'

Update your operating system packages (software). This is an important first step because it ensures you have the latest updates and security fixes for your operating system’s default software packages:

sudo dnf check-upgrade || sudo dnf upgrade -y

Install some essential packages that are necessary for basic administration of the Fedora operating system:

sudo dnf install -y curl wget vim bash-completion git socat

For simplicity’s sake, disable SELinux and Firewall:

sudo setenforce 0; sudo systemctl stop firewalld.service; sudo systemctl disable firewalld.service

Step 1: Install Node.js and npm

NodeBB is built on Node.js. We are going to install recommended version for NodeBB which is version 8 at the time of this writing. On Linux, you have a few Node.js installation options: Linux Binaries (x86/x64), Source Code or via Package Managers. We will use Package Management option which makes installing and updating Node.js a breeze.

Download and install the latest Long-Term Support (LTS) release of Node.js from the Fedora repo:

sudo dnf -y install nodejs

To compile and install native add-ons from npm you may also need to install build tools:

sudo dnf install -y gcc-c++ make
# or
# sudo dnf groupinstall -y 'Development Tools'

NOTEnpm is distributed with Node.js – which means that when you download Node.js, you automatically get npm installed on your system.

Check the Node.js and npm versions:

node -v && npm -v
# v10.15.0
# 6.4.1

Npm is a separate project from Node.js, and tends to update more frequently. As a result, even if you’ve just downloaded Node.js (and therefore npm), you’ll probably need to update your npm. Luckily, npm knows how to update itself! To update your npm, type this into your terminal:

sudo npm install -g npm@latest

This command will update npm to the latest stable version.

Re-check npm version with:

npm -v
# 6.7.0

And it should return latest version numbers.

Step 2: Install and configure MongoDB

NodeBB needs a database to store its data, and it supports MongoDB and Redis. In this tutorial, we chose MongoDB as data store engine. So, in the next few steps, we will download and install MongoDB database from the official MongoDB rpm repository:

To install the stable version of MongoDB package, issue the following command:

sudo dnf install -y mongodb mongodb-server

Check the MongoDB version:

mongo --version | head -n 1 && mongod --version | head -n 1
# MongoDB shell version v4.0.1
# db version v4.0.1

Start and enable (set it to start on reboot) MongoDB service:

sudo systemctl start mongod.service
sudo systemctl enable mongod.service

Check the MongoDB Database Server status by running:

sudo systemctl status mongod.service
# active (running)

Next, create MongoDB database and user for NodeBB.

Connect to MongoDB server first.

mongo

Switch to the built-in admin database.

> use admin

Create an administrative user.

> db.createUser( { user: "admin", pwd: "<Enter a secure password>", roles: [ { role: "readWriteAnyDatabase", db: "admin" }, { role: "userAdminAnyDatabase", db: "admin" } ] } )

NOTE: Replace the placeholder <Enter a secure password> with your own selected password.

Add a new database called nodebb.

> use nodebb

The database will be created and context switched to nodebb. Next create the nodebb user with the appropriate privileges.

> db.createUser( { user: "nodebb", pwd: "<Enter a secure password>", roles: [ { role: "readWrite", db: "nodebb" }, { role: "clusterMonitor", db: "admin" } ] } )

NOTE: Again, replace the placeholder <Enter a secure password> with your own selected password.

Exit the Mongo shell.

> quit()

Restart MongoDB and verify that the administrative user created earlier can connect.

sudo systemctl restart mongod.service
mongo -u admin -p your_password --authenticationDatabase=admin

If all went well, your MongoDB should be installed and prepared for NodeBB. In the next step, we will deal with web server installation and configuration.

Step 3 – Install acme.sh client and obtain Let’s Encrypt certificate (optional)

Securing your NodeBB Forum with HTTPS is not necessary, but it is a good practice to secure your site traffic. In order to obtain TLS certificate from Let’s Encrypt we will use acme.sh client. Acme.sh is a pure unix shell software for obtaining TLS certificates from Let’s Encrypt with zero dependencies.

Download and install acme.sh:

sudo su - root
git clone https://github.com/Neilpang/acme.sh.git
cd acme.sh 
./acme.sh --install --accountemail your_email@example.com
source ~/.bashrc
cd ~

Check acme.sh version:

acme.sh --version
# v2.8.0

Obtain RSA and ECC/ECDSA certificates for your domain/hostname:

# RSA 2048
acme.sh --issue --standalone -d example.com --keylength 2048
# ECDSA
acme.sh --issue --standalone -d example.com --keylength ec-256

If you want fake certificates for testing you can add --staging flage to the above commands.

After running the above commands, your certificates and keys will be in:

  • For RSA/home/username/example.com directory.
  • For ECC/ECDSA/home/username/example.com_ecc directory.

To list your issued certs you can run:

acme.sh --list

Create a directories to store your certs. We will use /etc/letsencrypt directory.

mkdir -p /etc/letsecnrypt/example.com
sudo mkdir -p /etc/letsencrypt/example.com_ecc

Install/copy certificates to /etc/letsencrypt directory.

# RSA
acme.sh --install-cert -d example.com --cert-file /etc/letsencrypt/example.com/cert.pem --key-file /etc/letsencrypt/example.com/private.key --fullchain-file /etc/letsencrypt/example.com/fullchain.pem --reloadcmd "sudo systemctl reload nginx.service"
# ECC/ECDSA
acme.sh --install-cert -d example.com --ecc --cert-file /etc/letsencrypt/example.com_ecc/cert.pem --key-file /etc/letsencrypt/example.com_ecc/private.key --fullchain-file /etc/letsencrypt/example.com_ecc/fullchain.pem --reloadcmd "sudo systemctl reload nginx.service"

All the certificates will be automatically renewed every 60 days.

After obtaining certs exit from root user and return back to normal sudo user:

exit

Step 4: Install and configure Nginx

NodeBB can work fine with many web servers. In this tutorial, we selected Nginx.

Install Nginx package, by issue the following command:

sudo dnf install -y nginx

After the installation, you can verify Nginx version by running:

nginx -v
# 1.14.1

Start and enable (set it to start on reboot) Nginx service:

sudo systemctl start nginx.service
sudo systemctl enable nginx.service

Check the Nginx web server status by running:

sudo systemctl status nginx.service
# active (running)

NodeBB by default runs on port 4567. To avoid typing http://example.com:4567, we will configure Nginx as a reverse proxy for the NodeBB application. Every request on port 80 or 443 (if SSL is used) will be forwarded to port 4567.

Run sudo vim /etc/nginx/conf.d/nodebb.conf and configure Nginx as an HTTPS reverse proxy.

server {
  listen [::]:443 ssl http2;
  listen 443 ssl http2;
  listen [::]:80;
  listen 80;
  
  server_name forum.example.com;
  
  client_max_body_size 50M;

  # RSA
  ssl_certificate /etc/letsencrypt/example.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/example.com/private.key;
  # ECDSA
  ssl_certificate /etc/letsencrypt/example.com_ecc/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/example.com_ecc/private.key;

  location / {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $http_host;
    proxy_set_header X-NginX-Proxy true;
    proxy_pass http://127.0.0.1:4567;
    proxy_redirect off;
    # Socket.IO Support
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade"; 
  }

}

Check the Nginx configuration:

sudo nginx -t

Finally, for changes to take effect, we need to reload Nginx:

sudo systemctl reload nginx.service

Step 5: Install and setup NodeBB

Create a document root directory where NodeBB should reside in:

sudo mkdir -p /var/www/nodebb

Navigate to the document root directory:

cd /var/www/nodebb

Change ownership of the /var/www/nodebb directory to your_user.

sudo chown -R [your_user]:[your_user] /var/www/nodebb

NOTE: Replace your_user in the above command with your non-root user that you should have created as a prerequisite for this tutorial.

Clone the latest NodeBB repository into document root folder:

git clone -b v1.11.x https://github.com/NodeBB/NodeBB.git .

Initiate the setup script by running the app with the setup flag. Answer each of the questions:

./nodebb setup

After NodeBB setup is completed, run ./nodebb start to manually start your NodeBB server:

./nodebb start

After running this command, you should be able to access your brand new forum in your web browser:

NodeBB in Browser

Step 6: Run NodeBB as a System Service

When started via ./nodebb start, NodeBB will not automatically start up again when the system reboots. To avoid that, we will need to setup NodeBB as a system service.

If running, stop NodeBB:

./nodebb stop

Create a new nodebb user:

sudo useradd nodebb

Change the ownership of the /var/www/nodebb directory to nodebb user:

sudo chown -R nodebb:nodebb /var/www/nodebb

Create nodebb.service systemd unit config file. This unit file will handle startup of NodeBB deamon. Run sudo vim /etc/systemd/system/nodebb.service and add the below content:

[Unit]
Description=NodeBB
Documentation=https://docs.nodebb.org
After=system.slice multi-user.target mongod.service

[Service]
Type=forking
User=nodebb

StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=nodebb

Environment=NODE_ENV=production
WorkingDirectory=/var/www/nodebb
PIDFile=/var/www/nodebb/pidfile
ExecStart=/usr/bin/env node loader.js
Restart=always

[Install]
WantedBy=multi-user.target

NOTE: Set username and directory paths according to your chosen names.

Enable nodebb.service on reboot and immediately start nodebb.service:

sudo systemctl enable nodebb.service
sudo systemctl start nodebb.service

Check the nodebb.service status:

sudo systemctl status nodebb.service
sudo systemctl is-enabled nodebb.service

Congratulations! You have successfully installed and deployed NodeBB discussion platform on Fedora 29 system. You should be able to access your forum on your domain and interact with your forum.

Links

Source

Automate WebSocket API Creation in Amazon API Gateway Using AWS CloudFormation

Posted On: Feb 7, 2019

You can now use AWS CloudFormation templates to build WebSocket APIs in Amazon API Gateway. AWS CloudFormation provides a common language for you to describe and provision all the infrastructure resources in your cloud environment across all regions and accounts, simplifying how you build applications in the cloud.

Using CloudFormation, you can build fully-managed WebSocket APIs in API Gateway. WebSocket APIs allow you to reduce the overall cost and complexity of building real-time, two-way communication applications such as chat applications, alerts and notifications applications, and real-time dashboards. CloudFormation will allow you to automate the creation of the resources you need to build WebSocket APIs in API Gateway, such as APIs, routes, stages, and deployments.

To learn more about the WebSocket API resources supported by CloudFormation, read our documentation or take a look at our sample chat application in GitHub.

CloudFormation support for building WebSocket APIs in API Gateway is available in all regions where API Gateway and CloudFormation are available. To see a list of these regions, view the AWS region table.

Source

Download yelp-tools Linux 3.28.0 / 3.32.0 Beta

yelp-tools is an open source and free command-line software designed as part of the Yelp project, providing the necessary scripts for generating, maintaining and publishing documentation for the GNOME desktop environment.

The program can also be used to publish documentation on the Internet. It is comprised of various scripts, such as yelp-check and yelp-build, as well as an yelp.m4 file that provides autotools integration.

What is Yelp?

Yelp is an open source, free and very useful software project, a collection of documentation utilities for the GNOME desktop environment, containing a set of utilities for building documentation.

The Yelp project also contains the yelp-xsl utility, which provides core XSLT stylesheets used by libyelp and Yelp itself, as well as the libyelp GTK+ library, which makes it easy to build a help viewer, or embed one in an application.

Getting started yelp-tools

Usually, yelp-tools can be installed through the package manager of your GNU/Linux distribution, but it gets automatically installed with Yelp, when installing the GNOME desktop environment.

It can also be used on other open-source desktop environments. To install and use the yelp-tools package on your distro, first check if a pre-built binary package is available on the main software repositories.

If not, download the latest stable version from Softpedia, save the archive on your PC, preferably your Home directory, extract its contents using an archive manager tool, open a Terminal app and navigate to the location of the extracted archive files (e.g. cd /home/softpedia/yelp-tools-3.14.1).

Arrived at the location of the extracted archive files, run the ‘./configure && make’ command to configure and compile the program, followed by the ‘sudo make install’ command to install it system wide.

The commands are available through the Yelp software or directly from the command-line interface, using a terminal emulator.

Yelp script Create documentation Publish documentation Yelp Documentation Publish Create

Source

How to Configure Software Repositories in Fedora

Your Fedora distribution obtains its software from repositories and each of these repositories comes with number of free and proprietary software applications available for you to install. The official Fedora repositories have thousands of free and open source applications.

In this article, we will show how to configure software repositories in Fedora distribution using the DNF package manager tool from the command line.

View Enabled Repositories in Fedora

To list all enabled repositories on your Fedora system, in the format repository ID, name, and status (number of packages it provides), run the following command.

$ sudo dnf repolist
List Enabled Repositories in Fedora

List Enabled Repositories in Fedora

You can list packages from a specified repository, for instance fedora, by running the following command. It will list all packages available and installed from the repository specified.

$ sudo dnf repository-packages fedora list

To display only a list of those packages available or installed from the specified repository, add the available or installed option respectively.

$ sudo dnf repository-packages fedora list available
OR
$ sudo dnf repository-packages fedora list installed

Adding, Enabling, and Disabling a DNF Repository

Before you add a new repository to your Fedora system, you need to define it by either adding a [repository]section to the /etc/dnf/dnf.conf file, or to a .repo file in the /etc/yum.repos.d/ directory. Most developers or package maintainers provide DNF repositories with their own .repo file.

For example to define the repository for Grafana in a .repo file, create it as shown.

$ sudo vim /etc/yum.repos.d/grafana.repo

Then add the [repository] section in the file and save it. If you observe carefully, in the repository configuration shown in the image, it is not enabled as indicated by the parameter (enabled=0); we changed this for demonstration purposes.

Add New DNF Repository in Fedora

Add New DNF Repository in Fedora

Next, to add and enable new repository, run the following command.

$ sudo dnf config-manager --add-repo /etc/yum.repos.d/grafana.repo
Add and Enable DNF Repo

Add and Enable DNF Repo

To enable or disable a DNF repository, for instance while trying to install a package from it, use the --enablerepo or --disablerepo option.

$ sudo dnf --enablerepo=grafana install grafana  
OR
$ sudo dnf --disablerepo=fedora-extras install grafana  
Install Package from Enabled Repository

Install Package from Enabled Repository

You can also enable or disable more than one repositories with a single command.

$ sudo dnf --enablerepo=grafana, repo2, repo3 install grafana package2 package3 
OR
$ sudo dnf --disablerepo=fedora, fedora-extras, remi install grafana 

You can also enable and disable repositories at the same time, for example.

$ sudo dnf --enablerepo=grafana --disablerepo=fedora, fedora_extra, remi, elrepo install grafana

To permanently enable a particular repository, use the --set-enabled option.

$ sudo grep enable /etc/yum.repos.d/grafana.repo
$ sudo dnf config-manager --set-enabled grafana
$ sudo grep enable /etc/yum.repos.d/grafana.repo
Permanently Enable DNF Repo

Permanently Enable DNF Repo

To permanently disable a particular repository, use the --set-disabled switch.

$ sudo dnf config-manager --set-disabled grafana

That’s all for now! In this article, we have explained how to configure software repositories in Fedora. Share your comments or ask questions via the feedback form below.

Source

Amazon RDS for Oracle Now Supports January 2019 Oracle Patch Set Updates (PSU) and Release Updates (RU)

Amazon RDS for Oracle now supports the January 2019 Patch Set Updates (PSU) for Oracle Database 11.2 and 12.1. Oracle PSU contains critical security updates and other important updates. Beginning with Oracle Database version 12.2.0.1, Amazon RDS for Oracle supports Release Updates (RU) in place of the PSU. To learn more about the Oracle PSUs supported on Amazon RDS, visit the Amazon RDS patch update documentation.

Amazon RDS for Oracle makes it easy to set up, operate, and scale Oracle Database deployments in the cloud. See the Amazon RDS for Oracle Database Pricing page for complete regional availability information.

Source

WP2Social Auto Publish Powered By : XYZScripts.com