The flex-direction property accepts 4 different values:

What are the background properties?

All CSS Background Properties
Property Description

How do you change position in CSS?

You can use two values top and left along with the position property to move an HTML element anywhere in the HTML document.

What is Z-index in CSS?

The z-index CSS property sets the z-order of a positioned element and its descendants or flex items. Overlapping elements with a larger z-index cover those with a smaller one.
If you want to create a custom stacking order, you can use the z-index property on a positioned element. The z-index property can be specified with an integer value (positive, zero, or negative), which represents the position of the element along the z-axis.

How do I fix Z-index in CSS?

To sum up, most issues with z-index can be solved by following these two guidelines:
Check that the elements have their position set and z-index numbers in the correct order.
Make sure that you don’t have parent elements limiting the z-index level of their children.

How do you use sticky position in CSS?

CSS Demo: position

To see the effect of sticky positioning, select the position: sticky option and scroll this container. The element will scroll along with its container, until it is at the top of the container (or reaches the offset specified in top ), and will then stop scrolling, so it stays visible.

How do you flex vertically?

Vertical alignment using align-self

The post Some important CSS property for uses in your responsive bootstrap 4 pages appeared first on scmGalaxy.

More Important Build Definitions

Reference: The Build Master: Microsoft’s Software Configuration Management Best Practices

It is also important for groups or teams to define these terms on a project-wide basis so that everyone is clear on what he is getting when a build is released.

Pre-build— Steps taken or tools run on code before the build is run to ensure zero build errors. Also involved are necessary steps to prepare the build and release machines for the daily build, such as checking for appropriate disk space.

Post-build— Includes scripts that are run to ensure that the proper build verification tests (BVTs) are run. This also includes security tests to make sure the correct code was built and nothing was fused into the build.

Clean build— Deleting all obj files, resource files, precompiled headers, generated import libraries, or other byproducts of the build process. I like to call this cleaning up the “build turds.” This is the first part of a clean build definition. Most of the time, build tools such as NMake.exe or DevEnv.exe handle this procedure automatically, but sometimes you have to specify the file extensions that need to be cleaned up. The second part of a clean build definition is rebuilding every component and every piece of code in a project. Basically the perfect clean build would be building on a build machine with the operating system and all build tools freshly installed.

Incremental build— The secret to getting out a daily build to the test team, regardless of circumstances, is to perform incremental builds instead of daily clean builds. This is also the best way that you can maintain quality and a known state of a build. An incremental build includes only the code of the source tree that has changed since the previous build. As you can guess, the build time needed for an incremental build is just a fraction of what a clean build takes.

Continuous integration build— This term is borrowed from the extreme programming (XP) practice. It means that software is built and tested several times per day as opposed to the more traditional daily builds. A typical setup is to perform a build every time a code check-in occurs.

Build break— In the simplest definition, a build break is when a compiler, linker, or other software development tool (such as a help file generator) outputs an error caused by the source code it was run against.

Build defect— This type of problem does not generate an error during the build process; however, something is checked into the source tree that breaks another component when the application is run. A build break is sometimes referred to or subclassed as a build defect.

Last known good (LKG) or internal developers workstation (IDW) builds— These terms are used as markers to indicate that the build has reached a certain quality assurance criterion and that it contains new high-priority fixes that are critical to the next baseline of the shipping code. The term LKG originated in the Visual Studio team, and IDW came from the Windows NT organization. LKG seems to be the more popular term at Microsoft.

The post More Important Build Definitions | Different Build Definitions | Build Terminologies appeared first on scmGalaxy.

Main Responsibilities of the Linux System Administrator is as follows:

1. Maintaining User Accounts
2. Security
3. Managing the disk space and Backup
4. Provisiom the new Linux Server based on the need
5. Linux Server Updates and Patching
6. Authentication and Authorization Management
7. Trubleshooting of Linux Severs and QA Deployments
8. Managing the Large number of VMS in VMWARE
9. Montoring all the vms and their health
10. Montoring Major Important Services
11. Backup & Restore all the imporant data of the servers
12. Server and OS process monitoring
13. Disk managment and montoring

The Administrator’s Privileges:

1. Change the contents or attributes of any file like its permission and ownership
2. He can delete any file eith rm even if it is write-protected.
3. Initiate or Kill Any Process
4. Change any user’s password without knowing the existing one
5. Set the system clock with date
6. Limit the maximum size of files that users are permitted to create with ulimlit
7. Controls users access to the scheduling services like at and cron
8. Control users access to many networking services like Telnet, FTP, etc

The post Main Responsibilities of the Linux System Administrator | What Linux System Administrators do ? appeared first on scmGalaxy.