lukeshortcloud / rootpages Goto Github PK

https://linuxcontainers.org/lxc/getting-started/

My Python notes should be moved over to Root Pages.

Sphinx is one of the top standards for building various types of documentation formats (ePub, HTML, PDF, etc.) based on RST or Markdown source code. This can even be used to create a full book. Root Pages should start using Sphinx for it's build process.

http://www.sphinx-doc.org/en/stable/contents.html

• Convert documents from Markdown to ReStructuredText.
• Run "sphinx-quickstart" to setup the build configuration files.
• Remove old build scripts.
• Update the README file on how to use Sphinx to build documentation.
• Correct the headers to only have the title of each document (for example, "Ansible") be the #1 header. All other headers should be bumped down by one level to be nested under the document's title's name within a table of contents.

With using the package manager for a particular operating system, it is possible to bootstrap a full installation of the operating system into a directory. This can then be used as a simple chroot or a container.

http://lukeluo.blogspot.com/2015/09/how-to-bootstrap-different-linux.html

http://superuser.openstack.org/articles/simple-auto-scaling-environment-with-heat/

https://sourceforge.net/p/predef/wiki/OperatingSystems/

https://www.freedesktop.org/software/systemd/man/systemd.exec.html

1. The Sphinx configuration file src/config.py needs to have the version updated to reflect the release date in ISO format (for example, 2018.01.01 for January 1, 2018). A new version will be created and tagged every 3 months.

2. New contributors should look for these labels:

• "new content"
• "help wanted"

3. Special notes:

• OpenStack notes only have a major update when a new Red Hat OpenStack Platform long-life release comes out (every third release, starting with Newton). This update requires a lot of research to determine what has changed since the last long-life release.
• Before a new release, one of the final commits should be a check for spelling corrections.

https://superuser.com/questions/1057959/windows-10-in-kvm-change-boot-disk-to-virtio https://fedoraproject.org/wiki/Windows_Virtio_Drivers#Direct_download https://kahdev.wordpress.com/2011/05/30/using-virtio-drivers-in-a-kvm-windows-guest-vm/

Explain how to use stdout, stdin, and stderr. Also explain how to CRUD files.

How to setup and maintain GlusterFS.

http://blog.gluster.org/linux-scale-out-nfsv4-using-nfs-ganesha-and-glusterfs-one-step-at-a-time/

https://www.maketecheasier.com/setup-two-factor-authentication-ubuntu/

Despite the linux_commands guide being in a pretty format as Excel sheets, it would be more ideal to have it in a CSV (or similar) file format for viewing it via the CLI.

• Administrative
• Clustering
• Compression
• Configuration Management
• Firewalls
• Hardware
• Linux File System Hierarchy (LFH)
• OpenStack
• Networking
• NoSQL
• Package Managers
• Permissions
• Phones
• Regular Expression (RegEx)
• Security
• Shell
• Source Code Management
• SQL
• Storage
• Text Editors
• Tips & Tricks
• Virtualization

hey noticed this great awesome project! I forked a project before that someone that started doing something similar. Is called linuxjourney. I moved it to gitlab cause I love gitlab.
https://gitlab.com/sysadminonlinux/linuxjourney
Maybe we should merge this stuff ? and avoid re-doing work ?

make deb and make rpm

http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen

http://sirlagz.net/2012/06/20/how-to-resize-partitions-on-an-image-file/

Using Apt/Pacman/urpmi/Yum/Zypper as an end-user.

https://pages.github.com/

Explain how to use:

• if
• for
• while

Sphinx has support to translate documentation into other languages. This should be explained in the README file.

http://www.sphinx-doc.org/en/stable/intl.html

These guides should be unified into a "Databases" guide.

https://jfearn.fedorapeople.org/fdocs/en-US/Documentation/0.1/html/Fedora_Multiboot_Guide/freespace-ntfs.html

https://superuser.com/questions/237247/how-do-i-add-a-apt-get-repository-without-editing-etc-apt-sources-list

Since these documents have been converted from Markdown to reStructuredText, the spacing within table boxes has been slightly off. Extra spaces were placed within the various sentences. This should be cleaned up and corrected.

https://www.digitalocean.com/community/tutorials/how-to-run-a-multi-node-cluster-database-with-cassandra-on-ubuntu-14-04

My authentication services notes should be moved over to Root Pages.

Explain how to use classes, objects, inheritance, etc. in Python.

https://mariadb.com/kb/en/library/optimization-and-tuning/ https://dev.mysql.com/doc/refman/5.6/en/optimization.html

The builtin RST function .. contents:: will automatically generate a table of contents based on the defined headers. Each stub mentioned in the old table of contents should be removed and have a GitHub issue opened requesting it should be added.

• ansible
• authentication
• bootloaders
• c_and_c++
• clustering
• databases
• dns_servers
• file_systems
• http_servers
• linux
• mail_servers
• monitoring
• networking
• openstack
• operating_systems
• packages
• python
• security
• virtualization
• wine

Document the repository that holds all of the end-of-life versions of CentOS.

http://vault.centos.org/

Currently only the "Ansible" document has a bibliography due to it's large size. Other documents in Root Pages will have a short bibliography at the end of each section, instead of at the end of the entire document. For consistency, the references used should be stated at the end of each subject's document.

• ansible
• authentication
• bootloaders
• c_and_c++
• clustering
• dns_servers
• file_systems
• http_servers
• linux
• mail_servers
• monitoring
• networking
• nosql
• openstack
• operating_systems
• packages
• python
• security
• sql
• virtualization
• wine

Explain the creation and usage of a clouds.yaml configuration file for OpenStack cloud operators.

https://docs.openstack.org/python-openstackclient/pike/configuration/index.html

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/security-enhanced_linux/sect-security-enhanced_linux-working_with_selinux-booleans#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans

Explain how to search for dynamically linked libraries required by a program using ldd.

http://linux.101hacks.com/unix/ldd/

How to upgrade Fedora using DNF.

https://fedoraproject.org/wiki/DNF_system_upgrade

Every use of a code block should also use syntax highlighting, as supported by the reStructuredText format.

See: http://www.sphinx-doc.org/en/stable/markup/code.html

https://www.howtoforge.com/how-to-resize-raid-partitions-shrink-and-grow-software-raid

How to increase performance with Nginx caching.

https://www.nginx.com/blog/nginx-caching-guide/

https://wiki.winehq.org/List_of_Commands

Reference against the top popularity on DistroWatch: https://distrowatch.com/

http://www.slideshare.net/planetcassandra/datastax-extreme-cassandra-optimization-the-sequel

Load balance both HTTP and HTTPS connections coming in using a single exposed port.

http://timjrobinson.com/haproxy-how-to-run-http-https-on-the-same-port/

https://blog.inkubate.io/install-and-configure-openstack-ocata-with-kolla-as-a-standalone/

The conversion from Markdown to reStructuredText resulted in the "Virtualization" Root Page to not render correctly on GitHub. It works fine when using Sphinx on a local machine to convert it into HTML. This page will need to be have it's format checked over and possibly corrected.

Explain how to use:

• Exceptions
• Logging
• Unit Tests

Explain how to create and use virtual Python environments.

How to secure ports with iptables and port knocking techniques.

http://www.boynux.com/how-to-enable-port-knocking-in-linux/

Explain the naming scheme that systemd uses to create names for the physical network interface ports.

https://major.io/2015/08/21/understanding-systemds-predictable-network-device-names/

https://www.postgresql.org/docs/10/static/high-availability.html