NinjaBot is a Discord bot written in C#.

Its primary focus was to help out guilds in World of Warcraft. I will be shifting to more administrative / Discord tasks for the time being as I am no longer actively playing World of Warcraft.

This project has been an awesome way for me to learn C#, feel free to toss in a pull request if there’s a better way to do something!

10.2.x updates coming soon

The first thing you’ll need to do is invite the bot to your server. It will need permissions to read and post messages at the very minimum. If you wish to use NinjaBot to assist with admin tasks (kicking/banning users, message management, etc), please use this link.

This bot is now using slash commands, be sure to use the updated invites above to invite it to your discord server. If it is already on your server, you may need to ensure users can use the commands:

Go to Server Settings → Integrations, and then 'Manage' (next to NinjaBot).

There are a limited number of classic WoW commands now available. You can associate your guild, and watch/get logs from Warcraft logs. Currently there is no way to get classic armory or guild information via the API, and I’ll be watching to see when/if things get added!

More information on the bot and getting started here.

Associating a WoW guild with your Discord server allows you to use the Warcraft Logs watching command, as well as some autocomplete features for guild member names when using various WoW commands.

To associate your guild with NinjaBot, use the following command:

/setguild realmName, guildName, region

Here are some examples of using the command:

/setguild Blackwater Raiders, Raiders of the Lost Ark, us

/setguild Silvermoon, Rome in a Day, eu

/setguild Ревущий фьорд, Порейдим месяц, ru

To associate your classic WoW guild with NinjaBot, use the following command:

/setclassicguild "guild name" "realm" "region"

Valid regions: US, EU, KR, TW, and CN

NinjaBot will associate what you enter as the guild attached to your server. That data will then be used to watch / retrieve logs from Warcraft Logs.

Example:

/setclassicguild "Disorder" "Rattlegore"

To use the auto log poster, use this command in the channel you want them automatically posted to:

/watchlogs

You can use the same exact command to disable the auto log posting, and then use it again to enable it (in the channel you want them posted to).

To get the last three of your guild’s logs, use:

/logs

To get the last three of your guild’s logs, use:

/logsclassic

Command Help:

/rio

Try to find character (first in guild, then best guess)

/rio characterName

Long form version to try to find someone not in the same region

/rio characterName realmName region(us or eu)

/ginfo

NinjaBot can greet people joining the server, and notify the server when someone leaves. The messages the bot uses are customizable.

In the channel you’d like to have the greetings in (this will either enable or disable, as a toggle):

/toggle-greetings

If greetings are enabled, and you’d like to set a different channel to handle leaving/parting messages, use (in the channel you want it to be):

/set-parting-channel

When setting greetings, you can use emojis the bot has access to. For example, you can use 😂, and it will translate to 😂.

If you’d like to link to a specific channel, you’d use:

Please check out this channel for information: <#channel-id-here>

(to get the ID, just right click a text channel and click “Copy Channel ID“)

To change the greeting message, use:

/set-join-message

To change the leaving/parting message, use:

/set-part-message 

Server members with kick permissions and above can set a server wide note via:

/set-note

Anyone in the server can retrieve the note via:

/get-note

(note: updating the website in the mere future!) Visit the NinjaBot website for more information.

If you’re having trouble using any of the WoW commands, the first thing to try is re-associating your WoW guild with your Discord server. If that doesn’t help, check out the following resources below:

Discord Chat

NinjaBot Website

Feel free to open an issue here for any bugs or problems you come across!

Enjoy.

Доброго всім дня.

Це невеличкий конспект з допомоги тим, хто хоче вивчати DevOps у 2023 році.

Матеріали тут зустрічаються трьома мовами – українською, англійською та мовою країни-загарбника. На жаль, зовсім без останніх обійтися було неможливо, бо для новачків такі пояснення нерідко є зрозумілішими, особливо коли рівень англійської вдосконалюється по ходу справи. Але, як сказав класик, і чужому навчайтесь, і свого не цурайтесь.

Перелік не є закінченим. Доповнення і зауваження дуже вітаються.

Також дякую телеграм-спільноті https://t.me/DevOpsMarathon та її очільнику – @edemus, телеграм-спільноті DevOps Geeks та україномовному каналу DevOps 01.

Never give up!

• Roadmaps
• Resouses
  • Computer Science Guide
  • Courses
  • Youtube
  • Github
  • Labs/Trainings
  • Trainings
  • Coding
• Git
• Linux
• Networking
• CI/CD
  • Ansible
  • Jenkins
  • Gitlab
• Infrastructure as code
• Containerization
  • Docker
  • Kubernetes
• Clouds
  • AWS
  • Microsoft Azure
  • Google Cloud Platform
• Programming and Scripting
  • Bash
    • Games for Bash learning
  • Powershell
  • Python
  • Go
  • Rust
• SQL
• Monitoring
• DevSecOps
• Interview
• English

Цей розділ присвячено роадмапам для зручності навчання та самопідготовки.

Name	URL	Description	Meta
90DaysOfDevOps	github.com/MichaelCade/90DaysOfDevOps	The most famous roadmap for newbies DevOps-engineers
Another DevOps Roadmap	github.com/milanm/DevOps-Roadmap	Another detailed DevOps roadmap
DevOps-Roadmap	github.com/devopshobbies/devops-roadmap	DevOps Roadmap by Ahmadali Bagheri (free resourses included)
Become A DevOps Engineer in 2023	devopscube.com	Simple and nice roadmap
DevOps Roadmap	roadmap.sh/devops	FOR NEWBIE! Step by step guide for DevOps, SRE or any other Operations Role
DevOps Roadmap	roadmap.sh	Step by step guide for DevOps, SRE or any other Operations Role in 2023
DevOps Roadmap	techworld-with-nana.com	Step by step guide outlining the most efficient path to become a DevOps engineer by TechWorld with Nana
Learn to Cloud	learntocloud.guide	Skills you need to learn to get into Cloud Computing
From Zero to DevOps Engineer – DevOps Roadmap for YOUR specific background	YouTube	Roadmap in a video
Как стать DevOps Инженером с Нуля, что учить и в каком порядке	YouTube	Roadmap in a video

Цей розділ містить посилання на корисні ресурси для DevOps-інженерів.

Name	URL	Description	Meta
Ukrainian IT Communities	github.com/nikit0ns/Ukrainian_IT_Communities#-devops	Українські DevOps коммʼюніті і не тільки

Name	URL	Description	Meta
TeachYourselfCS-UK	github.com/babieiev/TeachYourselfCS-UK/	Збірник-посібник для самостійного фундаментального вивчення компʼютерних наук
TeachYourselfCS-EN	github.com/ossu/computer-science	The same in English
CS50	YouTube	Основы программирования: Легендарный Гарвардский курс CS50 (2015 – old but gold)	ru

Вказані добірки курсів та платформ зазвичай платні, якщо не зазначено інше (безкоштовні навчальні матеріали розміщені у відповідних розділах).

Name	URL	Description	Meta
DevOps Bash Tools	github.com/HariSekhon/DevOps-Bash-tools	Scripts for many popular DevOps technologies
DevOps resources	github.com/bregman-arie/devops-resources	This repository is about gathering any useful resources and information regarding DevOps
How They DevOps	github.com/bregman-arie/howtheydevops	A curated collection of publicly available resources on how companies around the world practice DevOps
DevOps exercises	github.com/bregman-arie/devops-exercises	This repo contains questions and exercises on various technical topics, sometimes related to DevOps and SRE
Free DevOps Books	github.com/rootusercop/Free-DevOps-Books-1	This is a curated collection of free DevOps eBooks available on the Internet
Awesome Site Reliability Engineering	github.com/dastergon/awesome-sre	A curated list of awesome Site Reliability and Production Engineering resources
SRE Learning Platform	github.com/ViktorUJ/cks	An open-source hub designed to help IT engineers effectively prepare for the CKA, CKS, and CKAD exams
Test your Sysadmin skills	github.com/trimstray/test-your-sysadmin-skills	This project contains 284 test questions and answers that can be used as a test your knowledge or during an interview such as Linux/Networks
DevOps-Bash-tools	github.com/HariSekhon/DevOps-Bash-tools	Scripts for many popular DevOps technologies
Coding Interview University	github.com/jwasham/coding-interview-university	A short to-do list of study topics for becoming a software engineer (useful for your coding skills)

Тренажери для прокачки скілу програмування будь-якою мовою.

Матеріали для ознайомлення з системою контролю версій Git (VCS).

Розділ для вдосконалення знань з Linux – для новачків та не тільки.

Розділ для вивчення та повторення компʼютерних мереж.

CI/CD та які тулзи у ньому використовуються.

Розділ для тих, хто починає працювати з інструментами для Infrastructure as Code.

Розділ з лінками на ресурси по контейнеризації та оркеструванню.

Розділ для вивчення хмарних середовищ і де їх шукати.

Розділ для вивчення програмування та автоматизації всього, що рухається.

Розділ з вивчення побудови безпечного CI/CD знаходиться тут.

Самопідготовка та селф-чекінг.

London is the capital of Great Britain.

Integration of FontAwesome and vaadin-icon for Vaadin 10+

• Version 1.0.4 (based on FontAwesome 5.11.2) is compatible with Vaadin 10-13 and Vaadin 14 in bower mode.
• Version 2.2.2 (based on FontAwesome 5.15.4) is compatible with Vaadin 14-23 in npm mode.
• Version 3.2.x (based on the latest version of FontAwesome 6, using polymer iron-icon) is compatible with Vaadin 14-23 in npm mode.
• Version 4.4.x (based on the latest version of FontAwesome 6, using vaadin-icon) is compatible with Vaadin 23.
• Version 5.2.x (based on the latest version of FontAwesome 6, using vaadin-icon) is compatible with Vaadin 24.

For details on which version of FontAwesome is used by each release of this addon, see the Release Notes

If you want to use Font Awesome Pro icons with this addon, see here

Online demo here

Available in Vaadin Directory

Available in npm.js (since 2.1.0)

Add the following dependencies in your pom.xml file:

<dependency>
   <groupId>com.flowingcode.addons</groupId>
   <artifactId>font-awesome-iron-iconset</artifactId>
   <version>X.Y.Z</version>
</dependency>

<repository>
   <id>vaadin-addons</id>
   <url>https://maven.vaadin.com/vaadin-addons</url>
</repository>

For SNAPSHOT versions see here.

• git clone repository
• mvn clean install jetty:run

To see the demo, navigate to http://localhost:8080/

The issues for this add-on are tracked on its github.com page. All bug reports and feature requests are appreciated.

Contributions are welcome, but there are no guarantees that they are accepted as such.

As first step, please refer to our Development Conventions page to find information about Conventional Commits & Code Style requeriments.

Then, follow these steps for creating a contribution:

• Fork this project.
• Create an issue to this project about the contribution (bug or feature) if there is no such issue about it already. Try to keep the scope minimal.
• Develop and test the fix or functionality carefully. Only include minimum amount of code needed to fix the issue.
• For commit message, use Conventional Commits to describe your change.
• Send a pull request for the original project.
• Comment on the original issue that you have implemented a fix for it.

This add-on is distributed under Apache License 2.0. For license terms, see LICENSE.txt.

FontAwesomeIronIconset Addon is written by Flowing Code S.A.

Font Awesome Free 5.13.0 by @fontawesome is distributed under CC BY 4.0 license. For license terms see THIRD-PARTY.txt

• Use the create method from the enum type, for instantiating a new Icon component based on that icon. There is an enum type for each font family (solid, regular and brands)

add(new Button("SAVE", FontAwesome.Solid.SAVE.create()));

• You can also use the enumerated value for obtaining the qualified icon name (e.g. fas:plane-departure), that can be set in the icon attribute of the vaadin-icon element. This can be helpful if you are writing a template renderer, such as:

	grid.addColumn(LitRenderer.<Flight>of(
	   "<vaadin-icon icon='"+FontAwesome.Solid.PLANE_DEPARTURE+"'></vaadin-icon>${item.takeoff_time}"
	).withProperty("takeoff_time", Flight::getTakeOffTime));

In this latter case, you’ll need to import the corresponding iconset:

@Uses(FontAwesome.Solid.Icon.class)

• Use in a Lit or Polymer template:

import '@vaadin/vaadin-icon/vaadin-icon.js';
import '@flowingcode/font-awesome-iron-iconset/fab.js';

<vaadin-icon icon="fab:font-awesome" style="width: 48px; height: 48px"></vaadin-icon>

By default, Vaadin Flow only includes com/vaadin/flow/component to be always scanned for UI components and views. For this reason, the addon might need to be whitelisted in order to display correctly.

To do so, just add com.flowingcode to the vaadin.whitelisted-packages property in src/main/resources/application.properties, like:

vaadin.whitelisted-packages = com.vaadin,org.vaadin,dev.hilla,com.flowingcode

More information on Spring whitelisted configuration here.

Because of Font Awesome Pro license terms, the Pro icons cannot published as part of an open source addon. However, if you have a Font Awesome Pro license, you can recompile this addon in order to embed the Pro Icons.

This process will:

• Update the enumerations so that they define constants for the additional Pro Icons
• Create new enumerations for the Ligth and Duotone icon families.
• Embed the Pro Icons as vaadin-iconset.

The JAR created in this way will include a copy of the Font Awesome Pro icons, thus it will be subject to the Font Awesome Pro restrictions. You’ll need to install it locally or make it available from your internal artifact repository.

1. Checkout a copy of this project: git clone git@github.com:FlowingCode/FontAwesomeIronIconset.git
2. Download Font Awesome Pro SVG sprites into src/main/sprites OR Font Awesome Pro SVG icons into /src/main/icons (/src/main/icons/solid, /src/main/icons/regular, etc.)
3. Modify the groupId, artifactId and version in the pom.xml file.
4. Modify the following properties in the pom.xml file:

<fontawesome.version>Pro 5.13.1</fontawesome.version>
<project.build.generatedResources>${project.basedir}/src/main/resources/META-INF/resources/frontend</project.build.generatedResources>
<codegen.sprites>${project.basedir}/src/main/sprites</codegen.sprites>
<codegen.skipDownload>true</codegen.skipDownload>
<codegen.embedded>true</codegen.embedded>

5. Execute mvn -Pgenerate clean package. The code generation process will use the sprites provided in /src/main/sprites/ (it will not check out Font Awesome Free), and resources will be embedded in the JAR file instead of being available as npm dependencies (the properties npm.package and npm.version will be ignored).

If you want to import the JS iconset from a Polymer Template when using the integration with Font Awesome Pro, the js module is
@vaadin/flow-frontend/font-awesome-iron-iconset/fab.js instead of @flowingcode/font-awesome-iron-iconset/fab.js (you’ll need to execute the mvn vaadin:prepare-frontend on your project in order to extract the module from the JAR file).

Duotone styling is based on CSS variables (--fa-primary-color, --fa-primary-opacity, --fa-secondary-color, and --fa-secondary-opacity) that are applied to the <duotone-icon>. When importing the iconset from a Polymer Template, you’ll also need @vaadin/flow-frontend/font-awesome-duotone/duotone.js in addition to @vaadin/flow-frontend/font-awesome-iron-iconset/fad.js.

When compiling icons for FontAwesome Pro 6 you need to need to use at least JDK 15. This is because of a limitation in the maximum number of constants allowed in an enum compiled by javac with earlier JDKs. This only affects the generated bytecode: the compatibility level remains 11 so that the library is still compatible with Java 11 (or Java 8 if using version 3.x of this addon).

If any enum exceeds 4103 constants (which may happen when compiling the whole FontAwesome 6 Pro iconset plus aliases), you need to enable the alternative compilation profile with mvn -Pbigenum,generate clean package.

In this project we are working on a loan dataset, customer credit card dataset and a bank transaction dataset by using Apache Spark, which is a data processing framework that can quickly perform processing tasks on very large data sets, and can also distribute data processing tasks across multiple computers, either on its own or in tandem with other distributed computing tools. Using these datasets and Spark SQL we have created various use cases pertaining to real life scenarios in banking.

https://databricks-prod-cloudfront.cloud.databricks.com/public/4027ec902e239c93eaaa8714f173bcfc/553931998293758/1733511036908678/113857780564717/latest.html

• SPARK
• HDFS
• HIVE
• DATAFRAMES
• PYSPARK
• SPARK SQL
• JUPYTER NOTEBOOK
• DATABRICKS

• We can easily know the number of customer and their nature by performing this usecases.
• List of usecases performed on each datasets

• The number of loans on each category
• The number of loans taken on each occupation
• Know the number of members who taken more than 1lack loan
• Number of members whose overdue is more than 5
• The number of members whose debt record is less than 20k
• Marital status of loans takers
• Number of loans in each category
• Partitioning dataframe on column ‘Loan Category’
• Number of people with 2 or more returned cheques and income less than 50000

• The number of members who are eligible for credit card
• The number of members who are eligible and active on bank
• The number of targeted persons for credit card
• The targeted persons count whose tenure is less than 5
• The targeted persons count who exited
• The number of targeted persons whose number of product is equal to 1
• Credit card users in Spain
• Number of customers who’s Estimated Salary less than 1 lakh and number of products more than 1.

• Count of transaction on every account.
• Maximum withdrawal amount of an account
• Minimum withdrawal amount of an account
• Maximum deposit amount of an account
• Minimum deposit amount of an account
• Sum of balance in every bank account
• Count of transaction methods what customers used for transaction.
• Number of transaction on each date.
• List of customers with withdrawal amount more than 1 lakh

GitHub clone URL: https://github.com/rajib1007/PROJECT1.git

https://ubuntu.com/download/desktop

https://www.digitalocean.com/community/tutorials/how-to-set-up-jupyter-notebook-with-python-3-on-ubuntu-20-04-and-connect-via-ssh-tunneling

sudo apt-get install openjdk-8-jdk

wget https://dlcdn.apache.org/spark/spark-3.1.2/spark-3.1.2-bin-hadoop3.2.tgz

tar xvzf spark-3.1.2-bin-hadoop3.2.tgz

wget https://archive.apache.org/dist/kafka/2.0.0/kafka_2.11-2.0.0.tgz

tar xvzf kafka_2.11-2.0.0.tgz

pip install kafka-python

• SIDHANT SEHGAL
• ABHILASH REDDY
• AKHIL
• ANAND KUMAR
• VENKATESH VENKAT

This project uses the following license: MIT License.

In this project we are working on a loan dataset, customer credit card dataset and a bank transaction dataset by using Apache Spark, which is a data processing framework that can quickly perform processing tasks on very large data sets, and can also distribute data processing tasks across multiple computers, either on its own or in tandem with other distributed computing tools. Using these datasets and Spark SQL we have created various use cases pertaining to real life scenarios in banking.

https://databricks-prod-cloudfront.cloud.databricks.com/public/4027ec902e239c93eaaa8714f173bcfc/553931998293758/1733511036908678/113857780564717/latest.html

• SPARK
• HDFS
• HIVE
• DATAFRAMES
• PYSPARK
• SPARK SQL
• JUPYTER NOTEBOOK
• DATABRICKS

• We can easily know the number of customer and their nature by performing this usecases.
• List of usecases performed on each datasets

• The number of loans on each category
• The number of loans taken on each occupation
• Know the number of members who taken more than 1lack loan
• Number of members whose overdue is more than 5
• The number of members whose debt record is less than 20k
• Marital status of loans takers
• Number of loans in each category
• Partitioning dataframe on column ‘Loan Category’
• Number of people with 2 or more returned cheques and income less than 50000

• The number of members who are eligible for credit card
• The number of members who are eligible and active on bank
• The number of targeted persons for credit card
• The targeted persons count whose tenure is less than 5
• The targeted persons count who exited
• The number of targeted persons whose number of product is equal to 1
• Credit card users in Spain
• Number of customers who’s Estimated Salary less than 1 lakh and number of products more than 1.

• Count of transaction on every account.
• Maximum withdrawal amount of an account
• Minimum withdrawal amount of an account
• Maximum deposit amount of an account
• Minimum deposit amount of an account
• Sum of balance in every bank account
• Count of transaction methods what customers used for transaction.
• Number of transaction on each date.
• List of customers with withdrawal amount more than 1 lakh

GitHub clone URL: https://github.com/rajib1007/PROJECT1.git

https://ubuntu.com/download/desktop

https://www.digitalocean.com/community/tutorials/how-to-set-up-jupyter-notebook-with-python-3-on-ubuntu-20-04-and-connect-via-ssh-tunneling

sudo apt-get install openjdk-8-jdk

wget https://dlcdn.apache.org/spark/spark-3.1.2/spark-3.1.2-bin-hadoop3.2.tgz

tar xvzf spark-3.1.2-bin-hadoop3.2.tgz

wget https://archive.apache.org/dist/kafka/2.0.0/kafka_2.11-2.0.0.tgz

tar xvzf kafka_2.11-2.0.0.tgz

pip install kafka-python

• SIDHANT SEHGAL
• ABHILASH REDDY
• AKHIL
• ANAND KUMAR
• VENKATESH VENKAT

This project uses the following license: MIT License.

@cryb/api – Core services

• Info
  • Status
• Codebase
  • Folder Structure
  • Code Style
  • First time setup
    • Installation
  • Running the app locally
    • Background services
    • Starting @cryb/api
• Questions / Issues

@cryb/api is the core service used to handle requests from clients over REST and WebSocket.

Events such as Room creation, user authentication and requests to @cryb/portals to create VM instances are sent from @cryb/api.

@cryb/api has been actively developed internally since August 2019, and is now open source as of October 2019.

The codebase for @cryb/api is written in JavaScript, utilising TypeScript and Node.js. Express.js is used for our REST API, while the WebSocket API uses the ws module.

MongoDB is used as the primary database, while Redis is used for cache and PUB/SUB.

We ask that you follow our code style guidelines when contributing to this repository.

We use ESLint in order to lint our code. Run yarn lint before committing any code to ensure it’s clean.

Note: while we have most rules covered in our .eslintrc.js config, it’s good practice to familarise yourself with our code style guidelines.

cryb/api/
└──┐ src # The core source code
   ├── config # Config files for Redis, Passport, etc
   ├── controllers # Our REST route controller files
   ├── drivers # Methods used to talk to other microservices, such as @cryb/portals
   ├── models # Models for our a data types, such as users and rooms
   ├── schemas # Mongoose schema files
   ├── server # Our Express.js setup
   ├── services # Abstractions for Oauth2, etc
   └── utils # Helper methods

First, clone the @cryb/api repository locally:

git clone https://github.com/crybapp/api.git

The following services need to be installed for @cryb/api to function:

• MongoDB
• Redis

We recommend that you run the following services alongside @cryb/api, but it’s not required.

• @cryb/portals
• @cryb/aperture

You also need to install the required dependencies by running yarn.

Ensure that .env.example is either copied and renamed to .env, or is simply renamed to .env.

In this file, you’ll need some values. Documentation is available in the .env.example file.

Make sure that you have installed MongoDB and Redis, and they are both running locally on port 27017 and 6379 respectively.

The command to start MongoDB is mongod, and the command to start Redis is redis-server. Most Linux distributions will have those packaged, and will start automatically with your system.

If you’re developing a feature that requires the VM infrastructure, then make sure @cryb/portals and @cryb/aperture are running.

To run @cryb/api in development mode, run yarn dev.

It is recommended that in production you run yarn build, then yarn start.

If you have an issues with @cryb/api, please either open a GitHub issue, contact a maintainer or join the Cryb Discord Server and ask in #tech-support.

Nesta pasta, você encontrará uma coleção de comandos essenciais para o uso do Linux, organizados de forma a facilitar o entendimento e a aplicação no dia a dia. Cada comando é acompanhado de uma breve explicação sobre sua funcionalidade, além de exemplos práticos de uso.

• Guia de Instalação do WSL: Passo a passo para configurar o WSL no Windows.
• Comandos Básicos de Linux: Uma coleção de comandos essenciais para uso no Linux, disponíveis dentro das pastas organizadas por categorias.

A História do Linux

O Linux é um sistema operacional baseado em Unix que se tornou uma das plataformas mais populares e influentes do mundo. Sua história começa em 1991, quando Linus Torvalds, um estudante da Universidade de Helsinki, na Finlândia, começou a desenvolver um novo kernel como um hobby. Ele se inspirou no sistema Unix, que era amplamente utilizado em ambientes acadêmicos e de pesquisa, mas caro e restritivo para usuários comuns. Sua intenção inicial era criar um sistema operacional gratuito que pudesse ser usado em computadores pessoais e que permitisse maior flexibilidade.

Antes de criar o Linux, Linus usava o Minix, um sistema operacional semelhante ao Unix criado por Andrew S. Tanenbaum para fins educacionais. Embora o Minix fosse funcional, tinha limitações, e Linus queria mais controle e personalização. Por isso, começou a escrever o seu próprio kernel. Em 25 de agosto de 1991, ele fez um anúncio no grupo de notícias comp.os.minix, onde disse que estava trabalhando em um sistema gratuito inspirado no Unix e pediu feedback da comunidade.

Pouco tempo depois, em setembro de 1991, Linus lançou a primeira versão do kernel Linux (0.01). Naquela época, ele ainda não tinha muitos recursos, mas era suficiente para que outros programadores o ajudassem a expandi-lo. Um dos maiores marcos foi quando Linus decidiu licenciar o Linux sob a Licença Pública Geral GNU (GPL), criada pela Free Software Foundation (FSF), que permitia que qualquer pessoa usasse, modificasse e redistribuísse o software gratuitamente, com a condição de manter o código-fonte aberto.

A decisão de usar a GPL permitiu que o Linux crescesse rapidamente. Desenvolvedores de todo o mundo começaram a contribuir com melhorias e funcionalidades. Um elemento importante foi o conjunto de ferramentas e bibliotecas criadas pelo projeto GNU, que complementaram o kernel Linux, resultando em um sistema completo. Este “sistema operacional Linux” logo se espalhou pelo mundo, sendo adotado por entusiastas de tecnologia, desenvolvedores e empresas.

Nos anos 1990, distribuições Linux começaram a surgir. Essas distribuições consistem no kernel Linux, somado a um conjunto de software que facilita a instalação e uso do sistema. Entre as primeiras e mais conhecidas estão Slackware (1993), Debian (1993) e Red Hat (1994). Cada uma oferecia suas próprias ferramentas de gerenciamento de pacotes e características específicas, mas todas baseadas no mesmo kernel Linux.

O Linux se consolidou principalmente em servidores, onde sua estabilidade e eficiência conquistaram administradores de sistemas e empresas que procuravam alternativas aos sistemas comerciais. Além disso, com a explosão da internet na década de 1990, muitos servidores web passaram a rodar Linux, o que contribuiu ainda mais para sua popularidade.

Com o tempo, o Linux evoluiu e conquistou diversos mercados, desde supercomputadores até dispositivos móveis. Em 2003, foi lançado o Android, um sistema operacional baseado em Linux, que se tornou o sistema mais popular para smartphones. Hoje, o Linux está presente em milhões de dispositivos ao redor do mundo, desde servidores e datacenters até eletrodomésticos, sistemas embarcados e automóveis.

Seu modelo de desenvolvimento aberto, apoiado por uma vasta comunidade e grandes empresas de tecnologia, como IBM, Google, Red Hat e outras, garantiu a contínua inovação e expansão do Linux. Ele também é fundamental para o movimento de software livre, que promove a liberdade dos usuários em usar, modificar e distribuir software.

O Linux transformou o mundo da computação ao promover o conceito de código aberto e oferecer uma alternativa poderosa, gratuita e colaborativa aos sistemas operacionais proprietários. De uma criação humilde por um estudante universitário, o Linux se tornou um dos pilares da infraestrutura digital moderna, influenciando a forma como desenvolvemos, distribuímos e utilizamos a tecnologia.

• Código aberto
• Alta personalização
• Estabilidade e segurança
• Grande comunidade de suporte

Contribuições são bem-vindas! Sinta-se à vontade para abrir issues ou enviar pull requests com melhorias, novos comandos ou correções.

Este projeto está licenciado sob a MIT License.

Explore Curiosity Navcams 3D images in Oculus Quest.

Stereoscopic view.

https://physicslibrary.github.io/Threejs-VR-Curiosity-Navcams/

Oculus Quest tested (6DoF headset/controllers).

Oculus Browser (tested Quest update > 17.0).

No installation.

In Oculus Quest, open Oculus Browser and link (let browser finish loading before “Enter VR”).

https://physicslibrary.github.io/Threejs-VR-Curiosity-Navcams/examples/threejs_vr_curiosity_sol1151.html

File sol1151_wheel_measure.glb shows one of Curiosity’s six wheels on the lower right. Any Navcam image with wheel(s) is selected because a wheel is used in Blender to scale the 3D mesh. The author of Blender-Navcam-Importer has stated that, “resulting mesh…is in no way scientifically accurate”. Nevertheless, the result does not appear distorted or unusual.

If no Oculus Quest (tested 2018 9.7″ iPad/iPadOS 13/Safari, Windows 10/Google Chrome/Firefox, Raspberry Pi 3 B+/Raspbian Buster).

https://physicslibrary.github.io/Threejs-VR-Curiosity-Navcams/examples/threejs_curiosity_sol1151.html

Let browser finish loading before “Enter VR”.

https://physicslibrary.github.io/Threejs-VR-Curiosity-Navcams/examples/threejs_vr_curiosity_sol_1431.html

In front are two images combined as one stereoscopic view using three.js. The left and right Navcams are separated by 42 centimeters apart so it is not what a person would see standing there, someday. Humans IPD averages from 5.1 to 7.7 cm.

The image on the left is a monoscopic view of NLB_524534514EDR_F0562034NCAM00280M_.jpeg.

The 3D model on the right is constructed from two images NLB_524534514EDR_F0562034NCAM00280M_.jpeg and NRB_524534514EDR_F0562034NCAM00280M_.jpeg using Blender-Navcam-Importer.

This project uses images taken by Curiosity Navcams.

https://mars.nasa.gov/

Lot of excellent materials. Do a search for “raw images”.

http://mars.jpl.nasa.gov/msl/multimedia/raw/

The Sol 1431 VR experience is created from left image.

https://mars.nasa.gov/msl-raw-images/proj/msl/redops/ods/surface/sol/01431/opgs/edr/ncam/NLB_524534514EDR_F0562034NCAM00280M_.JPG

And by changing “NLB” to “NRB”, get corresponding right image.

https://mars.nasa.gov/msl-raw-images/proj/msl/redops/ods/surface/sol/01431/opgs/edr/ncam/NRB_524534514EDR_F0562034NCAM00280M_.JPG

Sometimes a left image is available but a matching right image is not available. Move to other images.

Curiosity’s location for Sol 1431.

https://mars.nasa.gov/resources/curiosity-rovers-location-for-sol-1431/

Artist’s scaled image for Sol 1432.

https://www.planetary.org/multimedia/space-images/mars/sean-doran-astronaut-sol1432ml002.html

Images NLB_524534514EDR_F0562034NCAM00280M_.JPG and NRB_524534514EDR_F0562034NCAM00280M_.JPG
Courtesy NASA/JPL-Caltech.

JPL Image Use Policy
https://www.jpl.nasa.gov/imagepolicy/

Go to Curiosity, Multimedia, Raw Images in link:

https://mars.nasa.gov/msl/home/

Or Sol images for left navigation camera:

Curiosity Left Navigation Camera

To find the image used to make sol1151_wheel_measure.glb, enter 1151 for Sol and sort by “oldest to newest”. It should be the 13th image (2015-11-01T21:33:08.000Z).

Raw image used to make sol1151_wheel_measure.glb

A Blender addon is used to import Curiosity Navcams.

https://github.com/phaseIV/Blender-Navcam-Importer

The Blender-Navcam-Importer github has an excellent introduction about the addon.

Blender 2.82 is used to export “glTF Binary” sol1511-wheel-measure.glb with Decimate Modifier(Ratio 0.1) and Draco compression.

https://www.blender.org/

https://mars.nasa.gov/msl/spacecraft/rover/cameras/#navcams

https://mars.nasa.gov/msl/spacecraft/rover/wheels/

https://threejs.org/

https://github.com/mrdoob/three.js/

Three.js examples is the best place to learn and experiment:

https://github.com/mrdoob/three.js/tree/dev/examples

Three.js’ excellent documentation on how to convert WebGL examples to WebVR:

https://threejs.org/docs/index.html#manual/en/introduction/How-to-create-VR-content

Three.js example of how to load .glb file:

https://github.com/mrdoob/three.js/blob/dev/examples/webgl_loader_gltf.html

https://en.wikipedia.org/wiki/Pupillary_distance

Copyright (c) 2020 Hartwell Fong

When you deploy web assets to the Akamai network, you create rules that tell Akamai edge servers how to process end-user requests for your content. Akamai is always seeking ways to make managing complex configurations seamless and quick. With the Property Manager extension, you can edit and validate Property Manager API (PAPI) JSON rule trees the same way you interact with other parts of your infrastructure. Once you’ve updated and validated the configuration file, use PAPI or Property Manager CLI to push the updated file back to the Akamai platform.

• Editing rules, adding behaviors and criteria
• Integration with external, non-Property Manager resources such as CP codes or NetStorage groups
• Syntax highlighting
• Syntax autocomplete based on your Akamai product
• Inline JSON syntax checker
• Property Manager variables support
• Rule tree validation
• Error handling with links to code lines

Before you use this extension, make sure you have access to Akamai Control Center with the appropriate roles and permissions to create API clients and manage credentials. An API client contains authentication tokens that secure the interactions between your application and the Akamai platform. Contact an Akamai administrator within your company and ask them to create the API credentials for you if you don’t have either of these permissions in your role:

• IDM: API Clients – User Access
• IDM: API Clients – Admin Access

With admin access to Akamai Control Center, you can configure your own tokens and client secrets.

1. Launch Identity and Access Management. In Akamai Control Center, click ≡ ⇒ ACCOUNT ADMIN ⇒ Identity & access.
2. From the Users and API Clients tab, click New API client for me to open the Customize API client screen.
3. Follow one of the scenarios:
   • To instantly create an API client and credentials for the Akamai APIs you can access, click Quick. This client’s API access levels, group roles, and permissions are identical to yours. For details about roles, permissions, and access levels, see Identity and Access Management.
   • To make updates to one or more of the accounts you manage, click Advanced. In the Details section, select Let this client manage multiple accounts . For details, see Manage multiple accounts with one API client.

The client’s name, description, and notification list populate for you in the Details section. You can change this information at any time. The set of credentials that appears in the Credentials section includes the client token and client secret needed to authenticate the extension.

4. To check that you have READ-WRITE access to the Property Manager API:
   1. Under Details, click Show additional details.
   2. Scroll through the APIs for Property Manager.
   3. If the API isn’t listed, contact your account representative for assistance.
5. Click Download, then add the credentials to the .edgerc file.

Configure the EdgeGrid credential file that includes client tokens and client secrets for the Akamai accounts you manage. You’ll need this file to authenticate the connection between the extension and the Akamai platform.

1. Open the file you downloaded in a text editor.

2. Add a line above the credentials for your account as follows: [default]

   

NOTE: You can add other credentials to this file as needed. Separate each set of credentials with a [header] as shown in the example. Then, while setting up the authentication in VS Code, you can select the credentials you want to use for editing.

3. Save the file in your home directory with the name .edgerc

1. Install the Property Manager extension by clicking the install link in the marketplace, or install it from the Extensions tab in Visual Studio Code.
2. In Command Palette, enter Edit Rules
3. When you run the extension for the first time, you need to set up your credentials:
   1. Upload the .edgerc file. For MacOS, press Command+Shift+Dot to show the hidden files.
   2. From the menu, select your EdgeGrid credentials that provide access to the properties you want to edit.
   3. Optional: If you created an API client that can manage multiple accounts, enter the Account Switch Key.
   4. Click Submit.

To start editing a JSON configuration file, you can either:

• Download a rules file from the platform. Enter an existing property name and look it up with a search button. Once confirmed, select a version and click Download.
• Use a local rules file. Open a local file in VS Code and in the extension tab, verify that the file path and property name populated correctly. Click Edit.

With the Property Manager extension, you can manage rules, behaviors, criteria, and variables in your existing configurations.

Press Control+Space and the automatic completion prompts you with the building blocks available for your product and module. To learn more about how these elements work together, see PAPI Catalog .

This feature also lists possible option values.

In some behaviors, you need to specify information that comes from the Akamai applications other than Property Manager. Instead of running separate API or CLI calls to get that data, navigate to the option value and press Control+Space. This gets a list of external resources available for the property ID and version associated with your rule tree.

Supported external resources:

• Content Provider (CP) codes
• NetStorage groups for the originServer behavior
• AWS and GCS access keys for the originCharacteristics behavior
• Beacon data sources for the adaptiveAcceleration behavior
• Revocation lists for the segmentedContentProtection behavior
• EdgeWorker IDs
• Stream names for the datastream behavior
• JWT key locations for the verifyJsonWebToken behavior
• Locations for the cloudWrapper behavior
• Custom behavior IDs

Make sure your JSON file is correct before deploying it on the Akamai platform. The validation returns a list of errors and warnings that point you directly to the lines of code you need to fix.

To validate your configuration:

1. Save the rules JSON file.
2. In Command Palette, enter Validate Rules. This opens a new file with a list of errors and warnings.
3. Right-click the errorLocation value and select Go to Definition. The result points you to the line of code that caused the problem.

To learn more about configuration errors and warnings, in the validation file, go to the link in the type value.

After you’ve made your changes and validated the configuration, use PAPI or Property Manager CLI to push the updated file back to the Akamai platform.

When you deploy web assets to the Akamai network, you create rules that tell Akamai edge servers how to process end-user requests for your content. Akamai is always seeking ways to make managing complex configurations seamless and quick. With the Property Manager extension, you can edit and validate Property Manager API (PAPI) JSON rule trees the same way you interact with other parts of your infrastructure. Once you’ve updated and validated the configuration file, use PAPI or Property Manager CLI to push the updated file back to the Akamai platform.

• Editing rules, adding behaviors and criteria
• Integration with external, non-Property Manager resources such as CP codes or NetStorage groups
• Syntax highlighting
• Syntax autocomplete based on your Akamai product
• Inline JSON syntax checker
• Property Manager variables support
• Rule tree validation
• Error handling with links to code lines

Before you use this extension, make sure you have access to Akamai Control Center with the appropriate roles and permissions to create API clients and manage credentials. An API client contains authentication tokens that secure the interactions between your application and the Akamai platform. Contact an Akamai administrator within your company and ask them to create the API credentials for you if you don’t have either of these permissions in your role:

• IDM: API Clients – User Access
• IDM: API Clients – Admin Access

With admin access to Akamai Control Center, you can configure your own tokens and client secrets.

1. Launch Identity and Access Management. In Akamai Control Center, click ≡ ⇒ ACCOUNT ADMIN ⇒ Identity & access.
2. From the Users and API Clients tab, click New API client for me to open the Customize API client screen.
3. Follow one of the scenarios:
   • To instantly create an API client and credentials for the Akamai APIs you can access, click Quick. This client’s API access levels, group roles, and permissions are identical to yours. For details about roles, permissions, and access levels, see Identity and Access Management.
   • To make updates to one or more of the accounts you manage, click Advanced. In the Details section, select Let this client manage multiple accounts . For details, see Manage multiple accounts with one API client.

The client’s name, description, and notification list populate for you in the Details section. You can change this information at any time. The set of credentials that appears in the Credentials section includes the client token and client secret needed to authenticate the extension.

4. To check that you have READ-WRITE access to the Property Manager API:
   1. Under Details, click Show additional details.
   2. Scroll through the APIs for Property Manager.
   3. If the API isn’t listed, contact your account representative for assistance.
5. Click Download, then add the credentials to the .edgerc file.

Configure the EdgeGrid credential file that includes client tokens and client secrets for the Akamai accounts you manage. You’ll need this file to authenticate the connection between the extension and the Akamai platform.

1. Open the file you downloaded in a text editor.

2. Add a line above the credentials for your account as follows: [default]

   

NOTE: You can add other credentials to this file as needed. Separate each set of credentials with a [header] as shown in the example. Then, while setting up the authentication in VS Code, you can select the credentials you want to use for editing.

3. Save the file in your home directory with the name .edgerc

1. Install the Property Manager extension by clicking the install link in the marketplace, or install it from the Extensions tab in Visual Studio Code.
2. In Command Palette, enter Edit Rules
3. When you run the extension for the first time, you need to set up your credentials:
   1. Upload the .edgerc file. For MacOS, press Command+Shift+Dot to show the hidden files.
   2. From the menu, select your EdgeGrid credentials that provide access to the properties you want to edit.
   3. Optional: If you created an API client that can manage multiple accounts, enter the Account Switch Key.
   4. Click Submit.

To start editing a JSON configuration file, you can either:

• Download a rules file from the platform. Enter an existing property name and look it up with a search button. Once confirmed, select a version and click Download.
• Use a local rules file. Open a local file in VS Code and in the extension tab, verify that the file path and property name populated correctly. Click Edit.

With the Property Manager extension, you can manage rules, behaviors, criteria, and variables in your existing configurations.

Press Control+Space and the automatic completion prompts you with the building blocks available for your product and module. To learn more about how these elements work together, see PAPI Catalog .

This feature also lists possible option values.

In some behaviors, you need to specify information that comes from the Akamai applications other than Property Manager. Instead of running separate API or CLI calls to get that data, navigate to the option value and press Control+Space. This gets a list of external resources available for the property ID and version associated with your rule tree.

Supported external resources:

• Content Provider (CP) codes
• NetStorage groups for the originServer behavior
• AWS and GCS access keys for the originCharacteristics behavior
• Beacon data sources for the adaptiveAcceleration behavior
• Revocation lists for the segmentedContentProtection behavior
• EdgeWorker IDs
• Stream names for the datastream behavior
• JWT key locations for the verifyJsonWebToken behavior
• Locations for the cloudWrapper behavior
• Custom behavior IDs

Make sure your JSON file is correct before deploying it on the Akamai platform. The validation returns a list of errors and warnings that point you directly to the lines of code you need to fix.

To validate your configuration:

1. Save the rules JSON file.
2. In Command Palette, enter Validate Rules. This opens a new file with a list of errors and warnings.
3. Right-click the errorLocation value and select Go to Definition. The result points you to the line of code that caused the problem.

To learn more about configuration errors and warnings, in the validation file, go to the link in the type value.

After you’ve made your changes and validated the configuration, use PAPI or Property Manager CLI to push the updated file back to the Akamai platform.