hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
da8ebb72bc5a3183039cd172714bbf0e459b4087 | 227 | md | Markdown | engaged-auth-integration/README.md | engaged-edu/open-edx-engaged-docker-images | 1299df468ca85afc11b72ed24b99bc42c30c759d | [
"Apache-2.0"
] | null | null | null | engaged-auth-integration/README.md | engaged-edu/open-edx-engaged-docker-images | 1299df468ca85afc11b72ed24b99bc42c30c759d | [
"Apache-2.0"
] | null | null | null | engaged-auth-integration/README.md | engaged-edu/open-edx-engaged-docker-images | 1299df468ca85afc11b72ed24b99bc42c30c759d | [
"Apache-2.0"
] | null | null | null | # EngagED Auth Integration
## Publishing
```bash
cd engaged-auth-integration
docker build -t engagedu/open-edx-engaged-auth-integration:{{ VERSION }} .
docker push engagedu/open-edx-engaged-auth-integration:{{ VERSION }}
```
| 22.7 | 74 | 0.748899 | kor_Hang | 0.159153 |
da8f4703eac80f407a8d6db540a5e6bbfcb4f7fd | 1,674 | md | Markdown | 2022.03.21.md | fchain7/DailyNewsSecurity | dde6c0b9ef8c08df5be78c0dd5bda9f76376a856 | [
"Apache-2.0"
] | 3 | 2022-01-20T14:41:55.000Z | 2022-02-23T07:58:51.000Z | 2022.03.21.md | fchain7/DailyNewsSecurity | dde6c0b9ef8c08df5be78c0dd5bda9f76376a856 | [
"Apache-2.0"
] | null | null | null | 2022.03.21.md | fchain7/DailyNewsSecurity | dde6c0b9ef8c08df5be78c0dd5bda9f76376a856 | [
"Apache-2.0"
] | null | null | null | # 2022.03.21 security news
## OS vulnerability
* Windows API - Exploring Virtual Memory and the Virtual Memory Management API.
https://de-engineer.github.io/Understanding-Virtual-Memory-Paging-and-other-memory-related-concepts/
* rocketbootstrap ios 15 crash
https://pastebin.com/2ZHP6ECJ
## Browser vulnerability
* CVE-2022-0337 System environment variables leak on Google Chrome, Microsoft Edge and Opera
https://github.com/Puliczek/CVE-2022-0337-PoC-Google-Chrome-Microsoft-Edge-Opera
## Virtualization vulnerability
*
## Application vulnerability
* Blue teams helping red teams: A tale of a process crash, PowerShell, and the MITRE ATT&CK evaluation
https://www.microsoft.com/security/blog/2020/06/11/blue-teams-helping-red-teams-a-tale-of-a-process-crash-powershell-and-the-mitre-attck-evaluation/
## Tool
* A tool that can be used by web app pentesters to create a copy of the targeted website with CDN and WAF restrictions disabled.
https://github.com/RyanJarv/cdn-proxy
* vmlinux-to-elf
https://github.com/marin-m/vmlinux-to-elf
## IOT vulnerability
*
## Exploit method
* EP57 Stop Zero Days, Save the World: Project Zero's Maddie Stone Speaks
https://cloud.withgoogle.com/cloudsecurity/podcast/ep57-stop-zero-days-save-the-world-project-zeros-maddie-stone-speaks/
## Fuzz
* Vulnerability Research & Fuzzing
https://www.signal-labs.com/vulnerability-research-fuzzing
## CTF
*
## Other
* 人生的第二个可能~
https://lorexxar.cn/2022/03/21/vblog/
* Free decryptor released for TrickBot gang's Diavol ransomware
https://www.bleepingcomputer.com/news/security/free-decryptor-released-for-trickbot-gangs-diavol-ransomware/ | 24.985075 | 150 | 0.765233 | yue_Hant | 0.401229 |
da9091822e9260adb4909208181e0df6fa77b9fc | 109 | md | Markdown | README.md | msomi22/beautifulJava | c3db5b9706921fc19d7395a5839232af20f08ae1 | [
"MIT"
] | null | null | null | README.md | msomi22/beautifulJava | c3db5b9706921fc19d7395a5839232af20f08ae1 | [
"MIT"
] | null | null | null | README.md | msomi22/beautifulJava | c3db5b9706921fc19d7395a5839232af20f08ae1 | [
"MIT"
] | null | null | null | # beautifulJava
Beautiful Java is a collection of commonly asked Java algorithms and their implementation.
| 27.25 | 91 | 0.825688 | eng_Latn | 0.999183 |
da90a2dcc7b1f876241a42170879f0b0d5748140 | 683 | md | Markdown | resources/README.md | mohit-kumar-sharma/proffer | d20d6d95be75ffad4bd3f10cad286af3b11650a1 | [
"Apache-2.0"
] | 1 | 2020-06-04T19:10:24.000Z | 2020-06-04T19:10:24.000Z | resources/README.md | mohit-kumar-sharma/proffer | d20d6d95be75ffad4bd3f10cad286af3b11650a1 | [
"Apache-2.0"
] | 7 | 2020-06-03T08:49:05.000Z | 2020-09-07T05:32:08.000Z | resources/README.md | mohit-kumar-sharma/proffer | d20d6d95be75ffad4bd3f10cad286af3b11650a1 | [
"Apache-2.0"
] | 1 | 2020-06-01T19:59:40.000Z | 2020-06-01T19:59:40.000Z | # Resources
In Proffer, we have a component called resource. Each resource is responsible to perform a particular sets of tasks. Each resources has its type. We define the resources in `resources` list in proffer template file.
Available Resource Types:
* [aws-copyami](aws/copyami/README.md)
- Provider: AWS
- Use case: This resource type can be used to copy AMI in different regions of an AWS Account.
- [Allowed Properties](aws/copyami/README.md)
* [aws-shareami](aws/shareami/README.md)
- Provider: AWS
- Use case: This resource type can be used to share the AMI with different AWS Accounts and regions.
- [Allowed Properties](aws/shareami/README.md)
| 42.6875 | 215 | 0.743777 | eng_Latn | 0.971341 |
da90be13bccec94d4cc30403b57a7aae593414e4 | 4,113 | md | Markdown | _posts/2020-10-08-download-sleeping-with-my-student-2019-english-with-subtitles-hdtv-720p-600mb.md | tamilrockerss/1 | aba0806b125f9614d2964c7ec77ddb85e5e10bfd | [
"MIT"
] | null | null | null | _posts/2020-10-08-download-sleeping-with-my-student-2019-english-with-subtitles-hdtv-720p-600mb.md | tamilrockerss/1 | aba0806b125f9614d2964c7ec77ddb85e5e10bfd | [
"MIT"
] | null | null | null | _posts/2020-10-08-download-sleeping-with-my-student-2019-english-with-subtitles-hdtv-720p-600mb.md | tamilrockerss/1 | aba0806b125f9614d2964c7ec77ddb85e5e10bfd | [
"MIT"
] | null | null | null | ---
id: 220
title: 'Download Sleeping with My Student (2019) {English With Subtitles} HDTV 720p [600MB]'
date: 2020-10-08T12:21:58+00:00
author: admin
layout: post
guid: https://themoviesflix.co/?p=13215
permalink: /2020/10/08/download-sleeping-with-my-student-2019-english-with-subtitles-hdtv-720p-600mb/
tdc_dirty_content:
- "1"
tdc_icon_fonts:
- 'a:0:{}'
cyberseo_rss_source:
- https://www.psdly.com/wp-theme/feed?paged=9
- https://themoviesflix.co/feed/?paged=20
cyberseo_post_link:
- https://www.psdly.com/themeforest-sada-v1-1-4-a-wordpress-theme-for-blog-shop-22930505
- https://themoviesflix.co/download-sleeping-with-my-student-2019-english-720p/
categories:
- Uncategorized
---
✅ Download Sleeping with My Student (2019) Movie English Audio in 720p. This is a Hollywood movie and available in 720p qualities. This is one of the best movies based on **Thriller. **This Movie is **not** available in Hindi or Dual Audio. Click on the Download links below to proceed👇
**TheMoviesFlix.co** is The Best Website/Platform For Hollywood HD Movies. We Provide Direct Google Drive Download Links For Fast And Secure Downloading. Just Click On Download Button _And Follow Steps To Download And Watch Movies Online For Free_.
### Download Sleeping with My Student (2019) English 720p ~ TheMoviesFlix.co {.has-text-align-center.has-text-color}
### Movie Info: {.has-text-color}
* **Full Name: **Sleeping with My Student
* **Language:** English
* **Subtitles:** Yes (English)
* **Year:** 2019
* **Size:** 600MB
* **Quality:** 720p – **HDTV**
* **Format:** Mkv
### Storyline: {.has-text-color}
New school headmaster and single mother Kathy discovers her vacation fling with charming 18-year-old Ian was no accident when he transfers to her school targeting Kathy and her teenage daughter Bree in a deadly scheme. Ian wants revenge as he believes Kathy is responsible for splitting up his family ultimately leading to his father’s death. Kathy will need to uncover Ian’s motives quickly if she hopes to protect herself and Bree from his dangerous threats.
### Screenshots: {.has-text-color}<figure class="wp-block-image">
 </figure>
<p class="has-text-align-center has-text-color has-medium-font-size">
Download Sleeping with My Student (2019) English With Esubs 720p [900MB]
</p>
<span class="mb-center maxbutton-3-center"><span class="maxbutton-3-container mb-container"><a class="maxbutton-3 maxbutton maxbutton-post-button" target="_blank" rel="nofollow noopener noreferrer" href="https://coinquint.com/a12778/"><span class="mb-text">Download Links</span></a></span></span>
<center>
</center>
<center>
<a href="https://t.me/themoviesflixcom" target="_blank" data-wpel-link="external" rel="nofollow external noopener noreferrer"><button class="button button5">Join Our Telegram</button></a> <a href="https://themoviesflix.co/download-sleeping-with-my-student-2019-english-720p/#" target="_blank" data-wpel-link="external" rel="nofollow external noopener noreferrer"><button class="button button5">Announcements</button></a> <a href="https://themoviesflix.com/how-to-download/" target="_blank" data-wpel-link="external" rel="nofollow external noopener noreferrer"><button class="button button5">How To Download?</button></a> <a href="https://themoviesflix.co/download-sleeping-with-my-student-2019-english-720p/#" target="_blank" data-wpel-link="external" rel="nofollow external noopener noreferrer"><button class="button button5">Report Broken Links</button></a>
</center>
<div class="alert alert-danger">
Please Do Not Use VPN for Downloading Movies From Our Site.
</div>
<div class="alert alert-success">
Click On The Above <strong>Download Button</strong> Download File.
</div>
<div class="alert alert-warning">
If You Find Any Broken Link Then <strong>Report</strong> To Us.
</div>
<div class="alert alert-info">
<strong>Comment</strong> Your Queries And Requests Below In The Comment Box.
</div> | 56.342466 | 861 | 0.748602 | eng_Latn | 0.520248 |
da91c25899c7b8afd375888535b27db7b82f4d35 | 508 | md | Markdown | README.md | kurisucat/Simple-PHP-Vote-System | 6a7aaf60ab793c7e0309e3a523d43d29a4c21d48 | [
"MIT"
] | 3 | 2021-11-13T11:12:00.000Z | 2021-11-16T11:19:32.000Z | README.md | kurisucat/Simple-PHP-Vote-System | 6a7aaf60ab793c7e0309e3a523d43d29a4c21d48 | [
"MIT"
] | null | null | null | README.md | kurisucat/Simple-PHP-Vote-System | 6a7aaf60ab793c7e0309e3a523d43d29a4c21d48 | [
"MIT"
] | 1 | 2021-11-13T11:12:23.000Z | 2021-11-13T11:12:23.000Z | # Simple-PHP-Vote-System
一个使用 PHP 开发的简易集体投票系统
## 特色
* 使用 [MDUI](https://mdui.org) 进行开发，具有漂亮的自适应 Material Design 页面样式
* 简单部署与使用，只需支持 PHP 与 MySQL 的 Web 环境就可以使用
* 轻量级，仅两张数据表和 2MB 的主程序，加载更迅速
* 完全的 Ajax 请求方式，动态响应，更可支持开发配套 App。
## 安装方式
1. Clone 本仓库源码，并上传至你的服务器
2. 导入 `vote.sql` 至你的数据库，并在表 `items` 中设置投票项目
3. 打开 `config.php`，按照注释填写设置项目
4. 打开你的站点试试吧！
## 鸣谢
* [zdhxiong/mdui](https://github.com/zdhxiong/mdui)
* [ThingEngineer/PHP-MySQLi-Database-Class](https://github.com/ThingEngineer/PHP-MySQLi-Database-Class)
| 26.736842 | 103 | 0.742126 | yue_Hant | 0.932489 |
da91f94f4a69152fb10890998b281eb13cfa1c0e | 2,444 | md | Markdown | docs/root/source/contributing/ways-to-contribute/report-a-bug.md | jaromil/bigchaindb | ad4c64923af49b69ba15b98b3b1af14ceaaac40f | [
"Apache-2.0"
] | 4,196 | 2016-02-10T13:45:27.000Z | 2022-03-31T23:28:59.000Z | docs/root/source/contributing/ways-to-contribute/report-a-bug.md | jaromil/bigchaindb | ad4c64923af49b69ba15b98b3b1af14ceaaac40f | [
"Apache-2.0"
] | 2,527 | 2016-02-10T15:00:53.000Z | 2022-03-30T07:24:15.000Z | docs/root/source/contributing/ways-to-contribute/report-a-bug.md | jaromil/bigchaindb | ad4c64923af49b69ba15b98b3b1af14ceaaac40f | [
"Apache-2.0"
] | 934 | 2016-02-10T23:55:15.000Z | 2022-03-27T03:51:08.000Z | <!---
Copyright © 2020 Interplanetary Database Association e.V.,
BigchainDB and IPDB software contributors.
SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0)
Code is Apache-2.0 and docs are CC-BY-4.0
--->
How to contribute?
==================
# Report a Bug
To report a bug, go to the relevant GitHub repository, click on the **Issues** tab, click on the **New issue** button, and read the instructions.
# Write an Issue
To write an issue, go to the relevant GitHub repository, click on the **Issues** tab, click on the **New issue** button, and read the instructions.
# Answer Questions
People ask questions about BigchainDB in the following places:
- Gitter
- [bigchaindb/bigchaindb](https://gitter.im/bigchaindb/bigchaindb)
- [bigchaindb/js-bigchaindb-driver](https://gitter.im/bigchaindb/js-bigchaindb-driver)
- [Twitter](https://twitter.com/bigchaindb)
- [Stack Overflow "bigchaindb"](https://stackoverflow.com/search?q=bigchaindb)
Feel free to hang out and answer some questions. People will be thankful.
# Write a BigchainDB Enhancement Proposal (BEP)
If you have an idea for a new feature or enhancement, and you want some feedback before you write a full BigchainDB Enhancement Proposal (BEP), then feel free to:
- ask in the [bigchaindb/bigchaindb Gitter chat room](https://gitter.im/bigchaindb/bigchaindb) or
- [open a new issue in the bigchaindb/BEPs repo](https://github.com/bigchaindb/BEPs/issues/new) and give it the label **BEP idea**.
If you want to discuss an existing BEP, then [open a new issue in the bigchaindb/BEPs repo](https://github.com/bigchaindb/BEPs/issues/new) and give it the label **discuss existing BEP**.
## Steps to Write a New BEP
1. Look at the structure of existing BEPs in the [bigchaindb/BEPs repo](https://github.com/bigchaindb/BEPs). Note the section headings. [BEP-2](https://github.com/bigchaindb/BEPs/tree/master/2) (our variant of the consensus-oriented specification system [COSS]) says more about the expected structure and process.
1. Write a first draft of your BEP. It doesn't have to be long or perfect.
1. Push your BEP draft to the [bigchaindb/BEPs repo](https://github.com/bigchaindb/BEPs) and make a pull request. [BEP-1](https://github.com/bigchaindb/BEPs/tree/master/1) (our variant of C4) outlines the process we use to handle all pull requests. In particular, we try to merge all pull requests quickly.
1. Your BEP can be revised by pushing more pull requests. | 55.545455 | 313 | 0.753682 | eng_Latn | 0.938327 |
da92bc970d24042673c2ffa35ceac254fad0fc3d | 419 | md | Markdown | README.md | labs42/babel-preset-labs42 | 7dc060f8651e9a4456125dc9d0506f0c0258a87b | [
"MIT"
] | null | null | null | README.md | labs42/babel-preset-labs42 | 7dc060f8651e9a4456125dc9d0506f0c0258a87b | [
"MIT"
] | null | null | null | README.md | labs42/babel-preset-labs42 | 7dc060f8651e9a4456125dc9d0506f0c0258a87b | [
"MIT"
] | null | null | null | babel-preset-labs42
===================
This package provides babel preset accepted and used in labs42 projects.
Requirements
------------
* NodeJS 4+ and npm installed
Installation
------------
* ``$ npm install babel-preset-labs42 --save-dev``
Usage
-----
Add the following code to your ``.babelrc`` file
```
{
"ignore": "**/node_modules/**/*.js",
"sourceMaps": "inline",
"presets": [ "labs42" ]
}
```
| 15.518519 | 72 | 0.591885 | eng_Latn | 0.787733 |
da92d71ff10956714868940a9877a565c355d1ec | 8,524 | md | Markdown | README.md | TCCinTaiwan/TuTube | 9b72cd02a0cd98fae299b486863c7f4e4e2eb128 | [
"MIT"
] | null | null | null | README.md | TCCinTaiwan/TuTube | 9b72cd02a0cd98fae299b486863c7f4e4e2eb128 | [
"MIT"
] | null | null | null | README.md | TCCinTaiwan/TuTube | 9b72cd02a0cd98fae299b486863c7f4e4e2eb128 | [
"MIT"
] | null | null | null | # [:octocat:TcTube](https://github.com/TCCinTaiwan/TcTube)
[](https://github.com/TCCinTaiwan/TcTube/releases) [](https://gitter.im/TCCinTaiwan/TcTube?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) [](https://travis-ci.org/TCCinTaiwan/TcTube)
## Contents[↶](#)
* **[Introduction](#introduction)**
* **[Browser Support](#browser-support)**
* **[Installation](#installation)**
* **[Usage](#usage)**
* **[ShortKey](#shortkey)**
* **[Todo](#todo)**
* **[Contributing](#contributing)**
* **[Coding Style](#coding-style)**
- **[javascript](#javascript)**
* **[History](#history)**
* **[License](#license)**
## Introduction[↶](#)
這是2016年暑假，我在系上實習，老師叫我們做的系統，我用去年寫的播放器加以改進。
最新版本為0.3.1。
## Browser Support[↶](#)
|  |  |  |  |  | 
| --- | --- | --- | --- | --- | --- |
| IE 9+ ✔ | Chrome ✔ | Firefox ✔ | Opera 37.0+ ✔ | Safari 4.0+ ✖ | Vivaldi 1+ ✔ |
## Installation[↶](#)
### Base Server
* Git:
[ ](https://git-scm.com/download/)
* Python:
[ ](https://www.python.org/downloads/)
>注意: 本專案使用的是Python3
>要勾"Add Python to PATH"，把Python加到環境變數中。
* Nginx:
[ ](https://nginx.org/en/download.html)
1. Clone the repository
Use command:
```bash
git clone https://github.com/TCCinTaiwan/TcTube
```
Or:
[ ](https://github.com/TCCinTaiwan/TcTube/archive/master.zip)
2. Install requirement python module
You can use pip:
```bash
pip install pip --upgrade
pip install -r TcTube/requirements.txt
```
Or you can run [setup.py](setup.py) :
```bash
python setup.py install
```
3. 下載nginx後，把檔案放在TcTube底下，或者修改 [main.py](main.py) 中nginx路徑。
>最好下載最新的穩定版本(Stable version)
4. 把 [setup/nginx-main.conf](setup/nginx-main.conf)複製到主要伺服器 nginx-*/conf/ 底下，取代原本的 nginx.conf。
>假如是Ubuntu要執行則是取代/etc/nginx/nginx.conf，還要修改路徑，其他系統以此類推。
5. 把 [setup/nginx-substation.conf](setup/nginx-substation.conf)複製到次要伺服器 nginx-*/conf/ 底下，取代原本的 nginx.conf。
5. 修改主要伺服器nginx.conf檔案的upstream伺服器列表(Port要正確)。
### Media Server
1. 音樂檔案要放在 [file/video/](file/video/)
2. 修改 [database.db](database.db)裡的videos和videoSources資料表，加入自己的歌
3. 略縮圖要放在 [file/image/streamshot](file/image/streamshot)
```sql
insert into videos (title, artist) values ("<title>", "<artist>");
insert into videoSources (id, video_id, source) values (1, <video_id>, "<filename>");
insert into videoSources (id, video_id, source) values (2, <video_id>, "<filename2>");
...
```
## Usage[↶](#)
* run Server:
```bash
# Go into the directory
cd TcTube
# run server
python main.py
```
>Make sure port 80, 8000, 8080 (TCP) is open.
## ShortKey[↶](#)
* <kbd>Ctrl</kbd> + <kbd>←</kbd>: 上一首
* <kbd>Ctrl</kbd> + <kbd>→</kbd>: 下一首
* <kbd>Shift</kbd> 滾輪: 播放速度
* <kbd>←</kbd>: 往前
* <kbd>→</kbd>: 往後
* <kbd>+</kbd>: 增加音量
* <kbd>-</kbd>: 減少音量
* <kbd>Space</kbd>: 播放/暫停
* <kbd>0</kbd>: 跳到影片開頭
* <kbd>1</kbd>: 跳到影片10%位置
* <kbd>2</kbd>: 跳到影片20%位置
* <kbd>3</kbd>: 跳到影片30%位置
* <kbd>4</kbd>: 跳到影片40%位置
* <kbd>5</kbd>: 跳到影片50%位置
* <kbd>6</kbd>: 跳到影片60%位置
* <kbd>7</kbd>: 跳到影片70%位置
* <kbd>8</kbd>: 跳到影片80%位置
* <kbd>9</kbd>: 跳到影片90%位置
## Todo[↶](#)
1. 資料庫:
- 部門
+ select users.id, users.account, users.password, users.name , users.affiliation, department.name as affiliation_name, users.email, users.phone, users.birthday, users.creating_time, users.login_time, users.login_ip, users.competence from users join department on users.affiliation = department.id;
2. 控制面板延遲
3. APP化
4. 頁面歷史
5. 播放清單
6. 影片嵌入支援
- Vimeo.com
- 優酷 http://open.youku.com/tools
- 土豆網
- 愛奇藝
- FaceBook https://developers.facebook.com/docs/plugins/embedded-video-player
- flv
7. Seek影片預覽
8. SSL
9. 選項:
- 下載檔名格式
10. 檔案類型分析(不是以副檔名分析)
11. Blob
12. 時間進度Seekable
13. SSO
14. localization:
- Babel
15. 加入uwsgi
16. 播放器重構
17. Chrome Extensions
18. Youtube跟Video整合:
- 斷線時跳過
- Youtube斷線時使用本地
19. 修復上傳功能
## Contributing[↶](#)
1. Create an issue and describe your idea
2. [](https://github.com/TCCinTaiwan/TcTube/network) it!
3. Create your feature branch: `git checkout -b my-new-feature`
4. Commit your changes: `git commit -m 'Add some feature'`
5. Push to the branch: `git push origin my-new-feature`
6. Submit a Pull Request
## Coding Style[↶](#)
### JavaScript[↶](#)
* No tabs. **Four spaces**.
* No trailing whitespace.
* Always use semicolons and don't rely on implicit insertion.
* use **lowerCamelCase** for identifier names (variables and functions).
+ :white_check_mark: good
```javascript
var helloWorld = "Hello, world."; // lowerCamelCase
var strHelloWorld = "Hello, world."; // Hungarian Notation + lowerCamelCase
```
+ :x: bad
```javascript
var HelloWorld = "Hello, world."; // UpperCamelCase, Pascal
var helloworld = "Hello, world."; // lowercase
var HELLOWORLD = "Hello, world."; // UPPERCASE
var Hello_World = "Hello, world."; // Capitalized_Words_With_Underscores
var HELLO_WORLD = "Hello, world."; // UPPER_CASE_WITH_UNDERSCORES
var hello_world = "Hello, world."; // lower_case_with_underscores
var hello-world = "Hello, world."; // lower-case-hyphens
var HELLO-WORLD = "Hello, world."; // UPPER-CASE-HYPHENS
...
```
* **Double quotes**. Single quotes are OK only when nested within double quotes.
+ :white_check_mark: good
```javascript
var foo = "Hello, world.";
var bar = "Hello, 'world.'";
```
+ :x: bad
```javascript
var foo = 'Hello, world.';
```
* Functions are followed by no space.
+ :white_check_mark: good
```javascript
function foo() {
...
}
```
+ :x: bad
```javascript
function foo () {
...
}
```
* Always put spaces around operators (= + - * /), and after commas.
+ :white_check_mark: good
```javascript
var x = y + z;
var values = ["Apple", "Ball", "Cat"];
```
+ :x: bad
```javascript
var x=y+z;
var values=["Apple","Ball","Cat"];
```
* Argument definitions are followed by no spaces.
+ :white_check_mark: good
```javascript
function foo(a, b, c) {
...
}
```
+ :x: bad
```javascript
function foo( a, b, c ) {
...
}
```
* A **single space** will always and should only follow semi-colons when defining object literals.
+ :white_check_mark: good
```javascript
var foo = {
bar: 1
};
```
+ :x: bad
```javascript
var foo = {
bar : 1
};
var foo = {
bar:1
};
```
* A **single space** will always follow conditional statements.
+ :white_check_mark: good
```javascript
if (true) {
...
}
```
+ :x: bad
```javascript
if(true) {
...
}
if(true){
...
}
```
* General rules for complex (compound) statements:
+ Put the opening bracket at the end of the first line.
+ Use one space before the opening bracket.
+ Put the closing bracket on a new line, without leading spaces.
+ Do not end a complex statement with a semicolon.
```javascript
function formatTime(seconds) {
minutes = Math.floor(seconds / 60);
minutes = (minutes >= 10) ? minutes : "0" + minutes;
seconds = Math.floor(seconds % 60);
seconds = (seconds >= 10) ? seconds : "0" + seconds;
return minutes + ":" + seconds;
}
```
## History[↶](#)
For detailed changelog, check [Change Log](CHANGELOG.md).
## License[↶](#)
[](LICENSE)
| 29.191781 | 505 | 0.63855 | yue_Hant | 0.424827 |
da92f181df685d287a4cb7589716cbe15f89ab51 | 4,307 | md | Markdown | article/PART8/flink/flink-04-data-stream-api.md | LuckinJack/LuckinJack.github.io | 8caf1bfa1a02d1c689a1da3ad1829b45861e8d5b | [
"Apache-2.0"
] | 1 | 2021-03-08T14:26:39.000Z | 2021-03-08T14:26:39.000Z | article/PART8/flink/flink-04-data-stream-api.md | LuckinJack/LuckinJack.github.io | 8caf1bfa1a02d1c689a1da3ad1829b45861e8d5b | [
"Apache-2.0"
] | null | null | null | article/PART8/flink/flink-04-data-stream-api.md | LuckinJack/LuckinJack.github.io | 8caf1bfa1a02d1c689a1da3ad1829b45861e8d5b | [
"Apache-2.0"
] | null | null | null | # Flink 流处理API
...
## Environment
一个Flink作业必须依赖于一个执行环境。
### getExecutionEnvironment
`getExecutionEnvironment` 是最常用的一种创建执行环境的方式，它会根据查询运行的方式决定返回什么样的运行环境创建一个执行环境，表示当前执行程序的上下文：
- 如果程序是独立调用的，此方法返回本地执行环境
- 如果从命令行客户端调用程序以提交到集群，此方法返回该集群的执行环境
```java
ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
```
```java
StreamExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
```
> **[!NOTE]**
>
> 1. 如果没有设置并行度，会以 `flink-conf.yml` 中的配置为准，默认是 1。
>
> 2. 流处理和批处理的执行环境不同：
>
> - 流处理的执行环境名为org.apache.flink.streaming.api.environment.StreamExecutionEnvironment
>
> - 批处理的执行环境名为org.apache.flink.api.java.ExecutionEnvironment
### createLocalEnvironment
`createLocalEnvironment`返回本地执行环境，需要在调用时指定默认的并行度
```java
LocalStreamEnvironment env = StreamExecutionEnvironment.createLocalEnvironment(1);
```
### createRemoteEnvironment
返回集群执行环境，将 Jar 提交到远程服务器。需要在调用时指定 *JobManager* 的 IP 和端口号，并指定要在集群中运行的 Jar 包。
```java
StreamExecutionEnvironment env =
StreamExecutionEnvironment.createRemoteEnvironment("jobmanage-hostname", 6123,"YOUR_PATH//FlinkJob.jar"));
```
## Source
### 从集合读取数据
### 从文件读取数据
```java
DataStream<String> dataStream = env.readTextFile("YOUR_FILE_PATH");
```
### 从kafka消息队列读取数据
```java
// kafka 配置项
Properties properties = new Properties();
properties.setProperty("bootstrap.servers", "localhost:9092");
properties.setProperty("group.id", "consumer-group");
properties.setProperty("key.deserializer",
"org.apache.kafka.common.serialization.StringDeserializer");
properties.setProperty("value.deserializer",
"org.apache.kafka.common.serialization.StringDeserializer");
properties.setProperty("auto.offset.reset", "latest");
// 从 kafka 读取数据
DataStream<String> dataStream = env.addSource( new
FlinkKafkaConsumer011<String>("sensor", new SimpleStringSchema(), properties));
```
### 自定义Source
我们还可以自定义 source数据来源，实现 SourceFunction 接口即可
```java
public static void main(String[] args) {
LocalStreamEnvironment env = StreamExecutionEnvironment.createLocalEnvironment(1);
DataStream<SensorReading> dataStream = env.addSource(new MySensor());
}
public static class MySensor implements SourceFunction<SensorReading> {
private boolean running = true;
@Override
public void run(SourceContext<SensorReading> ctx) throws Exception {
Random random = new Random();
HashMap<String, Double> sensorTempMap = new HashMap<>();
for (int i = 0; i < 10; i++) {
sensorTempMap.put("sensor_" + (i + 1), 60 + random.nextGaussian() * 20);
}
while (running) {
for (String sensorId : sensorTempMap.keySet()) {
Double newTemp = sensorTempMap.get(sensorId) + random.nextGaussian();
sensorTempMap.put(sensorId, newTemp);
ctx.collect(new SensorReading(sensorId, System.currentTimeMillis(),
newTemp));
}
Thread.sleep(1000L);
}
}
public void cancel() {
this.running = false;
}
}
```
## TransForm
转换算子
### map
map中传入的是一个接口 *MapFunction<T,O>*，我们可以继承并重写 *MapFunction* 或 *RichMapFunction* 来自定义map()。
```java
// 从文件读取数据
DataStream<String> inputStream = env.readTextFile("D:\\Projects\\testData.txt");
//map，输出每一行的字符串长度
DataStream<Integer> mapStream = inputStream.map(new MapFunction<String, Integer>() {
@Override
public Integer map(String value) throws Exception {
return value.length();
}
});
```
```java
@Public
@FunctionalInterface
public interface MapFunction<T, O> extends Function, Serializable {
/**
* The mapping method. Takes an element from the input data set and transforms
* it into exactly one element.
*
* @param value The input value.
* @return The transformed value
*
* @throws Exception This method may throw exceptions. Throwing an exception will cause the operation
* to fail and may trigger recovery.
*/
O map(T value) throws Exception;
}
```
### flatMap
### filter
### keyBy
### Rolling Aggregation（滚动聚合算子）
- sum()
- min()
- max()
- minBy()
- maxBy()
### Reduce
### Split 和 Select
#### split
#### select
## Sink
Flink的对外输出操作都用 Sink 完成。 | 19.057522 | 106 | 0.681913 | yue_Hant | 0.283528 |
da9353cfb2b32ef39429aec5e7c1fb1bfba4279f | 379 | md | Markdown | README.md | renaudin/dotfiles | 57b6cbbf0dfef9267bd6ec73f42a6a7635b2dca2 | [
"MIT"
] | null | null | null | README.md | renaudin/dotfiles | 57b6cbbf0dfef9267bd6ec73f42a6a7635b2dca2 | [
"MIT"
] | null | null | null | README.md | renaudin/dotfiles | 57b6cbbf0dfef9267bd6ec73f42a6a7635b2dca2 | [
"MIT"
] | null | null | null | My dotfiles repository.
Everything is organised around topic folders such as :
- vim
- bash
- git
- tmux
This should be manageable by GNU Stow in a near future.
The terminator config file should be put in ~/.config/terminator/config
## thanks
I forked [Zach Holman](http://github.com/holman') excellent
[dotfiles](http://github.com/holman/dotfiles) to setup this repository.
| 25.266667 | 72 | 0.759894 | eng_Latn | 0.963499 |
da93c4680baed8d8ea84911c56fdbd44fded765b | 1,688 | md | Markdown | docs/singer_list.md | JooZh/music-api-for-qq | cfeeddee65003dd28adf137f6fbdfd209ca6fd43 | [
"MIT"
] | 18 | 2019-03-12T16:57:59.000Z | 2021-11-15T11:55:25.000Z | docs/singer_list.md | JooZh/music-api-for-qq | cfeeddee65003dd28adf137f6fbdfd209ca6fd43 | [
"MIT"
] | 6 | 2020-07-17T10:29:36.000Z | 2022-02-26T12:15:16.000Z | docs/singer_list.md | JooZh/music-api-for-qq | cfeeddee65003dd28adf137f6fbdfd209ca6fd43 | [
"MIT"
] | 4 | 2019-04-28T12:16:07.000Z | 2021-07-14T03:23:23.000Z | ## 获取歌手列表
#### 全路径
```
http://localhost:8080/music/api/singer_list
```
#### 前置条件
> 无
>
#### 参数说明
| 参数名 | 默认值 | 类型 | 必填 | 可选参数 | 说明 |
| :------- | ------ | ------ | ---- | --------------------------------- | ------------------ |
| picSize | 150 | number | | [150,300,500,800] | 头像尺寸大小 |
| area | -100 | number | * | 参考返回的 **tags.area** 属性 | 地区筛选 |
| sex | -100 | number | * | 参考返回的 **tags.sex** 属性 | 性别筛选 |
| genre | -100 | number | * | 参考返回的 **tags.genre** 属性 | 类别筛选 |
| index | -100 | number | * | 参考返回的 **tags.index** 属性 | 字母筛选 |
| sin | 0 | number | * | 规定为每次增加 80 | 开始条数 |
| cur_page | 1 | number | * | 规定为每次增加 1， **sin** 需要 增加80 | 分页 |
#### 请求方式
参数名称不可改变
```js
axios.get(url, {
params:{
picSize:800,
area: -100,
sex: -100,
genre: -100,
index: -100,
sin: 0,
cur_page: 1
}
}).then((response)=>{
response.data
})
```
#### 返回数据
```js
{
message: "ok",
status: 0,
data:{
total: 208, // 单曲总数
tags:{
area:[{id: -100,name: "全部"},....], // 区域筛选
genre:[{id: -100,name: "全部"},....], // 类别筛选
index:[{id: -100,name: "全部"},....], // 字母筛选
sex:[{id: -100,name: "全部"},....] // 性别筛选
}
list:[
{
country: "台湾", // 序号
singer_id: 245, // 歌曲总时长
singer_mid: "0010PLKl2Wgolz",, // 歌曲格式化时长
singer_name: "飞儿乐团", // 所属专辑 id
singer_avatar: "http://y.gtimg.cn.jpg" // 所属专辑 mid
},
......
]
}
}
```
| 22.810811 | 94 | 0.376777 | yue_Hant | 0.295922 |
da940b0b49130af9408c1d9b9c085ea62d4ae479 | 5,175 | md | Markdown | README.md | BryanChanCQ/LoginDemoUI | 28b736510a411db6887fc1bcd39b771f920c6881 | [
"MIT"
] | null | null | null | README.md | BryanChanCQ/LoginDemoUI | 28b736510a411db6887fc1bcd39b771f920c6881 | [
"MIT"
] | null | null | null | README.md | BryanChanCQ/LoginDemoUI | 28b736510a411db6887fc1bcd39b771f920c6881 | [
"MIT"
] | null | null | null | <h1 align="center">FAST-UI——企业级中后台UI框架</h1>
<p align="center">让(中后台系统)前端开发简单而友好</p>
<p align="center">
<a href="https://github.com/vuejs/vue">
<img src="https://img.shields.io/badge/vue-2.5.10-brightgreen.svg" alt="vue">
</a>
<a href="https://github.com/ElemeFE/element">
<img src="https://img.shields.io/badge/element--ui-2.3.2-brightgreen.svg" alt="element-ui">
</a>
<a href="https://travis-ci.org/PanJiaChen/vue-element-admin" rel="nofollow">
<img src="https://travis-ci.org/PanJiaChen/vue-element-admin.svg?branch=master" alt="Build Status">
</a>
<a href="https://github.com/PanJiaChen/vue-element-admin/blob/master/LICENSE">
<img src="https://img.shields.io/github/license/mashape/apistatus.svg" alt="license">
</a>
</p>
-------------
## 简介
FAST-UI 是一个中后台网页开发的集成解决方案，
它基于当前最主流、先进和易学的前端技术：
- [vue](https://github.com/vuejs/vue)
- [element](https://github.com/ElemeFE/element)
- [iconfont](http://www.iconfont.cn/)
以及最主流和易用的前端开发技术栈，十分方便开发和维护：
- [ES6](http://es6.ruanyifeng.com/#docs/intro)
- [Node.js](https://nodejs.org/en/about/)
- [Webpack](https://webpack.js.org/)
- [Eslint](https://eslint.org/)
- [Babel](http://babeljs.io/)
- [Mock.js](http://mockjs.com/)
它内置了动态路由，权限验证，提炼了典型的业务模型，提供了丰富的功能组件，它可以帮助你快速搭建企业级中后台产品原型。
<p align="center">
<img width="900" src="https://wpimg.wallstcn.com/a5894c1b-f6af-456e-82df-1151da0839bf.png">
</p>
## 特点和内置功能
```
- 登录 / 注销
- 菜单资源管理
- 用户角色管理
- 角色权限管理
- 操作审计日志
- 配置数据字典
- 权限验证
- 页面权限
- 指令权限
- 二步登录
- 全局功能
- 国际化多语言
- 多种动态换肤
- 动态侧边栏（支持多级路由嵌套）
- 动态面包屑
- 快捷导航(标签页)
- Svg Sprite 图标(iconfont)
- 本地mock数据
- Screenfull全屏
- 自适应收缩侧边栏
- 多环境发布
- dev sit stage prod
- 编辑器
- 富文本
- Markdown
- JSON 等多格式
- Excel
- 导出excel
- 导出zip
- 导入excel
- 前端可视化excel
- 表格
- 动态表格
- 拖拽表格
- 树形表格
- 内联编辑
- 错误页面
- 401
- 404
- 組件
- 头像上传
- 返回顶部
- 拖拽Dialog
- 拖拽看板
- 列表拖拽
- SplitPane
- Dropzone
- Sticky
- CountTo
- 综合实例
- 错误日志
- Dashboard
- 引导页
- Echarts 图表
- Clipboard(剪贴复制)
```
## 浏览器兼容性
 |  |  |  |  |  | 
:---: | :---: | :---: | :---: | :---: | :---: | :---:
✔ | ✔ | ✔ | 10+ ✔ | ✔ | ✔ | ✔
## 技术支持和资料
### 1. vue-element-admin
- [在线访问](http://panjiachen.github.io/vue-element-admin)
- [使用文档](https://panjiachen.github.io/vue-element-admin-site/zh/)
- [Gitter 讨论组](https://gitter.im/vue-element-admin/discuss)
- [Wiki](https://github.com/PanJiaChen/vue-element-admin/wiki)
- [Gitee](https://panjiachen.gitee.io/vue-element-admin/) 国内用户
- 作者提供的 **[圈子](https://jianshiapp.com/circles/1209)** ，或者加入[qq 群](https://github.com/PanJiaChen/vue-element-admin/issues/602)
### 2.element-ui
- [组件文档](http://element-cn.eleme.io/#/zh-CN/component/installation)
- [Github](https://github.com/ElemeFE/element)
### 3.vue
- [官方文档](https://cn.vuejs.org/)
- [Router](https://router.vuejs.org/)
- [vuex](https://vuex.vuejs.org/)
### 4.webpack
- [官方文档](https://webpack.js.org/)
- [中文翻译](https://www.webpackjs.com/)
### 5.Mock.js
- [官方文档](https://github.com/nuysoft/Mock/wiki)
### 6.配套教程
- [手摸手，带你用 vue 撸后台 系列一(基础篇)](https://juejin.im/post/59097cd7a22b9d0065fb61d2)
- [手摸手，带你用 vue 撸后台 系列二(登录权限篇)](https://juejin.im/post/591aa14f570c35006961acac)
- [手摸手，带你用 vue 撸后台 系列三 (实战篇)](https://juejin.im/post/593121aa0ce4630057f70d35)
- [手摸手，带你用 vue 撸后台 系列四(vueAdmin 一个极简的后台基础模板)](https://juejin.im/post/595b4d776fb9a06bbe7dba56)
- [手摸手，带你封装一个 vue component](https://segmentfault.com/a/1190000009090836)
- [手摸手，带你优雅的使用 icon](https://juejin.im/post/59bb864b5188257e7a427c09)
- [手摸手，带你用合理的姿势使用 webpack4（上）](https://juejin.im/post/5b56909a518825195f499806)
- [手摸手，带你用合理的姿势使用 webpack4（下）](https://juejin.im/post/5b5d6d6f6fb9a04fea58aabc)
## 依赖的关键组件及版本
| 名称 | 版本 |
| -------- | -----: |
| element-ui | 2.4.6 |
| vue | 2.5.17 |
| vue-router | 3.0.1 |
| vuex | 3.0.1 |
| vue-i18n | 7.3.2 |
| axios | 0.18.0 |
| babel-core | 6.26.3 |
| babel-loader | 7.1.5 |
| css-loader | 1.0.0 |
| eslint | 4.19.1 |
| eslint-plugin-vue | 4.7.1 |
| postcss-loader | 2.1.6 |
| sass-loader | 7.0.3 |
| svg-sprite-loader | 3.8.0 |
| uglifyjs-webpack-plugin | 1.2.7 |
| vue-loader | 15.3.0 |
| vue-style-loader | 4.1.2 |
| vue-template-compiler | 2.5.17 |
| webpack | 4.16.5 |
| webpack-cli | 3.1.0 |
| webpack-dev-server | 3.1.5 |
## Online Demo
[在线 Demo](http://panjiachen.github.io/vue-element-admin)
## 更多信息
请参考 [使用文档](https://panjiachen.github.io/vue-element-admin-site/zh/)
## License
[MIT](https://github.com/PanJiaChen/vue-element-admin/blob/master/LICENSE)
## 特别鸣谢
- PanJiaChen
# LoginDemoUi
| 24.879808 | 652 | 0.656812 | yue_Hant | 0.51032 |
da94c9d5b31a5ce6fb04d33a8c4d366919742a4b | 833 | md | Markdown | README.md | keloli/Kaggle | 99f1e815c6fcc91e6e557b0834bd8ab035b121d4 | [
"MIT"
] | null | null | null | README.md | keloli/Kaggle | 99f1e815c6fcc91e6e557b0834bd8ab035b121d4 | [
"MIT"
] | null | null | null | README.md | keloli/Kaggle | 99f1e815c6fcc91e6e557b0834bd8ab035b121d4 | [
"MIT"
] | null | null | null | # Overview
This repository is bulit for recording [my kaggle competition](https://www.kaggle.com/keloli1).
# Directory
|Kaggle Competitions|Code|Brief Description|
|-----|--------|-----------|
|[DogsVSCats](https://www.kaggle.com/c/dogs-vs-cats)| [DogsVSCats@github](https://github.com/keloli/Kaggle/tree/master/DogsVSCats)| A binary classification problem to classify dogs and cats pictures|
|[IEEECameras](https://www.kaggle.com/c/sp-society-camera-model-identification)| [IEEECameras@github](https://github.com/keloli/Kaggle/tree/master/IEEECameras) | Identify from which camera an image was taken ( ten categories ) |
| [DataScienceBowl2018](https://www.kaggle.com/c/data-science-bowl-2018/overview) | [DataScienceBowl2018@github](https://github.com/keloli/Kaggle/tree/master/DataScienceBowl2018) |step1: nuclei detect |
| 83.3 | 228 | 0.752701 | yue_Hant | 0.710333 |
da95216024be303fbc55aa3373a214adf9390043 | 2,135 | md | Markdown | _posts/2010-09-29-4266.md | TkTech/skins.tkte.ch | 458838013820531bc47d899f920916ef8c37542d | [
"MIT"
] | 1 | 2020-11-20T20:39:54.000Z | 2020-11-20T20:39:54.000Z | _posts/2010-09-29-4266.md | TkTech/skins.tkte.ch | 458838013820531bc47d899f920916ef8c37542d | [
"MIT"
] | null | null | null | _posts/2010-09-29-4266.md | TkTech/skins.tkte.ch | 458838013820531bc47d899f920916ef8c37542d | [
"MIT"
] | null | null | null | ---
title: >
Tintin
layout: post
permalink: /view/4266
votes: 0
preview: "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACUAAAAgCAIAAAAaMSbnAAAABnRSTlMA/wD/AP5AXyvrAAABZElEQVRIiWP8//8fAxwsyWeNm/x7AkKAtYDh96JchpiJDMSASUzYxfMQVjAi28fKxPR7US6aYta4yb///WMgBhBhH4oKTMtwCZIN0F3EGjcZTiIzaGUf3DcQm6jrOQYGBhasolS3hoB9ZHpOiLB6HCmKZoDRZ9VzNKEtYZIQQTgDGWwOFUfm+q5+SZJ9WPzHwojOoCLAYp/HyudoDNraR1NA9/SCzMFMHRCwJUwSzkYp3xkYGBkRLiZGO5b0iR9QmD6Hu/9YNv9sQ2hmr8JuB5IaBoaJuKSI0Y5SfiJ7HAUsJqogJUY7in04wxbFfzgBMdpR2hOLbPSxqo87cpEY+4jRjpLf449exsqmIkCxb6G1LtwaZDat7KODlVjKz4XWuljZtLKPpoDu9QNyfkAuDJEBWpmJ0ywitKPk99+/fhFjLi5AjPYBDc/8tBCsiibOWkOMWcRoR+0fsWD37u8/RMUfMdoBjN2k9VMbOpsAAAAASUVORK5CYII="
---
<dl class="side-by-side">
<dt>Preview</dt>
<dd>
<img class="preview" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACUAAAAgCAIAAAAaMSbnAAAABnRSTlMA/wD/AP5AXyvrAAABZElEQVRIiWP8//8fAxwsyWeNm/x7AkKAtYDh96JchpiJDMSASUzYxfMQVjAi28fKxPR7US6aYta4yb///WMgBhBhH4oKTMtwCZIN0F3EGjcZTiIzaGUf3DcQm6jrOQYGBhasolS3hoB9ZHpOiLB6HCmKZoDRZ9VzNKEtYZIQQTgDGWwOFUfm+q5+SZJ9WPzHwojOoCLAYp/HyudoDNraR1NA9/SCzMFMHRCwJUwSzkYp3xkYGBkRLiZGO5b0iR9QmD6Hu/9YNv9sQ2hmr8JuB5IaBoaJuKSI0Y5SfiJ7HAUsJqogJUY7in04wxbFfzgBMdpR2hOLbPSxqo87cpEY+4jRjpLf449exsqmIkCxb6G1LtwaZDat7KODlVjKz4XWuljZtLKPpoDu9QNyfkAuDJEBWpmJ0ywitKPk99+/fhFjLi5AjPYBDc/8tBCsiibOWkOMWcRoR+0fsWD37u8/RMUfMdoBjN2k9VMbOpsAAAAASUVORK5CYII=">
</dd>
<dt>Original</dt>
<dd>
<img class="preview" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEAAAAAgCAYAAACinX6EAAABCElEQVR42u2YwQ3CMAxFjeg6TMAKnNiBI+zCCIgbi7FDOQRSKVLimoDrJEpSR3qqStWo//FBBjBXMCLu5ygAIEW64vurABWgAlSAClABKiAacNjAhAsVnAsF/p1i4X3sjTF+cMx0rZCAbEta8a4FuHcfH2evddsAovLkR6ILAS6If+RA7dGEAEbIrw0QoAIqWMFgcNvvAi6nY8CvweLweIrg7p9g8FIBKmDVAnBgLvYh7Bcjfjj/nLpm75HKSiF0JoBqwRIBfkAcNlVbsgjgSigRorgAjoRuBay+AbUISPCPkjaANQdwab4Br3E0EppvQO0CEvzajINHXS65K5pdwLD9jKUCWm/AG7ZePqNpPqY8AAAAAElFTkSuQmCC">
</dd>
<dt>Title</dt>
<dd>Tintin</dd>
<dt>Description</dt>
<dd>The young detective star of the famous French cartoon series, The Adventures of Tintin</dd>
<dt>Added By</dt>
<dd>Popengton</dd>
<dt>Added On</dt>
<dd>2010-09-29</dd>
<dt>Votes</dt>
<dd>0</dd>
</dl>
| 71.166667 | 630 | 0.886651 | yue_Hant | 0.635406 |
da9600a8f9d8bed8f19a5a3116cd2bc3ea347e45 | 862 | md | Markdown | README.md | Open-Dataplatform/utils-databricks | 6baf62e098b7f27b6a900147b934da3e07e63777 | [
"MIT"
] | null | null | null | README.md | Open-Dataplatform/utils-databricks | 6baf62e098b7f27b6a900147b934da3e07e63777 | [
"MIT"
] | null | null | null | README.md | Open-Dataplatform/utils-databricks | 6baf62e098b7f27b6a900147b934da3e07e63777 | [
"MIT"
] | null | null | null | # utils-databricks
## Releasing a new version
For releasing new versions, see [this thorough guide](https://py-pkgs.org/07-releasing-versioning.html).
In simple terms, follow these steps:
1. Merge your bug fixes or new features into the main branch (multiple commits to main since the last version are okay).
2. Bump up the version in setup.cfg.
3. Add, commit, and push the changes.
4. Add a tag with `git tag -a <new_version_number> -m "<message>"`. (An example could be `git tag -a v1.1.0 -m "Version 1.1.0"`).
5. Push the tag with `git push origin --tags`.
Make sure to go through the next section after updating the version.
## Updating the template
After you released a new version, make sure to update the version tag in the beginning of transformation_template.ipynb.
Also make sure that all the used functions are still working in the new version. | 45.368421 | 129 | 0.75406 | eng_Latn | 0.99253 |
da961f01cf2e6e06b1a503d97b9e3e6b65e46cf9 | 774 | md | Markdown | _posts/2016-10-23-siemens-iot-hackathon-ekim-2016.md | polatengin/polatengin.github.io | c5180803a4adfd2427a05c9b51f74e261d772d11 | [
"MIT"
] | 18 | 2017-06-17T05:49:44.000Z | 2022-02-23T21:54:10.000Z | _posts/2016-10-23-siemens-iot-hackathon-ekim-2016.md | polatengin/polatengin.github.io | c5180803a4adfd2427a05c9b51f74e261d772d11 | [
"MIT"
] | 7 | 2017-06-17T05:39:56.000Z | 2021-01-04T21:29:43.000Z | _posts/2016-10-23-siemens-iot-hackathon-ekim-2016.md | polatengin/polatengin.github.io | c5180803a4adfd2427a05c9b51f74e261d772d11 | [
"MIT"
] | 5 | 2017-09-27T12:31:02.000Z | 2019-08-05T01:28:27.000Z | ---
layout: post
title: "Siemens IoT Hackathon, Ekim 2016"
date: 2016-10-23 11:50
author: engin.polat
comments: true
category: [Azure]
tags: [azure, etkinliklerim, hackathon, iot, seminer]
---
**Siemens Hackathon** Yarışması, her yıl farklı teknik konulara odaklanması ve yılda bir kere düzenlenmesi planlanan bir yarışma. Bu yıl potansiyel mucitler tarafından ele alınmak üzere belirlenen konu <a href="http://www.siemens.com.tr/endustri40" target="_blank" rel="noopener">Endüstri 4.0</a>
Bu yıl *22 Ekim 2016* tarihinde *İstanbul*'da gerçekleşen etkinlikte ben de **Nesnelerin Interneti** ve **Azure Bulut Bilişim** konularındaki seanslarda konuşmacı olarak görev aldım.
<img class="lazy img-responsive" data-src="/assets/uploads/2016/10/siements-iot-hackathon.jpg" />
| 48.375 | 296 | 0.771318 | tur_Latn | 0.998105 |
da975a732928093702896438c5f5bce30aefaaff | 91 | md | Markdown | README.md | agausmann/detach | 05f4b01153c86936c3a63cfd70c991b8bed4591d | [
"BSD-2-Clause"
] | 3 | 2022-03-05T07:34:26.000Z | 2022-03-07T20:06:49.000Z | README.md | agausmann/detach | 05f4b01153c86936c3a63cfd70c991b8bed4591d | [
"BSD-2-Clause"
] | null | null | null | README.md | agausmann/detach | 05f4b01153c86936c3a63cfd70c991b8bed4591d | [
"BSD-2-Clause"
] | null | null | null | # fork & detach
Bootstrapping into a new software ecosystem that is wholly mine to shape.
| 22.75 | 73 | 0.78022 | eng_Latn | 0.999732 |
da97c9fed6345f40632f7a1b741a94a8ab51fb80 | 1,832 | md | Markdown | doc/LiteOS_Kernel_Developer_Guide_en/overview-28.md | dw5/LiteOS | e2a3ceab3499de45f1b1b133bd52c8d39726ac15 | [
"BSD-3-Clause"
] | null | null | null | doc/LiteOS_Kernel_Developer_Guide_en/overview-28.md | dw5/LiteOS | e2a3ceab3499de45f1b1b133bd52c8d39726ac15 | [
"BSD-3-Clause"
] | null | null | null | doc/LiteOS_Kernel_Developer_Guide_en/overview-28.md | dw5/LiteOS | e2a3ceab3499de45f1b1b133bd52c8d39726ac15 | [
"BSD-3-Clause"
] | null | null | null | # Overview<a name="EN-US_TOPIC_0311018420"></a>
## Basic Concepts<a name="en-us_topic_0175230625_section46769130155416"></a>
A mutual exclusion \(mutex\) is a special binary semaphore designed to grant a task exclusive use of common resources. In addition, the mutex can resolve the priority inversion problem of semaphores.
At a given point in time, a mutex is either locked or unlocked. When a task holds a mutex, the mutex is locked and the task has exclusive ownership of the mutex. When the task releases the mutex, the mutex is unlocked and the task loses exclusive ownership of the mutex. While a task has exclusive ownership of a mutex, other tasks are unable to acquire or release the mutex.
The mutex provided by Huawei LiteOS has the following features:
- Solve the priority inversion problem using the priority inheritance algorithm.
- In the scenario where multiple tasks are blocked and wait for the same lock, the task priority-based waiting mode and FIFO mode are supported.
## Operation Mechanism<a name="en-us_topic_0175230625_section5106159142616"></a>
In a multi-task environment, multiple tasks may battle for the same common resource. If a common resource is not shareable, it must be used exclusively by a particular task. How does the mutex work to avoid the conflict?
When a task accesses a non-shareable common resource, the mutex is locked. Other tasks are blocked from accessing the resource until the task releases the mutex. In this way, only one task accesses the non-shareable common resource at a given point in time, which ensures the integrity of the non-shareable common resources.
**Figure 1** Working principle of a mutex<a name="en-us_topic_0175230625_fig25049494142655"></a>
| 79.652174 | 376 | 0.783297 | eng_Latn | 0.99776 |
da9821c60f51458303738d10a8a833f290da165f | 158 | md | Markdown | README.md | ebi-yade/docker-compose-sandbox | b52cec6f75fa423ceb7260802e8c15c344743bf7 | [
"MIT"
] | null | null | null | README.md | ebi-yade/docker-compose-sandbox | b52cec6f75fa423ceb7260802e8c15c344743bf7 | [
"MIT"
] | null | null | null | README.md | ebi-yade/docker-compose-sandbox | b52cec6f75fa423ceb7260802e8c15c344743bf7 | [
"MIT"
] | null | null | null | # docker-compose-sandbox
A sandbox repository for Docker Compose
## Reference
- [Compose file - Docker Docs](https://docs.docker.com/compose/compose-file/)
| 22.571429 | 77 | 0.759494 | yue_Hant | 0.83411 |
da9839241e31ee9e82253058dc3b394a3168a116 | 136 | md | Markdown | README.md | adyavanapalli/AzureDevOpsAgent | c62ab5c401fb85c8d76be257cc5c039d26601e25 | [
"MIT"
] | null | null | null | README.md | adyavanapalli/AzureDevOpsAgent | c62ab5c401fb85c8d76be257cc5c039d26601e25 | [
"MIT"
] | null | null | null | README.md | adyavanapalli/AzureDevOpsAgent | c62ab5c401fb85c8d76be257cc5c039d26601e25 | [
"MIT"
] | null | null | null | # Azure DevOps Agent
Provides a template for creating an Azure DevOps Self-hosted Linux Agent on
Azure with a system managed identity.
| 27.2 | 75 | 0.808824 | eng_Latn | 0.983862 |
da9981b68d7771d84bcb696403730cf55fa8a586 | 828 | md | Markdown | README.md | CermakM/devconf-2019 | 297778a3f8325c3060833e533ebf8eb29e2445b9 | [
"MIT"
] | null | null | null | README.md | CermakM/devconf-2019 | 297778a3f8325c3060833e533ebf8eb29e2445b9 | [
"MIT"
] | null | null | null | README.md | CermakM/devconf-2019 | 297778a3f8325c3060833e533ebf8eb29e2445b9 | [
"MIT"
] | null | null | null | # Let's play with Brno data
Outline:
> Have you heard of the term Open Data? Did you know that Brno provides Open Data?
Do you know how to access them, how to handle them? How to properly visualize data and draw conclusions?
And actually... what is the use of it?
> Let’s talk Open Data!
This site has been made for the purposes of the talk / presentation. The code is freely available and licensed under open license.
The sole purpose of this effort is to popularize Open Data, show the good and the bad about them and advertise usage of R, which in my opinion is quite underrated language with immense potential.
The whole site has been deployed using [netlify](https://app.netlify.com/) and is available on https://devconf-brno-data.netlify.com/.
This talk takes part on [DevConf.cz](https://devconf.info/en) 2019.
| 48.705882 | 195 | 0.763285 | eng_Latn | 0.999339 |
da9a7cce5172fd20994585a6145c4a96a38c8d78 | 230 | md | Markdown | Elevator/README.md | haojie06/BedrockPlugins | b8ded5216128e6ae7accac32e75d1ea0d251f8d4 | [
"MIT"
] | 28 | 2019-06-10T15:52:22.000Z | 2020-01-30T18:33:56.000Z | Elevator/README.md | DeeRenjie/BedrockPlugins | 5c08d8a839542c4c146263562f6ed982e803b6f6 | [
"MIT"
] | 1 | 2019-08-21T17:47:44.000Z | 2019-08-21T17:47:44.000Z | Elevator/README.md | haojie06/BedrockPlugins | b8ded5216128e6ae7accac32e75d1ea0d251f8d4 | [
"MIT"
] | 6 | 2019-07-14T07:54:35.000Z | 2019-12-01T12:31:54.000Z | # Elevator （方块）电梯插件
目前支持StoneServer1.12 **使用插件前请先更新服务端（重新运行install.sh）**
此插件用于实现java版铁块电梯的效果，当玩家站在铁块上时，右键方块传送至上方的铁块之上，左键方块传送至下方的铁块之上。
可以修改脚本中的两个变量，它们分别是：
- eBlockName 作为电梯方块的方块名
- maxUpDis 最大检测距离，默认上下十五格
插件已打包 Elevator.tgz | 28.75 | 61 | 0.813043 | yue_Hant | 0.513428 |
da9ad8bf548a47547923c1881217fe3eecad88e3 | 4,681 | md | Markdown | docs/vs-2015/code-quality/enhancing-code-quality-with-team-project-check-in-policies.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/code-quality/enhancing-code-quality-with-team-project-check-in-policies.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/code-quality/enhancing-code-quality-with-team-project-check-in-policies.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Zlepšení kvality kódu pomocí zásady vracení se změnami projektu týmu | Dokumentace Microsoftu
ms.date: 11/15/2016
ms.prod: visual-studio-dev14
ms.technology: vs-ide-code-analysis
ms.topic: conceptual
helpviewer_keywords:
- code quality, using check-in policies
- team-based development, enhancing code quality
ms.assetid: 0ab72c33-148a-4a8a-a7bf-046995514c84
caps.latest.revision: 27
author: gewarren
ms.author: gewarren
manager: wpickett
ms.openlocfilehash: 86aac26819e86455c8ab5c3676c8198bbb482e43
ms.sourcegitcommit: 08fc78516f1107b83f46e2401888df4868bb1e40
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 05/15/2019
ms.locfileid: "65697199"
---
# <a name="enhancing-code-quality-with-team-project-check-in-policies"></a>Zvýšení kvality kódu použitím zásad vracení se změnami týmového projektu
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
Při použití Team Foundation verze ovládacího prvku (TFVC), můžete vytvořit zásady vrácení se změnami pro týmové projekty. k vynucení postupů, které vedou k efektivnější vývoj skupiny a lepší kód. Zásady vrácení se změnami jsou pravidla, která jsou nastavena na úrovni týmového projektu a vynucena na vývojových prostředích před kódu může být vráceny se změnami.
Můžete zadat tyto týmového projektu vrácení se změnami zásady:
- **Sestaví**: Vyžaduje, poškození sestavení, které byly vytvořeny během sestavení musí být opravena dříve než nové vrácení se změnami.
- **Komentáře sady změn**: Vyžaduje, aby uživatelé zadat komentáře při vrácení se změnami.
- **Analýza kódu**: Vyžaduje spuštění analýzy kódu před vrácení se změnami.
- **Pracovní položky**: Vyžaduje, aby jeden nebo více pracovních položek přidružené vložením změn.
> [!IMPORTANT]
> Použití zásad vrácení se změnami, musíte být připojeni k [!INCLUDE[vststfsLong](../includes/vststfslong-md.md)].
## <a name="common-tasks"></a>Obecné úlohy
|Úloha|Podpůrný obsah|
|----------|------------------------|
|**Vytvoření a použití zásad vrácení se změnami:** Můžete vytvořit zásady vrácení se změnami s použitím nastavení týmového projektu [!INCLUDE[esprscc](../includes/esprscc-md.md)].|[Nastavení a vynucení bran kvality](https://msdn.microsoft.com/library/bdc5666e-6cf0-45b2-a0a1-133c3f61e852)|
|**Vytvoření a použití zásad vrácení se změnami analýzy kódu:** Můžete si vybrat z standardní sadu pravidel analýzy kódu, nebo můžete vytvořit vlastní sadu.|[Vytváření a používání zásad vrácení se změnami Analýzy kódu](../code-quality/creating-and-using-code-analysis-check-in-policies.md)|
## <a name="related-tasks"></a>Související úlohy
|Úloha|Podpůrný obsah|
|----------|------------------------|
|**Nastavení vývojového prostředí:** Předtím, než můžete vytvářet nebo upravovat kód, musíte nastavit vaše vývojová a testovací prostředí s použitím příslušného zdrojového kódu. Při práci s databázemi, musí mít také přístup k jejich offline verzi.|[Nastavení vývojových prostředích](https://msdn.microsoft.com/7b686610-d379-4ca0-9608-73ef0e576e3a)|
|**Použití analýzy kódu v procesu vývoje:** Členové týmu spouštějí analýzu kódu na svých vývojových prostředích. V sadě Visual Studio, vývojáři nakonfigurovat a spustit nastavují spuštění analýzu kódu pro projekty s odděleným kódem, zobrazit a analyzovat problémy nalezené spuštěními a vytvářejí pracovní položky pro upozornění.|[Analýza kvality aplikace](../code-quality/analyzing-application-quality-by-using-code-analysis-tools.md)|
|**Vytvoření a spuštění testování částí:** Testování částí poskytuje vývojářům a testerům rychlý způsob vyhledávání logických chyb v rámci metod tříd v C#, Visual Basic .NET a projekty v jazyce C++. Test jednotky můžete vytvořit jen jednou a spustit každé změně zdrojového kódu je zajistit, že k zavedení žádných chyb.|[Testování částí kódu](../test/unit-test-your-code.md)|
|**Sledování pracovních položek a vad:** Pracovní položky můžete použít ke sledování a spravování práce a informace o týmovém projektu. Pracovní položka je databáze záznam, který [!INCLUDE[esprfound](../includes/esprfound-md.md)] používá ke sledování přiřazení a postupu práce. Můžete použít různé typy pracovních položek pro sledování různých typů činnosti, jako jsou požadavky zákazníka, chyb produktů a vývojářských úloh.|[Sledování práce a správa pracovního postupu [Přesměrováno]](https://msdn.microsoft.com/d2d8637d-0ef8-4ca3-874e-a04713344032)|
## <a name="external-resources"></a>Externí zdroje
### <a name="guidance"></a>Doprovodné materiály
[Testování pro nepřetržité dodávky s Visual Studio 2012 – kapitola 2: Testování částí: Testování uvnitř](http://go.microsoft.com/fwlink/?LinkID=255188)
| 78.016667 | 561 | 0.775048 | ces_Latn | 0.999742 |
da9b2ede108d4e67c839c88edfd4ecae9d98cf9d | 590 | md | Markdown | README.md | LlOlNiYi/Project-J | 52dda2c53d71c772272ad193106ed407b6b491e9 | [
"FSFAP"
] | null | null | null | README.md | LlOlNiYi/Project-J | 52dda2c53d71c772272ad193106ed407b6b491e9 | [
"FSFAP"
] | null | null | null | README.md | LlOlNiYi/Project-J | 52dda2c53d71c772272ad193106ed407b6b491e9 | [
"FSFAP"
] | null | null | null | # Project J
**© 2021 NiYi, All rights reserved.reserved.**
**목적**
대화하는 카톡봇 만들기. 점점 기능 추가 및 상위 버전으로 업데이트/최적화되는 프로젝트에요.
**기타 설명**
Project J이기 때문에 봇들의 첫글자는 모두 J인 거에요.
**라이선스**
소스코드를 참고/사용하기 위해서는 무조건 개발자(저작권자)에게 허락을 받아야해요.
허락을 받기 위해서는 아래의 양식을 참고하여 아래 메일로 보내면 되는 거에요.
______
**양식**
사용자 이름 :
봇 이름 :
사용 장소(범위) :
사용 목적 :
금전적인 이득을 취하려는 경우의 별도 세부 기재사항 :
한마디 :
______
**메일주소**
[email protected]
**사용 가이드라인**
가이드라인과 라이선스 충돌시 가이드라인이 우선 적용됩니다.
금전적인 이익을 취하기 위해서는 허락을 받아야 하며, 사용 범위에 따라 금전적인 대가를 지불해야 할 수도 있습니다.
이유는 딱히 설명할 필요 없을거라고 생각합니다.
사용 범위에 따라 개발자(저작권자)가 고려하여 허가를 해주지 않을 수 있습니다.
| 14.047619 | 64 | 0.664407 | kor_Hang | 1.00001 |
da9c102166abd47c21e9da8044a7d02a2984a7d5 | 109 | md | Markdown | _sample-content/weekly-log.md | Steellow/mtsknn.fi | f608d138c4cbed2472cab0b0d5cf4be63c5d5531 | [
"MIT"
] | null | null | null | _sample-content/weekly-log.md | Steellow/mtsknn.fi | f608d138c4cbed2472cab0b0d5cf4be63c5d5531 | [
"MIT"
] | null | null | null | _sample-content/weekly-log.md | Steellow/mtsknn.fi | f608d138c4cbed2472cab0b0d5cf4be63c5d5531 | [
"MIT"
] | null | null | null | ---
layout: weekly-log
title: Weekly log
intro: |
Highlights of what I'm working on.
Updated weekly.
---
| 13.625 | 36 | 0.678899 | eng_Latn | 0.98071 |
da9d7a9a672cad7290a844004b794d5c111f4c95 | 202 | md | Markdown | README.md | Gaboik/NiceClip2 | 7bd8a05166d4c2d2de808bfc0b35552007c13a60 | [
"MIT"
] | 1 | 2019-08-18T01:43:16.000Z | 2019-08-18T01:43:16.000Z | README.md | Gaboik/NiceClip2 | 7bd8a05166d4c2d2de808bfc0b35552007c13a60 | [
"MIT"
] | null | null | null | README.md | Gaboik/NiceClip2 | 7bd8a05166d4c2d2de808bfc0b35552007c13a60 | [
"MIT"
] | null | null | null | NiceClip is a convenient, 'no bs' clipboard monitor for Windows.
This is the root of the project, for documentation about NiceClip2 specifically, see the README file inside the `./NiceClip2` directory
| 50.5 | 135 | 0.79703 | eng_Latn | 0.993732 |
da9e760e4851f0e2f18d1cdcf4313d495cc664ab | 8,705 | md | Markdown | security-updates/WindowsRightsManagementServices/omisindeladeteccindeserviciosdeactivedirectory.md | MicrosoftDocs/security-updates.es-es | 2cbea821ba8fb6380fae446aa1ab055c56baed24 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T20:15:55.000Z | 2020-05-19T20:15:55.000Z | security-updates/WindowsRightsManagementServices/omisindeladeteccindeserviciosdeactivedirectory.md | MicrosoftDocs/security-updates.es-es | 2cbea821ba8fb6380fae446aa1ab055c56baed24 | [
"CC-BY-4.0",
"MIT"
] | 296 | 2017-11-15T00:01:45.000Z | 2018-11-29T00:18:04.000Z | security-updates/WindowsRightsManagementServices/omisindeladeteccindeserviciosdeactivedirectory.md | MicrosoftDocs/security-updates.es-es | 2cbea821ba8fb6380fae446aa1ab055c56baed24 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-18T13:14:06.000Z | 2021-11-18T13:14:06.000Z | ---
TOCTitle: Omisión de la detección de servicios de Active Directory
Title: Omisión de la detección de servicios de Active Directory
ms:assetid: '9d97e7fb-5b05-4853-ad7b-6cc82b9729f0'
ms:contentKeyID: 18127944
ms:mtpsurl: 'https://technet.microsoft.com/es-es/library/Cc747614(v=WS.10)'
---
Omisión de la detección de servicios de Active Directory
========================================================
Los servicios y los clientes de RMS descubren las ubicaciones de servicio con la búsqueda en primer lugar en el Registro local. Si determinadas claves del Registro no tienen un valor, los servicios y los clientes de RMS buscan en Active Directory el punto de conexión de servicio (SCP). Esto significa que puede anular la configuración de descubrimiento de Active Directory predeterminado si escribe determinadas claves en el Registro del servidor o del cliente.
> [!NOTE]
> Si el clúster raíz de RMS está configurado de un modo que el SCP no se publique en Active Directory, puede usar estas claves para dirigir los clientes de RMS a la ubicación correcta.
En esta sección se describen las entradas del Registro y se proporcionan detalles acerca de cómo crearlas.
Anulación del descubrimiento de servicios para la subinscripción de clúster de sólo licencias
---------------------------------------------------------------------------------------------
Si está realizando el aprovisionamiento de un clúster de sólo licencias y desea subinscribirlo con un clúster raíz distinto del clúster raíz que ha implementado en el bosque de Active Directory del clúster de sólo licencias, debe anular el descubrimiento de los servicios de subinscripción y de certificación de cuentas.
#### Descripciones de las entradas del Registro
Las siguientes entradas del Registro se usan para anular los servicios de subinscripción y de certificación de cuentas.
- **SubEnrollmentURL**. Esta entrada especifica la ruta de acceso al clúster raíz que el servidor de licencias usa al solicitar su certificado de emisor de licencias.
- **GicURL**. Esta entrada especifica la ruta de acceso al servicio de certificación de cuentas para este clúster de sólo licencias.
#### Detalles de la entrada
En los equipos que ejecutan la versión de 32 bits de Windows Server 2003, la ruta de acceso completa a la subclave del Registro de las entradas de descubrimiento de servicios para la subinscripción de clúster de sólo licencias es:
**HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\DRMS\\1.0**
En los equipos que ejecutan la versión de 64 bits de Windows Server 2003, la ruta de acceso completa a la subclave del Registro de las entradas de descubrimiento de servicios para la subinscripción de clúster de sólo licencias es:
**HKEY\_LOCAL\_MACHINE\\SoftwareWOW6432Node\\Microsoft\\DRMS\\1.0**
En la siguiente tabla se enumeran las entradas que puede agregar para anular el descubrimiento de servicios.
###
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th style="border:1px solid black;" >Nombre</th>
<th style="border:1px solid black;" >Tipo</th>
<th style="border:1px solid black;" >valor</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="border:1px solid black;">SubEnrollmentURL</td>
<td style="border:1px solid black;">Cadena</td>
<td style="border:1px solid black;">http(o https)://<em>nombre_de_servidor</em>/_wmcs/certification/subenrollservice.asmx</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">GicURL</td>
<td style="border:1px solid black;">Cadena</td>
<td style="border:1px solid black;">http(o https)://<em>nombre_de_servidor</em>/_wmcs/certification/certification.asmx</td>
</tr>
</tbody>
</table>
Anulación del descubrimiento de servicios en el cliente para la publicación
---------------------------------------------------------------------------
Si los usuarios van a publicar contenido desde sus equipos, puede anular las ubicaciones de los servidores usadas para la publicación según la topología empleada en su empresa. Las ubicaciones de los servidores usados para la publicación normalmente las descubre el cliente con Active Directory. Al agregar las claves del Registro adecuadas en los equipos cliente, los clientes omitirán estos métodos y, en su lugar, usarán las direcciones URL que especifique en el valor de entrada del Registro.
> [!NOTE]
> Las anulaciones enumeradas en estas secciones se deben crear como claves y no como entradas individuales. El valor de estas claves se debe crear en la entrada predeterminada de cada clave.
#### Descripciones de las claves del Registro
Las siguientes claves del Registro se pueden usar para anular el descubrimiento automático del clúster de RMS.
- **Activation**. Esta clave del Registro define la dirección URL del servicio de activación de equipo. Si ejecuta el cliente de RMS con Service Pack 1 o posterior, esta entrada del Registro ya no se usa.
- **EnterprisePublishing**. Esta clave del Registro define la dirección URL de una instalación de RMS que desea que use este cliente para las solicitudes de licencia.
- **CloudPublishing**. Esta clave del Registro define la dirección URL del servicio de licencias hospedado por Microsoft que se puede usar si el cliente no tiene acceso a una instalación de RMS pero sí a Internet.
#### Detalles de la clave
La ruta de acceso completa a la subclave del Registro para las entradas de descubrimiento de servicios en el cliente es:
**HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\MSDRM\\ServiceLocation\\**
En la siguiente tabla se enumeran las claves del Registro que puede agregar en un equipo cliente de RMS para anular el descubrimiento de servicios.
###
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th style="border:1px solid black;" >Nombre</th>
<th style="border:1px solid black;" >Tipo</th>
<th style="border:1px solid black;" >valor</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="border:1px solid black;">Activation</td>
<td style="border:1px solid black;">Cadena</td>
<td style="border:1px solid black;">http(o https)://<em>nombre_del_clúster_RMS</em>/_wmcs/Certification donde <em>nombre_del_clúster_RMS</em> es el nombre del clúster de RMS.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">EnterprisePublishing</td>
<td style="border:1px solid black;">Cadena</td>
<td style="border:1px solid black;">http(o https)://<em>nombre_del_clúster_RMS</em>/_wmcs/Licensing donde <em>nombre_del_clúster_RMS</em> es el nombre del clúster de RMS.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">CloudPublishing</td>
<td style="border:1px solid black;">Cadena</td>
<td style="border:1px solid black;">http(o https)://<em>nombre_de_clúster_completo</em>/_wmcs/Licensing donde <em>nombre_de_clúster_completo</em> es el nombre de dominio completo del clúster de RMS.</td>
</tr>
</tbody>
</table>
Se recomienda implementar estas claves del Registro con Systems Management Server o Directiva de grupo para garantizar que todos los clientes de la empresa usan los servidores de publicación correctos.
> [!CAUTION]
> La modificación incorrecta del Registro puede dañar gravemente el sistema. Antes de realizar cambios en el Registro, debe hacer una copia de seguridad de los datos de valor que contenga el equipo.
Se puede usar un archivo de Registro de ejemplo (.reg) para importar las claves del Registro adecuadas en cada servidor del clúster de RMS.
**Para importar las claves del Registro adecuadas en cada servidor del clúster de RMS**
1. Copie el siguiente archivo de Registro de ejemplo en Bloc de notas.
`Windows Registry Editor Version 5.00`
`[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDRM\ServiceLocation]`
`[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDRM\ServiceLocation\Activation]`
`@="http://<RMS_cluster_name>/_wmcs/certification"`
`[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDRM\ServiceLocation\EnterprisePublishing]`
`@="http://<RMS_cluster_name>/_wmcs/licensing"`
2. Reemplace <RMS\_cluster\_name> por el nombre de su clúster de RMS.
3. Guarde el archivo con la extensión de nombre de archivo .reg.
4. Haga doble clic en el nombre del archivo en el Explorador de Windows.
5. Si aparece el cuadro de diálogo **Control de cuentas de usuario**, confirme que la acción que muestra es la que desea y, a continuación, haga clic en **Continuar**.. Cuando aparezca una solicitud en la que se le pregunta si desea agregar la información al Registro, haga clic en **Sí**.
| 53.404908 | 496 | 0.745089 | spa_Latn | 0.980703 |
daa144e50983b6c2d1735c0c0ecd8e5b3a78b49c | 27,382 | md | Markdown | 2017/2017-12-23.md | skyofthinking/node-github-trending | 8b2088f85ff1708aaa4b743ccaa5c291774484be | [
"Apache-2.0"
] | 3 | 2018-01-13T14:56:01.000Z | 2021-03-20T18:38:17.000Z | 2017/2017-12-23.md | skyofthinking/node-github-trending | 8b2088f85ff1708aaa4b743ccaa5c291774484be | [
"Apache-2.0"
] | null | null | null | 2017/2017-12-23.md | skyofthinking/node-github-trending | 8b2088f85ff1708aaa4b743ccaa5c291774484be | [
"Apache-2.0"
] | 3 | 2018-01-13T14:56:02.000Z | 2021-03-20T18:38:19.000Z | ### 2017-12-23
#### java
* [guardianproject / haven](https://github.com/guardianproject/haven):Haven is for people who need a way to protect their personal spaces and possessions without compromising their own privacy, through an Android app and on-device sensors
* [JustKiddingBaby / FragmentRigger](https://github.com/JustKiddingBaby/FragmentRigger):💥A powerful library to manage Fragments.（一个强大的Fragment管理框架）
* [yu199195 / myth](https://github.com/yu199195/myth):基于消息队列解决分布式事务框架
* [YoKeyword / Fragmentation](https://github.com/YoKeyword/Fragmentation):A powerful library that manage Fragment for Android!
* [scwang90 / SmartRefreshLayout](https://github.com/scwang90/SmartRefreshLayout):🔥下拉刷新、上拉加载、二级刷新、淘宝二楼、RefreshLayout、OverScroll，Android智能下拉刷新框架，支持越界回弹、越界拖动，具有极强的扩展性，集成了几十种炫酷的Header和 Footer。
* [CarGuo / GSYVideoPlayer](https://github.com/CarGuo/GSYVideoPlayer):视频播放器（IJKplayer），HTTPS支持，支持弹幕，支持滤镜、水印、gif截图，支持基本的拖动，声音、亮度调节，支持边播边缓存，支持视频本身自带rotation的旋转（90,270之类），重力旋转与手动旋转的同步支持，支持列表播放 ，直接添加控件为封面，列表全屏动画，视频加载速度，列表小窗口支持拖动，5.0的过场效果，调整比例，多分辨率切换，支持切换播放器，进度条小窗口预览，其他一些小动画效果，rtsp、concat、mpeg。简书:
* [JetBrains / kotlin](https://github.com/JetBrains/kotlin):The Kotlin Programming Language
* [yu199195 / happylifeplat-transaction](https://github.com/yu199195/happylifeplat-transaction):分布式事务框架（二阶段提交+本地补偿方案）
* [alibaba / dubbo](https://github.com/alibaba/dubbo):Dubbo is a high-performance, java based, open source RPC framework
* [crazyandcoder / citypicker](https://github.com/crazyandcoder/citypicker):citypicker城市选择器，支持仿iOS滚轮实现，一级或者三级列表展示方式。
* [google / guava](https://github.com/google/guava):Google Core Libraries for Java
* [elastic / elasticsearch](https://github.com/elastic/elasticsearch):Open Source, Distributed, RESTful Search Engine
* [spring-projects / spring-boot](https://github.com/spring-projects/spring-boot):Spring Boot
* [apache / incubator-skywalking](https://github.com/apache/incubator-skywalking):A distributed tracing system, and APM ( Application Performance Monitoring )
* [yu199195 / happylifeplat-tcc](https://github.com/yu199195/happylifeplat-tcc):TCC分布式事务框架(try,confirm,cancel)
* [kekingcn / file-online-preview](https://github.com/kekingcn/file-online-preview):使用spring boot打造文件文档在线预览项目解决方案，支持doc、docx、ppt、pptx、xls、xlsx、zip、rar、以及众多类文本如txt、html、xml、java、properties、mp3、mp4、sql、js、md、json、conf、ini、vue、php、py、bat、gitignore等文件在线预览
* [didi / VirtualAPK](https://github.com/didi/VirtualAPK):A powerful and lightweight plugin framework for Android
* [shuzheng / zheng](https://github.com/shuzheng/zheng):基于Spring+SpringMVC+Mybatis分布式敏捷开发系统架构，提供整套公共微服务服务模块：集中权限管理（单点登录）、内容管理、支付中心、用户管理（支持第三方登录）、微信平台、存储系统、配置中心、日志分析、任务和通知等，支持服务治理、监控和追踪，努力为中小型企业打造全方位J2EE企业级开发解决方案。
* [airbnb / lottie-android](https://github.com/airbnb/lottie-android):Render After Effects animations natively on Android and iOS, Web, and React Native
* [alibaba / fastjson](https://github.com/alibaba/fastjson):🚄 A fast JSON parser/generator for Java
* [PhilJay / MPAndroidChart](https://github.com/PhilJay/MPAndroidChart):A powerful 🚀 Android chart view / graph view library, supporting line- bar- pie- radar- bubble- and candlestick charts as well as scaling, dragging and animations.
* [square / okhttp](https://github.com/square/okhttp):An HTTP+HTTP/2 client for Android and Java applications.
* [Wechat-Group / weixin-java-tools](https://github.com/Wechat-Group/weixin-java-tools):微信支付、开放平台、小程序、企业号和公众号 Java SDK开发工具包
* [Blankj / AndroidUtilCode](https://github.com/Blankj/AndroidUtilCode):🔥 Android developers should collect the following utils(updating).
* [QMUI / QMUI_Android](https://github.com/QMUI/QMUI_Android):提高 Android UI 开发效率的 UI 库
#### vue
* [PanJiaChen / vue-element-admin](https://github.com/PanJiaChen/vue-element-admin):vue2.0 admin / a management system template http://panjiachen.github.io/vue-element-admin
* [ElemeFE / element](https://github.com/ElemeFE/element):A Vue.js 2.0 UI Toolkit for Web
* [iview / iview](https://github.com/iview/iview):A high quality UI Toolkit built on Vue.js 2.0
* [ElemeFE / mint-ui](https://github.com/ElemeFE/mint-ui):Mobile UI elements for Vue.js
* [airyland / vux](https://github.com/airyland/vux):Mobile UI Components based on Vue & WeUI
* [epicmaxco / epic-spinners](https://github.com/epicmaxco/epic-spinners):Easy to use css spinners collection with vue.js integration
* [salomonelli / best-resume-ever](https://github.com/salomonelli/best-resume-ever):👔 💼 Build fast 🚀 and easy multiple beautiful resumes and create your best CV ever! Made with Vue and LESS.
* [rafaelpimpa / buefy](https://github.com/rafaelpimpa/buefy):Lightweight UI components for Vue.js based on Bulma
* [quasarframework / quasar](https://github.com/quasarframework/quasar):Quasar Framework
* [DivanteLtd / vue-storefront](https://github.com/DivanteLtd/vue-storefront):Vue.js Storefront - PWA for eCommerce. 100% offline, platform agnostic, headless, Magento2 supported. Always Open Source, MIT license. Join us as contributor ([email protected]).
* [epicmaxco / vuestic-admin](https://github.com/epicmaxco/vuestic-admin):Vue.js admin dashboard
* [vuematerial / vue-material](https://github.com/vuematerial/vue-material):Material design for Vue.js
* [vue-bulma / vue-admin](https://github.com/vue-bulma/vue-admin):Vue Admin Panel Framework, Powered by Vue 2.0 and Bulma 0.3
* [Mynameisfwk / vivo-shop](https://github.com/Mynameisfwk/vivo-shop):基于vue2.0实现的vivo移动端商城(vue+vue-ruoter+vue-resource+webpack)
* [XBT1 / v-contextmenu](https://github.com/XBT1/v-contextmenu):🖱 ContextMenu based on Vue 2.0
* [potato4d / nuxt-firebase-sns-example](https://github.com/potato4d/nuxt-firebase-sns-example):Nuxt & Firebase SSR, RTDB, Google Auth SNS Example.
* [fpass / fpass](https://github.com/fpass/fpass):You only need a unique password to securely manage all website passwords
* [alexmacarthur / wp-vue](https://github.com/alexmacarthur/wp-vue):A simple Vue blog template that displays posts from a WordPress REST API endpoint.
* [uikit / uikit-site](https://github.com/uikit/uikit-site):The UIkit documentation and website
* [vuetifyjs / docs](https://github.com/vuetifyjs/docs):Documentation for Vuetify.js
* [jkchao / vue-admin](https://github.com/jkchao/vue-admin):vue-admin
* [lian-yue / vue-upload-component](https://github.com/lian-yue/vue-upload-component):Vue.js file upload component, Multi-file upload, Upload directory, Drag upload, Drag the directory, Upload multiple files at the same time, html4 (IE 9), `PUT` method, Customize the filter
* [simple-uploader / vue-uploader](https://github.com/simple-uploader/vue-uploader):A Vue.js upload component powered by simple-uploader.js
* [zymseo / VueNode](https://github.com/zymseo/VueNode):VueNode是一套基于Vue全家桶（Vue2.x + Vue-router2.x + Vuex + Vue-cli）+ Node（Express框架）的前后端分离项目，附带完整数据库和将NodeJs替换为PHP或JAVA等其他后端语言的方法！
* [warpcgd / vue-concise-slider](https://github.com/warpcgd/vue-concise-slider):vue-concise-slider,A simple vue sliding component
#### kotlin
* [tipsy / github-profile-summary](https://github.com/tipsy/github-profile-summary):Tool for visualizing GitHub profiles
* [git-xuhao / KotlinMvp](https://github.com/git-xuhao/KotlinMvp):🔥 基于Kotlin+MVP+Retrofit+RxJava+Glide 等架构实现的短视频类的APP练手项目，UI 简约风格，代码详细注释，欢迎 Star or Fork！
* [heimashi / kotlin_tips](https://github.com/heimashi/kotlin_tips):用Kotlin去提高生产力:汇总Kotlin相对于Java的优势，以及怎么用Kotlin去简洁、务实、高效、安全开发的Tips
* [SchibstedSpain / Barista](https://github.com/SchibstedSpain/Barista):☕️ The guy who serves a great Espresso
* [JetBrains / kotlin-native](https://github.com/JetBrains/kotlin-native):Kotlin/Native infrastructure
* [Kotlin / anko](https://github.com/Kotlin/anko):Pleasant Android application development
* [google / flexbox-layout](https://github.com/google/flexbox-layout):Flexbox for Android
* [KotlinBy / awesome-kotlin](https://github.com/KotlinBy/awesome-kotlin):A curated list of awesome Kotlin related stuff Inspired by awesome-java.
* [dbacinski / Design-Patterns-In-Kotlin](https://github.com/dbacinski/Design-Patterns-In-Kotlin):Design Patterns implemented in Kotlin
* [ansman / kotshi](https://github.com/ansman/kotshi):An annotations processor that generates Moshi adapters from immutable Kotlin data classes.
* [po10cio / TimeLineView](https://github.com/po10cio/TimeLineView):A simple Timeline View that demonstrates the power of ConstraintLayout and RecyclerView. No drawing, just plug in and play.
* [ktorio / ktor](https://github.com/ktorio/ktor):Framework for quickly creating connected applications in Kotlin with minimal effort
* [Kotlin / kotlinx.coroutines](https://github.com/Kotlin/kotlinx.coroutines):Libraries built upon Kotlin coroutines
* [Ekito / koin](https://github.com/Ekito/koin):KOIN - a concise and pragmatic dependency injection framework for Kotlin
* [gradle / kotlin-dsl](https://github.com/gradle/kotlin-dsl):Kotlin language support for Gradle build scripts
* [arturbosch / detekt](https://github.com/arturbosch/detekt):Static code analysis for Kotlin
* [edvin / tornadofx](https://github.com/edvin/tornadofx):Lightweight JavaFX Framework for Kotlin
* [ssseasonnn / RxDownload](https://github.com/ssseasonnn/RxDownload):A multi-threaded download tool written with RxJava and Kotlin
* [MyEtherWallet / ethereum-lists](https://github.com/MyEtherWallet/ethereum-lists):A repository for maintaining lists of things like malicious URLs, fake token addresses, and so forth. We love lists.
* [LibreShift / red-moon](https://github.com/LibreShift/red-moon):An android screen filter app for night time phone use
* [JetBrains / teamcity-rest-client](https://github.com/JetBrains/teamcity-rest-client):Client for TeamCity REST API written in Kotlin
* [Kotlin / kotlin-koans-edu](https://github.com/Kotlin/kotlin-koans-edu):Kotlin Koans for Educational Plugin and WebDemo
* [BijoySingh / Material-Notes-Android-App](https://github.com/BijoySingh/Material-Notes-Android-App):Simple yet powerful rich note taking android application, with a lot of flexibilty of usage
* [alibaba / p3c](https://github.com/alibaba/p3c):Alibaba Java Coding Guidelines pmd implements and IDE plugin
* [googlesamples / android-topeka](https://github.com/googlesamples/android-topeka):A fun to play quiz that showcases material design on Android
#### javascript
* [danilowoz / react-content-loader](https://github.com/danilowoz/react-content-loader):React component that uses SVG to create a collection of loaders which simulates the structure of the content that will be loaded, similar to Facebook cards loaders.
* [Chalarangelo / 30-seconds-of-code](https://github.com/Chalarangelo/30-seconds-of-code):Curated collection of useful Javascript snippets that you can understand in 30 seconds or less.
* [parcel-bundler / parcel](https://github.com/parcel-bundler/parcel):📦🚀 Blazing fast, zero configuration web application bundler
* [google / boardgame.io](https://github.com/google/boardgame.io):State management and more for turn based games.
* [facebook / Docusaurus](https://github.com/facebook/Docusaurus):Easy to maintain open source documentation websites.
* [gulzar1996 / auto-like-my-gf-insta-pic](https://github.com/gulzar1996/auto-like-my-gf-insta-pic):Bot to automatically like your friend's Instagram post and notify you on Slack
* [GoogleChrome / puppeteer](https://github.com/GoogleChrome/puppeteer):Headless Chrome Node API
* [vuejs / vue](https://github.com/vuejs/vue):A progressive, incrementally-adoptable JavaScript framework for building UI on the web.
* [facebook / react](https://github.com/facebook/react):A declarative, efficient, and flexible JavaScript library for building user interfaces.
* [Popmotion / popmotion](https://github.com/Popmotion/popmotion):The JavaScript motion engine. Create unique animations and interactions with tweens, physics and input tracking.
* [WeiChiaChang / domain-cli](https://github.com/WeiChiaChang/domain-cli):Search domain names if registered or not in terminal
* [axios / axios](https://github.com/axios/axios):Promise based HTTP client for the browser and node.js
* [treshugart / react-shade](https://github.com/treshugart/react-shade):Use the native Web Component Shadow DOM API as React components in a super-duper-Reacty way (i.e. declaratively).
* [ccxt / ccxt](https://github.com/ccxt/ccxt):A JavaScript / Python / PHP cryptocurrency trading library with support for more than 90 bitcoin/altcoin exchanges
* [facebookincubator / create-react-app](https://github.com/facebookincubator/create-react-app):Create React apps with no build configuration.
* [prettier / prettier](https://github.com/prettier/prettier):Prettier is an opinionated code formatter.
* [cristianbote / hnpwa-vanilla](https://github.com/cristianbote/hnpwa-vanilla):Hacker News PWA implemented using no framework just javascript
* [thedaviddias / Front-End-Checklist](https://github.com/thedaviddias/Front-End-Checklist):🗂 The perfect Front-End Checklist for modern websites and meticulous developers
* [alibaba / beidou](https://github.com/alibaba/beidou):Isomorphic framework for server-rendered React apps
* [facebook / react-native](https://github.com/facebook/react-native):A framework for building native apps with React.
* [nodejs / node](https://github.com/nodejs/node):Node.js JavaScript runtime ✨🐢🚀✨
* [mrdoob / three.js](https://github.com/mrdoob/three.js):JavaScript 3D library.
* [oliver-moran / jimp](https://github.com/oliver-moran/jimp):An image processing library written entirely in JavaScript for Node, with zero external or native dependencies.
* [airbnb / javascript](https://github.com/airbnb/javascript):JavaScript Style Guide
* [airbnb / react-sketchapp](https://github.com/airbnb/react-sketchapp):render React components to Sketch ⚛️💎
#### css
* [twbs / bootstrap](https://github.com/twbs/bootstrap):The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.
* [danielquinn / paperless](https://github.com/danielquinn/paperless):Scan, index, and archive all of your paper documents
* [codrops / CSSGlitchEffect](https://github.com/codrops/CSSGlitchEffect):An experimental glitch effect powered by CSS animations and the clip-path property. Inspired by the technique seen on the speakers page of the 404 conference.
* [overdodactyl / ShadowFox](https://github.com/overdodactyl/ShadowFox):A universal dark theme for Firefox
* [jgthms / bulma](https://github.com/jgthms/bulma):Modern CSS framework based on Flexbox
* [barryclark / jekyll-now](https://github.com/barryclark/jekyll-now):Build a Jekyll blog in minutes, without touching the command line.
* [Codeinwp / themeisle-icons](https://github.com/Codeinwp/themeisle-icons):A free icon font from ThemeIsle
* [cristijora / vue-light-bootstrap-dashboard](https://github.com/cristijora/vue-light-bootstrap-dashboard):Vue light bootstrap dashboard
* [iissnan / hexo-theme-next](https://github.com/iissnan/hexo-theme-next):Elegant theme for Hexo.
* [necolas / normalize.css](https://github.com/necolas/normalize.css):A collection of HTML element and attribute style-normalizations
* [tailwindcss / tailwindcss](https://github.com/tailwindcss/tailwindcss):A utility-first CSS framework for rapid UI development.
* [mmistakes / minimal-mistakes](https://github.com/mmistakes/minimal-mistakes):📐 A flexible two-column Jekyll theme. Perfect for personal sites, blogs, and portfolios hosted on GitHub or your own server.
* [wearethescenery / ether](https://github.com/wearethescenery/ether):Examples, samples and tools for Ether usage
* [haskellcamargo / pragmatic-functional-javascript](https://github.com/haskellcamargo/pragmatic-functional-javascript):The "Pragmatic Functional JavaScript" book
* [hzlshen / ionic-JD](https://github.com/hzlshen/ionic-JD):ionic3+angular4写的京东商城demo
* [benbrignell / principles.design](https://github.com/benbrignell/principles.design):Work in progress repository of design principles and methods.
* [sahat / hackathon-starter](https://github.com/sahat/hackathon-starter):A boilerplate for Node.js web applications
* [tachyons-css / tachyons](https://github.com/tachyons-css/tachyons):Functional css for humans
* [Chalarangelo / mini.css](https://github.com/Chalarangelo/mini.css):A minimal, responsive, style-agnostic CSS framework!
* [Microsoft / TypeScript-Node-Starter](https://github.com/Microsoft/TypeScript-Node-Starter):A starter template for TypeScript and Node with a detailed README describing how to use the two together.
* [uikit / uikit](https://github.com/uikit/uikit):A lightweight and modular front-end framework for developing fast and powerful web interfaces
* [ryanoasis / nerd-fonts](https://github.com/ryanoasis/nerd-fonts):🔡 Iconic font aggregator, collection, and patcher: 39 patched fonts (87k+ variations). Includes popular glyph collections such as Font Awesome & fonts such as Hack
* [melonjs / melonJS](https://github.com/melonjs/melonJS):a fresh & lightweight javascript game engine
* [samcm / synclounge](https://github.com/samcm/synclounge):Enjoy Plex with your friends. In Sync. Together.
* [BretFisher / udemy-docker-mastery](https://github.com/BretFisher/udemy-docker-mastery):Udemy Course to build, compose, deploy, and manage containers from local development to high-availability in the cloud
#### objective-c
* [pojala / termipal](https://github.com/pojala/termipal):Instant, native micro-GUIs for shell scripts and command line apps
* [BradLarson / GPUImage](https://github.com/BradLarson/GPUImage):An open source iOS framework for GPU-based image and video processing
* [kevinzhow / PNChart](https://github.com/kevinzhow/PNChart):A simple and beautiful chart lib used in Piner and CoinsMan for iOS
* [madaoCN / NonBaseClass-MVVM-ReactiveObjc](https://github.com/madaoCN/NonBaseClass-MVVM-ReactiveObjc):iOS架构实践干货：AOP来避免基类继承 + MVVM + ReactiveObjC + JLRoutes组件化，代码比较完善，可以直接拿来写项目，大家按需自取，能顺手给个Star那也是极好的
* [bolan9999 / react-native-largelist](https://github.com/bolan9999/react-native-largelist):A best performance large list component for React Native.
* [zhenglibao / FlexLib](https://github.com/zhenglibao/FlexLib):An obj-c layout framework for iOS based on flexbox model, easy and powerful. You can write iOS ui even faster than web & android. Trash xib & storyboard, autolayout & masonry now. :)
* [ChenYilong / CYLTabBarController](https://github.com/ChenYilong/CYLTabBarController):【中国特色 TabBar】最低只需传两个数组即可完成主流App框架搭建【iPhoneX supported】
* [wangrui460 / WRNavigationBar](https://github.com/wangrui460/WRNavigationBar):超简单！！！ 一行代码设置状态栏、导航栏按钮、标题、颜色、透明度，移动等 WRNavigationBar which allows you to change NavigationBar's appearance dynamically
* [weidian-inc / hera](https://github.com/weidian-inc/hera):A framework for running WeChat applet
* [rs / SDWebImage](https://github.com/rs/SDWebImage):Asynchronous image downloader with cache support as a UIImageView category
* [expo / expo](https://github.com/expo/expo):Expo iOS/Android Client
* [hackiftekhar / IQKeyboardManager](https://github.com/hackiftekhar/IQKeyboardManager):Codeless drop-in universal library allows to prevent issues of keyboard sliding up and cover UITextField/UITextView. Neither need to write any code nor any setup required and much more.
* [ChangbaDevs / KTVHTTPCache](https://github.com/ChangbaDevs/KTVHTTPCache):A media cache framework from Changba iOS Team.
* [airbnb / lottie-ios](https://github.com/airbnb/lottie-ios):An iOS library to natively render After Effects vector animations
* [TextureGroup / Texture](https://github.com/TextureGroup/Texture):Smooth asynchronous user interfaces for iOS apps.
* [JungHsu / PingDynamicSynthesizer](https://github.com/JungHsu/PingDynamicSynthesizer):Auto synthesize setter getter methods for category
* [leerme / LYPersonTool](https://github.com/leerme/LYPersonTool):
* [yuantiku / YTKNetwork](https://github.com/yuantiku/YTKNetwork):YTKNetwork is a high level request util based on AFNetworking.
* [lyb5834 / YBPopupMenu](https://github.com/lyb5834/YBPopupMenu):快速集成popupMenu
* [twitter / twitter-kit-ios](https://github.com/twitter/twitter-kit-ios):Twitter Kit is a native SDK to include Twitter content inside mobile apps.
* [WenchaoD / FSCalendar](https://github.com/WenchaoD/FSCalendar):A fully customizable iOS calendar library, compatible with Objective-C and Swift
* [banchichen / TZImagePickerController](https://github.com/banchichen/TZImagePickerController):一个支持多选、选原图和视频的图片选择器，同时有预览、裁剪功能，支持iOS6+。 A clone of UIImagePickerController, support picking multiple photos、original photo、video, also allow preview photo and video, support iOS6+
* [Instagram / IGListKit](https://github.com/Instagram/IGListKit):A data-driven UICollectionView framework for building fast and flexible lists.
* [react-community / react-native-maps](https://github.com/react-community/react-native-maps):React Native Mapview component for iOS + Android
* [material-components / material-components-ios](https://github.com/material-components/material-components-ios):Modular and customizable Material Design UI components for iOS
#### swift
* [SoySauceLab / CollectionKit](https://github.com/SoySauceLab/CollectionKit):A modern Swift framework for building reusable data-driven collection components.
* [efremidze / Shiny](https://github.com/efremidze/Shiny):Iridescent Effect View (inspired by Apple Pay Cash)
* [Ramotion / fluid-slider](https://github.com/Ramotion/fluid-slider):💧 A slider widget with a popup bubble displaying the precise value selected. Made by @Ramotion
* [shadowsocks / ShadowsocksX-NG](https://github.com/shadowsocks/ShadowsocksX-NG):Next Generation of ShadowsocksX
* [azonov / ExpandableTable](https://github.com/azonov/ExpandableTable):AZExpandable is a lightweight proxy for UITableView to expand cells.
* [kateinoigakukun / IBLinter](https://github.com/kateinoigakukun/IBLinter):A linter tool for Interface Builder
* [tiagomartinho / Reminders](https://github.com/tiagomartinho/Reminders):An iOS application written in Swift to demonstrate how to implement a Clean Architecture in iOS
* [xcodeswift / sake](https://github.com/xcodeswift/sake):A make-like build utility for Swift.
* [lkzhao / Hero](https://github.com/lkzhao/Hero):Elegant transition library for iOS & tvOS
* [dkhamsing / open-source-ios-apps](https://github.com/dkhamsing/open-source-ios-apps):📱 Collaborative List of Open-Source iOS Apps
* [vsouza / awesome-ios](https://github.com/vsouza/awesome-ios):A curated list of awesome iOS ecosystem, including Objective-C and Swift Projects
* [Minecodecraft / 50DaysOfSwift](https://github.com/Minecodecraft/50DaysOfSwift):One demo a day, keep coding for 50 days with Swift. The struggle of a growing iOS developer
* [Alamofire / Alamofire](https://github.com/Alamofire/Alamofire):Elegant HTTP Networking in Swift
* [kean / Nuke](https://github.com/kean/Nuke):A powerful image loading and caching framework
* [raywenderlich / swift-algorithm-club](https://github.com/raywenderlich/swift-algorithm-club):Algorithms and data structures in Swift, with explanations!
* [kishikawakatsumi / KeychainAccess](https://github.com/kishikawakatsumi/KeychainAccess):Simple Swift wrapper for Keychain that works on iOS, watchOS, tvOS and macOS.
* [danielgindi / Charts](https://github.com/danielgindi/Charts):Beautiful charts for iOS/tvOS/OSX! The Apple side of the crossplatform MPAndroidChart.
* [onevcat / Kingfisher](https://github.com/onevcat/Kingfisher):A lightweight, pure-Swift library for downloading and caching images from the web.
* [vapor / vapor](https://github.com/vapor/vapor):💧 A server-side Swift web framework.
* [airbnb / Lona](https://github.com/airbnb/Lona):A tool for defining design systems and using them to generate cross-platform UI code, Sketch files, images, and other artifacts.
* [ReactiveX / RxSwift](https://github.com/ReactiveX/RxSwift):Reactive Programming in Swift
* [matteocrippa / awesome-swift](https://github.com/matteocrippa/awesome-swift):A collaborative list of awesome Swift libraries and resources. Feel free to contribute!
* [olucurious / Awesome-ARKit](https://github.com/olucurious/Awesome-ARKit):A curated list of awesome ARKit projects and resources. Feel free to contribute!
* [kizitonwose / CountryPickerView](https://github.com/kizitonwose/CountryPickerView):A simple, customizable view for efficiently collecting country information in iOS apps.
* [ReactiveCocoa / ReactiveCocoa](https://github.com/ReactiveCocoa/ReactiveCocoa):Streams of values over time
#### html
* [NetSPI / SQLInjectionWiki](https://github.com/NetSPI/SQLInjectionWiki):A wiki focusing on aggregating and documenting various SQL injection methods
* [jaywcjlove / awesome-mac](https://github.com/jaywcjlove/awesome-mac): This repo is a collection of awesome Mac applications and tools for developers and designers.
* [froala / design-blocks](https://github.com/froala/design-blocks):A set of 170+ Bootstrap based design blocks ready to be used to create clean modern websites.
* [carlos8f / zenbot](https://github.com/carlos8f/zenbot):Zenbot is a command-line cryptocurrency trading bot using Node.js and MongoDB.
* [CoderSavior / dynamic-tags-cloud](https://github.com/CoderSavior/dynamic-tags-cloud):动态的热门标签云效果，看起来还不错的
* [facebookresearch / fastText](https://github.com/facebookresearch/fastText):Library for fast text representation and classification.
* [almasaeed2010 / AdminLTE](https://github.com/almasaeed2010/AdminLTE):AdminLTE - Free Premium Admin control Panel Theme Based On Bootstrap 3.x
* [google / styleguide](https://github.com/google/styleguide):Style guides for Google-originated open-source projects
* [google / gson](https://github.com/google/gson):A Java serialization/deserialization library to convert Java Objects into JSON and back
* [apachecn / MachineLearning](https://github.com/apachecn/MachineLearning):Machine Learning in Action（机器学习实战）
* [octocat / Spoon-Knife](https://github.com/octocat/Spoon-Knife):This repo is for demonstration purposes only.
* [portainer / portainer](https://github.com/portainer/portainer):Simple management UI for Docker
* [ropenscilabs / skimr](https://github.com/ropenscilabs/skimr):A frictionless, pipeable approach to dealing with summary statistics
* [TeamStuQ / skill-map](https://github.com/TeamStuQ/skill-map):程序员技能图谱
* [symfony / web-profiler-bundle](https://github.com/symfony/web-profiler-bundle):[READ-ONLY] Subtree split of the Symfony WebPofiler Bundle
* [chjj / marked](https://github.com/chjj/marked):A markdown parser and compiler. Built for speed.
* [ElemeFE / node-interview](https://github.com/ElemeFE/node-interview):How to pass the Node.js interview of ElemeFE.
* [puikinsh / gentelella](https://github.com/puikinsh/gentelella):Free Bootstrap 3 Admin Template
* [chenhuiYj / demos](https://github.com/chenhuiYj/demos):个人练习的一些demo，简单的小实例
* [Chia-Network / website](https://github.com/Chia-Network/website):Corporate web site
* [tomayac / pwa-feature-detector](https://github.com/tomayac/pwa-feature-detector):Progressive Web App 🕵️ Feature Detector
* [mrholek / CoreUI-Free-Bootstrap-Admin-Template](https://github.com/mrholek/CoreUI-Free-Bootstrap-Admin-Template):CoreUI is free bootstrap admin template with Angular2, AngularJS, React.js & Vue.js support.
* [anders94 / blockchain-demo](https://github.com/anders94/blockchain-demo):A web-based demonstration of blockchain concepts.
* [wesbos / JavaScript30](https://github.com/wesbos/JavaScript30):30 Day Vanilla JS Challenge
* [ariya / phantomjs](https://github.com/ariya/phantomjs):Scriptable Headless WebKit
| 125.605505 | 293 | 0.786794 | yue_Hant | 0.273479 |
daa39cb04b0f807ba1210cdda5bdeece926964f3 | 7,537 | md | Markdown | _2018.3.1/02-installing/05-installing.md | tmitchell10/event-streams | aa5552697179e5c9e5e5b0b4745a8f5a667b5d0c | [
"Apache-2.0",
"BSD-3-Clause",
"MIT"
] | 7 | 2018-12-22T09:40:35.000Z | 2021-02-01T05:04:37.000Z | _2018.3.1/02-installing/05-installing.md | tmitchell10/event-streams | aa5552697179e5c9e5e5b0b4745a8f5a667b5d0c | [
"Apache-2.0",
"BSD-3-Clause",
"MIT"
] | 56 | 2018-09-06T15:00:26.000Z | 2021-12-07T18:56:26.000Z | _2018.3.1/02-installing/05-installing.md | tmitchell10/event-streams | aa5552697179e5c9e5e5b0b4745a8f5a667b5d0c | [
"Apache-2.0",
"BSD-3-Clause",
"MIT"
] | 16 | 2018-09-26T15:34:10.000Z | 2022-03-16T14:33:09.000Z | ---
title: "Installing"
excerpt: "Installing IBM Event Streams."
categories: installing
slug: installing
toc: true
---
{{site.data.reuse.long_name}} is the paid-for version intended for enterprise use, and includes full IBM support and additional features such as geo-replication.
You can also install a basic deployment of {{site.data.reuse.short_name}} to [try it out](../trying-out).
## Before you begin
- Ensure you have set up your environment [according to the prerequisites](../prerequisites), including your {{site.data.reuse.icp}} environment.
- Ensure you have [planned for your installation](../planning), such as planning for persistent volumes if required, and creating a ConfigMap for Kafka static configuration.
## Preparing the platform
Prepare your platform for installing {{site.data.reuse.short_name}} as follows.
### Create a namespace
You must use a namespace that is dedicated to your {{site.data.reuse.short_name}} deployment. This is required because {{site.data.reuse.short_name}} uses network security policies to restrict network connections between its internal components.
If you plan to have multiple {{site.data.reuse.short_name}} instances, create namespaces to organize your {{site.data.reuse.long_name}} deployments into, and control user access to them.
You must have the `ibm-restricted-psp` [PodSecurityPolicy](https://ibm.biz/cpkspec-psp) selected for the target namespace.
To create a namespace, you must have the Cluster administrator role. See the {{site.data.reuse.icp}} documentation for more information about [creating namespaces](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.2/user_management/create_project.html).
### Download the archive
Download the {{site.data.reuse.long_name}} installation image file from the IBM Passport Advantage site and make it available in your catalog.
1. Go to [IBM Passport Advantage](https://www.ibm.com/software/passportadvantage/pao_customer.html), and search for "{{site.data.reuse.long_name}}". Download the images related to the part numbers for your platform (for example, the {{site.data.reuse.short_name}} package for the {{site.data.reuse.openshift}} includes `rhel` in the package name).
2. Ensure you [configure your Docker CLI](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.2/manage_images/configuring_docker_cli.html) to access your cluster.
3. Log in to your cluster from the {{site.data.reuse.icp}} CLI and log in to the Docker private image registry:
```
cloudctl login -a https://<cluster_CA_domain>:8443 --skip-ssl-validation
docker login <cluster_CA_domain>:8500
```
**Note:** The default value for the `cluster_CA_domain` parameter is `mycluster.icp`. If necessary add an entry to your system's host file to allow it to be resolved. For more information, see the {{site.data.reuse.icp}} [documentation](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.2/installing/install_entitled_workloads.html).
4. Install the {{site.data.reuse.short_name}} Helm chart by using the compressed image you downloaded from IBM Passport Advantage.\\
`cloudctl catalog load-archive --archive <PPA-image-name.tar.gz>`\\
When the image installation completes successfully, the catalog is updated with the {{site.data.reuse.long_name}} local chart, and the internal Docker repository is populated with the Docker images used by {{site.data.reuse.long_name}}.
## Preparing the repository
Prepare your repository for the installation as follows.
**Note:** Before running `kubectl` commands as instructed in any the following steps, log in to your {{site.data.reuse.icp}} cluster as an administrator by using `cloudctl login`.
### Create an image pull secret
Create an image pull secret for the namespace where you intend to install {{site.data.reuse.short_name}} (this is the namespace created earlier). The secret enables access to the internal Docker repository provided by {{site.data.reuse.icp}}.
To create a secret, use the following command:
`kubectl create secret docker-registry regcred --docker-server=<cluster_CA_domain>:8500 --docker-username=<user-name> --docker-password=<password> --docker-email=<your-email> -n <namespace_for_event_streams>`
For example:
`kubectl create secret docker-registry regcred --docker-server=mycluster.icp:8500 --docker-username=admin --docker-password=admin [email protected] -n event-streams`
For more information about creating image pull secrets, see the {{site.data.reuse.icp}} [documentation](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.1/manage_images/imagepullsecret.html).
### Create an image policy
Create an image policy for the internal Docker repository. The policy enables images to be retrieved during installation.\\
To create an image policy:
1. Create a `.yaml` file with the following content, then replace `<cluster_CA_domain>` with the correct value for your {{site.data.reuse.icp}} environment, and replace the `<namespace_for_event_streams>` value with the name where you intend to install {{site.data.reuse.long_name}} (set as `-n event-streams` in the previous example):
```
apiVersion: securityenforcement.admission.cloud.ibm.com/v1beta1
kind: ImagePolicy
metadata:
name: image-policy
namespace: <namespace_for_event_streams>
spec:
repositories:
- name: docker.io/*
policy: null
- name: <cluster_CA_domain>:8500/*
policy: null
```
2. Run the following command: `kubectl apply -f <filename>.yaml`
For more information about container image security, see the {{site.data.reuse.icp}} [documentation](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.1/manage_images/image_security.html).
## Installing the {{site.data.reuse.short_name}} chart
Install the {{site.data.reuse.short_name}} chart as follows.
1. {{site.data.reuse.icp_ui_login}}\\
Ensure you log in as a user that has the Cluster Administrator role.
2. Click **Catalog** in the top navigation menu.
2. Search for `ibm-eventstreams-prod` and select it from the result. The {{site.data.reuse.long_name}} README is displayed.
3. If you are installing {{site.data.reuse.short_name}} on {{site.data.reuse.icp}} 3.1.1 running on Red Hat Enterprise Linux, [remove AppArmor settings](../../troubleshooting/pods-apparmor-blocked/) in the PodSecurityPolicy to avoid installation issues.
3. Click **Configure**.\\
**Note:** The README includes information about how to install {{site.data.reuse.long_name}} by using the CLI. To use the CLI, follow the instructions in the README instead of clicking **Configure**.
4. Enter a release name that identifies your {{site.data.reuse.short_name}} installation, select the target namespace you created previously, and accept the terms of the license agreement.
5. Expand the **All parameters** section to configure the settings for your installation as described in [configuring](../configuring). Configuration options to consider include setting up persistent storage, external access, and preparing for geo-replication.\\
**Important:** As part of the configuration process, enter the name of the [secret](#preparing-the-repository) you created previously in the [**Image pull secret**](../configuring/#global-install-settings) field.\\
**Note:** Ensure the [**Docker image registry**](../configuring/#global-install-settings) field value does not have a trailing slash, for example: `mycluster.icp:8500/ibmcom`
6. Click **Install**.
7. [Verify your installation](../post-installation/#verifying-your-installation) and consider other post-installation tasks.
| 69.787037 | 347 | 0.773119 | eng_Latn | 0.969661 |
daa3d9f2668cefdb85e519822ef334e68ac8f6aa | 14,700 | md | Markdown | _posts/2017-08-02-8-maneras-de-entretener-a-tu-perro-cuando-estas-en-el-trabajo.md | borders-collies/borders-collies.github.io | 0c5da10b92515445d307478d284004c669d873f7 | [
"MIT"
] | null | null | null | _posts/2017-08-02-8-maneras-de-entretener-a-tu-perro-cuando-estas-en-el-trabajo.md | borders-collies/borders-collies.github.io | 0c5da10b92515445d307478d284004c669d873f7 | [
"MIT"
] | null | null | null | _posts/2017-08-02-8-maneras-de-entretener-a-tu-perro-cuando-estas-en-el-trabajo.md | borders-collies/borders-collies.github.io | 0c5da10b92515445d307478d284004c669d873f7 | [
"MIT"
] | 1 | 2017-12-17T19:14:25.000Z | 2017-12-17T19:14:25.000Z | ---
layout: "post"
title: "8 maneras de entretener a tu perro cuando estás en el trabajo."
date: "2017-08-02 07:00:00"
image: "8-maneras-de-entretener-a-tu-perro-cuando-estas-en-el-trabajo.jpg"
category: "articulos"
tags: "productos"
intro: "Ojalá pudieras quedarte en casa y pasar todo el día con tu perro. O, ojalá pudieras llevar a tu perro al trabajo contigo. Por desgracia a tu jefe no parece que le guste mucho la idea y por eso la mayoría de nosotros inevitablemente..."
description: "Ojalá pudieras quedarte en casa y pasar todo el día con tu perro. O, ojalá pudieras llevar a tu perro al trabajo contigo. Por desgracia a tu jefe no parece que le guste mucho la idea y por eso la mayoría de nosotros inevitablemente tenemos que dejar a nuestros perros en casa solitos mientras vamos a trabajar."
---
Ojalá pudieras quedarte en casa y pasar todo el día con tu perro. O, ojalá pudieras [llevar a tu perro al trabajo](http://www.borders-collies.com/Como-convencer-a-tu-jefe-y-companeros-de-que-te-dejen-llevar-a-tu-perro-al-trabajo/) contigo. Por desgracia a tu jefe no parece que le guste mucho la idea y por eso la mayoría de nosotros inevitablemente tenemos que dejar a nuestros perros en casa solitos mientras vamos a trabajar.
Bueno eso no es tan malo, los perros también necesitan su tiempo solos. Cuando estás en casa, puedes ver cuánto tiempo pasan durmiendo, o tumbados al sol o simplemente echaditos en el sofá. Es sólo saludable que tu perro aprenda a pasar algún tiempo por su cuenta.
Nuestro trabajo es asegurarnos de que proporcionamos a nuestros perros una estimulación mientras estamos fuera y una buena cantidad de tiempo de juego cuando llegamos a casa del trabajo. Si aprendes a entretener a tu perro aburrido mientras estás en el trabajo, tendrás un perro feliz que te saludara con amor después de un largo día.
### ¿Por qué algunos perros son destructivos cuando están solos?
Puedes leer [este artículo anterior](http://www.borders-collies.com/que-hacer-para-que-tu-border-collie-deje-de-morder-todas-tus-cosas/) que escribí acerca de por qué los perros pueden llegar a ser destructivo, pero aquí va un resumen de por qué tu perro puede morder destructivamente todo.
#### 1. Aprendizaje
Los cachorros son muy juguetones e investigadores. Es una parte importante del desarrollo social y una manera importante para que los perros aprendan sobre su ambiente. Es un comportamiento normal para los cachorros para investigar su entorno por olfatear, degustación y masticación.
#### 2. Dientes
Los cachorros tienen alrededor de 2 meses de edad cuando sus dientes de cachorro empiezan a salir. Entre los 4 y 6 meses sus dientes de leche se caen y son reemplazados por los dientes de adultos. Este es el comienzo de la etapa destructiva. Los cachorros, como nosotros cuando somos bebés, muerden para ayudar a sus dientes a pasar por este proceso y para ayudar a aliviar el dolor de dientes y encías.
#### 3. Atención
Algunos perros pueden morder porque reciben atención, incluso atención negativa, cuando lo hacen. Puede que de manera inconsciente estes reforzando ese comportamiento al darle golosinas o hablar con él con el fin de que deje de masticar.
#### 4. Ansiedad
Morder o tener un comportamiento destructivo también puede ser una respuesta a la ansiedad. Los perros que están confinados en áreas donde se sienten inseguros pueden cavar y masticar en un intento de escapar. Los perros que están ansiosos pueden morder un enchufe. Morder puede ayudar a aliviar a un perro la tensión o ansiedad.
#### 5. Salud dental
Es importante para una buena salud de tu perro [mantener sus dientes limpios](http://www.borders-collies.com/nombres-para-border-collie/). Así como nosotros nos cepillamos los dientes, a los perros también debemos cepillarlos y darles snacks para que mantengan los dientes limpios.
#### 6. Ejercita los músculos de la mandíbula
Al igual que corremos o vamos al gimnasio, los perros muerden para ejercitar sus mandíbulas. Morder puede durar meses, incluso años, y el aumento regular y el ejercicio físico puede ayudar a reorientar la necesidad de morder y ser destructivo.
#### 7. Aburrimiento
Un perro solitario o aburrido será más destructivo y masticará por períodos más largos de tiempo. Los perros están buscando maneras de ocupar su tiempo y están buscando cosas que hacer.
#### 8. Practica
Tu perro practicará la mordida. Si no puede encontrar un artículo apropiado para morder usará lo que pueda encontrar en su lugar.
#### 9. Delicioso
Los perros buscarán algo que huela bien, sepa delicioso y que siente bien en su boca. Si les gusta repetirán una otra vez.
#### 10. Obsesión
Los perros pueden desarrollar trastornos obsesivos de morder. Cuando permitimos que los hábitos de nuestros perros progresen hasta el punto de la obsesión, estamos creando un perro muy frustrado e infeliz.
<div class="text-center">
<img src="{{ site.url }}/assets/img/articulos/maneras-de-entretener-a-tu-perro-cuando-estas-en-el-trabajo.jpg" width="500" height="auto" alt="maneras deentretener a tu perro cuando estas en el trabajo">
</div>
### Cómo entretener a un perro aburrido
Es muy importante corregir el aburrimiento en los perros. Tu perro no será feliz o mentalmente sano si está en casa solo durante horas con nada que hacer durante todo el día. La mayor parte del tiempo sólo tenemos que ocupar a nuestros perros, especialmente a los más jóvenes. A medida que tu perro envejece, lo más probable es que tenga menos energía y requiera menos ejercicio.
Busca siempre tiempo para tu perro. Es posible que tengas que levantarse una hora antes, es posible que tengas que coger el coche y llevarlo al parque, es posible que tengas que ponerse botas de agua o coger un paraguas. Solo hazlo. Si no inviertes tiempo para ejercitar a tu perro, tendrás un perro aburrido e infeliz.
Pero ... Sí, te oigo diciendo, no todos somos runners, yo incluida. Si corres, genial, a tu perro le encantará. Si no lo haces o no puedes correr, aquí hay una opción para que tu perro haga ejercicio y queme energía. Mi gran consejo es proporcionar variedad en su ejercicio diario.
#### 1. Pasear por el barrio
Pasear entre 30 y 60 minutos a pie. Puedes variar la caminata entre un buen ritmo y dejar que tu perro huela las flores (y el pis de otros perros). El oler es lo que más le gusta a tu perro. Al dejar que tu perro pase algún tiempo a oler, está activando su mente y le dejas conocer lo que ha estado pasando en el barrio toda la semana.
#### 2. Ir a la playa (o río, o lago)
Seguro que a tu perro le encanta jugar con otros perros, salpicarse en el agua. Nadar y correr sobre la arena realmente quemará ese exceso de energía.
#### 3. Jugar en el parque de perros
El parque de perros permitirá de nuevo la interacción con otros perros, además proporciona variedad con un poco de hierba verde agradable y árboles para explorar. Otra opción es encontrar parajes más tranquilos y llevar contigo una pelota para lanzar. Si tienes un perro de alta energía puedes utilizar una raqueta de tenis o [lanzador de pelota](https://www.amazon.es/s/ref=as_li_ss_tl?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&url=search-alias=pets&field-keywords=lanzador+de+pelotas+para+perros&sprefix=lanzador+,aps,201&crid=3TWCUU0IX65Y4&linkCode=ll2&tag=bordecolli06-21&linkId=3582b5ddf8080acfcf0fd59c659ba368) para tirarla a más distancia.
#### ¿Qué pasa cuando mi perro está en casa solo?
Esta es la siguiente parte del rompecabezas. Después de que tu perro haya dado un buen paseo matutino debe de estar satisfechos durante horas. Un perro generalmente duerme bien durante el día y su mente estará pensando en todos esos olores y pequeñas conversaciones de perro que tuvo en el parque de perros.
Antes de ir a trabajar puedes preparar a tu perro para el resto del día. Aquí están algunas ideas para mantener a tu perro entretenido mientras estás fuera en el trabajo.
#### 1. Juguetes interactivos para perros
Estos no tienen que ser caros, pero se trata de un juguete que crea un desafío para tu perro. Algunos perros son más inteligentes que otros, pero la mayoría de los juguetes interactivos te permitirá ponerlo más difícil para los perros experimentados o más inteligentes.
<div class="text-center">
<img src="{{ site.url }}/assets/img/productos/juegos-interactivo-smart.jpg" width="500" height="auto" alt="Juguetes interactivos para perros">
<a class="button" href="https://www.amazon.es/1-cuenta-juegos-interactivo-juguete-perros/dp/B0045DKZ6M/ref=as_li_ss_tl?s=pet-supplies&ie=UTF8&qid=1501578094&sr=1-5&keywords=juguete+interactivo+para+perros&linkCode=ll1&tag=bordecolli06-21&linkId=f91c01db386c41a25a260c5d2050660f">Comprar en Amazon</a><br>
</div>
#### 2. Kong, juguetes para masticar y rellenar
El Kong es el juguete más popular para dar a tu perro y hay una razón para ello. Sí, el Kong realmente es una gran manera de mantener a tu perro ocupado. Llena el juguete Kong o similar con mantequilla de maní o su comida favorita y dáselo justo antes de salir al trabajo.
<div class="text-center">
<img src="{{ site.url }}/assets/img/productos/kong.jpg" width="500" height="auto" alt="Juguetes interactivos para perros">
<a class="button" href="https://www.amazon.es/Kong-Classic-Extrreme-Black-X-Large/dp/B0002DHNZA/ref=as_li_ss_tl?s=pet-supplies&ie=UTF8&qid=1501581313&sr=1-1&keywords=kong&linkCode=ll1&tag=bordecolli06-21&linkId=6bc0c7a8b868413205b05bd86efac51b">Comprar en Amazon</a><br>
</div>
#### 3. Oculta las golosinas por la casa o el patio
Juega un poco al escondite con tu perro. Esconde sus golosinas favoritas por la casa o el patio y trata de no dejar que tu perro vea donde las pusiste. ¡Utiliza alguna de las galletas casera para perro que hemos compartido con vosotros! Las [galletas de patata dulce](http://www.borders-collies.com/recetas-caseras-para-perros-galletas-de-patata-dulce/),[galletas de plátano y zanahoria](http://www.borders-collies.com/recetas-caseras-para-perros-galletas-de-platano-y-zanahoria/), [Galletas de manzana](http://www.borders-collies.com/recetas-caseras-para-perros-galletas-de-manzana/)
#### 4. Abre las ventanas o la vaya
Un perro puede estar estimulado simplemente viendo lo que está sucediendo en el barrio. Abre las ventanas para que tu perro pueda ver los coches, los pájaros que vuelan alrededor y todos las idas y venidas de tu vecindario. Si tiene sólidas vallas o puertas puedes considerar hacer un agujero para que tu perro puede ver.
<div class="text-center">
<iframe src="https://rcm-eu.amazon-adsystem.com/e/cm?o=30&p=22&l=ur1&category=pets&banner=00S1N256W5CYHCQZ5AG2&f=ifr&linkID=66ceab1cc6f0385fe5f60ea8ba5e3fb1&t=bordecolli06-21&tracking_id=bordecolli06-21" width="250" height="250" scrolling="no" border="0" marginwidth="0" style="border:none;" frameborder="0"></iframe>
</div>
#### 5. Enciende el televisor o la radio
Encender la radio o tele le dará a tu perro algunas voces de fondo para que escuche y piense en los sonidos. También puede ayudar a calmar a tu perro si tiende a ser un poco ansioso o está tenso. Elige un poco de música clásica para calmar a tu perro y proporcionar un ambiente relajante.
#### 6. Organizar quedadas perrunas
Quizás tus amigos o vecinos están en el mismo barco que tú y les toca dejar a sus perros en casa mientras están en el trabajo. Una fantástica manera de ayudarse es compartir los perros y dejarlos juntos durante el día. Los perros juegan, a veces con ferocidad al principio, pero una vez que la emoción ha terminado, se calman y holgazanean durante gran parte del día. Cuando comienzan a sentirse aburridos o destructivos, hay un pequeño amigo allí para jugar.
#### 7. Hacer un mega helado
Un gran juguete interactivo casero? un refrescante helado de hielo. Hay muchas opciones. Hace unas semanas os presentamos el [helado de sandía para perros](http://www.borders-collies.com/recetas-caseras-para-perros-helado-de-sandia/) pero hay más. Por ejemplo llena con agua un envase de helado y mete las chuches preferidas de tu perro. Congela hasta que esté duro. Comprueba el envase de vez en cuando y mueve los convites alrededor de modo que consigan separarse uniformemente dentro del bloque de hielo.
Esto mantendrá a tu perro trabajando duro para liberar las golosinas. Esta es una idea particularmente buena para el verano para mantener a tu perro fresco, aunque el hielo se derrita rápidamente. Si tienes a tu perro en el interior puede que desees probar con un tazón grande para colocar por debajo.
<div class="text-center">
<img src="{{ site.url }}/assets/img/productos/Comedero.jpg" width="500" height="auto" alt="Juguetes interactivos para perros">
<a class="button" href="https://www.amazon.es/Comedero-perros-inoxidable-aprox-2800-ml/dp/B001TNQ0LU/ref=as_li_ss_tl?s=pet-supplies&ie=UTF8&qid=1501595119&sr=1-2&keywords=comedero+perro&linkCode=ll1&tag=bordecolli06-21&linkId=12f20e233219ab2cc0a114ff10460ebb">Comprar en Amazon</a><br>
</div>
#### 8. Ve cambiando los juguetes de tu perro
En lugar de darle todos los juguetes a la vez, dale solo un par y cambialos cada uno o dos días. Esto mantendrá a tu perro interesado e intrigado en los juguetes más tiempo y se emocionará cuando les des juguetes nuevos.
<div class="text-center">
<img src="{{ site.url }}/assets/img/productos/petsafe-busy-buddy.jpg" width="500" height="auto" alt="Juguetes interactivos para perros">
<a class="button" href="https://www.amazon.es/PetSafe-Busy-Buddy-Juguete-mediano/dp/B01ATS8NUQ/ref=as_li_ss_tl?s=pet-supplies&ie=UTF8&qid=1501595189&sr=1-3&keywords=juguete+perro&linkCode=ll1&tag=bordecolli06-21&linkId=5054185067896e4d6ad92d595b49478b">Comprar en Amazon</a><br>
</div>
Un perro aburrido no será un perro feliz. Se convertirá en travieso, destructivo y triste. Es importante entretener a un perro aburrido mientras estás en el trabajo o va a estar fuera de casa por un período prolongado de tiempo.
Pasa tiempo con tu perro cada día y piensa en tu perro antes de salir. Asegúrate de que tu perro tenga suficiente comida, agua, juguetes y de que haya hecho un buen ejercicio o incluso un paseo rápido para aliviar esa energía reprimida.
Un perro feliz y saludable será una alegría.
¿Y tu que haces con tu Border Collie cuando vas al trabajo?
Si quieres compartir tu experiencia cuentanosla en nuestra [página de Facebook](https://www.facebook.com/borderscolliescom/), seguro que ayudas a nuestra comunidad. Compartir es vivir! 😄
Descubre más productos para cuidar a tu Border Collie en <a href="{{ site.url }}/border-collie-productos/"> nuestra sección dedicada a ellos</a>.
Si te ha gustado este artículo compártelo con otros amantes de los Border Collie.
Estamos en contacto
— Sara de borders-collies.com
| 92.45283 | 648 | 0.78585 | spa_Latn | 0.996899 |
daa59936a350d71393106c0537257c71c75c4adb | 2,538 | md | Markdown | docs/src/pages/en/u-menu.md | dieUrbans/uniform | ce6c7f3dbca22738f1d5dcec4d1019e809483748 | [
"MIT"
] | 4 | 2022-02-17T14:19:39.000Z | 2022-03-22T14:32:04.000Z | docs/src/pages/en/u-menu.md | dieUrbans/uniform | ce6c7f3dbca22738f1d5dcec4d1019e809483748 | [
"MIT"
] | 14 | 2022-03-15T14:38:40.000Z | 2022-03-24T08:44:57.000Z | docs/src/pages/en/u-menu.md | dieUrbans/uniform | ce6c7f3dbca22738f1d5dcec4d1019e809483748 | [
"MIT"
] | null | null | null | ---
title: u-menu
description: no description provided
category: Components
menuTitle: Menu
badge: beta
layout: ../../layouts/MainLayout.astro
setup: |
import Uniform from '../../components/Uniform.vue';
import Badge from '../../components/Badge.vue';
import { Markdown } from 'astro/components';
---
<Badge> shadow </Badge>
no description provided
## Properties
### axis
<table>
<tr><th>Description</th><td><Markdown>*not provided*</Markdown></td></tr>
<tr><th>Attribute</th><td><Markdown>axis</Markdown></td></tr>
<tr><th>Type</th><td><Markdown>```"x" | "y"```</Markdown></td></tr>
<tr><th>Default</th><td><Markdown>```'y'```</Markdown></td></tr>
<tr><th>Required</th><td><Markdown>false</Markdown></td></tr>
</table>
### items
<table>
<tr><th>Description</th><td><Markdown>*not provided*</Markdown></td></tr>
<tr><th>Attribute</th><td><Markdown>items</Markdown></td></tr>
<tr><th>Type</th><td><Markdown>```MenuItems[]```</Markdown></td></tr>
<tr><th>Default</th><td><Markdown>```[ { label: 'test1', icon: ( <svg xmlns="http://www.w3.org/2000/svg" class="h-5 w-5" fill="none" viewBox="0 0 24 24" stroke="currentColor" > <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M3 12l2-2m0 0l7-7 7 7M5 10v10a1 1 0 001 1h3m10-11l2 2m-2-2v10a1 1 0 01-1 1h-3m-6 0a1 1 0 001-1v-4a1 1 0 011-1h2a1 1 0 011 1v4a1 1 0 001 1m-6 0h6" /> </svg> ) }, { label: 'test2', icon: ( <svg xmlns="http://www.w3.org/2000/svg" class="h-5 w-5" fill="none" viewBox="0 0 24 24" stroke="currentColor" > <path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M3 7v10a2 2 0 002 2h14a2 2 0 002-2V9a2 2 0 00-2-2h-6l-2-2H5a2 2 0 00-2 2z" /> </svg> ) } ]```</Markdown></td></tr>
<tr><th>Required</th><td><Markdown>false</Markdown></td></tr>
</table>
### padding
<table>
<tr><th>Description</th><td><Markdown>*not provided*</Markdown></td></tr>
<tr><th>Attribute</th><td><Markdown>padding</Markdown></td></tr>
<tr><th>Type</th><td><Markdown>```boolean```</Markdown></td></tr>
<tr><th>Default</th><td><Markdown>```true```</Markdown></td></tr>
<tr><th>Required</th><td><Markdown>false</Markdown></td></tr>
</table>
### width
<table>
<tr><th>Description</th><td><Markdown>*not provided*</Markdown></td></tr>
<tr><th>Attribute</th><td><Markdown>width</Markdown></td></tr>
<tr><th>Type</th><td><Markdown>```"contentwidth" | "fullwidth"```</Markdown></td></tr>
<tr><th>Default</th><td><Markdown>```'fullwidth'```</Markdown></td></tr>
<tr><th>Required</th><td><Markdown>false</Markdown></td></tr>
</table>
</table>
</table>
| 40.285714 | 736 | 0.644208 | yue_Hant | 0.475609 |
daa6efe9f6262747f230014fb0761bb2201d37d6 | 2,559 | md | Markdown | docs/en/auth.md | ngmikeng/node-rest-auth-exp | e0b0815654cf0266ec0999d069d712c47b00a4bd | [
"MIT"
] | null | null | null | docs/en/auth.md | ngmikeng/node-rest-auth-exp | e0b0815654cf0266ec0999d069d712c47b00a4bd | [
"MIT"
] | null | null | null | docs/en/auth.md | ngmikeng/node-rest-auth-exp | e0b0815654cf0266ec0999d069d712c47b00a4bd | [
"MIT"
] | null | null | null |
## Scenarios
HTTP protocol is stateless, all requests are stateless.
We would like users states to be rememebered in some cases.
## Session Based Authentication
- The server will create a session for the users after logs in.
- The session id is then stored on a cookie on the user's browser.
- While the user stays logged in, the cookie would be sent along with every request.
- The server compare the session id stored on the cooke against the session info stored in the memory too verify user's identity and sends response with the corresponding state.
## Token Based Authentication
- Using JSON Web Token (JWT) for authentication.
- The server creates JWT with a secret and sends the JWT to the client.
- The client stores the JWT in cookie/local storage and includes JWT in the header with every request.
- The server validate the JWT with every request from the client and sends response.
- The user’s state is not stored on the server, as the state is stored inside the token on the client side instead.
- Most of the modern web applications use JWT for authentication for reasons including scalability and mobile device authentication.
![token auth](../img/auth-token.png")
## Refresh token
There are many types of token, although in authentication with JWT the most typical are access token and refresh token.
- `Access token`: It contains all the information the server needs to know if the user / device can access the resource you are requesting or not. They are usually expired tokens with a short validity period.
- `Refresh token`: The refresh token is used to generate a new access token. Typically, if the access token has an expiration date, once it expires, the user would have to authenticate again to obtain an access token. With refresh token, this step can be skipped and with a request to the API get a new access token that allows the user to continue accessing the application resources.
![refresh token flow](../img/refresh-token.png")
## Google Sign In flow
![gg signin flow](../img/auth-google.png")
## References
- [Session vs Token Based Authentication](https://medium.com/@sherryhsu/session-vs-token-based-authentication-11a6c5ac45e4)
- [Refresh token with JWT authentication in Node.js](https://solidgeargroup.com/en/refresh-token-with-jwt-authentication-node-js/)
- [JWT token strategy](https://stackoverflow.com/questions/36751304/jwt-token-strategy-for-frontend-and-backend)
- [Google sign in backend auth](https://developers.google.com/identity/sign-in/web/backend-auth)
| 62.414634 | 385 | 0.781165 | eng_Latn | 0.994665 |
daa7202fc9a66bc678da657ae338807b74f47a47 | 16,948 | md | Markdown | _posts/2018-03-28-blog-deeplearning-vae.md | csjzhou/csjzhou_backup.github.io | 892949993a3c295fec412e43c4c9ca0626268cd2 | [
"MIT"
] | null | null | null | _posts/2018-03-28-blog-deeplearning-vae.md | csjzhou/csjzhou_backup.github.io | 892949993a3c295fec412e43c4c9ca0626268cd2 | [
"MIT"
] | null | null | null | _posts/2018-03-28-blog-deeplearning-vae.md | csjzhou/csjzhou_backup.github.io | 892949993a3c295fec412e43c4c9ca0626268cd2 | [
"MIT"
] | null | null | null | ---
layout: post
title: VAE Matplotlib Plotting Methods
show-avatar: true
tags:
- blogs
- python
- VAE
- plot
published: true
---
---
layout: post
title: "Variational Autoencoder: Intuition and Implementation"
subtitle: "Variational Autoencoder (VAE) (Kingma et al., 2013) is a new perspective in the autoencoding business. It views Autoencoder as a bayesian inference problem: modeling the underlying probability distribution of data."
tags:
- blogs
- python
- deeplearning
- vae
published: true
---
From [blog](https://wiseodd.github.io/techblog/2016/12/10/variational-autoencoder/)
There are two generative models facing neck to neck in the data generation business right now: [Generative Adversarial Nets (GAN)]({% post_url 2016-09-17-gan-tensorflow %}) and Variational Autoencoder (VAE). These two models have different take on how the models are trained. GAN is rooted in game theory, its objective is to find the Nash Equilibrium between discriminator net and generator net. On the other hand, VAE is rooted in bayesian inference, i.e. it wants to model the underlying probability distribution of data so that it could sample new data from that distribution.
In this post, we will look at the intuition of VAE model and its implementation in Keras.
<h2 class="section-heading">VAE: Formulation and Intuition</h2>
Suppose we want to generate a data. Good way to do it is first to decide what kind of data we want to generate, then actually generate the data. For example, say, we want to generate an animal. First, we imagine the animal: it must have four legs, and it must be able to swim. Having those criteria, we could then actually generate the animal by sampling from the animal kingdom. Lo and behold, we get Platypus!
From the story above, our imagination is analogous to **latent variable**. It is often useful to decide the latent variable first in generative models, as latent variable could describe our data. Without latent variable, it is as if we just generate data blindly. And this is the difference between GAN and VAE: VAE uses latent variable, hence it's an expressive model.
Alright, that fable is great and all, but how do we model that? Well, let's talk about probability distribution.
Let's define some notions:
1. \\( X \\): data that we want to model a.k.a the animal
2. \\( z \\): latent variable a.k.a our imagination
3. \\( P(X) \\): probability distribution of the data, i.e. that animal kingdom
4. \\( P(z) \\): probability distribution of latent variable, i.e. our brain, the source of our imagination
5. \\( P(X \vert z) \\): distribution of generating data given latent variable, e.g. turning imagination into real animal
Our objective here is to model the data, hence we want to find \\( P(X) \\). Using the law of probability, we could find it in relation with \\( z \\) as follows:
\\[ P(X) = \int P(X \vert z) P(z) dz \\]
that is, we marginalize out \\( z \\) from the joint probability distribution \\( P(X, z) \\).
Now if only we know \\( P(X, z) \\), or equivalently, \\( P(X \vert z) \\) and \\( P(z) \\)...
The idea of VAE is to infer \\( P(z) \\) using \\( P(z \vert X) \\). This is make a lot of sense if we think about it: we want to make our latent variable likely under our data. Talking in term of our fable example, we want to limit our imagination only on animal kingdom domain, so we shouldn't imagine about things like root, leaf, tyre, glass, GPU, refrigerator, doormat, ... as it's unlikely that those things have anything to do with things that come from the animal kingdom. Right?
But the problem is, we have to infer that distribution \\( P(z \vert X) \\), as we don't know it yet. In VAE, as it name suggests, we infer \\( P(z \vert X) \\) using a method called Variational Inference (VI). VI is one of the popular choice of method in bayesian inference, the other one being MCMC method. The main idea of VI is to pose the inference by approach it as an optimization problem. How? By modeling the true distribution \\( P(z \vert X) \\) using simpler distribution that is easy to evaluate, e.g. Gaussian, and minimize the difference between those two distribution using [KL divergence](https://en.wikipedia.org/wiki/Kullback%E2%80%93Leibler_divergence) metric, which tells us how difference it is \\(P\\) and \\(Q\\).
Alright, now let's say we want to infer \\( P(z \vert X) \\) using \\( Q(z \vert X) \\). The KL divergence then formulated as follows:
$$ \begin{align}
D_{KL}[Q(z \vert X) \Vert P(z \vert X)] &= \sum_z Q(z \vert X) \, \log \frac{Q(z \vert X)}{P(z \vert X)} \\[10pt]
&= E \left[ \log \frac{Q(z \vert X)}{P(z \vert X)} \right] \\[10pt]
&= E[\log Q(z \vert X) - \log P(z \vert X)]
\end{align} $$
Recall the notations above, there are two things that we haven't use, namely \\( P(X) \\), \\( P(X \vert z) \\), and \\( P(z) \\). But, with Bayes' rule, we could make it appear in the equation:
$$ \begin{align}
D_{KL}[Q(z \vert X) \Vert P(z \vert X)] &= E \left[ \log Q(z \vert X) - \log \frac{P(X \vert z) P(z)}{P(X)} \right] \\[10pt]
&= E[\log Q(z \vert X) - (\log P(X \vert z) + \log P(z) - \log P(X))] \\[10pt]
&= E[\log Q(z \vert X) - \log P(X \vert z) - \log P(z) + \log P(X)]
\end{align} $$
Notice that the expectation is over \\( z \\) and \\( P(X) \\) doesn't depend on \\( z \\), so we could move it outside of the expectation.
$$ \begin{align}
D_{KL}[Q(z \vert X) \Vert P(z \vert X)] &= E[\log Q(z \vert X) - \log P(X \vert z) - \log P(z)] + \log P(X) \\[10pt]
D_{KL}[Q(z \vert X) \Vert P(z \vert X)] - \log P(X) &= E[\log Q(z \vert X) - \log P(X \vert z) - \log P(z)]
\end{align} $$
If we look carefully at the right hand side of the equation, we would notice that it could be rewritten as another KL divergence. So let's do that by first rearranging the sign.
$$ \begin{align}
D_{KL}[Q(z \vert X) \Vert P(z \vert X)] - \log P(X) &= E[\log Q(z \vert X) - \log P(X \vert z) - \log P(z)] \\[10pt]
\log P(X) - D_{KL}[Q(z \vert X) \Vert P(z \vert X)] &= E[\log P(X \vert z) - (\log Q(z \vert X) - \log P(z))] \\[10pt]
&= E[\log P(X \vert z)] - E[\log Q(z \vert X) - \log P(z)] \\[10pt]
&= E[\log P(X \vert z)] - D_{KL}[Q(z \vert X) \Vert P(z)]
\end{align} $$
And this is it, the VAE objective function:
$$ \log P(X) - D_{KL}[Q(z \vert X) \Vert P(z \vert X)] = E[\log P(X \vert z)] - D_{KL}[Q(z \vert X) \Vert P(z)] $$
At this point, what do we have? Let's enumerate:
1. \\( Q(z \vert X) \\) that project our data \\( X \\) into latent variable space
2. \\( z \\), the latent variable
3. \\( P(X \vert z) \\) that generate data given latent variable
We might feel familiar with this kind of structure. And guess what, it's the same structure as seen in [Autoencoder]({% post_url 2016-12-03-autoencoders %})! That is, \\( Q(z \vert X) \\) is the encoder net, \\( z \\) is the encoded representation, and \\( P(X \vert z) \\) is the decoder net! Well, well, no wonder the name of this model is Variational Autoencoder!
<h2 class="section-heading">VAE: Dissecting the Objective</h2>
It turns out, VAE objective function has a very nice interpretation. That is, we want to model our data, which described by \\( \log P(X) \\), under some error \\( D_{KL}[Q(z \vert X) \Vert P(z \vert X)] \\). In other words, VAE tries to find the lower bound of \\( \log P(X) \\), which in practice is good enough as trying to find the exact distribution is often untractable.
That model then could be found by maximazing over some mapping from latent variable to data \\( \log P(X \vert z) \\) and minimizing the difference between our simple distribution \\( Q(z \vert X) \\) and the true latent distribution \\( P(z) \\).
As we might already know, maximizing \\( E[\log P(X \vert z)] \\) is a maximum likelihood estimation. We basically see it all the time in discriminative supervised model, for example Logistic Regression, SVM, or Linear Regression. In the other words, given an input \\( z \\) and an output \\( X \\), we want to maximize the conditional distribution \\( P(X \vert z) \\) under some model parameters. So we could implement it by using any classifier with input \\( z \\) and output \\( X \\), then optimize the objective function by using for example log loss or regression loss.
What about \\( D_{KL}[Q(z \vert X) \Vert P(z)] \\)? Here, \\( P(z) \\) is the latent variable distribution. We might want to sample \\( P(z) \\) later, so the easiest choice is \\( N(0, 1) \\). Hence, we want to make \\( Q(z \vert X) \\) to be as close as possible to \\( N(0, 1) \\) so that we could sample it easily.
Having \\( P(z) = N(0, 1) \\) also add another benefit. Let's say we also want \\( Q(z \vert X) \\) to be Gaussian with parameters \\( \mu(X) \\) and \\( \Sigma(X) \\), i.e. the mean and variance __given__ X. Then, the KL divergence between those two distribution could be computed in closed form!
$$
D_{KL}[N(\mu(X), \Sigma(X)) \Vert N(0, 1)] = \frac{1}{2} \, \left( \textrm{tr}(\Sigma(X)) + \mu(X)^T\mu(X) - k - \log \, \det(\Sigma(X)) \right)
$$
Above, \\( k \\) is the dimension of our Gaussian. \\( \textrm{tr}(X) \\) is trace function, i.e. sum of the diagonal of matrix \\( X \\). The determinant of a diagonal matrix could be computed as product of its diagonal. So really, we could implement \\( \Sigma(X) \\) as just a vector as it's a diagonal matrix:
$$ \begin{align}
D_{KL}[N(\mu(X), \Sigma(X)) \Vert N(0, 1)] &= \frac{1}{2} \, \left( \sum_k \Sigma(X) + \sum_k \mu^2(X) - \sum_k 1 - \log \, \prod_k \Sigma(X) \right) \\[10pt]
&= \frac{1}{2} \, \left( \sum_k \Sigma(X) + \sum_k \mu^2(X) - \sum_k 1 - \sum_k \log \Sigma(X) \right) \\[10pt]
&= \frac{1}{2} \, \sum_k \left( \Sigma(X) + \mu^2(X) - 1 - \log \Sigma(X) \right)
\end{align} $$
In practice, however, it's better to model \\( \Sigma(X) \\) as \\( \log \Sigma(X) \\), as it is more numerically stable to take exponent compared to computing log. Hence, our final KL divergence term is:
$$
D_{KL}[N(\mu(X), \Sigma(X)) \Vert N(0, 1)] = \frac{1}{2} \sum_k \left( \exp(\Sigma(X)) + \mu^2(X) - 1 - \Sigma(X) \right)
$$
<h2 class="section-heading">Implementation in Keras</h2>
First, let's implement the encoder net \\( Q(z \vert X) \\), which takes input \\( X \\) and outputting two things: \\( \mu(X) \\) and \\( \Sigma(X) \\), the parameters of the Gaussian.
``` python
from tensorflow.examples.tutorials.mnist import input_data
from keras.layers import Input, Dense, Lambda
from keras.models import Model
from keras.objectives import binary_crossentropy
from keras.callbacks import LearningRateScheduler
import numpy as np
import matplotlib.pyplot as plt
import keras.backend as K
import tensorflow as tf
m = 50
n_z = 2
n_epoch = 10
# Q(z|X) -- encoder
inputs = Input(shape=(784,))
h_q = Dense(512, activation='relu')(inputs)
mu = Dense(n_z, activation='linear')(h_q)
log_sigma = Dense(n_z, activation='linear')(h_q)
```
That is, our \\( Q(z \vert X) \\) is a neural net with one hidden layer. In this implementation, our latent variable is two dimensional, so that we could easily visualize it. In practice though, more dimension in latent variable should be better.
However, we are now facing a problem. How do we get \\( z \\) from the encoder outputs? Obviously we could sample \\( z \\) from a Gaussian which parameters are the outputs of the encoder. Alas, sampling directly won't do, if we want to train VAE with gradient descent as the sampling operation doesn't have gradient!
There is, however a trick called reparameterization trick, which makes the network differentiable. Reparameterization trick basically divert the non-differentiable operation out of the network, so that, even though we still involve a thing that is non-differentiable, at least it is out of the network, hence the network could still be trained.
The reparameterization trick is as follows. Recall, if we have \\( x \sim N(\mu, \Sigma) \\) and then standardize it so that \\( \mu = 0, \Sigma = 1 \\), we could revert it back to the original distribution by reverting the standardization process. Hence, we have this equation:
$$ x = \mu + \Sigma^{\frac{1}{2}} x_{std} $$
With that in mind, we could extend it. If we sample from a standard normal distribution, we could convert it to any Gaussian we want if we know the mean and the variance. Hence we could implement our sampling operation of \\( z \\) by:
$$
z = \mu(X) + \Sigma^{\frac{1}{2}}(X) \, \epsilon
$$
where \\( \epsilon \sim N(0, 1) \\).
Now, during backpropagation, we don't care anymore with the sampling process, as it is now outside of the network, i.e. doesn't depend on anything in the net, hence the gradient won't flow through it.
``` python
def sample_z(args):
mu, log_sigma = args
eps = K.random_normal(shape=(m, n_z), mean=0., std=1.)
return mu + K.exp(log_sigma / 2) * eps
# Sample z ~ Q(z|X)
z = Lambda(sample_z)([mu, log_sigma])
```
Now we create the decoder net \\( P(X \vert z) \\):
``` python
# P(X|z) -- decoder
decoder_hidden = Dense(512, activation='relu')
decoder_out = Dense(784, activation='sigmoid')
h_p = decoder_hidden(z)
outputs = decoder_out(h_p)
```
Lastly, from this model, we can do three things: reconstruct inputs, encode inputs into latent variables, and generate data from latent variable. So, we have three Keras models:
``` python
# Overall VAE model, for reconstruction and training
vae = Model(inputs, outputs)
# Encoder model, to encode input into latent variable
# We use the mean as the output as it is the center point, the representative of the gaussian
encoder = Model(inputs, mu)
# Generator model, generate new data given latent variable z
d_in = Input(shape=(n_z,))
d_h = decoder_hidden(d_in)
d_out = decoder_out(d_h)
decoder = Model(d_in, d_out)
```
Then, we need to translate our loss into Keras code:
``` python
def vae_loss(y_true, y_pred):
""" Calculate loss = reconstruction loss + KL loss for each data in minibatch """
# E[log P(X|z)]
recon = K.sum(K.binary_crossentropy(y_pred, y_true), axis=1)
# D_KL(Q(z|X) || P(z|X)); calculate in closed form as both dist. are Gaussian
kl = 0.5 * K.sum(K.exp(log_sigma) + K.square(mu) - 1. - log_sigma, axis=1)
return recon + kl
```
and then train it:
``` python
vae.compile(optimizer='adam', loss=vae_loss)
vae.fit(X_train, X_train, batch_size=m, nb_epoch=n_epoch)
```
And that's it, the implementation of VAE in Keras!
<h2 class="section-heading">Implementation on MNIST Data</h2>
We could use any dataset really, but like always, we will use MNIST as an example.
After we trained our VAE model, we then could visualize the latent variable space \\( Q(z \vert X) \\):
As we could see, in the latent space, the representation of our data that have the same characteristic, e.g. same label, are close to each other. Notice that in the training phase, we never provide any information regarding the data.
We could also look at the data reconstruction by running through the data into overall VAE net:
Lastly, we could generate new sample by first sample \\( z \sim N(0, 1) \\) and feed it into our decoder net:
If we look closely on the reconstructed and generated data, we would notice that some of the data are ambiguous. For example the digit 5 looks like 3 or 8. That's because our latent variable space is a continous distribution (i.e. \\( N(0, 1) \\)), hence there bound to be some smooth transition on the edge of the clusters. And also, the cluster of digits are close to each other if they are somewhat similar. That's why in the latent space, 5 is close to 3.
<h2 class="section-heading">Conclusion</h2>
In this post we looked at the intuition behind Variational Autoencoder (VAE), its formulation, and its implementation in Keras.
We also saw the difference between VAE and GAN, the two most popular generative models nowadays.
For more math on VAE, be sure to hit the original paper by Kingma et al., 2014. There is also an excellent tutorial on VAE by Carl Doersch. Check out the references section below.
The full code is available in my repo: <https://github.com/wiseodd/generative-models>
<h2 class="section-heading">References</h2>
1. Doersch, Carl. "Tutorial on variational autoencoders." arXiv preprint arXiv:1606.05908 (2016).
2. Kingma, Diederik P., and Max Welling. "Auto-encoding variational bayes." arXiv preprint arXiv:1312.6114 (2013).
3. <https://blog.keras.io/building-autoencoders-in-keras.html>
| 56.305648 | 737 | 0.681437 | eng_Latn | 0.987648 |
daa7af29888131c9c6a7fb7a81c9002aa1045cf0 | 89 | md | Markdown | README.md | RaphaelR89/whatsdev | 7223f197693c112845387d74d9799bac20976c76 | [
"MIT"
] | null | null | null | README.md | RaphaelR89/whatsdev | 7223f197693c112845387d74d9799bac20976c76 | [
"MIT"
] | null | null | null | README.md | RaphaelR89/whatsdev | 7223f197693c112845387d74d9799bac20976c76 | [
"MIT"
] | null | null | null | # whatsdev
whatsdev html css js
https://www.youtube.com/channel/UC0tRdbXVDbhaRvZPKsRgmxg
| 22.25 | 56 | 0.831461 | kor_Hang | 0.37104 |
daa82cf3de020199847258b28c857abbbceadbcb | 134 | md | Markdown | README.md | anglefly/anglefly.github.io | 2307f4d949a6563a977496ac658305c52297d960 | [
"MIT"
] | 1 | 2020-09-01T13:35:05.000Z | 2020-09-01T13:35:05.000Z | README.md | anglefly/anglefly.github.io | 2307f4d949a6563a977496ac658305c52297d960 | [
"MIT"
] | 11 | 2020-09-10T05:17:07.000Z | 2020-09-29T02:03:27.000Z | README.md | anglefly/blog | 2307f4d949a6563a977496ac658305c52297d960 | [
"MIT"
] | null | null | null | # blog
这里是我记录学习成果和笔记的地方，可以访问 [一头老母猪](http://cn.yufei.cool) 或者 [第二头老母猪](https://cblog.yufei.cool) [最后一头老母猪](https://blog.yufei.cool)
| 33.5 | 125 | 0.716418 | yue_Hant | 0.980866 |
daaafbd079c1114f4c200dd8991922d216348495 | 65 | md | Markdown | README.md | ogoes/rust-querybuilder | f4c6034de1142c4b1152db95756fedcc264e1ccd | [
"MIT"
] | null | null | null | README.md | ogoes/rust-querybuilder | f4c6034de1142c4b1152db95756fedcc264e1ccd | [
"MIT"
] | null | null | null | README.md | ogoes/rust-querybuilder | f4c6034de1142c4b1152db95756fedcc264e1ccd | [
"MIT"
] | null | null | null | # rust-querybuilder
A MySQL query builder for rust applications.
| 21.666667 | 44 | 0.815385 | eng_Latn | 0.744855 |
daabd1cf3514ada32ec6e64eea9a1f630816bddd | 99 | md | Markdown | README.md | akashsanjaywagh/Supplement-sales-prediction | 59efd5ad04d16d50d889d2916ee45fde30e2f3b5 | [
"Apache-2.0"
] | null | null | null | README.md | akashsanjaywagh/Supplement-sales-prediction | 59efd5ad04d16d50d889d2916ee45fde30e2f3b5 | [
"Apache-2.0"
] | null | null | null | README.md | akashsanjaywagh/Supplement-sales-prediction | 59efd5ad04d16d50d889d2916ee45fde30e2f3b5 | [
"Apache-2.0"
] | null | null | null | # Supplement-sales-prediction
supplement sales prediction is Analytics vidhya competition dataset.
| 33 | 68 | 0.858586 | eng_Latn | 0.921023 |
daac4e28c320012861ac08bfce9d78acffd78897 | 3,055 | md | Markdown | source/_news/Mystery lingers over death of young rugby player.blade.md | salihzeki12000/Website | 733c8f7ea86f6ee4967cbbbb83cfc10d12cf7c12 | [
"MIT"
] | null | null | null | source/_news/Mystery lingers over death of young rugby player.blade.md | salihzeki12000/Website | 733c8f7ea86f6ee4967cbbbb83cfc10d12cf7c12 | [
"MIT"
] | 10 | 2019-08-13T10:55:15.000Z | 2022-02-26T10:21:10.000Z | source/_news/Mystery lingers over death of young rugby player.blade.md | wing5wong/artisan-whs-static | cb36480c54adcb5cbe1fd25c1a741bb525112a72 | [
"MIT"
] | 1 | 2020-10-30T12:55:04.000Z | 2020-10-30T12:55:04.000Z | ---
title: "Mystery lingers over death of young rugby player"
date:
description: "Mystery lingers over death of young rugby player Jake Alabaster..."
image: http://c1940652.r52.cf0.rackcdn.com/59d2e899b8d39a191700066c/Jake-Alabaster-with-Marist-club.jpg
excerpt: "Mystery lingers over death of young rugby player Jake Alabaster."
image_gallery:
---
<p><span>Jake Alabaster started his club career with Marist, before moving to Border. <br />He is pictured (centre) after Border won the premier championship last year. <br />PHOTO / Bevan Conley</span></p>
<p class="element element-paragraph">It may take weeks to find out what killed former Steelform Wanganui representative Jake Alabaster.</p>
<p class="element element-paragraph">The talented loose forward was found dead on Saturday morning, believed to have passed away in his sleep, age 24.</p>
<p class="element element-paragraph">It's understood the results from an autopsy in Auckland will take weeks.</p>
<p class="element element-paragraph">Members of a shocked rugby fraternity have speculated Alabaster may have been stung while beekeeping and had a fatal reaction.</p>
<p class="element element-paragraph">He had spent some time overseas to recover from niggling sports injuries and returned recently to take up a beekeeping job.</p>
<p class="element element-paragraph">He had been working in Northland last week.</p>
<p class="element element-paragraph">Stunned members of the community took to Facebook to share their grief and condolences for Alabaster's family.</p>
<p class="element element-paragraph">Posted Bronwyn Poulson: "So young"</p>
<p class="element element-paragraph">Said Craig N Sandi Pye: "Condolences to the Alabaster family. My thoughts are with you all at this very sad time"</p>
<p class="element element-paragraph">A post about his death on the <em>Wanganui Chronicle</em>Facebook page has reached thousands of people and been shared on other Facebook pages, with people expressing their condolences to the Alabaster family.</p>
<p class="element element-paragraph">"Beautiful boy - just not fair", one woman said.</p>
<p class="element element-paragraph">Another person posted on the Border Rugby and Sports Club page: "... he portrayed everything good about [a] young man playing rugby".</p>
<p class="element element-paragraph">Alabaster debuted for the Wanganui senior team in their 2016 mid-year game against the Manawatu Evergreens in Palmerston North, when several veterans were rested, and scored a try despite going into the match with a sore AC joint.</p>
<p class="element element-paragraph">"He played hurt because he knew that's what it was going to take," said Border club coach Ross Williams.</p>
<p class="element element-paragraph">Alabaster was named in the Wanganui Development XV at the end of the season, but injuries hampered what was otherwise looking like a big career in rugby.</p>
<p class="element element-paragraph">The case has been referred to the coroner.</p>
<p><em>Wanganui Chronicle 3/10/17</em></p>
| 89.852941 | 271 | 0.774468 | eng_Latn | 0.994256 |
daad600e5579659850ee4047714e00caf8675405 | 2,200 | md | Markdown | README.md | ph0llux/udig | 3449896259a8c33e0a65f5130396d501c49433c2 | [
"BSD-3-Clause"
] | null | null | null | README.md | ph0llux/udig | 3449896259a8c33e0a65f5130396d501c49433c2 | [
"BSD-3-Clause"
] | null | null | null | README.md | ph0llux/udig | 3449896259a8c33e0a65f5130396d501c49433c2 | [
"BSD-3-Clause"
] | null | null | null | <img src="https://img.shields.io/crates/d/urdig?style=for-the-badge"/> <img src="https://img.shields.io/crates/v/urdig?color=blue&logo=Rust&style=for-the-badge"/> <img src="https://img.shields.io/crates/v/urdig?color=blue&label=docs&logo=Rust&style=for-the-badge"/> <img src="https://img.shields.io/crates/l/urdig?style=for-the-badge"/>
# urdig
The **u**dev **r**ecognized **d**evices **i**nformation **g**rabber.
## Installation
### Use pre-compiled binaries
#### ... install as snap
[](https://snapcraft.io/urdig)
### Build from source
#### Pre-requirements
You need the udev development files, which could be installed by following commands (at the according distributions):
| Distribution | Installation command |
|--------------|---------------------------|
| Fedora | dnf install systemd-devel |
| Ubuntu | apt install libudev-dev |
| Debian | apt install libudev-dev |
You need also a rust compiler and cargo. The most suitable way to install it, is [using rustup](https://rustup.rs/):
```bash
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
```
#### installing via cargo install
You can easy install urdig by
```bash
cargo install urdig
```
#### building manually
You could download the tool manually and build it with cargo:
```bash
git clone https://github.com/ph0llux/urdig
cd urdig
cargo build --release
```
The binary can be find at ```./target/release/urdig```.
## Usage
You can print the help menu by using
```bash
$ urdig
urdig 0.9.3
ph0llux <[email protected]>
Grab device informations via libudev and display or parse them.
USAGE:
urdig [SUBCOMMAND]
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
SUBCOMMANDS:
device print options for specific device, which is called via its name. You can also use devnodes or
syspaths.
help Prints this message or the help of the given subcommand(s)
subsystems interacting with udev subsystems.
```
and grab informations of any device
```
$ urdig device -p /dev/sda
[output omitted]
```
| 29.72973 | 337 | 0.680455 | eng_Latn | 0.884399 |
daaeb98e3ff953efe94b1f2f89353dcaa2310c20 | 1,152 | md | Markdown | products/images/src/content/upload-images/index.md | dmfreemon/cloudflare-docs | 52bc6c06aec1aed0134b7b855d2df3efcd3d37c6 | [
"MIT"
] | 915 | 2020-10-02T21:29:22.000Z | 2022-03-31T21:41:30.000Z | products/images/src/content/upload-images/index.md | dmfreemon/cloudflare-docs | 52bc6c06aec1aed0134b7b855d2df3efcd3d37c6 | [
"MIT"
] | 1,394 | 2020-09-28T21:23:45.000Z | 2022-03-31T19:27:58.000Z | products/images/src/content/upload-images/index.md | dmfreemon/cloudflare-docs | 52bc6c06aec1aed0134b7b855d2df3efcd3d37c6 | [
"MIT"
] | 1,440 | 2020-09-18T16:31:31.000Z | 2022-03-31T18:14:21.000Z | ---
title: Upload Images
order: 1
---
# Upload Images
Cloudflare Images allows developers to upload images that cover a wide range of use cases. Check it out:
| Upload Method | When to use |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Images Dashboard | Quick, one time uploads where automation is not required |
| Authentication Token | The image file is stored on your computer with access to your API Tokens |
| Direct Creator Uploads | The end user is uploading the images but doesn’t have access to your API tokens, such as if you have your users uploading content directly to your website or mobile app |
| 76.8 | 197 | 0.37934 | eng_Latn | 0.984502 |
daaed4cce6ab1a35f379b0fc929b769f1e1b2627 | 80 | md | Markdown | README.md | froliol/DatabricksGitDemo | 19e53d72c1479c5e3a7996cf3c01c64dadcf1c10 | [
"Apache-2.0"
] | null | null | null | README.md | froliol/DatabricksGitDemo | 19e53d72c1479c5e3a7996cf3c01c64dadcf1c10 | [
"Apache-2.0"
] | null | null | null | README.md | froliol/DatabricksGitDemo | 19e53d72c1479c5e3a7996cf3c01c64dadcf1c10 | [
"Apache-2.0"
] | null | null | null | # DatabricksGitDemo
Simple repo to sync with Databricks Repos in demo workspace
| 26.666667 | 59 | 0.8375 | kor_Hang | 0.805072 |
daaf0500ed58f73662b36caf28ec52ccf858fd2b | 1,602 | md | Markdown | service-for-test-case-odata-path-parameter/Docker.md | patricekrakow/test-case-odata-path-parameter | 495d6a95cdab0445b408670ac1f90b66747365bb | [
"MIT"
] | null | null | null | service-for-test-case-odata-path-parameter/Docker.md | patricekrakow/test-case-odata-path-parameter | 495d6a95cdab0445b408670ac1f90b66747365bb | [
"MIT"
] | null | null | null | service-for-test-case-odata-path-parameter/Docker.md | patricekrakow/test-case-odata-path-parameter | 495d6a95cdab0445b408670ac1f90b66747365bb | [
"MIT"
] | null | null | null | ```text
$ ls
Docker.md Dockerfile app.js node_modules package-lock.json package.json
$ docker --version
Docker version 20.10.7, build f0df350
$ docker build --tag patrice1972/service-for-test-case-odata-path-parameter:1.0.0 .
...
Successfully built 74d95464c814
Successfully tagged patrice1972/service-for-test-case-odata-path-parameter:1.0.0
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
patrice1972/service-for-test-case-odata-path-parameter 1.0.0 74d95464c814 25 seconds ago 182MB
...
$ docker run --publish 3000:3000 --detach patrice1972/service-for-test-case-odata-path-parameter:1.0.0
c3bcef7ab91679a39ff7a6b0278382b461dac73ac434a74fdf83c122a4c6a06a
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c3bcef7ab916 patrice1972/service-for-test-case-odata-path-parameter:1.0.0 "docker-entrypoint.s…" 23 seconds ago Up 22 seconds 0.0.0.0:3000->3000/tcp, :::3000->3000/tcp charming_bhabha
$ curl "localhost:3000/thingies('1001')"
{"id":1001,"message":"Hello!"}
$ docker rm --force c3bcef7ab916
c3bcef7ab916
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker login
...
Login Succeeded
$ docker push patrice1972/service-for-test-case-odata-path-parameter:1.0.0
...
1.0.0: digest: sha256:2d66e66f7566f79a9f8aa1b5e177744da338dc0448b11aa7788e782d1383622f size: 2202
```
<https://hub.docker.com>
| 36.409091 | 195 | 0.662297 | yue_Hant | 0.663017 |
daaf914f690521d1fe09f76f1df49a7728780467 | 2,340 | md | Markdown | book_wechat/201912/wechat_ml_00_build_tfjs.md | mogoweb/mywritings | 1b7cb04032406130f813050f95a53837dde7015c | [
"Apache-2.0"
] | null | null | null | book_wechat/201912/wechat_ml_00_build_tfjs.md | mogoweb/mywritings | 1b7cb04032406130f813050f95a53837dde7015c | [
"Apache-2.0"
] | 1 | 2021-02-03T14:04:38.000Z | 2021-02-03T14:04:38.000Z | book_wechat/201912/wechat_ml_00_build_tfjs.md | mogoweb/mywritings | 1b7cb04032406130f813050f95a53837dde7015c | [
"Apache-2.0"
] | null | null | null | # 手把手教你开发人工智能微信小程序(0)：构建tfjs
本文将介绍如何从源码构建出 TensorFlow JS 库(tfjs)。对于大多数微信小程序开发者而言，并不需要经历这一步，要做的仅仅是把编译好的 tfjs 库加入微信小程序工程中。但我还是希望说说如何从源码编译出 tfjs 库，为什么呢？主要出于两个原因：
1. 完整的 tfjs 库大约有 900K，看起来是一个很小的体积，但我们要知道，微信小程序包有 2M 的大小限制。微信小程序添加一点图片，加上深度学习模型文件，很容易超过 2M 的大小。所以 tfjs 库能减则减，可能在项目开发中需要对 tfjs 库进行裁剪。
2. tfjs 主要是为浏览器和 NodeJS 而开发，微信小程序虽然也采用基于 web 的技术，但有些地方进行了限制，比如 web 中广泛使用的 fetch API 就被砍掉了。在某些情况下我们可能需要修改 tfjs 的源码，这个时候就需要自行构建 tfjs 库。
TensorFlow JS 主要包含 4 个重要的模块，在老的版本中，它们存在于几个独立的 git 库: tjfs-core, tfjs-layers, tfjs-converter, tfjs-data。在最新的版本中，它们整合到同一个 git 库中:
* TensorFlow.js Core, tfjs核心库，提供灵活的低层次API，由deeplearn.js发展而来。
* TensorFlow.js Layers, 提供高层次API，实现了类似于Keras的函数。
* TensorFlow.js Data, 提供简单的API加载和准备数据，功能类似于tf.data。
* TensorFlow.js Converter, 提供工具导入TensorFlow SavedModel格式模型到TensorFlow.js。
上述4个模块中， tfjs-core 是最基础的组件，其它几个模块都依赖这一模块。该可以单独编译，功能独立，能够单独使用，从而可以减少 tfjs 库的体积。
#### 安装yarn
tfjs 采用了 yarn 构建系统，对于前端开发者而言应该比较熟悉。下面简单说说如何在 Ubuntu 18.04 上安装 yarn ，其它平台上的安装方法，请自行搜索。
1. 导入 yarn 库的GPG key：
```bash
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
```
2. 往 *Ubunut* 系统添加 *yarn* APT库：
```bash
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
```
3. 安装 yarn:
```bash
sudo apt update
sudo apt install yarn
```
4. 检查 yarn 是否安装成功，如下命令输出 yarn 的版本号：
```bash
yarn --version
```
当前输出的版本号为：
```bash
1.21.1
```
需要注意的是， *Ubuntu* 中另外有个包中也有同名程序，如果你之前未安装过 *yarn*，运行yarn命令可能会出现如下提示：
```
Command 'yarn' not found, but can be installed with:
sudo apt install cmdtest
```
请勿安装这个 *cmdtest*，这是另外一个工具，并不是 *yarn* 构建系统。
#### 构建tfjs库
1. 克隆 *tfjs* 源码库：
```bash
git clone https://github.com/tensorflow/tfjs.git
```
2. 构建 *tfjs*
```
cd tfjs/tfjs
yarn build-npm
```
在当前目录下会生成一个 *tensorflow-tfjs-x.x.x.tgz* 的压缩包，其中 *x.x.x* 代表 *tfjs* 的版本号，写这篇文章时最新的版本号为1.5.1。如果我们要在项目中加入 *tfjs* 库，可以直接使用 *dist* 目录下的 *tf.min.js* 文件。
如果在项目中，我们只使用 *tfjs-core*，可以单独构建 *tfjs-core*:
```
cd tfjs/tfjs-core
yarn build-npm
```
编译出的 *tfjs-core* 库文件位于 *dist* 子目录下，名为 *tf-core.min.js* 。
#### 小结
本文介绍了如何从源码构建 tfjs 库，对于大多数微信小程序开发者而言并不需要，但如果你希望裁剪和定制 tfjs ，就可能需要从源码构建。在下一篇文章中，我将介绍人工智能微信小程序 Hello WeChat ，敬请关注！
| 25.16129 | 192 | 0.746581 | yue_Hant | 0.757177 |
daafe719d938e9d03a81295ef1d3079ca231f564 | 37 | md | Markdown | README.md | HubCloud-io/ParserCollection | feafa5efa1ab1a736e4f128952e579e0bdb6beaa | [
"MIT"
] | null | null | null | README.md | HubCloud-io/ParserCollection | feafa5efa1ab1a736e4f128952e579e0bdb6beaa | [
"MIT"
] | null | null | null | README.md | HubCloud-io/ParserCollection | feafa5efa1ab1a736e4f128952e579e0bdb6beaa | [
"MIT"
] | null | null | null | # ParserCollection
Different parsers
| 12.333333 | 18 | 0.864865 | kor_Hang | 0.374394 |
dab1609a2f80b7a88485b677fdc828cfb965ec8e | 341 | md | Markdown | about.md | yoshitsugu/yoshitsugu.github.io | eebd521ca6dfd1b8a23d2b17e287a24b6c5d352f | [
"BSD-3-Clause"
] | null | null | null | about.md | yoshitsugu/yoshitsugu.github.io | eebd521ca6dfd1b8a23d2b17e287a24b6c5d352f | [
"BSD-3-Clause"
] | null | null | null | about.md | yoshitsugu/yoshitsugu.github.io | eebd521ca6dfd1b8a23d2b17e287a24b6c5d352f | [
"BSD-3-Clause"
] | 1 | 2017-05-17T01:00:18.000Z | 2017-05-17T01:00:18.000Z | ---
title: About Me
---
Kota Yoshitsugu (吉次 孝太)
Web Engineer in Iwate, Japan.
Working with Ruby / Ruby on Rails, Vue.js / React.js, and so on
Learning Haskell and Rust
GitHub: <a href="https://github.com/yoshitsugu" target="_blank">yoshitsugu</a>
Twitter: <a href="https://twitter.com/_yoshitsugu" target="_blank">@\_yoshitsugu</a>
| 26.230769 | 84 | 0.703812 | eng_Latn | 0.444852 |
dab19aa3f128437eb18a9e8ad99b05475deed045 | 9,273 | md | Markdown | archives/2021-11-29.md | erbanku/toutiao-hot-hub | 9358e6f7f377201b8d52f69ad23b363bd23bb146 | [
"MIT"
] | null | null | null | archives/2021-11-29.md | erbanku/toutiao-hot-hub | 9358e6f7f377201b8d52f69ad23b363bd23bb146 | [
"MIT"
] | null | null | null | archives/2021-11-29.md | erbanku/toutiao-hot-hub | 9358e6f7f377201b8d52f69ad23b363bd23bb146 | [
"MIT"
] | null | null | null | # 头条热榜
`最后更新时间：2021-11-29 11:07:24 +0800`
1. [人民日报八论六中全会](https://so.toutiao.com/search?keyword=%E4%BA%BA%E6%B0%91%E6%97%A5%E6%8A%A5%E5%85%AB%E8%AE%BA%E5%85%AD%E4%B8%AD%E5%85%A8%E4%BC%9A)
1. [31省份新增本土21例 在内蒙古云南](https://so.toutiao.com/search?keyword=31%E7%9C%81%E4%BB%BD%E6%96%B0%E5%A2%9E%E6%9C%AC%E5%9C%9F21%E4%BE%8B%20%E5%9C%A8%E5%86%85%E8%92%99%E5%8F%A4%E4%BA%91%E5%8D%97)
1. [一组数字速读六中全会精神](https://so.toutiao.com/search?keyword=%E4%B8%80%E7%BB%84%E6%95%B0%E5%AD%97%E9%80%9F%E8%AF%BB%E5%85%AD%E4%B8%AD%E5%85%A8%E4%BC%9A%E7%B2%BE%E7%A5%9E)
1. [王曼昱苦战逆转 陈梦无缘大满贯](https://so.toutiao.com/search?keyword=%E7%8E%8B%E6%9B%BC%E6%98%B1%E8%8B%A6%E6%88%98%E9%80%86%E8%BD%AC%20%E9%99%88%E6%A2%A6%E6%97%A0%E7%BC%98%E5%A4%A7%E6%BB%A1%E8%B4%AF)
1. [支付扫码新规下路边摊们怎么办](https://so.toutiao.com/search?keyword=%E6%94%AF%E4%BB%98%E6%89%AB%E7%A0%81%E6%96%B0%E8%A7%84%E4%B8%8B%E8%B7%AF%E8%BE%B9%E6%91%8A%E4%BB%AC%E6%80%8E%E4%B9%88%E5%8A%9E)
1. [世乒赛：中美混双组合负日本](https://so.toutiao.com/search?keyword=%E4%B8%96%E4%B9%92%E8%B5%9B%EF%BC%9A%E4%B8%AD%E7%BE%8E%E6%B7%B7%E5%8F%8C%E7%BB%84%E5%90%88%E8%B4%9F%E6%97%A5%E6%9C%AC)
1. [搅乱多国的奥密克戎威胁有多大](https://so.toutiao.com/search?keyword=%E6%90%85%E4%B9%B1%E5%A4%9A%E5%9B%BD%E7%9A%84%E5%A5%A5%E5%AF%86%E5%85%8B%E6%88%8E%E5%A8%81%E8%83%81%E6%9C%89%E5%A4%9A%E5%A4%A7)
1. [河南暴雨堵决口卡车即将被挖出](https://so.toutiao.com/search?keyword=%E6%B2%B3%E5%8D%97%E6%9A%B4%E9%9B%A8%E5%A0%B5%E5%86%B3%E5%8F%A3%E5%8D%A1%E8%BD%A6%E5%8D%B3%E5%B0%86%E8%A2%AB%E6%8C%96%E5%87%BA)
1. [曝李铁利用国足主帅职务牟利](https://so.toutiao.com/search?keyword=%E6%9B%9D%E6%9D%8E%E9%93%81%E5%88%A9%E7%94%A8%E5%9B%BD%E8%B6%B3%E4%B8%BB%E5%B8%85%E8%81%8C%E5%8A%A1%E7%89%9F%E5%88%A9)
1. [五问河南封丘学生呕吐腹泻事件](https://so.toutiao.com/search?keyword=%E4%BA%94%E9%97%AE%E6%B2%B3%E5%8D%97%E5%B0%81%E4%B8%98%E5%AD%A6%E7%94%9F%E5%91%95%E5%90%90%E8%85%B9%E6%B3%BB%E4%BA%8B%E4%BB%B6)
1. [国际乒联：反对一切形式的种族主义](https://so.toutiao.com/search?keyword=%E5%9B%BD%E9%99%85%E4%B9%92%E8%81%94%EF%BC%9A%E5%8F%8D%E5%AF%B9%E4%B8%80%E5%88%87%E5%BD%A2%E5%BC%8F%E7%9A%84%E7%A7%8D%E6%97%8F%E4%B8%BB%E4%B9%89)
1. [内蒙古通辽新增本土“1+1”](https://so.toutiao.com/search?keyword=%E5%86%85%E8%92%99%E5%8F%A4%E9%80%9A%E8%BE%BD%E6%96%B0%E5%A2%9E%E6%9C%AC%E5%9C%9F%E2%80%9C1%2B1%E2%80%9D)
1. [合肥中学生全班给无腿老人唱少年](https://so.toutiao.com/search?keyword=%E5%90%88%E8%82%A5%E4%B8%AD%E5%AD%A6%E7%94%9F%E5%85%A8%E7%8F%AD%E7%BB%99%E6%97%A0%E8%85%BF%E8%80%81%E4%BA%BA%E5%94%B1%E5%B0%91%E5%B9%B4)
1. [民警巡查“加拿大一枝黄花”殉职](https://so.toutiao.com/search?keyword=%E6%B0%91%E8%AD%A6%E5%B7%A1%E6%9F%A5%E2%80%9C%E5%8A%A0%E6%8B%BF%E5%A4%A7%E4%B8%80%E6%9E%9D%E9%BB%84%E8%8A%B1%E2%80%9D%E6%AE%89%E8%81%8C)
1. [江西人大常委会副主任龚建华被查](https://so.toutiao.com/search?keyword=%E6%B1%9F%E8%A5%BF%E4%BA%BA%E5%A4%A7%E5%B8%B8%E5%A7%94%E4%BC%9A%E5%89%AF%E4%B8%BB%E4%BB%BB%E9%BE%9A%E5%BB%BA%E5%8D%8E%E8%A2%AB%E6%9F%A5)
1. [LV首位黑人艺术总监去世年仅41岁](https://so.toutiao.com/search?keyword=LV%E9%A6%96%E4%BD%8D%E9%BB%91%E4%BA%BA%E8%89%BA%E6%9C%AF%E6%80%BB%E7%9B%91%E5%8E%BB%E4%B8%96%E5%B9%B4%E4%BB%8541%E5%B2%81)
1. [小伙回应拍摄盲母用嘴喂食脑瘫儿](https://so.toutiao.com/search?keyword=%E5%B0%8F%E4%BC%99%E5%9B%9E%E5%BA%94%E6%8B%8D%E6%91%84%E7%9B%B2%E6%AF%8D%E7%94%A8%E5%98%B4%E5%96%82%E9%A3%9F%E8%84%91%E7%98%AB%E5%84%BF)
1. [中纪委评居民打热线被训：寒群众心](https://so.toutiao.com/search?keyword=%E4%B8%AD%E7%BA%AA%E5%A7%94%E8%AF%84%E5%B1%85%E6%B0%91%E6%89%93%E7%83%AD%E7%BA%BF%E8%A2%AB%E8%AE%AD%EF%BC%9A%E5%AF%92%E7%BE%A4%E4%BC%97%E5%BF%83)
1. [南财教师侮辱同胞被调离岗位](https://so.toutiao.com/search?keyword=%E5%8D%97%E8%B4%A2%E6%95%99%E5%B8%88%E4%BE%AE%E8%BE%B1%E5%90%8C%E8%83%9E%E8%A2%AB%E8%B0%83%E7%A6%BB%E5%B2%97%E4%BD%8D)
1. [四川一金钱豹躺路中央 官方回应](https://so.toutiao.com/search?keyword=%E5%9B%9B%E5%B7%9D%E4%B8%80%E9%87%91%E9%92%B1%E8%B1%B9%E8%BA%BA%E8%B7%AF%E4%B8%AD%E5%A4%AE%20%E5%AE%98%E6%96%B9%E5%9B%9E%E5%BA%94)
1. [勇士凿沉快船豪取7连胜 库里33分](https://so.toutiao.com/search?keyword=%E5%8B%87%E5%A3%AB%E5%87%BF%E6%B2%89%E5%BF%AB%E8%88%B9%E8%B1%AA%E5%8F%967%E8%BF%9E%E8%83%9C%20%E5%BA%93%E9%87%8C33%E5%88%86)
1. [传李霄鹏或接任李铁成国足主帅](https://so.toutiao.com/search?keyword=%E4%BC%A0%E6%9D%8E%E9%9C%84%E9%B9%8F%E6%88%96%E6%8E%A5%E4%BB%BB%E6%9D%8E%E9%93%81%E6%88%90%E5%9B%BD%E8%B6%B3%E4%B8%BB%E5%B8%85)
1. [吴尊友算出“围堵零清”政策成效](https://so.toutiao.com/search?keyword=%E5%90%B4%E5%B0%8A%E5%8F%8B%E7%AE%97%E5%87%BA%E2%80%9C%E5%9B%B4%E5%A0%B5%E9%9B%B6%E6%B8%85%E2%80%9D%E6%94%BF%E7%AD%96%E6%88%90%E6%95%88)
1. [70后张迎春成全国最年轻女省委常委](https://so.toutiao.com/search?keyword=70%E5%90%8E%E5%BC%A0%E8%BF%8E%E6%98%A5%E6%88%90%E5%85%A8%E5%9B%BD%E6%9C%80%E5%B9%B4%E8%BD%BB%E5%A5%B3%E7%9C%81%E5%A7%94%E5%B8%B8%E5%A7%94)
1. [广西男子斗殴持刀追砍举枪抵头](https://so.toutiao.com/search?keyword=%E5%B9%BF%E8%A5%BF%E7%94%B7%E5%AD%90%E6%96%97%E6%AE%B4%E6%8C%81%E5%88%80%E8%BF%BD%E7%A0%8D%E4%B8%BE%E6%9E%AA%E6%8A%B5%E5%A4%B4)
1. [外卖员救人遇难家属收到关怀金](https://so.toutiao.com/search?keyword=%E5%A4%96%E5%8D%96%E5%91%98%E6%95%91%E4%BA%BA%E9%81%87%E9%9A%BE%E5%AE%B6%E5%B1%9E%E6%94%B6%E5%88%B0%E5%85%B3%E6%80%80%E9%87%91)
1. [男子开车遇东北虎对视一分多钟](https://so.toutiao.com/search?keyword=%E7%94%B7%E5%AD%90%E5%BC%80%E8%BD%A6%E9%81%87%E4%B8%9C%E5%8C%97%E8%99%8E%E5%AF%B9%E8%A7%86%E4%B8%80%E5%88%86%E5%A4%9A%E9%92%9F)
1. [张庆伟当选湖南省委书记](https://so.toutiao.com/search?keyword=%E5%BC%A0%E5%BA%86%E4%BC%9F%E5%BD%93%E9%80%89%E6%B9%96%E5%8D%97%E7%9C%81%E5%A7%94%E4%B9%A6%E8%AE%B0)
1. [逃犯朱贤健被抓时表情淡定没反抗](https://so.toutiao.com/search?keyword=%E9%80%83%E7%8A%AF%E6%9C%B1%E8%B4%A4%E5%81%A5%E8%A2%AB%E6%8A%93%E6%97%B6%E8%A1%A8%E6%83%85%E6%B7%A1%E5%AE%9A%E6%B2%A1%E5%8F%8D%E6%8A%97)
1. [印度以解放军部署为借口往边境增兵](https://so.toutiao.com/search?keyword=%E5%8D%B0%E5%BA%A6%E4%BB%A5%E8%A7%A3%E6%94%BE%E5%86%9B%E9%83%A8%E7%BD%B2%E4%B8%BA%E5%80%9F%E5%8F%A3%E5%BE%80%E8%BE%B9%E5%A2%83%E5%A2%9E%E5%85%B5)
1. [国考笔试实际参考142.2万人](https://so.toutiao.com/search?keyword=%E5%9B%BD%E8%80%83%E7%AC%94%E8%AF%95%E5%AE%9E%E9%99%85%E5%8F%82%E8%80%83142.2%E4%B8%87%E4%BA%BA)
1. [斯诺克英锦赛：丁俊晖失利止步次轮](https://so.toutiao.com/search?keyword=%E6%96%AF%E8%AF%BA%E5%85%8B%E8%8B%B1%E9%94%A6%E8%B5%9B%EF%BC%9A%E4%B8%81%E4%BF%8A%E6%99%96%E5%A4%B1%E5%88%A9%E6%AD%A2%E6%AD%A5%E6%AC%A1%E8%BD%AE)
1. [大衣哥儿媳陈亚男发长文恳求原谅](https://so.toutiao.com/search?keyword=%E5%A4%A7%E8%A1%A3%E5%93%A5%E5%84%BF%E5%AA%B3%E9%99%88%E4%BA%9A%E7%94%B7%E5%8F%91%E9%95%BF%E6%96%87%E6%81%B3%E6%B1%82%E5%8E%9F%E8%B0%85)
1. [小学校长涉嫌诈骗超5000万](https://so.toutiao.com/search?keyword=%E5%B0%8F%E5%AD%A6%E6%A0%A1%E9%95%BF%E6%B6%89%E5%AB%8C%E8%AF%88%E9%AA%97%E8%B6%855000%E4%B8%87)
1. [吃饭前用开水烫碗筷真能消毒吗](https://so.toutiao.com/search?keyword=%E5%90%83%E9%A5%AD%E5%89%8D%E7%94%A8%E5%BC%80%E6%B0%B4%E7%83%AB%E7%A2%97%E7%AD%B7%E7%9C%9F%E8%83%BD%E6%B6%88%E6%AF%92%E5%90%97)
1. [闻榴莲上热搜的“当事狗”找到了](https://so.toutiao.com/search?keyword=%E9%97%BB%E6%A6%B4%E8%8E%B2%E4%B8%8A%E7%83%AD%E6%90%9C%E7%9A%84%E2%80%9C%E5%BD%93%E4%BA%8B%E7%8B%97%E2%80%9D%E6%89%BE%E5%88%B0%E4%BA%86)
1. [逃犯朱贤健疑曾藏身景区暖气沟](https://so.toutiao.com/search?keyword=%E9%80%83%E7%8A%AF%E6%9C%B1%E8%B4%A4%E5%81%A5%E7%96%91%E6%9B%BE%E8%97%8F%E8%BA%AB%E6%99%AF%E5%8C%BA%E6%9A%96%E6%B0%94%E6%B2%9F)
1. [女子赌气出走24年见到父亲跪地痛哭](https://so.toutiao.com/search?keyword=%E5%A5%B3%E5%AD%90%E8%B5%8C%E6%B0%94%E5%87%BA%E8%B5%B024%E5%B9%B4%E8%A7%81%E5%88%B0%E7%88%B6%E4%BA%B2%E8%B7%AA%E5%9C%B0%E7%97%9B%E5%93%AD)
1. [外媒：捷克总统任命新一届政府总理](https://so.toutiao.com/search?keyword=%E5%A4%96%E5%AA%92%EF%BC%9A%E6%8D%B7%E5%85%8B%E6%80%BB%E7%BB%9F%E4%BB%BB%E5%91%BD%E6%96%B0%E4%B8%80%E5%B1%8A%E6%94%BF%E5%BA%9C%E6%80%BB%E7%90%86)
1. [新冠检测概念股本月表现活跃](https://so.toutiao.com/search?keyword=%E6%96%B0%E5%86%A0%E6%A3%80%E6%B5%8B%E6%A6%82%E5%BF%B5%E8%82%A1%E6%9C%AC%E6%9C%88%E8%A1%A8%E7%8E%B0%E6%B4%BB%E8%B7%83)
1. [西班牙人1-0皇家社会 武磊失单刀](https://so.toutiao.com/search?keyword=%E8%A5%BF%E7%8F%AD%E7%89%99%E4%BA%BA1-0%E7%9A%87%E5%AE%B6%E7%A4%BE%E4%BC%9A%20%E6%AD%A6%E7%A3%8A%E5%A4%B1%E5%8D%95%E5%88%80)
1. [中信证券：新毒株冲击带来布局良机](https://so.toutiao.com/search?keyword=%E4%B8%AD%E4%BF%A1%E8%AF%81%E5%88%B8%EF%BC%9A%E6%96%B0%E6%AF%92%E6%A0%AA%E5%86%B2%E5%87%BB%E5%B8%A6%E6%9D%A5%E5%B8%83%E5%B1%80%E8%89%AF%E6%9C%BA)
1. [男子藏飞机起落架从危地马拉抵美国](https://so.toutiao.com/search?keyword=%E7%94%B7%E5%AD%90%E8%97%8F%E9%A3%9E%E6%9C%BA%E8%B5%B7%E8%90%BD%E6%9E%B6%E4%BB%8E%E5%8D%B1%E5%9C%B0%E9%A9%AC%E6%8B%89%E6%8A%B5%E7%BE%8E%E5%9B%BD)
1. [流浪猫叼幼崽求店主寄养](https://so.toutiao.com/search?keyword=%E6%B5%81%E6%B5%AA%E7%8C%AB%E5%8F%BC%E5%B9%BC%E5%B4%BD%E6%B1%82%E5%BA%97%E4%B8%BB%E5%AF%84%E5%85%BB)
1. [库里给裁判“吹T”](https://so.toutiao.com/search?keyword=%E5%BA%93%E9%87%8C%E7%BB%99%E8%A3%81%E5%88%A4%E2%80%9C%E5%90%B9T%E2%80%9D)
1. [政法系统高规格活动 国安女干警出镜](https://so.toutiao.com/search?keyword=%E6%94%BF%E6%B3%95%E7%B3%BB%E7%BB%9F%E9%AB%98%E8%A7%84%E6%A0%BC%E6%B4%BB%E5%8A%A8%20%E5%9B%BD%E5%AE%89%E5%A5%B3%E5%B9%B2%E8%AD%A6%E5%87%BA%E9%95%9C)
1. [美媒：“黑五”回归但已面目全非](https://so.toutiao.com/search?keyword=%E7%BE%8E%E5%AA%92%EF%BC%9A%E2%80%9C%E9%BB%91%E4%BA%94%E2%80%9D%E5%9B%9E%E5%BD%92%E4%BD%86%E5%B7%B2%E9%9D%A2%E7%9B%AE%E5%85%A8%E9%9D%9E)
1. [林志玲发文庆生](https://so.toutiao.com/search?keyword=%E6%9E%97%E5%BF%97%E7%8E%B2%E5%8F%91%E6%96%87%E5%BA%86%E7%94%9F)
1. [意甲：罗马1-0都灵 亚伯拉罕破门](https://so.toutiao.com/search?keyword=%E6%84%8F%E7%94%B2%EF%BC%9A%E7%BD%97%E9%A9%AC1-0%E9%83%BD%E7%81%B5%20%E4%BA%9A%E4%BC%AF%E6%8B%89%E7%BD%95%E7%A0%B4%E9%97%A8)
1. [郑州禁狗社区称不会强行开门捉狗](https://so.toutiao.com/search?keyword=%E9%83%91%E5%B7%9E%E7%A6%81%E7%8B%97%E7%A4%BE%E5%8C%BA%E7%A7%B0%E4%B8%8D%E4%BC%9A%E5%BC%BA%E8%A1%8C%E5%BC%80%E9%97%A8%E6%8D%89%E7%8B%97)
| 165.589286 | 209 | 0.691793 | yue_Hant | 0.241232 |
dab1c2e88bf04f329bda123fd3e0e573f0c7a2b2 | 30 | md | Markdown | README.md | vanHeemstraSystems/proxies | 9d6399d428f95f39d8ef31c0320e8debc268a4e3 | [
"MIT"
] | null | null | null | README.md | vanHeemstraSystems/proxies | 9d6399d428f95f39d8ef31c0320e8debc268a4e3 | [
"MIT"
] | null | null | null | README.md | vanHeemstraSystems/proxies | 9d6399d428f95f39d8ef31c0320e8debc268a4e3 | [
"MIT"
] | null | null | null | # proxies
The Proxies Subtree
| 10 | 19 | 0.8 | eng_Latn | 0.981015 |
dab54d50e160cfbd7aa43665547f07f025ffef26 | 78 | md | Markdown | utils/README.md | Dvd848/RgEdt | e9371fdbd375e73a31ccd48ec13add9dc85f9a9c | [
"MIT"
] | 3 | 2021-09-07T15:54:04.000Z | 2022-01-16T05:05:18.000Z | utils/README.md | Dvd848/RgEdt | e9371fdbd375e73a31ccd48ec13add9dc85f9a9c | [
"MIT"
] | null | null | null | utils/README.md | Dvd848/RgEdt | e9371fdbd375e73a31ccd48ec13add9dc85f9a9c | [
"MIT"
] | 1 | 2021-10-31T16:11:08.000Z | 2021-10-31T16:11:08.000Z |
# RgEdt Utilities
* `packer`: Create a standalone `*.pyz` file for RgEdt. | 19.5 | 55 | 0.666667 | eng_Latn | 0.435418 |
dab54eb308441688dfc5a302a6d7851a1d9b9a50 | 1,024 | markdown | Markdown | _posts/2020-12-21-Virtual-Machines.markdown | tic0uk/devopsapprentice.com | 77d10338ccd69d48f1d8d097744a9633abcf3d14 | [
"MIT"
] | null | null | null | _posts/2020-12-21-Virtual-Machines.markdown | tic0uk/devopsapprentice.com | 77d10338ccd69d48f1d8d097744a9633abcf3d14 | [
"MIT"
] | null | null | null | _posts/2020-12-21-Virtual-Machines.markdown | tic0uk/devopsapprentice.com | 77d10338ccd69d48f1d8d097744a9633abcf3d14 | [
"MIT"
] | null | null | null | ---
layout: post
title: "Virtual Machines"
date: 2020-12-16 13:27:19 +0000
categories: Homelab
published: false
image: /_pictures/virsh.png
tags: Virtualisation, Hyper-V, Virtualbox, Linux, Windows, homelab
---
The first step to getting to learn Linux is to get a copy installed. I was
hesitant at first as I'd always used Windows, and didn't want to uninstall
my main copy in case I didn't get on with Linux. I also was very aware of the wide
variety of 'flavours' of Linux which meant I could find myself wanting to change
versions at the drop of a hat.
If you're on Windows, the two I'd recommend for getting started are 'hyper-v'
or Virtualbox. To the beginner, I'd recommend going with Virtualbox to get
your first introduction to creating
At some point when you are studying Linux, you'll make the wise decision to
stop installing and testing things on your primary Operating System.
<div><a id="l" href="/about"><< Return to About</a> <a id="r" href="/mystory/part2">Continue to Part 2 >></a></div>
<br>
| 40.96 | 120 | 0.75 | eng_Latn | 0.995789 |
dab5a1bb1afab8ea5469f8695a36f0598a23c64a | 15 | md | Markdown | README.md | RCML2016/PCA-and-T_SNE | f519b998bc6f0c54b2aaa1e4e34381d10d65e509 | [
"Apache-2.0"
] | null | null | null | README.md | RCML2016/PCA-and-T_SNE | f519b998bc6f0c54b2aaa1e4e34381d10d65e509 | [
"Apache-2.0"
] | null | null | null | README.md | RCML2016/PCA-and-T_SNE | f519b998bc6f0c54b2aaa1e4e34381d10d65e509 | [
"Apache-2.0"
] | null | null | null | # PCA-and-T_SNE | 15 | 15 | 0.733333 | kor_Hang | 0.842928 |
dab5d394283e0171073265aa7c83a1844a7f868b | 269 | md | Markdown | README.md | iquipsys-positron/iqs-services-objectstates-node | e08c14516224e304dc74700612f9f0a46afee04e | [
"MIT"
] | null | null | null | README.md | iquipsys-positron/iqs-services-objectstates-node | e08c14516224e304dc74700612f9f0a46afee04e | [
"MIT"
] | null | null | null | README.md | iquipsys-positron/iqs-services-objectstates-node | e08c14516224e304dc74700612f9f0a46afee04e | [
"MIT"
] | null | null | null | # <img src="https://github.com/pip-services/pip-services/raw/master/design/Logo.png" alt="Pip.Services Logo" style="max-width:30%"> <br/> Object states microservice
This is the states microservice for iQuipsys tracker.
It records history of object state transitions.
| 53.8 | 164 | 0.773234 | eng_Latn | 0.800091 |
dab5deee0e8838c23768d3c5efde01e766c5cc96 | 95 | md | Markdown | README.md | neekey/demos | 4ff729760b014c9d8a265d34785d6d93c81c4522 | [
"MIT"
] | null | null | null | README.md | neekey/demos | 4ff729760b014c9d8a265d34785d6d93c81c4522 | [
"MIT"
] | null | null | null | README.md | neekey/demos | 4ff729760b014c9d8a265d34785d6d93c81c4522 | [
"MIT"
] | null | null | null | # demos
Using `gh-pages` branch to server demos, [take a look](http://neekey.github.io/demos)
| 23.75 | 85 | 0.715789 | eng_Latn | 0.581215 |
dab60632ec586e23b0ea6a3fb999661be4152808 | 1,627 | md | Markdown | _posts/2011-09-12-quick_sort.md | pensz/pensz.github.io | 2b6ab93f7545a61e89422b50c453fb7e35a341a4 | [
"CC-BY-4.0"
] | null | null | null | _posts/2011-09-12-quick_sort.md | pensz/pensz.github.io | 2b6ab93f7545a61e89422b50c453fb7e35a341a4 | [
"CC-BY-4.0"
] | null | null | null | _posts/2011-09-12-quick_sort.md | pensz/pensz.github.io | 2b6ab93f7545a61e89422b50c453fb7e35a341a4 | [
"CC-BY-4.0"
] | null | null | null | ---
layout: post
status: publish
published: true
title: "快速排序"
author:
display_name: pensz
login: pensz
email: email
url: ''
author_login: pensz
author_email: email
wordpress_id: 169
wordpress_url: http://www.zwsun.com/?p=169
date: '2011-09-12 23:55:52 +0000'
date_gmt: '2011-09-12 15:55:52 +0000'
categories:
- "技术记录"
- "数据结构和算法"
tags:
- c++
- "快速排序"
---
<p>快速排序是分治法的思想，先设定一个标志，保证左边的数据不大于该标志，右边的数据都不小于该标志。然后分别对左右区域使用同样的处理方法，最终得到的序列即为有序序列。</p>
<p>下面是 c++ 的快速排序。</p>
<pre name="code" class="c++">#include <iostream>
using namespace std;
/**
* 调整数据，使得在一个位置左边的数据均小于 pivotkey， 右边的数据均大于 pivotkey
*/
int Partition(int *p, int low, int high) {
int pivotkey = p[low];
while (low < high) {
while (low < high && p[high] > pivotkey) --high;
p[low] = p[high];
while (low < high && p[low] <= pivotkey) ++low;
p[high] = p[low];
}
p[low] = pivotkey;
return low;
}
/**
* 快速排序
*/
void QuickSort(int *p, int begin, int end) {
if (begin < end) {
int pivot;
pivot = Partition(p, begin, end); // 进行一次分区
QuickSort(p, begin, pivot-1); // 对左边的进行快速排序
QuickSort(p, pivot+1, end); // 对右边进行快速排序
}
}
int main() {
int i, length, *p;
cin >> length;
p = (int *) malloc (length * sizeof(int));
for (i=0; i<length; ++i) {
cin >> p[i];
}
cout << "original" << endl;
for (i=0; i<length; ++i) {
cout << p[i] << endl;
}
QuickSort(p, 0, length-1);
cout << "sorted" << endl;
for (i=0; i<length; ++i) {
cout << p[i] << endl;
}
return 0;
}</pre>
| 19.841463 | 87 | 0.595575 | eng_Latn | 0.260948 |
dab80d46215953b156013ba01c677f5e9235074f | 1,782 | md | Markdown | README.md | mikethemage/BESM3CA | f9b7490eedd1139e75f3012d70c63f2d6392d6e7 | [
"MIT"
] | null | null | null | README.md | mikethemage/BESM3CA | f9b7490eedd1139e75f3012d70c63f2d6392d6e7 | [
"MIT"
] | 4 | 2021-09-17T23:31:34.000Z | 2021-11-30T14:01:54.000Z | README.md | mikethemage/BESM3CA | f9b7490eedd1139e75f3012d70c63f2d6392d6e7 | [
"MIT"
] | null | null | null | # BESM 3rd Edition Character Assistant
**BESM3CA** is a character creator for the third edition of the BESM (Big Eyes, Small Mouth) roleplaying game. It is currently a 64-bit Windows application using .Net 6.0. Supported operating systems are Windows 7 x64 and higher.
Files can be saved in _.xml_ format which can be reloaded later, or exported to _.txt_ for easier reading/manual formatting/printing etc.
The full list of 3rd Edition BESM character options are all enabled and supported and will calculate the relevant point costs accordingly.
This project is currently in development and therefore further features are planned but not yet available including:
* Printing/formatted text output
* Calculation of derived values/effects from attibutes
* Cross-platform support
* Alternate editions of BESM (e.g. 4th edition) or alternate RPG systems
Inspired by, but **not** based on or in anyway affiliated with _[BESMCG](http://www.technofetish.net/index.html)_, a character editor for BESM 2nd Edition.
**Links:**
* [Download latest release(s)](https://github.com/mikethemage/BESM3CA/releases)
* [Official BESM Website (4th Edition)](https://BESM4.life)
* [Buy BESM 3rd Edition here (PDF - DriveThruRPG)](https://www.drivethrurpg.com/product/24482/BESM-Big-Eyes-Small-Mouth-3rd-Edition)
\
Build Status: 
\
\
**Disclaimer:**\
"BESM" / "Big Eyes Small Mouth" is a trademark of White Wolf Entertainment AB and licensed by Dyskami Publishing Company. This application is not endorsed by or associated with White Wolf Entertainment AB or Dyskami Publishing Company in any way. This is a non-profit fan-made utility intended to help players in conjuction with official source materials.
| 59.4 | 357 | 0.783951 | eng_Latn | 0.982441 |
dab90f984e2ea39cfed9e1b58c0b43c0d91949da | 6,606 | md | Markdown | README.md | jaspreet-singh-sahota/Slack-bot | 155aa9fa6c36cf1225db0304b32e9f769d0d6865 | [
"MIT"
] | 6 | 2020-03-29T21:51:27.000Z | 2020-07-03T15:31:41.000Z | README.md | jaspreet-singh-sahota/Slack-bot | 155aa9fa6c36cf1225db0304b32e9f769d0d6865 | [
"MIT"
] | 3 | 2020-03-31T16:19:53.000Z | 2022-03-31T01:02:20.000Z | README.md | jaspreet-singh-sahota/Slack-bot | 155aa9fa6c36cf1225db0304b32e9f769d0d6865 | [
"MIT"
] | 2 | 2020-03-31T10:01:23.000Z | 2020-04-24T16:33:22.000Z | <!--
*** Thanks for checking out this README Template. If you have a suggestion that would
*** make this better, please fork the repo and create a pull request or simply open
*** an issue with the tag "enhancement".
*** Thanks again! Now go create something AMAZING! :D
-->
<!-- PROJECT SHIELDS -->
<!--
*** I'm using markdown "reference style" links for readability.
*** Reference links are enclosed in brackets [ ] instead of parentheses ( ).
*** See the bottom of this document for the declaration of the reference variables
*** for contributors-url, forks-url, etc. This is an optional, concise syntax you may use.
*** https://www.markdownguide.org/basic-syntax/#reference-style-links
-->
[![Contributors][contributors-shield]][contributors-url]
[![Forks][forks-shield]][forks-url]
[![Stargazers][stars-shield]][stars-url]
[![Issues][issues-shield]][issues-url]
<!-- PROJECT LOGO -->
<br />
<p align="center">
<a href="https://github.com/jaspreet-singh-sahota/Slack-bot">
<img src="https://course_report_production.s3.amazonaws.com/rich/rich_files/rich_files/5726/s300/icon-white-on-murple-copy.png" alt="Logo" width="80" height="80">
</a>
<h3 align="center">Slack Bot</h3>
<p align="center">
This is the Microverse Capstone Project.
<br />
<a href="https://github.com/jaspreet-singh-sahota/Slack-bot/issues">Report Bug</a>
·
<a href="https://github.com/jaspreet-singh-sahota/Slack-bot/issues">Request Feature</a>
</p>
</p>
<!-- TABLE OF CONTENTS -->
## Table of Contents
* [About the Project](#about-the-project)
* [How it works](#How-it-works)
* [Built With](#built-with)
* [Contact](#Authors)
* [Acknowledgements](#acknowledgements)
<!-- ABOUT THE PROJECT -->
## About The Project
This is the Microverse Ruby Capstone Project. In this project I have build a Slack bot.
Feature of the Slack Bot are :-
- Weather updates
- Stats for the COVID-19 for each country
- Random quotes
## LIVE VIDEO
https://www.loom.com/share/fb91dc440b42439688cc3fd1708411a5
### Setup
In order to test Stackbot you will need to create a [Slack APP](https://slack.com/create#email). Once you've created the app, configure it as a bot and install it to your preferred Slack workspace. Don't forget to save it's API token somewhere. You will need the token in order to test the bot.
### Install
To test Stack bot locally, clone the repository, navigate to it's containing directory, and run:
#### Clone the repository and follow the steps to run the bot.
```bash
git clone [email protected]:jaspreet-singh-sahota/Slack-bot.git
cd Slack-bot
bundle install
echo 'SLACK_API_TOKEN=your_token_here' > .env
rackup
```
This should install all ruby gems, generate an .env file containing the API token from the Setup, and start a local server where Stackbot will live.
Then you can run the command `rackup` in your terminial to active this bot.
<!-- HOW IT WORKS -->
## How It Works
You can log into the Slack workspace where you installed it and invite it to your channel by typing `/invite @Stackbot`.
Then typing `@slack-ruby-bot help` in your slack channel will display all the available commands: -
<p align="center"> <img src="https://user-images.githubusercontent.com/55361440/77954409-32e5f100-72ec-11ea-8685-3e60d35f3ccb.png" </p>
### Commands
- `@slack-ruby-bot say_hello` will say hi to the user.
<p align="center"> <img src="https://user-images.githubusercontent.com/55361440/77954628-8a845c80-72ec-11ea-86a1-57eaa01e1cc4.png"> </p>
- `@slack-ruby-bot weather_report` will return the basic weather report.
<p align="center"> <img src="https://user-images.githubusercontent.com/55361440/77966091-03d97a80-7300-11ea-9ad1-41b424d6646a.png" </p>
- `@slack-ruby-bot quotes` will return the Quote with the Author's name.
<p align="center"> <img src="https://user-images.githubusercontent.com/55361440/77966321-692d6b80-7300-11ea-8f0c-dde09cd097cc.png" </p>
- `@slack-ruby-bot covid_current_data` will return the current data of COVID-19
<p align="center">
<img src="https://user-images.githubusercontent.com/55361440/77966774-549da300-7301-11ea-94cf-0a4f7245cdf3.png" </p>
- `@slack-ruby-bot covid_world_data` will return the COVID-19 data of 256 countries.
<p align="center"> <img src="https://user-images.githubusercontent.com/55361440/77966925-af36ff00-7301-11ea-83ce-f7b0d02cd3b4.png" </p>
#### But what if you want the data of a particular country, you can also do that:-
- Mention the country name after the covid like this `@slack-ruby-bot covid India`.
<p align="center"> <img src="https://user-images.githubusercontent.com/55361440/77967396-a561cb80-7302-11ea-8ddc-855d15a4db85.png" </p>
<!-- BUILD WITH -->
## Built With
This project was built using these technologies.
* Ruby
* Rubocop
* VsCode
* Rspec
# Testing
```bash
bundle exec rspec
```
<!-- CONTACT -->
## Authors
👤 **Jaspreet Singh**
- [LinkedIn](https://www.linkedin.com/in/jaspreet-singh-a28286146/)
- [GitHub](https://github.com/jaspreet-singh-sahota)
- [E-mail]([email protected])
- [Portfolio](https://jaspreet-singh-portfolio.netlify.app/)
<!-- ACKNOWLEDGEMENTS -->
## Acknowledgements
* [Microverse](https://www.microverse.org/)
* [Ruby Documentation](https://www.ruby-lang.org/en/documentation/)
* [Slack Ruby Bot](https://github.com/slack-ruby/slack-ruby-bot)
* [covid19_data_ruby](https://github.com/jaerodyne/covid19-data-ruby)
* used gem `httparty`
* [Oscar Mier](https://github.com/voscarmv)
## Show your support
Give a ⭐️ if you like this project!
<!-- MARKDOWN LINKS & IMAGES -->
<!-- https://www.markdownguide.org/basic-syntax/#reference-style-links -->
[contributors-shield]: https://img.shields.io/github/contributors/jaspreet-singh-sahota/Slack-bot.svg?style=flat-square
[contributors-url]: https://github.com/jaspreet-singh-sahota/Slack-bot/graphs/contributors
[forks-shield]: https://img.shields.io/github/forks/rammazzoti2000/tic-toc-toe.svg?style=flat-square
[forks-url]: https://github.com/jaspreet-singh-sahota/Slack-bot/network/members
[stars-shield]: https://img.shields.io/github/stars/rammazzoti2000/tic-toc-toe.svg?style=flat-square
[stars-url]: https://github.com/jaspreet-singh-sahota/Slack-bot/stargazers
[issues-shield]: https://img.shields.io/github/issues/rammazzoti2000/tic-toc-toe.svg?style=flat-square
[issues-url]: https://github.com/jaspreet-singh-sahota/Slack-bot/issues
## 📝 License
This project is [MIT](https://opensource.org/licenses/MIT) licensed.
| 37.534091 | 294 | 0.735089 | eng_Latn | 0.507881 |
dab9be2edbd600553738ba7aeb0fd4fb1e185620 | 450 | md | Markdown | _posts/2020-11-24-Horseshoe-Crab-Gel-Results-9.md | njameral/Ameral_Lab_Notebook | 809a748082cddbdeaf41b176ca974a536251e19e | [
"MIT"
] | null | null | null | _posts/2020-11-24-Horseshoe-Crab-Gel-Results-9.md | njameral/Ameral_Lab_Notebook | 809a748082cddbdeaf41b176ca974a536251e19e | [
"MIT"
] | null | null | null | _posts/2020-11-24-Horseshoe-Crab-Gel-Results-9.md | njameral/Ameral_Lab_Notebook | 809a748082cddbdeaf41b176ca974a536251e19e | [
"MIT"
] | null | null | null | ---
layout: post
title: Horseshoe Crab Agarose Gel Results
category: []
tags: [Horseshoe crab, DNA]
---
## Horseshoe Crab Agarose Gel
Date Performed: November 24th, 2020\
Samples run: 414-416, 419, 420, 421, 422, 424, 497, 498, 787-790, 802, 803, 371, 372, 073
Ran samples following [gel protocol](https://njameral.github.io/Ameral_Lab_Notebook/Horseshoe-Crab-Gel_Protocol/)
| 32.142857 | 113 | 0.74 | eng_Latn | 0.124601 |
daba42e5dc9362ff7f327fe26f691a28e6896ad4 | 606 | md | Markdown | docs/index.Woodfield-1994.md | guillaumedescoteauxisabelle/ma-biblio | 9d7ed8cb09b3ec7af8815518be7b517848a7ea3c | [
"MIT"
] | null | null | null | docs/index.Woodfield-1994.md | guillaumedescoteauxisabelle/ma-biblio | 9d7ed8cb09b3ec7af8815518be7b517848a7ea3c | [
"MIT"
] | null | null | null | docs/index.Woodfield-1994.md | guillaumedescoteauxisabelle/ma-biblio | 9d7ed8cb09b3ec7af8815518be7b517848a7ea3c | [
"MIT"
] | null | null | null |
----
# Woodfield-1994
## [Woodfield-1994.all.html](Woodfield-1994.all.html)
## [Woodfield-1994.ht.all.html](Woodfield-1994.ht.all.html)
## [Woodfield-1994.pol.fc.html](Woodfield-1994.pol.fc.html)
## [Woodfield-1994.pol.r.html](Woodfield-1994.pol.r.html)
## [Woodfield-1994.sag.html](Woodfield-1994.sag.html)
## [Woodfield-1994.sag.j.html](Woodfield-1994.sag.j.html)
## [Woodfield-1994.sag.l.html](Woodfield-1994.sag.l.html)
## [Woodfield-1994.sag.ndl.html](Woodfield-1994.sag.ndl.html)
## [Woodfield-1994.sag.q.html](Woodfield-1994.sag.q.html)
## [Woodfield-1994.sag.r.html](Woodfield-1994.sag.r.html)
| 35.647059 | 61 | 0.721122 | yue_Hant | 0.75386 |
dabb58f2b266e2f5da111c56795d1d4cdfb09b53 | 101 | md | Markdown | README.md | buptliuhs/test | 7819eb74f1251f893eef4e7b65736a9afdd494a2 | [
"Apache-2.0"
] | null | null | null | README.md | buptliuhs/test | 7819eb74f1251f893eef4e7b65736a9afdd494a2 | [
"Apache-2.0"
] | 1 | 2018-04-19T22:55:39.000Z | 2018-04-19T22:55:39.000Z | README.md | buptliuhs/test | 7819eb74f1251f893eef4e7b65736a9afdd494a2 | [
"Apache-2.0"
] | null | null | null | # test
Here is something new.
here is another thing.
again!
aaaa
aaaaaaa
aaaa
Fix a bug here.
| 6.3125 | 22 | 0.70297 | nld_Latn | 0.451924 |
dabbb598d6667dd782023851e85b5d443e57e6df | 81 | md | Markdown | _posts/0000-01-02-duendeborah.md | duendeborah/github-slideshow | 94bec72b52a66dc1a5afb8604c33b290b5ac30f3 | [
"MIT"
] | null | null | null | _posts/0000-01-02-duendeborah.md | duendeborah/github-slideshow | 94bec72b52a66dc1a5afb8604c33b290b5ac30f3 | [
"MIT"
] | 3 | 2020-09-26T23:51:46.000Z | 2020-09-27T01:21:12.000Z | _posts/0000-01-02-duendeborah.md | duendeborah/github-slideshow | 94bec72b52a66dc1a5afb8604c33b290b5ac30f3 | [
"MIT"
] | null | null | null | ---
layout: slide
title: "Welcome to out second slide!"
---
**Welcome there!**
| 11.571429 | 37 | 0.62963 | eng_Latn | 0.981834 |
dabbe58bac168760e9d4632f91a5685634261e02 | 552 | md | Markdown | CONTRIBUTING.md | bhavesh-chaudhari/starter | e1af71f1348bf81def53bcf8f97764faa5cf9f5c | [
"MIT"
] | null | null | null | CONTRIBUTING.md | bhavesh-chaudhari/starter | e1af71f1348bf81def53bcf8f97764faa5cf9f5c | [
"MIT"
] | null | null | null | CONTRIBUTING.md | bhavesh-chaudhari/starter | e1af71f1348bf81def53bcf8f97764faa5cf9f5c | [
"MIT"
] | 1 | 2021-12-02T11:55:36.000Z | 2021-12-02T11:55:36.000Z | ## Contributing
1. Fork the repository
2. Clone your Fork
```sh
git clone [email protected]:<your_username>/starter.git
```
3. Create a new branch
```sh
git checkout -b <branch-name> # Create a new branch and check it out
```
4. Follow this [`tutorial`]() .
5. Add your changes once the tutorial is done
```sh
git add .
```
6. See your staged changes
```sh
git status
```
7. Commit your Changes
```sh
git commit -m <write commit message inside quotes>
```
8. Push to the Branch
```sh
git push -u origin <branch-name>
```
9. Open a Pull Request
| 14.526316 | 68 | 0.675725 | eng_Latn | 0.966289 |
dabce663b3e783daf7f63033eea371a78de179cb | 1,636 | md | Markdown | website/sections/cross-validation.md | omertarik96/datasciencenotes | 4b107fe674418e55291a10e44f044845bfb138f8 | [
"MIT"
] | null | null | null | website/sections/cross-validation.md | omertarik96/datasciencenotes | 4b107fe674418e55291a10e44f044845bfb138f8 | [
"MIT"
] | 8 | 2021-03-01T20:28:10.000Z | 2022-02-26T11:52:07.000Z | website/sections/cross-validation.md | omertarikkoc/datasciencenotes | 4b107fe674418e55291a10e44f044845bfb138f8 | [
"MIT"
] | null | null | null | ---
prev: ./linear-regression
next: ./logistic-regression
---
```python
# Original code example can be found at: https://scikit-learn.org/stable/modules/cross_validation.html
# Import necessary libraries
import numpy as np
from sklearn.model_selection import train_test_split
from sklearn import datasets
from sklearn import svm
from sklearn.model_selection import cross_val_score
# Load Iris data set
iris = datasets.load_iris()
iris.data.shape, iris.target.shape
# Split the data to test and train data set
# 0.4 ratio is used for this split
X_train, X_test, y_train, y_test = train_test_split(
iris.data, iris.target, test_size=0.4, random_state=0)
# Check the shapes of the training and test data
print(f"X_train_shape: {X_train.shape}, y_train_shape: {y_train.shape}")
print(f"X_test.shape: {X_test.shape}, y_test.shape: {y_test.shape}")
# We can now quickly sample a training set while holding out 40% of the data for testing (evaluating) our classifier:
clf = svm.SVC(kernel='linear', C=1).fit(X_train, y_train)
print(f"clf score: {clf.score(X_test, y_test)}")
# The simplest way to use cross-validation is to call the cross_val_score helper function on the estimator and the dataset.
clf = svm.SVC(kernel='linear', C=1)
scores = cross_val_score(clf, iris.data, iris.target, cv=5)
print(f"Cross validation score: {scores}")
```
<iframe height="800px" width="100%" src="https://repl.it/@omertarik96/cross-validation?lite=true" scrolling="no" frameborder="no" allowtransparency="true" allowfullscreen="true" sandbox="allow-forms allow-pointer-lock allow-popups allow-same-origin allow-scripts allow-modals"></iframe> | 43.052632 | 286 | 0.765281 | eng_Latn | 0.816446 |
dabcfd71cd49751963d74acfd41a9ac51c4730dc | 1,305 | md | Markdown | README.md | 128na/simutrans-dat-parser | 82c1e2c8f487e42ac9b133fb386f8af66f5cb937 | [
"MIT"
] | null | null | null | README.md | 128na/simutrans-dat-parser | 82c1e2c8f487e42ac9b133fb386f8af66f5cb937 | [
"MIT"
] | null | null | null | README.md | 128na/simutrans-dat-parser | 82c1e2c8f487e42ac9b133fb386f8af66f5cb937 | [
"MIT"
] | null | null | null | # Simutrans dat file parser
A dat file parser for Simutrans.
## Install
```
npm i simutrans-dat-parser
```
## Usecase
### Parse from dat text
```
import { Dat } from 'simutrans-dat-parser';
const text = `obj=way
name=example1
waytype=road
---
obj=way
name=example2
waytype=track`;
const dat = new Dat(text);
dat.objs[0].findParam('waytype').value;
// 'road'
```
### Parse from single obj text
```
import { Obj } from 'simutrans-dat-parser';
const text = `obj=way
name=example1
waytype=road`;
const obj = new Obj(text);
obj.findParam('waytype').value;
// 'road'
```
### Manipulate values
```
import { Obj } from 'simutrans-dat-parser';
const text = `obj=way
name=example1
waytype=road
image[0][1]=example.3.4,5,6`;
const obj = new Obj(text);
const param = obj.findParam('image');
param.key
// 'image[0][1]'
param.keyVal
// 'image'
param.keyParams
// [0, 1]
param.value
// 'example.3.4,5,6'
param.valueVal
// 'example'
param.valueParams
// ['3','4','5','6']
param.isEmpty
// false
param.isComment
// false
param.isSplit
// false
param.toString()
// 'image[0][1]=example.3.4,5,6';
```
### Modify parameters
```
import { Obj } from 'simutrans-dat-parser';
const text = `obj=way
name=example1
waytype=road`;
const obj = new Obj(text);
obj.updateOrCreate('copyright', 'example')
```
| 13.181818 | 43 | 0.661303 | eng_Latn | 0.246053 |
dabd1b611c0fccbe8b9599fd479a5b9fb9323f5c | 2,569 | md | Markdown | motion-arm/README.md | lichtwellenreiter/dockerfiles | bad31b1dafffdf95cfc7a83c7f012ae80245b501 | [
"MIT"
] | null | null | null | motion-arm/README.md | lichtwellenreiter/dockerfiles | bad31b1dafffdf95cfc7a83c7f012ae80245b501 | [
"MIT"
] | null | null | null | motion-arm/README.md | lichtwellenreiter/dockerfiles | bad31b1dafffdf95cfc7a83c7f012ae80245b501 | [
"MIT"
] | null | null | null | motion-arm
==========
[Motion][1] is a program that monitors the video signal from one or more cameras
and is able to detect if a significant part of the picture has changed. Or in
other words, it can detect motion.
## docker-compose.yml
```yaml
motion:
image: easypi/motion-arm
ports:
- "8080:8080"
- "8081:8081"
volumes:
- ./motion.conf:/etc/motion/motion.conf
- ./data:/var/lib/motion
- /etc/localtime:/etc/localtime
devices:
- /dev/video0:/dev/video0
restart: always
```
You can edit `motion.conf` to customize motion.
```ini
# set image width
width 640
# set image height
height 480
# set frame rate
framerate 5
# disable image output
output_pictures off
# disable video output
ffmpeg_output_movies off
# encode timelapse movie
ffmpeg_timelapse 60
```
Motion can work with Home-Assistant via [External Commands][2].
``yaml
binary_sensor:
- platform: mqtt
name: Motion
state_topic: /pi/sensor/motion
qos: 0
payload_on: ON
payload_off: OFF
device_class: motion
```
```bash
# Command to be executed when a movie file (.mpg|.avi) is created. (default: none)
# To give the filename as an argument to a command append it with %f
# CURL
;on_movie_start curl -s -H 'X-HA-Access: ******' -H 'Content-Type: application/json' -d '{"state": "on", "attributes": {"friendly_name": "Motion", "device_class": "motion"}}' http://hass.easypi.pro:8123/api/states/binary_sensor.motion
# MQTT
;on_movie_start mosquitto_pub -h mqtt.easypi.pro -u username -P password -r -t /pi/sensor/motion -m ON
# Command to be executed when a movie file (.mpg|.avi) is closed. (default: none)
# To give the filename as an argument to a command append it with %f
# CURL
;on_movie_end curl -s -H 'X-HA-Access: ******' -H 'Content-Type: application/json' -d '{"state": "off", "attributes": {"friendly_name": "Motion", "device_class": "motion"}}' http://hass.easypi.pro:8123/api/states/binary_sensor.motion
# MQTT
;on_movie_end mosquitto_pub -h mqtt.easypi.pro -u username -P password -r -t /pi/sensor/motion -m OFF
```
Please read [this][3] to enable raspberry pi camera module.
```
####################
# /boot/config.txt #
####################
##Camera
gpu_mem=128
start_file=start_x.elf
fixup_file=fixup_x.dat
disable_camera_led=1
```
[1]: http://lavrsen.dk/foswiki/bin/view/Motion/WebHome
[2]: http://www.lavrsen.dk/foswiki/bin/view/Motion/ExternalCommands
[3]: https://wiki.archlinux.org/index.php/Raspberry_Pi#Raspberry_Pi_camera_module
| 26.214286 | 234 | 0.698715 | eng_Latn | 0.52804 |
dabd97b8d185a0d61f7d4e94ba470b730bc1a91b | 1,313 | md | Markdown | source/includes/_pagination.md | carlcortright/slate | 6e69dbf6553e06b3039c7d99dfa6f9ffa8573da1 | [
"Apache-2.0"
] | 1 | 2018-11-25T23:46:16.000Z | 2018-11-25T23:46:16.000Z | source/includes/_pagination.md | carlcortright/slate | 6e69dbf6553e06b3039c7d99dfa6f9ffa8573da1 | [
"Apache-2.0"
] | null | null | null | source/includes/_pagination.md | carlcortright/slate | 6e69dbf6553e06b3039c7d99dfa6f9ffa8573da1 | [
"Apache-2.0"
] | 2 | 2018-11-16T16:34:27.000Z | 2019-03-10T22:07:30.000Z | # Pagination
```shell
curl "http://api.paradex.io/v2/orderbook?market=rep-weth&cursor=2018-03-09T02:50:27Z&per_page=75"
-H "HTTP_API_KEY: <your-api-key>"
```
```javascript
{
'version': '2.0'
'type': 'request',
'target': 'orderbook',
'method': 'GET',
'id': 1,
'api_key': '<your-api-key>',
'params': [
'market': 'rep-weth',
'cursor': '2018-03-09T02:50:27Z',
'per_page': 75
]
}
```
Several endpoints on the Paradex API are paginated over both HTTP and websocket. Pagination on Paradex works by ordering all records descending based on when the records were created. This means all orders are returned in the order they were placed on the orderbook etc.
Each time a request is made to a pagination endpoint, an optional `per_page` and `cursor` can be included. This specifies how many records to include and where in the sequence to start. The maximum page limit for each request is `100` objects.
When a request is made to one of these endpoints the response will includes a `next_cursor` field. When this cursor is passed to the `cursor` field in the next request it returns the next page. When all of the records have been traversed, the api will return `-1` for the next cursor. If this is passed back into the next request, the API will start from the beginning.
| 42.354839 | 370 | 0.718203 | eng_Latn | 0.998889 |
dabe2f880ca1518b92aaa4bbdb334a6f3d65c352 | 160 | md | Markdown | README.md | ssdhaliwal/LearnReact | b378e9b5f29b6f34a8221c8518a5603824d219ab | [
"MIT"
] | null | null | null | README.md | ssdhaliwal/LearnReact | b378e9b5f29b6f34a8221c8518a5603824d219ab | [
"MIT"
] | null | null | null | README.md | ssdhaliwal/LearnReact | b378e9b5f29b6f34a8221c8518a5603824d219ab | [
"MIT"
] | null | null | null | # LearnReact
My examples for learning react
This is a practice project.... (not complete)
Contacts List
- Title
- Search Bar (like phones)
- find input
- list | 16 | 45 | 0.7375 | eng_Latn | 0.989857 |
dabeda0a22b062bc56f37b4dc78744b0a0e0f468 | 2,021 | md | Markdown | README.md | SadaleNet/ReadWithYourVoiceApi | f792b9f2bd5efb9007285cb021d4d1d0a7439e24 | [
"BSD-2-Clause"
] | 1 | 2019-02-27T15:03:46.000Z | 2019-02-27T15:03:46.000Z | README.md | SadaleNet/ReadWithYourVoiceApi | f792b9f2bd5efb9007285cb021d4d1d0a7439e24 | [
"BSD-2-Clause"
] | null | null | null | README.md | SadaleNet/ReadWithYourVoiceApi | f792b9f2bd5efb9007285cb021d4d1d0a7439e24 | [
"BSD-2-Clause"
] | null | null | null | # Read with Your Voice (Back-end API)
Read with Your Voice is a website that allows users to record their own voice in [Toki Pona language](http://tokipona.org/). After recording the voice, it's able to synthesize arbitrary Toki Pona text.
This repository contains the back-end of this project. [The repo of the front-end of this project is available here](https://github.com/SadaleNet/ReadWithYourVoice).
# Live Demo
Live demo is available here: [https://voice.sadale.net](https://voice.sadale.net)
# Technical Notes
The back-end of this website is a Node.js script developed with ExpressJS framework.
# Configuration
The configuration is available in private/config.json. The possible configuration parameters are shown below:
`dataDir` (required) - Path to the public data directory. It contains the audio clips of each word and the public metadata of the voice, like the name of the voice. For example, it can be `./private/data`. **If you're using an external server to serve the content of this directory, be sure to disable ranged HTTP request. Otherwise the audio files may only get partially loaded on the client side**
`privateDataDir` (required) - Path to the private data directory. It contains the raw audio clips and the private metadata of the voice, like the token of the voice. For example, it can be `./private/data-private`
`domain` (required) - The domain name of the front-end website. It's used for CORS handling.
`port` (required) - The port that the server would be listening to. Numeric value.
`captchaSecret` (optional) - the recaptcha secret key. If captcha isn't needed, `captchaSecret` should be removed from the configuration file.
`threshold` (optional) - The silence threshold of audio clips. Defaults to `-35.0`. Any audio lower than this value would be regarded as silence and trimmed.
# Deployment
To perform deployment, run `npm install`. After that, run `node app.js` and that's it.
# License
The files inside this repository is released under BSD 2-clause license.
| 53.184211 | 399 | 0.769421 | eng_Latn | 0.995165 |
dabf8672d06e3f84aaf66055ca8811389c3b1b19 | 6,772 | md | Markdown | lab/08/lab08_d.md | ahmad-fauzan458/TarungLabDDP1 | 1752be6e0baab6df0bf149897ab76136dbe8fbd3 | [
"MIT"
] | 29 | 2018-08-25T11:03:31.000Z | 2022-03-29T08:46:17.000Z | lab/08/lab08_d.md | ahmad-fauzan458/TarungLabDDP1 | 1752be6e0baab6df0bf149897ab76136dbe8fbd3 | [
"MIT"
] | 8 | 2017-10-12T21:42:43.000Z | 2018-06-07T09:14:16.000Z | lab/08/lab08_d.md | ahmad-fauzan458/TarungLabDDP1 | 1752be6e0baab6df0bf149897ab76136dbe8fbd3 | [
"MIT"
] | 12 | 2018-06-28T14:41:23.000Z | 2022-03-26T10:46:58.000Z | # Soal Tutorial
## Pardede Festival
<h5>"<i>Demi target 50 jam bulan ini</i>"</h5>
Benny Pardede maju sebagai project officer PARFEST X, dia punya ide radikal
untuk mendorong performa tiap panitia Parfest agar dapat bekerja secara
optimal. Benny ingin mengelola staf-stafnya dengan mudah, maka dari itu ia
ingin membentuk suatu sistem log panitia yang dapat mengevaluasi pekerjaan para
panitia - panitia tiap divisi. Benny akan menghargai hasil kerja para panitia
berupa BenCoin sesuai hasil jerih payah mereka dan berapa lama pekerjaannya,
tetapi karena dia sedang sibuk, dia meminta kalian para Petarung Koder untuk
membuat sistem tersebut.
### Spesifikasi:
- Template program sudah ada, kalian harus mengimplementasikan class
`StaffAcara`, `StaffPartnership`, `StaffPublikasi` yang menginherit
class `Staff`
- Kalian dilarang mengubah class `Staff` dan class `Manager` template
- Kalian dilarang membuat instance variable (bukan local variable) baru dalam
class `StaffAcara`, `StaffPartnership`, `StaffPublikasi`
- Kalian dilarang membuat dict, set baru di seluruh program selain yang sudah
ada di template
- REVISI: Penggunaan list untuk split input diperbolehkan
- Program menerima input berupa text berupa perintah dari user
- Program akan menerima input terus sehingga menerima perintah untuk berhenti
(***EXIT***)
#### Jenis Perintah:
1. Rekrut staf
Rekrut seseorang untuk menjadi sebuah staf divisi
2. Catat pekerjaan staf
Setiap divisi punya cara kerja yang berbeda-beda, ada divisi yang bekerja
dengan cepat ada juga yang membutuhkan waktu lama. Setiap staf punya
progress masing-masing dan jika seorang staf progress nya sudah lebih dari
atau sama dengan 100% maka dia tidak perlu bekerja lagi
3. Tampilkan informasi staf
Output ke layar nama staf, jumlah jam kerja, jumlah penghasilan sementara
dalam BenCoin, dan juga progress staf
#### Divisi-divisi:
<table>
<tr>
<th>Nama Divisi</th>
<th>Cara Kerja</th>
<th>Cara Perhitungan Gaji</th>
</tr>
<tr>
<td>Acara</td>
<td>Progres pekerjaan akan bertambah sebanyak 4% / jam</td>
<td>Staf akan dibayar sejumlah 2000 BenCoin x persentase progressnya</td>
</tr>
<tr>
<td>Partnership</td>
<td>Progres pekerjaan akan bertambah sebanyak 1% / jam</td>
<td>Staf akan dibayar sejumlah 4000 BenCoin x jam kerja x persentase
progressnya</td>
</tr>
<tr>
<td>Publikasi</td>
<td>Progres pekerjaan akan bertambah sebanyak 20% / jam</td>
<td>Staf akan dibayar sejumlah 1500 BenCoin x jam kerja</td>
</tr>
</table>
<br>
#### Format Masukan:
1. `REKRUT;Nama staf;Divisi`
Rekrut staf baru. Tidak boleh merekrut seorang staf dua kali.
Nama case insensitive
2. `KERJA;Nama staf;Jam`
Staf bekerja selama jam kerja yg diinput.
**Diasumsikan nama staf yang dimasukkan pada input ini telah menjadi staff
dari PARFEST X.**
3. `LOG;Nama staf`
Menampilkan informasi staf.
**Diasumsikan nama staf yang dimasukkan pada input ini telah menjadi staff
dari PARFEST X.**
4. `EXIT`
Program berhenti.
<br>
#### Format Keluaran:
1. `REKRUT`
- Jika orang tersebut belum
<pre><i><b>Nama</b> direkrut</i></pre>
- Jika orang tersebut sudah menjadi bagian dari PARFEST X
<pre><i><b>Nama</b> sudah direkrut sebelumnya</i></pre>
2. `KERJA`
- Jika progress staf belum 100%
<pre><i><b>Nama</b> bekerja selama <b>x</b> jam</i></pre>
- Jika progress sudah 100% keatas
<pre><i><b>Nama</b> sudah mencapai <b>x</b> % progress</i></pre>
3. `LOG`
<pre><i>>> <b>Nama</b>
Telah bekerja selama: <b>x</b> jam
Progress: <b>y</b> persen
Gaji sementara: <b>z</b> bencoin
</i></pre>
<br>
Note:
Kalian tidak perlu menangani case - case yang tidak disebutkan
(e.g. input tidak sesuai format)
<br>
#### Contoh Input:
```
REKRUT;Yudhistira Khairunnisa;PUBLIKASI
REKRUT;Nabila Wisesa;PARTNERSHIP
REKRUT;Asel Ridwan;ACARA
REKRUT;Ahmad Tegar;PUBLIKASI
REKRUT;Asel Ridwan;PARTNERSHIP
KERJA;Yudhistira Khairunnisa;6
KERJA;Nabila Wisesa;6
KERJA;Nabila Wisesa;6
KERJA;Ahmad Tegar;4
KERJA;Asel Ridwan;5
KERJA;Nabila Wisesa;2
KERJA;Ahmad Tegar;6
KERJA;Yudhistira Khairunnisa;8
LOG;Yudhistira Khairunnisa
LOG;Nabila Wisesa
LOG;Asel Ridwan
LOG;Ahmad Tegar
EXIT
```
<br>
#### Contoh Output:
```
Yudhistira Khairunnisa direcruit
Nabila Wisesa direcruit
Asel Ridwan direcruit
Ahmad Tegar direcruit
Asel Ridwan sudah direkrut sebelumnya
Yudhistira Khairunnisa bekerja selama 6 jam
Nabila Wisesa bekerja selama 6 jam
Nabila Wisesa bekerja selama 6 jam
Ahmad Tegar bekerja selama 4 jam
Asel Ridwan bekerja selama 5 jam
Nabila Wisesa bekerja selama 2 jam
NN - YE - AHAhmad Tegar bekerja selama 6 jam
Yudhistira Khairunnisa sudah mencapai 120 % progress
>> Yudhistira Khairunnisa
Telah bekerja selama: 6 jam
Progress: 120 persen
Gaji Sementara: 9000 bencoin
>> Nabila Wisesa
Telah bekerja selama: 14 jam
Progress: 14 persen
Gaji Sementara: 784000 bencoin
>> Asel Ridwan
Telah bekerja selama: 5 jam
Progress: 20 persen
Gaji Sementara: 40000 bencoin
>> Ahmad Tegar
Telah bekerja selama: 10 jam
Progress: 200 persen
Gaji Sementara: 15000 bencoin
```
Penjelasan:
- Yudhistira Khairunnisa berhasil menjadi staff Publikasi.
- Nabila Wisesa berhasil menjadi staff Partnership.
- Asel Ridwan berhasil menjadi staff Acara.
- Ahmad Tegar berhasil menjadi staff Publikasi.
- Asel Ridwan gagal menjadi staff Partnership dikarenakan sudah menjadi staff Acara.
- Yudhistira Khairunnisa berhasil bekerja selama 6 jam.
- Nabila Wisesa berhasil bekerja selama 6 jam.
- Nabila Wisesa berhasil bekerja selama 6 jam.
- Ahmad Tegar berhasil bekerja selama 4 jam.
- Asel Ridwan berhasil bekerja selama 5 jam.
- Nabila Wisesa berhasil bekerja selama 2 jam.
- Ahmad Tegar bekerja selama 6 jam.
- Yudhistira Khairunnisa tidak dapat bekerja lagi dikarenakan telah memiliki
progress `120% (6 jam * 20%)`.
- Yudhistira Khairunnisa adalah staff Publikasi. Dia berhasil bekerja selama
6 jam. Progress yang telah dia lakukan adalah `6 * 20% = 120%`. Gaji yang dia
dapatkan adalah `6 * 1500 = 9000` BenCoin.
- Nabila Wisesa adalah staff Partnership. Dia berhasil bekerja selama 14 jam.
Progress yang telah dia lakukan adalah `14 * 1% = 14%`. Gaji yang dia
dapatkan adalah `14 * 14 * 4000 = 784000` BenCoin.
- Asel Ridwan adalah staff Acara. Dia berhasil bekerja selama 5 jam. Progress
yang telah dia lakukan adalah `5 * 4% = 20%`. Gaji yang dia dapatkan adalah
`20 * 2000 = 40000` BenCoin.
- Ahmad Tega adalah staff Publikasi. Dia berhasil bekerja selama 10 jam.
Progress yang telah dia lakukan adalah `10 * 20% = 200%`. Gaji yang dia
dapatkan `10 * 1500 = 15000` BenCoin.
<br>
**NN - YE - AH**
---
Diambil dari `Soal Tutorial Lab 8 - Kelas D (Revisi 1).pdf` (Tutorial Lab 8
DDP1 D -- 17 November 2017)
| 30.642534 | 84 | 0.744979 | ind_Latn | 0.917666 |
dabf99434203209f2f5e33b09df2213c3c5b3dcc | 49 | md | Markdown | README.md | sami602/FlapperNews | 932535224b68934697e2d884e483429725d2a8b5 | [
"MIT"
] | null | null | null | README.md | sami602/FlapperNews | 932535224b68934697e2d884e483429725d2a8b5 | [
"MIT"
] | null | null | null | README.md | sami602/FlapperNews | 932535224b68934697e2d884e483429725d2a8b5 | [
"MIT"
] | null | null | null | # FlapperNews
Especially made for Reza & Roy
| 16.333333 | 34 | 0.77551 | eng_Latn | 0.988439 |
dac01437896ff68da89b9d1e488a19901194f735 | 1,233 | md | Markdown | _posts/2018-12-22-distill.md | c-i-p-h-e-r/dhisite | 9d85bb01a55425fa479f670e82a954716e4d7377 | [
"MIT"
] | null | null | null | _posts/2018-12-22-distill.md | c-i-p-h-e-r/dhisite | 9d85bb01a55425fa479f670e82a954716e4d7377 | [
"MIT"
] | null | null | null | _posts/2018-12-22-distill.md | c-i-p-h-e-r/dhisite | 9d85bb01a55425fa479f670e82a954716e4d7377 | [
"MIT"
] | null | null | null | ---
title: Ground Hog Day
layout: distill
description: Are we on a loop...
date: '2021-05-09 05:30:00'
authors:
- name: Dhiman Saha
affiliations:
name: EECS, IIT Bhilai
bibliography: 2018-12-22-distill.bib
_styles: |-
.fake-img {
background: #bbb;
border: 1px solid rgba(0, 0, 0, 0.1);
box-shadow: 0 0px 4px rgba(0, 0, 0, 0.1);
margin-bottom: 12px;
} .fake-img p {
font-family: monospace;
color: white;
text-align: left;
margin: 12px 0;
text-align: center;
font-size: 16px;
}
---
Have you seen the movie “Ground Hog Day”. Amazing concept isn’t it?
I guess we all have our own Ground Hog Days. Days when we woke up to things that are perhaps repeating themselves. The days when we are back to square one and have to start all over again.
While as a researcher I have faced that more often than not. On the contrary, sometimes we feel that if only we could wake up to a day where we could relive the past, perhaps in a better way; most importantly avoiding those silly mistakes of the past that have played so much in shaping our future.
In this blog I want to share with you all my experiences as a cryptographer or should I say crypto-lover. Stay tuned. Oops…msg encrypted…
| 36.264706 | 299 | 0.709651 | eng_Latn | 0.997671 |
dac01969dcb818cd9fedb36066e5da23436c0633 | 397 | md | Markdown | README.md | kasvith/arm-project | f85dfb239a3ea9d67b900c88615e34a2292c2db1 | [
"MIT"
] | 1 | 2019-11-18T11:45:20.000Z | 2019-11-18T11:45:20.000Z | README.md | kasvith/arm-project | f85dfb239a3ea9d67b900c88615e34a2292c2db1 | [
"MIT"
] | null | null | null | README.md | kasvith/arm-project | f85dfb239a3ea9d67b900c88615e34a2292c2db1 | [
"MIT"
] | null | null | null | # Image processing with ARM
This is a simple ARM program which allows manipulation of matrixes.
Input `[rows] [cols] [opcode] {data}`
Opcodes are follow
- Original **0**
- Inversion **1**
- Rotate by 180 **2**
- Flip **3**
# Example
Input
```3 4 1 43 45 123 132 164 234 12 211 32 121 1 200```
Output
```
Inversion
212 210 132 123
91 21 243 44
223 134 254 55
```
| 14.178571 | 67 | 0.617128 | eng_Latn | 0.901632 |
dac06231425fceb644ef7f6be74b778951ee3349 | 705 | md | Markdown | README.md | deutwaffe/pcgImplement | e30b487f48cd463aad61a1b867ca6e5465e2c62f | [
"MIT"
] | null | null | null | README.md | deutwaffe/pcgImplement | e30b487f48cd463aad61a1b867ca6e5465e2c62f | [
"MIT"
] | null | null | null | README.md | deutwaffe/pcgImplement | e30b487f48cd463aad61a1b867ca6e5465e2c62f | [
"MIT"
] | null | null | null | # Procedural Content Generation
## CURRENT STATUS
Constantly Pushing Up To Implement Algorithms.
+ Add a SceneManager (to switch among different algorithms).
## ALGORITHM
### ~~Random Numbers~~
### ~~Height Map~~
### Sequence Generation
- [ ] Lindenmayer Systems
- [ ] Markov Chains
### Fill Space
- [ ] Random Walks
- [ ] Cellular Automata
- [ ] Settling
- [ ] Wang Tiles
- [x] Binary Space Partition
- There seems some wrong judgements when the player intersects with the rooms (when player goes into room, some rooms that not intersected light up),
- [ ] Voronoi Diagrams
- [ ] Dijkstra Maps
- [ ] Tree Mapping
| 21.363636 | 155 | 0.673759 | eng_Latn | 0.865683 |
dac0902183796e68dc2db81d8b593603548f312f | 6,778 | md | Markdown | _posts/2019-03-15-Download-discovering-french-nouveau-rouge-3-answers-workbook-pdf.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | _posts/2019-03-15-Download-discovering-french-nouveau-rouge-3-answers-workbook-pdf.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | _posts/2019-03-15-Download-discovering-french-nouveau-rouge-3-answers-workbook-pdf.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Discovering french nouveau rouge 3 answers workbook pdf book
" He met there a mage, if you'd track down an address for Tetsy's parents and "I'll know, in a vertiginous spiral. "By that time, he twitched when he recognized the tune. This somewhat shocks Curtis because he has until now been under the impression that she is too much better suited to juggling and acrobatic trapeze work? Ever?" am here and hold your hands, El Ijli and Er Recashi and Ibdan and Hassan el Feresdec and El Lauz and Es Seker and Omar et Tertis and Abou Nuwas (34) and Abou Ishac en Nedim and Aboulhusn el Khelia, too, thrown up dead on the coast of Behring Island. Luki looked back at me. She put their food on the table and they ate their meal in silence. Although not a scientist, through the power of positive thinking, but it might get as much as a year boost, rapidly closer, until they are completely consumed, or a starfish can. Even a portion of our Quaternary clays have Jacob had become discovering french nouveau rouge 3 answers workbook pdf card mechanic for one purpose. " She kissed the top of the girl's As the four of us stood there staring at him, needs must it befall me and my speech to the king shall not profit me, and so if he'd come back tonight, but the fact remained that somebody seemed to be exploring the potential for fomenting unrest among the Chironians. " Then said Azadbekht to him (and indeed his words were [prompted] by anger and those of the youth by presence of mind and good breeding), p, I don't dare dissect it. Why, he taught him From his hiding place in the Explorer on the lower deck of the car transport. Even now, iii, from the first collision with the pole or whatever it had been IS WITH THE DEEPEST GRATITUDE I look up as she bursts into raucous laughter, is very dangerous, that we would have expected to find here a "You escaped, his colour changed and he said to them, past flowering, when the phantom voice rose nearby. "You'd expect them to be high feet were grass-stained and filthy, in the farmhouse, canvas awnings create shaded areas for socializing, he'd taken brazen advantage of the discovering french nouveau rouge 3 answers workbook pdf when he "I'm not sure it's enough," he worries! Between the pieces of work by conversation was thus not in force hereabouts. And she wasn't a murderer, storehouses for train-oil with large thick dried blood, and of the number of words in every book ALEX. stealthily he enters the store itself, then the girl would be doing Junior a service even after her demise, behind a studded door of imitation oak and a high window of small. When it starts to get cold here and they know the cycle's drawing to an end, the carters. We have to make sure he never knows. I'd found a pattern for the victims, ii. They cannot! " true. Raised his right hand from his side. He confirmed my serious maladies, but the perhaps of ill fame, blotted her sweat-damped neck. There are besides, and set off down the valley towards the mine, alert and ready, she might easily have broken her neck. During our visits to that island in In spite of major earthquakes pending, hurt, collect valuable contributions occasionally necessary. She wanted to glance down, and she proved it to herself in the same way that Colman proved to himself that nobody was going to tell him what he was supposed discovering french nouveau rouge 3 answers workbook pdf think, and his face flushed with guilt, "Not anymore. Stairs. bear was fallen in with on land and was pierced by a bullet, please, a pretty diversified act. That was what happened when somebody set himself up so that he didn't dare turn his back! From the Norway are still the most skilful harpooners. " She kissed the top of the girl's As the four of us stood there staring at him, surveyed, with the _Vega's_ weak steam-power, not necessary. And share it. As he was wheeled headfirst into the operating room, shakenвno less afraid than she'd been a moment ago. never worried when the girl seemed to be developing too slowly, Captain in the General Staff F ignored this protestation, that a crisis was fast to the grub, yes, flamboyant young mutant "I hadn't thought of it that way," Crawford admitted, you sweet child, weighs two hundred fifty pounds lifted slightly to catch any sound of Mistress Mary, attention on the point. You bastard. Bathrooms. worms, but in reality to press a cool and slightly damp dishtowel against her eyes, you were hoping for a flower delivery. The first impression of the Japanese, contracting, or of dramatic instant conversions among the listeners. possibly inspire in him a greater thirst for knowledge than the one with which Naomi dead. " A floor-to-ceiling bookshelf was crammed with pulp magazines that had been published throughout the 1920s, the name tolled through him like the ominous note of the deepest bass bell in a cathedral carillon, a howl his sister-become; however, from the brake lights. meat! I remember how some of the best minds strove, who sleeps on. ] She had come out of her mother broken, discovering french nouveau rouge 3 answers workbook pdf under and over the 80th degree of sometimes. ISMAIL, drawn by ditto to work out a way to use her body to shield the kid when they made their run with reference to my visit to the town. An hour Here Comes Mr. My watering lips, and I have a research, the office of servant, coarse voice must have sounded not abraded. Now, lifted the hood. This was especially unusual, the last thing "They go to jail," he whispered solemnly. were thick as thieves. instruments of one another's salvation, her performance figure, and lay face down on the couch with his feet toward me, the base of one of those enormous columns that had astonished me written from oral communication by Atlassov himself. "What is this?" of the many remarkable mammalia occurring here, to sleep. " "Ours will be a good secret society. But he was no more trouble than the cat. In the window of the fourth, then?" [Footnote 204: According to Johannesen's determination? He filled the first cup and saying, massaging her uterus in discovering french nouveau rouge 3 answers workbook pdf same lazy pattern as that made by the piece of melting ice on her belly, unable to Now Junior threw back the discovering french nouveau rouge 3 answers workbook pdf and sprang out of bed, however. Enoch Cain. " After a pause he asked, he was troubled by the Instead, because he that she hadn't expected to discuss for years to come. You can't get married. They have marvelous carne cooking vessels, although her eyes never "To fake acute nervous emesis, passing all the cars. Caro It's rare but pleasant when both productions of a single story come out well. | 753.111111 | 6,649 | 0.789761 | eng_Latn | 0.999921 |
dac2797953e0e54e47b0e803d07a7819fe85fbed | 5,163 | md | Markdown | _drafts/2018-05-08-on-how-i-did-not-wear-a-lab-coat-at-work-and-sufferred.md | rutherblood/nudesfromamountaintop | 89b8b848b2027ff5dcbb5d7ad351612de48f22ad | [
"MIT"
] | null | null | null | _drafts/2018-05-08-on-how-i-did-not-wear-a-lab-coat-at-work-and-sufferred.md | rutherblood/nudesfromamountaintop | 89b8b848b2027ff5dcbb5d7ad351612de48f22ad | [
"MIT"
] | null | null | null | _drafts/2018-05-08-on-how-i-did-not-wear-a-lab-coat-at-work-and-sufferred.md | rutherblood/nudesfromamountaintop | 89b8b848b2027ff5dcbb5d7ad351612de48f22ad | [
"MIT"
] | null | null | null | ---
published: false
---
One of my current roommates works at a government centre for disease control research here at Currey Road. He is a biotechnology graduate and his work most requires him to collect data in experiments according to a strictly defined protocol. The word "protocol" here is key.
The experiments have to be performed according to a pre-established principle. Protocols become important in a setting where there is a high chance of a minor mistake invalidating the entire set of results which draw on the data generated by these experiments. These biotech protocols usually require years to master as they need one to work with and control unstable chemicals, living tissue, dirty vessels, one's own body, the environment itself. Dirt from under your dirty fingernails can invalidate six months of your work in a second. My roomate over the course of the year has worked on just two of these experiments.
Lately, I have come to take an interest in such matters because of a development in my own work. My current project requires me to work with the Touch API in browsers: filtering unrequired palm touches when one writes with a stylus on an HTML5 canvas on touch devices in the natural manner one writes with on a sheet of paper. My goto device on which I have been testing and for which I am polishing my results is an iPad 10.
A solution to the problem lies with machine learning. Inspired by [this](http://juliaschwarz.net/assets/palm-rejection/schwarz-chi14-palmrejection.pdf "Paper on palm rejection using probabilistic UI") paper I set out to train a decision tree in the matters of palm and stylus. How one trains a decision tree is by generating a relational (tabular) dataset with various characterstics of a touch contact (when I say _touch contact_, what I mean is a single touch gesture right from the start upon first contact, to the movements and to the end when you pick up your finger, stylus, palm or whatever you've set to rest on that screen) like the distance of the start contact from its neighbors startpoints within a given timewindow, mean radius and the like. Now, each entry in this dataset is labelled as _palm_ or _stylus_ and handed over to a decision-tree generation algorithm like the C4.5 or CART to juggle with. I take this decision tree, encode it to if-else clauses and use it in my final product. How I collect the data is by taking an HTML5 canvas, generating a random 10px circle anywhere on it and asking a labrat to try initiating a stroke from inside the circle using a stylus while naturally resting her palm on the iPad like she would on a sheet of paper. Simple right?
Except it's not if **YOU'RE AN UNDISCIPLINED AND INCONSISTENT FUCK**. You see I am that way and this is a protocol. I have the feeling and I think I am mostly right that when it comes to modern statistical machine learning things are not quite different from my roommate's experiments with stemcells. Machine learning is not the magical device of highly-paid wizards who sway their wand at any problem and the problem goes away, no sir. Generating the training set with a protocol, transforming it, feeding it to the algorithm with the perfect among the million variations of parameters you could tune, and testing the results with the perfect statistical formulae, mastering this entire chain of protocols is where the millions bucks in salaries lie at. It always helps to be a mathematician ofcourse.
Let me tell you what I'm ranting about and where I screwed up:
1. I collected multiple data sets for the various kind of gestures like panning, zooming and others which did not fall within the category of my prime target (i.e. stylus or palm) and which needed to be positively filtered. I mixed them with my stylus/palm data set to train the decision tree. Except I didn't label these data-sets descriptively and ended up with a hodge podge of them, taking a guess, mixing incompatible data-sets and ended up with unwanted decision trees. Do not ask me how many times I repeated this same mistake.
2. My test scripts compute their own characterstics on the raw touch event data that comes in. These characterstics need to strictly be computed in the same way the characterstics were computed during my training. Turns out I initially wasted a lot of time due to bugs in both my training code, testing code and inconsistencies in my own thinking which led to different ways some attributes/characterstics were computed while training and while testing.
Looking at the big picture, there are questions which come to mind now that I have been working with statistics and in an experimental framework: how can one _definitely_ tell if the inferences one makes from a dataset is right? Is testing the hypothesis on an unlooked dataset the only way? Is a _proof_ the hypothesis possible in any way? Turns out this is the [problem of induction](https://plato.stanford.edu/entries/induction-problem/ "SEP article on the Problem Of Induction") as put by David Hume in his _A Treatise of Human Nature_.
See you tomorrow,
Avi.
P.S.: **MORAL OF THE STORY:** It nevers helps to be not disciplined. Always be disciplined. Chao. | 206.52 | 1,283 | 0.800504 | eng_Latn | 0.999851 |
dac445396da34395f134a65dcba6db841aec6e31 | 59 | md | Markdown | README.md | crisstanza/java-mailer | 41e559cbd7bcf4d7494a4f487d784ae3bc14f956 | [
"Unlicense"
] | null | null | null | README.md | crisstanza/java-mailer | 41e559cbd7bcf4d7494a4f487d784ae3bc14f956 | [
"Unlicense"
] | null | null | null | README.md | crisstanza/java-mailer | 41e559cbd7bcf4d7494a4f487d784ae3bc14f956 | [
"Unlicense"
] | null | null | null | # java-mailer
Java standalone application to send e-mails.
| 19.666667 | 44 | 0.79661 | eng_Latn | 0.363119 |
dac46c920ae54b1ab9d7a774617eaaa8b41c4532 | 97 | md | Markdown | archive/458.md | vim-jp/reading-vimrc | b702916f1db77cdd75743fe73271a1aae8b47d2a | [
"CC-BY-4.0"
] | 78 | 2015-03-08T10:24:15.000Z | 2022-03-26T14:50:07.000Z | archive/458.md | vim-jp/reading-vimrc | b702916f1db77cdd75743fe73271a1aae8b47d2a | [
"CC-BY-4.0"
] | 12 | 2015-02-28T15:28:36.000Z | 2018-05-02T07:30:30.000Z | archive/458.md | vim-jp/reading-vimrc | b702916f1db77cdd75743fe73271a1aae8b47d2a | [
"CC-BY-4.0"
] | 4 | 2016-02-20T14:36:07.000Z | 2017-06-19T13:11:31.000Z | ---
layout: archive
title: 第458回 vimrc読書会
id: 458
category: archive
---
{% include archive.md %}
| 12.125 | 24 | 0.690722 | yue_Hant | 0.319694 |
dac4c6525e29f987f277e6a3060d58d742c08f91 | 1,005 | md | Markdown | AlchemyInsights/nla-error.md | isabella232/OfficeDocs-AlchemyInsights-pr.da-DK | a907697f48db2dc57c19d7e003d92831c111566e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T19:06:02.000Z | 2020-09-17T11:26:05.000Z | AlchemyInsights/nla-error.md | isabella232/OfficeDocs-AlchemyInsights-pr.da-DK | a907697f48db2dc57c19d7e003d92831c111566e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:59:12.000Z | 2022-02-09T06:59:36.000Z | AlchemyInsights/nla-error.md | isabella232/OfficeDocs-AlchemyInsights-pr.da-DK | a907697f48db2dc57c19d7e003d92831c111566e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-10-11T18:36:50.000Z | 2021-10-09T10:49:57.000Z | ---
title: NLA-fejl
ms.author: v-smandalika
author: v-smandalika
manager: dansimp
ms.date: 03/19/2021
audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "9032"
- "9005217"
ms.openlocfilehash: fde9896c58312ee8823a5f911bed3102ccec2495
ms.sourcegitcommit: c08bed4071baa3bb5879496df3ed44fb828c8367
ms.translationtype: MT
ms.contentlocale: da-DK
ms.lasthandoff: 03/19/2021
ms.locfileid: "51035488"
---
# <a name="nla-error"></a>NLA-fejl
Se følgende artikel, som kan hjælpe dig med at foretage fejlfinding af godkendelsesfejl eller NLA-fejl, der opstår, når du bruger RDP-forbindelse (Remote Desktop Protocol) til at oprette forbindelse til en virtuel Azure-maskine (VM):
[Fejlfinding af godkendelsesfejl, når du bruger RDP til at oprette forbindelse til Azure VM – virtuelle maskiner | Microsoft Docs.](https://docs.microsoft.com/troubleshoot/azure/virtual-machines/cannot-connect-rdp-azure-vm)
| 32.419355 | 233 | 0.8 | dan_Latn | 0.858532 |
dac4ea24b8f3866675568f97155b0e4c5bbd96bf | 665 | md | Markdown | README.md | alexpyzhianov/gitzilla | 52f498cc4534f35576775a3384ac7f6d99c56f9d | [
"MIT"
] | null | null | null | README.md | alexpyzhianov/gitzilla | 52f498cc4534f35576775a3384ac7f6d99c56f9d | [
"MIT"
] | null | null | null | README.md | alexpyzhianov/gitzilla | 52f498cc4534f35576775a3384ac7f6d99c56f9d | [
"MIT"
] | null | null | null | gitzilla
=======
A fork of shashankmehta's [gitster] theme.
What does it show?
------------------
* Current working directory, relative to the git root when in a git repo.
* Current git branch name, or commit short hash when in ['detached HEAD' state].
* Current branch name is green or yellow depending on the git state
Requirements
------------
Requires Zim's [git-info] module to show git information.
[gitster]: https://github.com/shashankmehta/dotfiles/blob/master/thesetup/zsh/.oh-my-zsh/custom/themes/gitster.zsh-theme
['detached HEAD' state]: http://gitfaq.org/articles/what-is-a-detached-head.html
[git-info]: https://github.com/zimfw/git-info
| 31.666667 | 120 | 0.712782 | eng_Latn | 0.759847 |
dac5cfd384093dd20ff931436edd0381ab586fbb | 776 | md | Markdown | README.md | hasenek/create_user | e2d1e53b0ea53b3190c17ff450f718a01a753525 | [
"MIT"
] | null | null | null | README.md | hasenek/create_user | e2d1e53b0ea53b3190c17ff450f718a01a753525 | [
"MIT"
] | null | null | null | README.md | hasenek/create_user | e2d1e53b0ea53b3190c17ff450f718a01a753525 | [
"MIT"
] | null | null | null | create_user
=========
Creaet a user and upload an ssh public key for remote authentication
Requirements
------------
No Specific required Ansible
Need a default ssh public key or a specific key needs to be called out in a variable
Role Variables
--------------
#Define the user you would like to create
user_name: default
#Define the user state as present or absent
user_state: present
#Definne the path to the ssh public key
ssh_key: ~/.ssh/cloud_key.pub
Dependencies
------------
None
Example Playbook
----------------
---
- hosts: all
tasks:
- include_role:
name: create_user
vars:
user_name: robert
ssh_key: ~/.ssh/cloud_key.pub
License
-------
MIT
Author Information
------------------
[email protected]
| 14.923077 | 85 | 0.64433 | eng_Latn | 0.972182 |
dac6bb9f437b2c49b87027001afdb400edc00869 | 107 | md | Markdown | analysis/JoshBasham/README.md | data301-2021-summer2/project-group72-project | 8d9a979b2892857810a47b3f069869fa88ddd03d | [
"MIT"
] | null | null | null | analysis/JoshBasham/README.md | data301-2021-summer2/project-group72-project | 8d9a979b2892857810a47b3f069869fa88ddd03d | [
"MIT"
] | 1 | 2021-08-16T23:51:29.000Z | 2021-08-16T23:51:29.000Z | analysis/JoshBasham/README.md | data301-2021-summer2/project-group72-project | 8d9a979b2892857810a47b3f069869fa88ddd03d | [
"MIT"
] | null | null | null |
**Explainer Video for Milestone 4:**
(Video)[https://youtu.be/195FTUmHcR8]
#Thank you for your patience | 15.285714 | 37 | 0.728972 | eng_Latn | 0.391513 |
dac6f3130ecf0de00a32cdfbf1459d745c3dd588 | 241 | md | Markdown | _examples/api/templates/response/Messaging.md | broodingdark/nexmo-developer | 61b09b90dfdc9c4035511e25b99b575b06917af8 | [
"MIT"
] | null | null | null | _examples/api/templates/response/Messaging.md | broodingdark/nexmo-developer | 61b09b90dfdc9c4035511e25b99b575b06917af8 | [
"MIT"
] | null | null | null | _examples/api/templates/response/Messaging.md | broodingdark/nexmo-developer | 61b09b90dfdc9c4035511e25b99b575b06917af8 | [
"MIT"
] | null | null | null | ---
title: Messaging
---
```json
{
"account_id": "xxxxxxxx",
"action_type": "sms",
"lg": "en-gb",
"version": 2,
"status": "pending",
"template": "${pin} is your ${brand} verification code.",
"type": "text"
}
```
| 15.0625 | 61 | 0.510373 | eng_Latn | 0.29409 |
dac7ad82e401b2ae41828aa5260a9c89c092ea90 | 976 | md | Markdown | new-docs/puppeteer.protocol.page.installabilityerror.md | hugodes/puppeteer | 15d1906e7c1b6ded6cfd802db38a2f906094c6fb | [
"Apache-2.0"
] | 1 | 2020-08-08T18:56:31.000Z | 2020-08-08T18:56:31.000Z | new-docs/puppeteer.protocol.page.installabilityerror.md | hugodes/puppeteer | 15d1906e7c1b6ded6cfd802db38a2f906094c6fb | [
"Apache-2.0"
] | 1 | 2020-10-06T18:53:37.000Z | 2020-10-06T18:53:37.000Z | new-docs/puppeteer.protocol.page.installabilityerror.md | hugodes/puppeteer | 15d1906e7c1b6ded6cfd802db38a2f906094c6fb | [
"Apache-2.0"
] | 1 | 2020-09-14T04:23:23.000Z | 2020-09-14T04:23:23.000Z | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [puppeteer](./puppeteer.md) > [Protocol](./puppeteer.protocol.md) > [Page](./puppeteer.protocol.page.md) > [InstallabilityError](./puppeteer.protocol.page.installabilityerror.md)
## Protocol.Page.InstallabilityError interface
The installability error
<b>Signature:</b>
```typescript
export interface InstallabilityError
```
## Properties
| Property | Type | Description |
| --- | --- | --- |
| [errorArguments](./puppeteer.protocol.page.installabilityerror.errorarguments.md) | [InstallabilityErrorArgument](./puppeteer.protocol.page.installabilityerrorargument.md)<!-- -->\[\] | The list of error arguments (e.g. {<!-- -->name:'minimum-icon-size-in-pixels', value:'64'<!-- -->}<!-- -->). |
| [errorId](./puppeteer.protocol.page.installabilityerror.errorid.md) | string | The error id (e.g. 'manifest-missing-suitable-icon'). |
| 44.363636 | 300 | 0.685451 | eng_Latn | 0.170484 |
dac82df4847f313d94fb384928d9aba8218cc588 | 30 | md | Markdown | _site/projects/test1.md | pjpaulpj/pjpaulpj.github.io | 6f52e8f2dc18d04d751085836aea94632683ebb2 | [
"MIT"
] | null | null | null | _site/projects/test1.md | pjpaulpj/pjpaulpj.github.io | 6f52e8f2dc18d04d751085836aea94632683ebb2 | [
"MIT"
] | null | null | null | _site/projects/test1.md | pjpaulpj/pjpaulpj.github.io | 6f52e8f2dc18d04d751085836aea94632683ebb2 | [
"MIT"
] | 2 | 2017-05-09T15:44:15.000Z | 2020-03-08T05:08:56.000Z | s---
title: Test1
---
Test1
| 4.285714 | 12 | 0.533333 | dan_Latn | 0.57919 |
dac86e938c377c8d29fb7cf4517e7eed3c7a7ce9 | 236,094 | md | Markdown | integrations/generated/linode/README.md | DataFire/integrations | 56332a12c8011cb27be25e3173a0f3b3729c08da | [
"MIT"
] | 137 | 2017-06-01T04:39:44.000Z | 2022-03-03T15:41:57.000Z | integrations/generated/linode/README.md | DataFire/integrations | 56332a12c8011cb27be25e3173a0f3b3729c08da | [
"MIT"
] | 42 | 2017-06-09T17:16:14.000Z | 2022-02-12T17:41:55.000Z | integrations/generated/linode/README.md | DataFire/integrations | 56332a12c8011cb27be25e3173a0f3b3729c08da | [
"MIT"
] | 61 | 2016-11-22T19:11:19.000Z | 2022-02-09T03:53:25.000Z | # @datafire/linode
Client library for Linode
## Installation and Usage
```bash
npm install --save @datafire/linode
```
```js
let linode = require('@datafire/linode').create({
access_token: "",
refresh_token: "",
client_id: "",
client_secret: "",
redirect_uri: "",
personalAccessToken: ""
});
.then(data => {
console.log(data);
});
```
## Description
# Introduction
The Linode API provides the ability to programmatically manage the full
range of Linode products and services.
This reference is designed to assist application developers and system
administrators. Each endpoint includes descriptions, request syntax, and
examples using standard HTTP requests. Response data is returned in JSON
format.
This document was generated from our OpenAPI Specification. See the
<a target="_top" href="https://www.openapis.org">OpenAPI website</a> for more information.
<a target="_top" href="https://developers.linode.com/api/docs/v4/openapi.yaml">Download the Linode OpenAPI Specification</a>.
# Changelog
<a target="_top" href="https://developers.linode.com/changelog">View our Changelog</a> to see release
notes on all changes made to our API.
# Access and Authentication
Some endpoints are publicly accessible without requiring authentication.
All endpoints affecting your Account, however, require either a Personal
Access Token or OAuth authentication (when using third-party
applications).
## Personal Access Token
The easiest way to access the API is with a Personal Access Token (PAT)
generated from the
<a target="_top" href="https://cloud.linode.com/profile/tokens">Linode Cloud Manager</a>.
All scopes for the OAuth security model (defined below) apply to this
security model as well.
### Authentication
| Security Scheme Type: | HTTP |
|-----------------------|------|
| **HTTP Authorization Scheme** | bearer |
## OAuth
The OAuth workflow is a three-step process to authenticate a User before an
application can start making API calls on the User's behalf. If all you need
is a Personal Access Token, feel free to skip ahead to the next section.
First, the User visits the application's website and is directed to log with
Linode. The User is then redirected to Linode's authentication server and
presented the scope levels the application is requesting. Once the User
accepts the request for access, we redirect them back to the application's
specified redirect URI with an access code.
Once the User has logged in to Linode and you have received an exchange code,
you will need to exchange that access code for an Authorization token. You
do this by making an HTTP POST request to the following address:
```
https://login.linode.com/oauth/token
```
Make this request as `application/x-www-form-urlencoded` or as
`multipart/form-data` and include the following parameters in the POST body:
| PARAMETER | DESCRIPTION |
|-----------|-------------|
| client_id | Your app's client ID |
| client_secret | Your app's client secret |
| code | The code you just received from the redirect |
You'll get a reponse like this:
```json
{
"scope": "linodes:read_write",
"access_token": "03d084436a6c91fbafd5c4b20c82e5056a2e9ce1635920c30dc8d81dc7a6665c"
"token_type": "bearer",
"expires_in": 7200,
}
```
Included in the reponse is `access_token`. With this token, you can proceed to make
authenticated HTTP requests to the API by adding this header to each request:
```
Authorization: Bearer 03d084436a6c91fbafd5c4b20c82e5056a2e9ce1635920c30dc8d81dc7a6665c
```
### Authentication
| Security Scheme Type: | Oauth2 |
|-----------------------|--------|
| **AuthorizationCode Oauth Flow** | **Authorization URL:** https://login.linode.com/oauth/authorize<br />**Token URL:** https://login.linode.com/oauth/token<br />**Scopes:**<br /><ul><li>`account:read_only` - Allows access to GET information about your Account.</li><li>`account:read_write` - Allows access to all endpoints related to your Account.</li><li>`domains:read_only` - Allows access to GET Domains on your Account.</li><li>`domains:read_write` - Allows access to all Domain endpoints.</li><li>`events:read_only` - Allows access to GET your Events.</li><li>`events:read_write` - Allows access to all endpoints related to your Events.</li><li>`images:read_only` - Allows access to GET your Images.</li><li>`images:read_write` - Allows access to all endpoints related to your Images.</li><li>`ips:read_only` - Allows access to GET your ips.</li><li>`ips:read_write` - Allows access to all endpoints related to your ips.</li><li>`linodes:read_only` - Allows access to GET Linodes on your Account.</li><li>`linodes:read_write` - Allow access to all endpoints related to your Linodes.</li><li>`longview:read_only` - Allows access to GET your Longview Clients.</li><li>`longview:read_write` - Allows access to all endpoints related to your Longview Clients.</li><li>`nodebalancers:read_only` - Allows access to GET NodeBalancers on your Account.</li><li>`nodebalancers:read_write` - Allows access to all NodeBalancer endpoints.</li><li>`stackscripts:read_only` - Allows access to GET your StackScripts.</li><li>`stackscripts:read_write` - Allows access to all endpoints related to your StackScripts.</li><li>`volumes:read_only` - Allows access to GET your Volumes.</li><li>`volumes:read_write` - Allows access to all endpoints related to your Volumes.</li></ul><br />|
# Requests
Requests must be made over HTTPS to ensure transactions are encrypted. The
following Request methods are supported:
| METHOD | USAGE |
|--------|-------|
| GET | Retrieves data about collections and individual resources. |
| POST | For collections, creates a new resource of that type. Also used to perform actions on action endpoints. |
| PUT | Updates an existing resource. |
| DELETE | Deletes a resource. This is a destructive action. |
# Responses
Actions will return one following HTTP response status codes:
| STATUS | DESCRIPTION |
|---------|-------------|
| 200 OK | The request was successful. |
| 204 No Content | The server successfully fulfilled the request and there is no additional content to send. |
| 400 Bad Request | You submitted an invalid request (missing parameters, etc.). |
| 401 Unauthorized | You failed to authenticate for this resource. |
| 403 Forbidden | You are authenticated, but don't have permission to do this. |
| 404 Not Found | The resource you're requesting does not exist. |
| 429 Too Many Requests | You've hit a rate limit. |
| 500 Internal Server Error | Please [open a Support Ticket](/api/v4/support-tickets/#post). |
# Errors
Success is indicated via <a href="https://en.wikipedia.org/wiki/List_of_HTTP_status_codes" target="_top">Standard HTTP status codes</a>.
`2xx` codes indicate success, `4xx` codes indicate a request error, and
`5xx` errors indicate a server error. A
request error might be an invalid input, a required parameter being omitted,
or a malformed request. A server error means something went wrong processing
your request. If this occurs, please
[open a Support Ticket](/api/v4/support-tickets/#post)
and let us know. Though errors are logged and we work quickly to resolve issues,
opening a ticket and providing us with reproducable steps and data is always helpful.
The `errors` field is an array of the things that went wrong with your request.
We will try to include as many of the problems in the response as possible,
but it's conceivable that fixing these errors and resubmitting may result in
new errors coming back once we are able to get further along in the process
of handling your request.
Within each error object, the `field` parameter will be included if the error
pertains to a specific field in the JSON you've submitted. This will be
omitted if there is no relevant field. The `reason` is a human-readable
explanation of the error, and will always be included.
# Pagination
Resource lists are always paginated. The response will look similar to this:
```json
{
"data": [ ... ],
"page": 1,
"pages": 3,
"results": 300
}
```
* Pages start at 1. You may retrieve a specific page of results by adding
`?page=x` to your URL (for example, `?page=4`). If the value of `page`
exceeds `2^64/page_size`, the last possible page will be returned.
* Page sizes default to 100,
and can be set to return between 25 and 100. Page size can be set using
`?page_size=x`.
# Filtering and Sorting
Collections are searchable by fields they include, marked in the spec as
`x-linode-filterable: true`. Filters are passed
in the `X-Filter` header and are formatted as JSON objects. Here is a request
call for Linode Types in our "standard" class:
```Shell
curl "https://api.linode.com/v4/linode/types" \
-H 'X-Filter: { \
"class": "standard"
}'
```
The filter object's keys are the keys of the object you're filtering,
and the values are accepted values. You can add multiple filters by
including more than one key. For example, filtering for "standard" Linode
Types that offer one vcpu:
```Shell
curl "https://api.linode.com/v4/linode/types" \
-H 'X-Filter: { \
"class": "standard",
"vcpus": 1
}'
```
In the above example, both filters are combined with an "and" operation.
However, if you wanted either Types with one vcpu or Types in our "standard"
class, you can add an operator:
```Shell
curl "https://api.linode.com/v4/linode/types" \
-H 'X-Filter: {
"+or": [
{ "vcpus": 1 },
{ "class": "standard" }
]
}'
```
Each filter in the `+or` array is its own filter object, and all conditions
in it are combined with an "and" operation as they were in the previous example.
Other operators are also available. Operators are keys of a Filter JSON
object. Their value must be of the appropriate type, and they are evaluated
as described below:
| OPERATOR | TYPE | DESCRIPTION |
|----------|--------|-----------------------------------|
| +and | array | All conditions must be true. |
| +or | array | One condition must be true. |
| +gt | number | Value must be greater than number. |
| +gte | number | Value must be greater than or equal to number. |
| +lt | number | Value must be less than number. |
| +lte | number | Value must be less than or equal to number. |
| +contains | string | Given string must be in the value. |
| +neq | string | Does not equal the value. |
| +order_by | string | Attribute to order the results by - must be filterable. |
| +order | string | Either "asc" or "desc". Defaults to "asc". Requires `+order_by`. |
For example, filtering for [Linode Types](/api/v4/linode-types)
that offer memory equal to or higher than 61440:
```Shell
curl "https://api.linode.com/v4/linode/types" \
-H 'X-Filter: {
"memory": {
"+gte": 61440
}
}'
```
You can combine and nest operators to construct arbitrarily-complex queries.
For example, give me all [Linode Types](/api/v4/linode-types)
which are either `standard` or `highmem` class, or
have between 12 and 20 vcpus:
```Shell
curl "https://api.linode.com/v4/linode/types" \
-H 'X-Filter: {
"+or": [
{
"+or": [
{
"class": "standard"
},
{
"class": "highmem"
}
]
},
{
"+and": [
{
"vcpus": {
"+gte": 12
}
},
{
"vcpus": {
"+lte": 20
}
}
]
}
]
}'
```
# CLI (Command Line Interface)
The <a href="https://github.com/linode/linode-cli" target="_top">Linode CLI</a> allows you to easily
work with the API using intuitive and simple syntax. It requires a
[Personal Access Token](#section/Personal-Access-Token)
for authentication, and gives you access to all of the features and functionality
of the Linode API that are documented here with CLI examples.
Endpoints that do not have CLI examples are currently unavailable through the CLI, but
can be accessed via other methods such as Shell commands and other third-party applications.
# APIv3
View the [Linode APIv3 Documentation](https://linode.com/apiv3).
## Actions
### oauthCallback
Exchange the code passed to your redirect URI for an access_token
```js
linode.oauthCallback({
"code": ""
}, context)
```
#### Input
* input `object`
* code **required** `string`
#### Output
* output `object`
* access_token `string`
* refresh_token `string`
* token_type `string`
* scope `string`
* expiration `string`
### oauthRefresh
Exchange a refresh_token for an access_token
```js
linode.oauthRefresh(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* access_token `string`
* refresh_token `string`
* token_type `string`
* scope `string`
* expiration `string`
### getAccount
Returns the contact and billing information related to your Account.
```js
linode.getAccount(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output [Account](#account)
### updateAccount
Updates contact and billing information related to your Account.
```js
linode.updateAccount({
"body": {}
}, context)
```
#### Input
* input `object`
* body **required** [Account](#account)
#### Output
* output [Account](#account)
### cancelAccount
Cancels an active Linode account. This action will cause Linode to attempt to charge the credit card on file for the remaining balance. An error will occur if Linode fails to charge the credit card on file. Restricted users will not be able to cancel an account.
```js
linode.cancelAccount({
"body": null
}, context)
```
#### Input
* input `object`
* body **required** `object`
* comments `string`: Any reason for cancelling the account, and any other comments you might have about your Linode service.
#### Output
* output `object`
* survey_link `string`: A link to Linode's exit survey.
### createCreditCard
Adds/edit credit card information to your Account.
Only one credit card can be associated with your Account, so using this endpoint will overwrite your currently active card information with the new credit card.
```js
linode.createCreditCard({
"body": null
}, context)
```
#### Input
* input `object`
* body **required**
* card_number **required** `string`: Your credit card number. No spaces or dashes allowed.
* expiry_month **required** `integer`: A value from 1-12 representing the expiration month of your credit card.
* expiry_year **required** `integer`: A four-digit integer representing the expiration year of your credit card.
* cvv `string`: The Card Verification Value on the back of the card.
#### Output
* output `object`
### getEvents
Returns a collection of Event objects representing actions taken on your Account. The Events returned depends on your grants.
```js
linode.getEvents({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [Event](#event)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getEvent
Returns a single Event object.
```js
linode.getEvent({
"eventId": 0
}, context)
```
#### Input
* input `object`
* eventId **required** `integer`: The ID of the Event.
#### Output
* output [Event](#event)
### eventRead
Marks a single Event as read.
```js
linode.eventRead({
"eventId": 0
}, context)
```
#### Input
* input `object`
* eventId **required** `integer`: The ID of the Event to designate as read.
#### Output
* output `object`
### eventSeen
Marks all Events up to and including this Event by ID as seen.
```js
linode.eventSeen({
"eventId": 0
}, context)
```
#### Input
* input `object`
* eventId **required** `integer`: The ID of the Event to designate as seen.
#### Output
* output `object`
### getInvoices
Returns a paginated list of Invoices against your Account.
```js
linode.getInvoices({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [Invoice](#invoice)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getInvoice
Returns a single Invoice object.
```js
linode.getInvoice({
"invoiceId": 0
}, context)
```
#### Input
* input `object`
* invoiceId **required** `integer`: The ID of the Invoice.
#### Output
* output [Invoice](#invoice)
### getInvoiceItems
Returns a paginated list of Invoice items.
```js
linode.getInvoiceItems({
"invoiceId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* invoiceId **required** `integer`: The ID of the Invoice.
#### Output
* output `object`
* data `array`
* items [InvoiceItem](#invoiceitem)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getNotifications
Returns a collection of Notification objects representing important, often time-sensitive items related to your Account.
You cannot interact directly with Notifications, and a Notification will disappear when the circumstances causing it have been resolved. For example, if you have an important Ticket open, you must respond to the Ticket to dismiss the Notification.
```js
linode.getNotifications(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [Notification](#notification)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getClients
Returns a paginated list of OAuth Clients registered to your Account. OAuth Clients allow users to log into applications you write or host using their Linode Account, and may allow them to grant some level of access to their Linodes or other entities to your application.
```js
linode.getClients({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [OAuthClient](#oauthclient)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createClient
Creates an OAuth Client, which can be used to allow users (using their Linode account) to log in to your own application, and optionally grant your application some amount of access to their Linodes or other entities.
```js
linode.createClient({}, context)
```
#### Input
* input `object`
* body
* public `boolean`: Whether to create a public or private client.
* id `string`: The OAuth Client ID. This is used to identify the client, and is a publicly-known value (it is not a secret).
* label `string`: The name of this application. This will be presented to users when they are asked to grant it access to their Account.
* public `boolean`: If this is a public or private OAuth Client. Public clients have a slightly different authentication workflow than private clients. See the <a target="_top" href="https://oauth.net/2/">OAuth spec</a> for more details.
* redirect_uri `string`: The location a successful log in from <a target="_top" href="https://login.linode.com">https://login.linode.com</a> should be redirected to for this client. The receiver of this redirect should be ready to accept an OAuth exchange code and finish the OAuth exchange.
* secret `string`: The OAuth Client secret, used in the OAuth exchange. This is returned as `<REDACTED>` except when an OAuth Client is created or its secret is reset. This is a secret, and should not be shared or disclosed publicly.
* status `string` (values: active, disabled, suspended): The status of this application. `active` by default.
* thumbnail_url `string`: The URL where this client's thumbnail may be viewed, or `null` if this client does not have a thumbnail set.
* public `boolean`: Whether to create a public or private client.
#### Output
* output [OAuthClient](#oauthclient)
### deleteClient
Deletes an OAuth Client registered with Linode. The Client ID and Client secret will no longer be accepted by <a target="_top" href="https://login.linode.com">https://login.linode.com</a>, and all tokens issued to this client will be invalidated (meaning that if your application was using a token, it will no longer work).
```js
linode.deleteClient({
"clientId": ""
}, context)
```
#### Input
* input `object`
* clientId **required** `string`: The OAuth Client ID to look up.
#### Output
* output `object`
### getClient
Returns information about a single OAuth client.
```js
linode.getClient({
"clientId": ""
}, context)
```
#### Input
* input `object`
* clientId **required** `string`: The OAuth Client ID to look up.
#### Output
* output [OAuthClient](#oauthclient)
### updateClient
Update information about an OAuth Client on your Account. This can be especially useful to update the `redirect_uri` of your client in the event that the callback url changed in your application.
```js
linode.updateClient({
"clientId": ""
}, context)
```
#### Input
* input `object`
* body [OAuthClient](#oauthclient)
* clientId **required** `string`: The OAuth Client ID to look up.
#### Output
* output [OAuthClient](#oauthclient)
### resetClientSecret
Resets the OAuth Client secret for a client you own, and returns the OAuth Client with the plaintext secret. This secret is not supposed to be publicly known or disclosed anywhere. This can be used to generate a new secret in case the one you have has been leaked, or to get a new secret if you lost the original. The old secret is expired immediately, and logins to your client with the old secret will fail.
```js
linode.resetClientSecret({
"clientId": ""
}, context)
```
#### Input
* input `object`
* clientId **required** `string`: The OAuth Client ID to look up.
#### Output
* output [OAuthClient](#oauthclient)
### getClientThumbnail
Returns the thumbnail for this OAuth Client. This is a publicly-viewable endpoint, and can be accessed without authentication.
```js
linode.getClientThumbnail({
"clientId": ""
}, context)
```
#### Input
* input `object`
* clientId **required** `string`: The OAuth Client ID to look up.
#### Output
* output `string`
### setClientThumbnail
Upload a thumbnail for a client you own. You must upload an image file that will be returned when the thumbnail is retrieved. This image will be publicly-viewable.
```js
linode.setClientThumbnail({
"body": "",
"clientId": ""
}, context)
```
#### Input
* input `object`
* body **required** `string`
* clientId **required** `string`: The OAuth Client ID to look up.
#### Output
* output `object`
### getPayments
Returns a paginated list of Payments made on this Account.
```js
linode.getPayments({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [Payment](#payment)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createPayment
Makes a Payment to your Account via credit card. This will charge your credit card the requested amount.
```js
linode.createPayment({
"body": {
"usd": ""
}
}, context)
```
#### Input
* input `object`
* body **required** [PaymentRequest](#paymentrequest)
#### Output
* output [Payment](#payment)
### createPayPalPayment
This begins the process of submitting a Payment via PayPal. After calling this endpoint, you must take the resulting `payment_id` along with the `payer_id` from your PayPal account and [POST /account/payments/paypal-execute](/api/v4/account-payments-paypal-execute/#post) to complete the Payment.
```js
linode.createPayPalPayment({
"body": {
"cancel_url": "",
"redirect_url": "",
"usd": ""
}
}, context)
```
#### Input
* input `object`
* body **required** [PayPal](#paypal)
#### Output
* output `object`
* checkout_token `string`: The checkout token generated for this Payment.
* payment_id `string`: The paypal-generated ID for this Payment. Used when authorizing the Payment in PayPal's interface.
### executePayPalPayment
Given a PaymentID and PayerID - as generated by PayPal during the transaction authorization process - this endpoint executes the Payment to capture the funds and credit your Linode Account.
```js
linode.executePayPalPayment({
"body": {
"payer_id": "",
"payment_id": ""
}
}, context)
```
#### Input
* input `object`
* body **required** [PayPalExecute](#paypalexecute)
#### Output
* output `object`
### getPayment
Returns information about a specific Payment.
```js
linode.getPayment({
"paymentId": 0
}, context)
```
#### Input
* input `object`
* paymentId **required** `integer`: The ID of the Payment to look up.
#### Output
* output [Payment](#payment)
### getAccountSettings
Returns information related to your Account settings: Managed service subscription, Longview subscription, and network helper.
```js
linode.getAccountSettings(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output [AccountSettings](#accountsettings)
### updateAccountSettings
Updates your Account settings.
```js
linode.updateAccountSettings({
"body": {}
}, context)
```
#### Input
* input `object`
* body **required** [AccountSettings](#accountsettings)
#### Output
* output [AccountSettings](#accountsettings)
### enableAccountManged
Enables Linode Managed for the entire account and sends a welcome email to the account's associated email address. Linode Managed can monitor any service or software stack reachable over TCP or HTTP. See our [Linode Managed guide](https://linode.com/docs/platform/linode-managed/) to learn more.
```js
linode.enableAccountManged(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
### getTransfer
Returns a Transfer object showing your network utilization, in GB, for the current month.
```js
linode.getTransfer(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output [Transfer](#transfer)
### getUsers
Returns a paginated list of Users on your Account. Users may access all or part of your Account based on their restricted status and grants. An unrestricted User may access everything on the account, whereas restricted User may only access entities or perform actions they've been given specific grants to.
```js
linode.getUsers({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [User](#user)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createUser
Creates a User on your Account. Once created, the User will be able to log in and access portions of your Account. Access is determined by whether or not they are restricted, and what grants they have been given.
```js
linode.createUser({}, context)
```
#### Input
* input `object`
* body `object`
* email **required** `string`: The new User's email address.
* restricted `boolean`: If true, the new User must be granted access to perform actions or access entities on this Account. See [/account/users/{username}/grants](/api/v4/account-users-username-grants) for details on how to configure grants for a restricted User.
* username **required** `string`: The new User's username. This is used for logging in, and may also be displayed alongside actions the User performs (for example, in Events or public StackScripts).
#### Output
* output [User](#user)
### deleteUser
Deletes a User. The deleted User will be immediately logged out and may no longer log in or perform any actions. All of the User's Grants will be removed.
```js
linode.deleteUser({
"username": ""
}, context)
```
#### Input
* input `object`
* username **required** `string`: The username to look up.
#### Output
* output `object`
### getUser
Returns information about a single User on your Account.
```js
linode.getUser({
"username": ""
}, context)
```
#### Input
* input `object`
* username **required** `string`: The username to look up.
#### Output
* output [User](#user)
### updateUser
Update information about a User on your Account. This can be used to change the restricted status of a User. When making a User restricted, no grants will be configured by default and you must then set up grants in order for the User to access anything on the Account.
```js
linode.updateUser({
"username": ""
}, context)
```
#### Input
* input `object`
* body [User](#user)
* username **required** `string`: The username to look up.
#### Output
* output [User](#user)
### getUserGrants
Returns the full grants structure for this User. This includes all entities on the Account alongside what level of access this User has to each of them. Individual users may view their own grants at the [/profile/grants](/api/v4/profile-grants) endpoint, but will not see entities that they have no access to.
```js
linode.getUserGrants({
"username": ""
}, context)
```
#### Input
* input `object`
* username **required** `string`: The username to look up.
#### Output
* output [GrantsResponse](#grantsresponse)
### updateUserGrants
Update the grants a User has. This can be used to give a User access to new entities or actions, or take access away. You do not need to include the grant for every entity on the Account in this request; any that are not included will remain unchanged.
```js
linode.updateUserGrants({
"body": {},
"username": ""
}, context)
```
#### Input
* input `object`
* body **required** [GrantsResponse](#grantsresponse)
* username **required** `string`: The username to look up.
#### Output
* output [GrantsResponse](#grantsresponse)
### getDomains
This is a collection of Domains that you have registered in Linode's DNS Manager. Linode is not a registrar, and in order for these to work you must own the domains and point your registrar at Linode's nameservers.
```js
linode.getDomains({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [Domain](#domain)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createDomain
Adds a new Domain to Linode's DNS Manager. Linode is not a registrar, and you must own the domain before adding it here. Be sure to point your registrar to Linode's nameservers so that the records hosted here are used.
```js
linode.createDomain({
"body": {
"id": 0,
"domain": "",
"type": ""
}
}, context)
```
#### Input
* input `object`
* body **required** [Domain](#domain)
#### Output
* output [Domain](#domain)
### importDomain
Imports a domain zone from a remote nameserver.
Your nameserver must allow zone transfers (AXFR) from the following IPs:
- 96.126.114.97
- 96.126.114.98
- 2600:3c00::5e
- 2600:3c00::5f
```js
linode.importDomain({}, context)
```
#### Input
* input `object`
* body
* domain `string`: The domain to import.
* remote_nameserver `string`: The remote nameserver that allows zone transfers (AXFR).
#### Output
* output [Domain](#domain)
### deleteDomain
Deletes a Domain from Linode's DNS Manager. The Domain will be removed from Linode's nameservers shortly after this operation completes. This also deletes all associated Domain Records.
```js
linode.deleteDomain({
"domainId": 0
}, context)
```
#### Input
* input `object`
* domainId **required** `integer`: The ID of the Domain to access.
#### Output
* output `object`
### getDomain
This is a single Domain that you have registered in Linode's DNS Manager. Linode is not a registrar, and in order for this Domain record to work you must own the domain and point your registrar at Linode's nameservers.
```js
linode.getDomain({
"domainId": 0
}, context)
```
#### Input
* input `object`
* domainId **required** `integer`: The ID of the Domain to access.
#### Output
* output [Domain](#domain)
### updateDomain
Update information about a Domain in Linode's DNS Manager.
```js
linode.updateDomain({
"body": {
"id": 0,
"domain": "",
"type": ""
},
"domainId": 0
}, context)
```
#### Input
* input `object`
* body **required** [Domain](#domain)
* domainId **required** `integer`: The ID of the Domain to access.
#### Output
* output [Domain](#domain)
### cloneDomain
Clones a Domain and all associated DNS records from a Domain that is registered in Linode's DNS manager.
```js
linode.cloneDomain({
"body": {
"domain": ""
},
"domainId": ""
}, context)
```
#### Input
* input `object`
* body **required** `object`
* domain **required** `string`: The new domain being created.
* domainId **required** `string`: ID of the Domain to clone.
#### Output
* output [Domain](#domain)
### getDomainRecords
Returns a paginated list of Records configured on a Domain in Linode's
DNS Manager.
```js
linode.getDomainRecords({
"domainId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* domainId **required** `integer`: The ID of the Domain we are accessing Records for.
#### Output
* output `object`
* data `array`
* items [DomainRecord](#domainrecord)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createDomainRecord
Adds a new Domain Record to the zonefile this Domain represents.
```js
linode.createDomainRecord({
"body": null,
"domainId": 0
}, context)
```
#### Input
* input `object`
* body **required**
* id `integer`: This Record's unique ID.
* name `string`: The name of this Record. This field's actual usage depends on the type of record this represents. For A and AAAA records, this is the subdomain being associated with an IP address.
* port `integer`: The port this Record points to.
* priority `integer`: The priority of the target host. Lower values are preferred.
* protocol `string`: The protocol this Record's service communicates with. Only valid for SRV records.
* service `string`: The service this Record identified. Only valid for SRV records.
* tag `string`: The tag portion of a CAA record. It is invalid to set this on other record types.
* target `string`: The target for this Record. This field's actual usage depends on the type of record this represents. For A and AAAA records, this is the address the named Domain should resolve to.
* ttl_sec `integer`: "Time to Live" - the amount of time in seconds that this Domain's records may be cached by resolvers or other domain servers. Valid values are 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200 - any other value will be rounded to the nearest valid value.
* type `string` (values: A, AAAA, NS, MX, CNAME, TXT, SRV, PTR, CAA): The type of Record this is in the DNS system. For example, A records associate a domain name with an IPv4 address, and AAAA records associate a domain name with an IPv6 address.
* weight `integer`: The relative weight of this Record. Higher values are preferred.
* domainId **required** `integer`: The ID of the Domain we are accessing Records for.
#### Output
* output [DomainRecord](#domainrecord)
### deleteDomainRecord
Deletes a Record on this Domain.
```js
linode.deleteDomainRecord({
"domainId": 0,
"recordId": 0
}, context)
```
#### Input
* input `object`
* domainId **required** `integer`: The ID of the Domain whose Record you are accessing.
* recordId **required** `integer`: The ID of the Record you are accessing.
#### Output
* output `object`
### getDomainRecord
View a single Record on this Domain.
```js
linode.getDomainRecord({
"domainId": 0,
"recordId": 0
}, context)
```
#### Input
* input `object`
* domainId **required** `integer`: The ID of the Domain whose Record you are accessing.
* recordId **required** `integer`: The ID of the Record you are accessing.
#### Output
* output [DomainRecord](#domainrecord)
### updateDomainRecord
Updates a single Record on this Domain.
```js
linode.updateDomainRecord({
"body": {},
"domainId": 0,
"recordId": 0
}, context)
```
#### Input
* input `object`
* body **required** [DomainRecord](#domainrecord)
* domainId **required** `integer`: The ID of the Domain whose Record you are accessing.
* recordId **required** `integer`: The ID of the Record you are accessing.
#### Output
* output [DomainRecord](#domainrecord)
### getImages
Returns a paginated list of Images.
* Calling this endpoint without authentication returns all public Images.
* Authentication is required to return a combined paginated list of all public and
your private Images.
```js
linode.getImages({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [ImagePublic](#imagepublic)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createImage
Creates a private gold-master Image from a Linode Disk. There is no additional charge to store Images for Linode users.
Images are limited to three per Account.
```js
linode.createImage({}, context)
```
#### Input
* input `object`
* body
* created `string`: When this Image was created.
* created_by `string`: The name of the User who created this Image.
* deprecated `boolean`: Whether or not this Image is deprecated. Will only be True for deprecated public Images.
* description `string`: A detailed description of this Image.
* expiry `string`: Only Images created automatically (from a deleted Linode; type=automatic) will expire.
* id `string`: The unique ID of this Image.
* is_public `boolean`: True if the Image is public.
* label `string`: A short description of the Image. Labels cannot contain special characters.
* size `integer`: The minimum size this Image needs to deploy. Size is in MB.
* type `string` (values: manual, automatic): How the Image was created. "Manual" Images can be created at any time. "Automatic" images are created automatically from a deleted Linode.
* vendor `string`: The upstream distribution vendor. `None` for private Images.
* description `string`: A detailed description of this Image.
* disk_id `integer`: The ID of the Linode Disk that this Image will be created from.
* label `string`: A short title of this Image. Defaults to the label of the Disk it is being created from if not provided.
#### Output
* output [ImagePrivate](#imageprivate)
### deleteImage
Deletes a private Image you have permission to `read_write`.
**Deleting an Image is a destructive action and cannot be undone.**
```js
linode.deleteImage({
"imageId": ""
}, context)
```
#### Input
* input `object`
* imageId **required** `string`: ID of the Image to look up.
#### Output
* output `object`
### getImage
Get information about a single Image.
```js
linode.getImage({
"imageId": ""
}, context)
```
#### Input
* input `object`
* imageId **required** `string`: ID of the Image to look up.
#### Output
* output [ImagePrivate](#imageprivate)
### updateImage
Updates a private Image that you have permission to `read_write`.
```js
linode.updateImage({
"body": {},
"imageId": ""
}, context)
```
#### Input
* input `object`
* body **required** [ImagePrivate](#imageprivate)
* imageId **required** `string`: ID of the Image to look up.
#### Output
* output [ImagePrivate](#imageprivate)
### getLinodeInstances
Returns a paginated list of Linodes you have permission to view.
```js
linode.getLinodeInstances({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [Linode](#linode)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createLinodeInstance
Creates a Linode Instance on your Account. In order for this
request to complete successfully, your User must have the `add_linodes` grant. Creating a
new Linode will incur a charge on your Account.
Linodes can be created using one of the available Types. See
[GET /linode/types](/api/v4/linode-types) to get more
information about each Type's specs and cost.
Linodes can be created in any one of our available
[Regions](/api/v4/regions) for a list
of available Regions you can deploy your Linode in.
Linodes can be created in a number of ways:
* Using a Linode Linux Distribution image or an Image you created based on another Linode.
* The Linode will be `running` after it completes `provisioning`.
* A default config with two Disks, one being a 512 swap disk, is created.
* `swap_size` can be used to customize the swap disk size.
* Requires a `root_pass` be supplied to use for the root User's Account.
* It is recommended to supply SSH keys for the root User using the `authorized_keys` field.
* You may also supply a list of usernames via the `authorized_users` field.
* These users must have an SSH Key associated with your Profile first. See [/profile/sshkeys](/api/v4/profile-sshkeys/#post) for more information.
* Using a StackScript.
* See [/linode/stackscripts](/api/v4/linode-stackscripts) for
a list of available StackScripts.
* The Linode will be `running` after it completes `provisioning`.
* Requires a compatible Image to be supplied.
* See [/linode/stackscript/{stackscriptId}](/api/v4/linode-stackscripts-stackscript-id) for compatible Images.
* Requires a `root_pass` be supplied to use for the root User's Account.
* It is recommended to supply SSH keys for the root User using the `authorized_keys` field.
* You may also supply a list of usernames via the `authorized_users` field.
* These users must have an SSH Key associated with your Profile first. See [/profile/sshkeys](/api/v4/profile-sshkeys/#post) for more information.
* Using one of your other Linode's backups.
* You must create a Linode large enough to accommodate the Backup's size.
* The Disks and Config will match that of the Linode that was backed up.
* The `root_pass` will match that of the Linode that was backed up.
* Create an empty Linode.
* The Linode will remain `offline` and must be manually started.
* See [POST /linode/instances/{linodeId}/boot](/api/v4/linode-instances-linode-id-boot/#post).
* Disks and Configs must be created manually.
* This is only recommended for advanced use cases.
**Important**: You must be an unrestricted User in order to add or modify
tags on Linodes.
```js
linode.createLinodeInstance({
"body": {
"type": "",
"region": ""
}
}, context)
```
#### Input
* input `object`
* body **required** `object`
* tags [Linode/properties/tags](#linode/properties/tags)
* authorized_keys `array`: A list of SSH public keys to deploy for the root user on the newly-created Linode. Only accepted if `image` is provided.
* items `string`
* authorized_users `array`: A list of usernames. If the usernames have associated SSH keys, the keys will be appended to the root users `~/.ssh/authorized_keys` file automatically.
* items `string`
* backup_id `integer`: A Backup ID from another Linode's available backups. Your User must have
* backups_enabled `boolean`: If this field is set to `true`, the created Linode will automatically be
* booted `boolean`: Whether to boot this Linode after the deploy is complete. Defaults to true if `image` is provided. Not accepted if not deploying from an Image.
* group [Linode/properties/group](#linode/properties/group)
* image `string`: An Image ID to deploy the Disk from. Official Linode Images start with `linode/ `, while your Images start with `private/`.
* label [Linode/properties/label](#linode/properties/label)
* private_ip `boolean`: If true, the created Linode will have private networking enabled.
* region **required** `string`: The [Region](/api/v4/regions) where the Linode will be located.
* root_pass [DiskRequest/properties/root_pass](#diskrequest/properties/root_pass)
* stackscript_data `object`: An object containing responses to any User Defined Fields present in the StackScript being deployed to this Linode. Only accepted if `stackscript_id` is given. The required values depend on the StackScript being deployed.
* stackscript_id `integer`: The StackScript to deploy to the newly-created Linode. If provided, "image" must also be provided, and must be an Image that is compatible with this StackScript.
* swap_size `integer`: When deploying from an Image, this field is optional, otherwise it is ignored. This is used to set the swap disk size for the newly-created Linode.
* type **required** `string`: The [Linode Type](/api/v4/linode-types) of the Linode you are creating.
#### Output
* output [Linode](#linode)
### deleteLinodeInstance
Deletes a Linode you have permission to `read_write`.
**Deleting a Linode is a destructive action and cannot be undone.**
Additionally, deleting a Linode:
* Gives up any IP addresses the Linode was assigned.
* Deletes all Disks, Backups, Configs, etc.
* Stops billing for the Linode and its associated services. You will be billed for time used
within the billing period the Linode was active.
```js
linode.deleteLinodeInstance({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up
#### Output
* output `object`
### getLinodeInstance
Get a specific Linode by ID.
```js
linode.getLinodeInstance({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up
#### Output
* output [Linode](#linode)
### updateLinodeInstance
Updates a Linode that you have permission to `read_write`.
**Important**: You must be an unrestricted User in order to add or modify tags on Linodes.
```js
linode.updateLinodeInstance({
"body": {},
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** [Linode](#linode)
* linodeId **required** `integer`: ID of the Linode to look up
#### Output
* output [Linode](#linode)
### getBackups
Returns information about this Linode's available backups.
```js
linode.getBackups({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The ID of the Linode the backups belong to.
#### Output
* output `object`
* automatic `array`
* items
* configs `array`: A list of the labels of the Configuration profiles that are part of the Backup.
* items `string`
* created `string`: The date the Backup was taken.
* disks `array`: A list of the disks that are part of the Backup.
* items `object`
* filesystem [Disk/properties/filesystem](#disk/properties/filesystem)
* label `string`
* size `integer`
* finished `string`: The date the Backup completed.
* id `integer`: The unique ID of this Backup.
* label `string`: A label for Backups that are of type `snapshot`.
* status `string` (values: paused, pending, running, needsPostProcessing, successful, failed, userAborted): The current state of a specific Backup.
* type `string` (values: auto, snapshot): This indicates whether the Backup is an automatic Backup or manual snapshot taken by the User at a specific point in time.
* updated `string`: The date the Backup was most recently updated.
* type `string`
* snapshot `object`
* current [Backup](#backup)
* in_progress [Backup](#backup)
### createSnapshot
Creates a snapshot Backup of a Linode.
** If you already have a snapshot of this Linode, this is a destructive action. The previous snapshot will be deleted.**
```js
linode.createSnapshot({
"body": {
"label": ""
},
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* label **required** `string`
* linodeId **required** `integer`: The ID of the Linode the backups belong to.
#### Output
* output [Backup](#backup)
### cancelBackups
Cancels the Backup service on the given Linode. Deletes all of this Linode's existing backups forever.
```js
linode.cancelBackups({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The ID of the Linode to cancel backup service for.
#### Output
* output `object`
### enableBackups
Enables backups for the specified Linode.
```js
linode.enableBackups({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The ID of the Linode to enable backup service for.
#### Output
* output `object`
### getBackup
Returns information about a Backup.
```js
linode.getBackup({
"linodeId": 0,
"backupId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The ID of the Linode the Backup belongs to.
* backupId **required** `integer`: The ID of the Backup to look up.
#### Output
* output [Backup](#backup)
### restoreBackup
Restores a Linode's Backup to the specified Linode.
```js
linode.restoreBackup({
"body": {
"linode_id": 0
},
"linodeId": 0,
"backupId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* linode_id **required** `integer`: The ID of the Linode to restore a Backup to.
* overwrite `boolean`: If True, deletes all Disks and Configs on the target Linode
* linodeId **required** `integer`: The ID of the Linode that the Backup belongs to.
* backupId **required** `integer`: The ID of the Backup to restore.
#### Output
* output `object`
### bootLinodeInstance
Boots a Linode you have permission to modify. If no parameters are given, a Config profile
will be chosen for this boot based on the following criteria:
* If there is only one Config profile for this Linode, it will be used.
* If there is more than one Config profile, the last booted config will be used.
* If there is more than one Config profile and none were the last to be booted (because the
Linode was never booted or the last booted config was deleted) an error will be returned.
```js
linode.bootLinodeInstance({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body `object`
* config_id `integer`: The Linode Config ID to boot into. If omitted, we will attempt to select a config to use. (This will do the right thing in most cases.)
* linodeId **required** `integer`: The ID of the Linode to boot.
#### Output
* output `object`
### cloneLinodeInstance
You can clone your Linode's existing Disks or Configuration profiles to
another Linode on your Account. In order for this request to complete
successfully, your User must have the `add_linodes` grant. Cloning to a
new Linode will incur a charge on your Account.
If cloning to an existing Linode, any actions currently running or
queued must be completed first before you can clone to it.
Up to five clone operations from any given source Linode can be run concurrently.
If more concurrent clones are attempted, an HTTP 400 error will be
returned by this endpoint.
```js
linode.cloneLinodeInstance({
"body": {},
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* backups_enabled `boolean`: If this field is set to `true`, the created Linode will
* configs `array`: An array of configuration profile IDs.
* items `integer`
* disks `array`: An array of disk IDs.
* items `integer`
* group `string`: A label used to group Linodes for display. Linodes are not required to have a group.
* label `string`: The label to assign this Linode when cloning to a new Linode.
* linode_id `integer`: If an existing Linode is to be the target for the clone, the ID of that Linode. The existing Linode must have enough resources to accept the clone.
* region `string`: This is the Region where the Linode will be deployed.
* type `string`: A Linode's Type determines what resources are available to
* linodeId **required** `integer`: ID of the Linode to clone.
#### Output
* output `object`
### getLinodeConfigs
Lists Configuration profiles associated with a Linode.
```js
linode.getLinodeConfigs({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* linodeId **required** `integer`: ID of the Linode to look up Configuration profiles for.
#### Output
* output `object`
* data `array`
* items [LinodeConfig](#linodeconfig)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### addLinodeConfig
Adds a new Configuration profile to a Linode.
```js
linode.addLinodeConfig({
"body": {
"label": "",
"devices": {}
},
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** [LinodeConfig](#linodeconfig)
* linodeId **required** `integer`: ID of the Linode to look up Configuration profiles for.
#### Output
* output [LinodeConfig](#linodeconfig)
### deleteLinodeConfig
Deletes the specified Configuration profile from the specified Linode.
```js
linode.deleteLinodeConfig({
"linodeId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The ID of the Linode whose Configuration profile to look up.
* configId **required** `integer`: The ID of the Configuration profile to look up.
#### Output
* output `object`
### getLinodeConfig
Returns information about a specific Configuration profile.
```js
linode.getLinodeConfig({
"linodeId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The ID of the Linode whose Configuration profile to look up.
* configId **required** `integer`: The ID of the Configuration profile to look up.
#### Output
* output [LinodeConfig](#linodeconfig)
### updateLinodeConfig
Updates a Configuration profile.
```js
linode.updateLinodeConfig({
"body": null,
"linodeId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* comments [LinodeConfig/properties/comments](#linodeconfig/properties/comments)
* devices **required** `object`: A dictionary of device disks to use as a device map in a Linode's configuration profile.
* sda [Device](#device)
* sdb [Device](#device)
* sdc [Device](#device)
* sdd [Device](#device)
* sde [Device](#device)
* sdf [Device](#device)
* sdg [Device](#device)
* sdh [Device](#device)
* helpers [LinodeConfig/properties/helpers](#linodeconfig/properties/helpers)
* id [LinodeConfig/properties/id](#linodeconfig/properties/id)
* kernel [LinodeConfig/properties/kernel](#linodeconfig/properties/kernel)
* label **required** [LinodeConfig/properties/label](#linodeconfig/properties/label)
* memory_limit [LinodeConfig/properties/memory_limit](#linodeconfig/properties/memory_limit)
* root_device `string`: The root device to boot.
* run_level [LinodeConfig/properties/run_level](#linodeconfig/properties/run_level)
* virt_mode [LinodeConfig/properties/virt_mode](#linodeconfig/properties/virt_mode)
* linodeId **required** `integer`: The ID of the Linode whose Configuration profile to look up.
* configId **required** `integer`: The ID of the Configuration profile to look up.
#### Output
* output [LinodeConfig](#linodeconfig)
### getLinodeDisks
View Disk information for Disks associated with this Linode.
```js
linode.getLinodeDisks({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* linodeId **required** `integer`: ID of the Linode to look up.
#### Output
* output `object`
* data `array`
* items [Disk](#disk)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### addLinodeDisk
Adds a new Disk to a Linode. You can optionally create a Disk from an Image (see [/images](/api/v4/images) for a list of available public images, or use one of your own), and optionally provide a StackScript to deploy with this Disk.
```js
linode.addLinodeDisk({
"body": {
"size": 0,
"label": ""
},
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** [DiskRequest](#diskrequest)
* linodeId **required** `integer`: ID of the Linode to look up.
#### Output
* output [Disk](#disk)
### deleteDisk
Deletes a Disk you have permission to `read_write`.
**Deleting a Disk is a destructive action and cannot be undone.**
```js
linode.deleteDisk({
"linodeId": 0,
"diskId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up.
* diskId **required** `integer`: ID of the Disk to look up.
#### Output
* output `object`
### getLinodeDisk
View Disk information for a Disk associated with this Linode.
```js
linode.getLinodeDisk({
"linodeId": 0,
"diskId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up.
* diskId **required** `integer`: ID of the Disk to look up.
#### Output
* output [Disk](#disk)
### updateDisk
Updates a Disk that you have permission to `read_write`.
```js
linode.updateDisk({
"body": {},
"linodeId": 0,
"diskId": 0
}, context)
```
#### Input
* input `object`
* body **required** [Disk](#disk)
* linodeId **required** `integer`: ID of the Linode to look up.
* diskId **required** `integer`: ID of the Disk to look up.
#### Output
* output [Disk](#disk)
### cloneLinodeDisk
Copies a disk, byte-for-byte, into a new Disk belonging to the same Linode. The Linode must have enough storage space available to accept a new Disk of the same size as this one or this operation will fail.
```js
linode.cloneLinodeDisk({
"linodeId": 0,
"diskId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up.
* diskId **required** `integer`: ID of the Disk to clone.
#### Output
* output [Disk](#disk)
### resetDiskPassword
Resets the password of a Disk you have permission to `read_write`.
```js
linode.resetDiskPassword({
"body": null,
"linodeId": 0,
"diskId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* password **required** `string`: The new root password for the OS installed on this Disk.
* linodeId **required** `integer`: ID of the Linode to look up.
* diskId **required** `integer`: ID of the Disk to look up.
#### Output
* output `object`
### resizeDisk
Resizes a Disk you have permission to `read_write`.
The Linode this Disk is attached to must be shut down for resizing to take effect.
If you are resizing the Disk to a smaller size, it cannot be made smaller than what is required by the total size of the files current on the Disk. The Disk must not be in use. If the Disk is in use, the request will succeed but the resize will ultimately fail.
```js
linode.resizeDisk({
"body": null,
"linodeId": 0,
"diskId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* size `integer`: The desired size, in MB, of the disk.
* linodeId **required** `integer`: ID of the Linode to look up.
* diskId **required** `integer`: ID of the Disk to look up.
#### Output
* output `object`
### getLinodeIPs
Returns networking information for a single Linode.
```js
linode.getLinodeIPs({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up.
#### Output
* output `object`
* ipv4 `object`: Information about this Linode's IPv4 addresses.
* private `array`: A list of private IP Address objects belonging to this Linode.
* items [IPAddressPrivate](#ipaddressprivate)
* public `array`: A list of public IP Address objects belonging to this Linode.
* items [IPAddress](#ipaddress)
* reserved `array`: A list of reserved IP Address objects belonging to this Linode.
* items [IPAddress](#ipaddress)
* shared `array`: A list of shared IP Address objects assigned to this Linode.
* items [IPAddress](#ipaddress)
* ipv6 `object`: Information about this Linode's IPv6 addresses.
* global [IPv6Pool](#ipv6pool)
* link_local [IPAddressV6LinkLocal](#ipaddressv6linklocal)
* slaac [IPAddressV6Slaac](#ipaddressv6slaac)
### addLinodeIP
Allocates a public or private IPv4 address to a Linode. Public IP Addresses, after the one included with each Linode, incur an additional monthly charge. If you need an additional public IP Address you must request one - please [open a support ticket](/api/v4/support-tickets/#post). You may not add more than one private IPv4 address to a single Linode.
```js
linode.addLinodeIP({
"body": null,
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* public **required** `boolean`: Whether to create a public or private IPv4 address.
* type **required** `string` (values: ipv4): The type of address you are allocating. Only IPv4 addresses may be allocated through this endpoint.
* linodeId **required** `integer`: ID of the Linode to look up.
#### Output
* output [IPAddress](#ipaddress)
### removeLinodeIP
Deletes a public IPv4 address associated with this Linode. This will fail if it is the Linode's last remaining public IPv4 address. Private IPv4 addresses cannot be removed via this endpoint.
```js
linode.removeLinodeIP({
"linodeId": 0,
"address": ""
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The ID of the Linode to look up.
* address **required** `string`: The IP address to look up.
#### Output
* output `object`
### getLinodeIP
View information about the specified IP address associated with the specified Linode.
```js
linode.getLinodeIP({
"linodeId": 0,
"address": ""
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The ID of the Linode to look up.
* address **required** `string`: The IP address to look up.
#### Output
* output [IPAddress](#ipaddress)
### updateLinodeIP
Updates a particular IP Address associated with this Linode. Only allows setting/resetting reverse DNS.
```js
linode.updateLinodeIP({
"linodeId": 0,
"address": ""
}, context)
```
#### Input
* input `object`
* body `object`
* rdns `string`
* address `string`: The IP address.
* gateway `string`: The default gateway for this address.
* linode_id `integer`: The ID of the Linode this address currently belongs to. For IPv4 addresses, this is by default the Linode that this address was assigned to on creation, and these addresses my be moved using the [/networking/ipv4/assign](/api/v4/networking-ipv-4-assign/#post) endpoint. For SLAAC and link-local addresses, this value may not be changed.
* prefix `integer`: The number of bits set in the subnet mask.
* public `boolean`: Whether this is a public or private IP address.
* rdns `string`: The reverse DNS assigned to this address. For public IPv4 addresses, this will be set to a default value provided by Linode if not explicitly set.
* region `string`: The Region this IP address resides in.
* subnet_mask `string`: The mask that separates host bits from network bits for this address.
* type `string` (values: ipv4, ipv6, ipv6/pool, ipv6/range): The type of address this is.
* linodeId **required** `integer`: The ID of the Linode to look up.
* address **required** `string`: The IP address to look up.
#### Output
* output [IPAddress](#ipaddress)
### migrateLinodeInstance
Initiate a pending host migration that has been scheduled by Linode or initiate a cross data center (DC) migration. A list of pending migrations, if any, can be accessed from [GET /account/notifications](/api/v4/account-notifications). When the migration begins, your Linode will be shutdown if not already off. If the migration initiated the shutdown, it will reboot the Linode when completed.
To initiate a cross DC migration, you must pass a `region` parameter to the request body specifying the target data center region. You can view a list of all available regions and their feature capabilities from [GET /regions](/api/v4/regions). If your Linode has a DC migration already queued or you have initiated a previously scheduled migration, you will not be able to initiate a DC migration until it has completed.
**Note:** Next Generation Network (NGN) data centers do not support IPv6 `/116` pools or IP Failover. If you have these features enabled on your Linode and attempt to migrate to an NGN data center, the migration will not initiate. NGN data centers include Toronto and Mumbai.
```js
linode.migrateLinodeInstance({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body `object`
* region `string`: The region to which the Linode will be migrated. Must be a valid region slug. A list of regions can be viewed by using the [GET /regions](/api/v4/regions) endpoint. A cross data center migration will cancel a pending migration that has not yet been initiated.
* linodeId **required** `integer`: ID of the Linode to migrate.
#### Output
* output `object`
### mutateLinodeInstance
Linodes created with now-deprecated Types are entitled to a free upgrade to the next generation. A mutating Linode will be allocated any new resources the upgraded Type provides, and will be subsequently restarted if it was currently running.
If any actions are currently running or queued, those actions must be completed first before you can initiate a mutate.
```js
linode.mutateLinodeInstance({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body `object`
* allow_auto_disk_resize `boolean`: Automatically resize disks when resizing a Linode. When resizing down to a smaller plan your Linode's data must fit within the smaller disk size.
* linodeId **required** `integer`: ID of the Linode to mutate.
#### Output
* output `object`
### rebootLinodeInstance
Reboots a Linode you have permission to modify. If any actions are currently running or queued, those actions must be completed first before you can initiate a reboot.
```js
linode.rebootLinodeInstance({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body `object`
* config_id `integer`: The Linode Config ID to reboot into. If null or omitted, the last booted config will be used. If there was no last booted config and this Linode only has one config, it will be used. If a config cannot be determined, an error will be returned.
* linodeId **required** `integer`: ID of the linode to reboot.
#### Output
* output `object`
### rebuildLinodeInstance
Rebuilds a Linode you have the `read_write` permission to modify.
A rebuild will first shut down the Linode, delete all disks and configs on the Linode, and then deploy a new `image` to the Linode with the given attributes. Additionally:
* Requires an `image` be supplied.
* Requires a `root_pass` be supplied to use for the root User's Account.
* It is recommended to supply SSH keys for the root User using the
`authorized_keys` field.
```js
linode.rebuildLinodeInstance({
"body": {
"image": "",
"root_pass": ""
},
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* image **required** `string`
* root_pass **required** `string`
* authorized_keys [DiskRequest/properties/authorized_keys](#diskrequest/properties/authorized_keys)
* authorized_users [DiskRequest/properties/authorized_users](#diskrequest/properties/authorized_users)
* booted `boolean`: This field defaults to `true` if the Linode is created with an Image or from a Backup.
* image [DiskRequest/properties/image](#diskrequest/properties/image)
* root_pass [DiskRequest/properties/root_pass](#diskrequest/properties/root_pass)
* stackscript_data [DiskRequest/properties/stackscript_data](#diskrequest/properties/stackscript_data)
* stackscript_id [DiskRequest/properties/stackscript_id](#diskrequest/properties/stackscript_id)
* linodeId **required** `integer`: ID of the Linode to rebuild.
#### Output
* output [Linode](#linode)
### rescueLinodeInstance
Rescue Mode is a safe environment for performing many system recovery and disk management tasks. Rescue Mode is based on the Finnix recovery distribution, a self-contained and bootable Linux distribution. You can also use Rescue Mode for tasks other than disaster recovery, such as formatting disks to use different filesystems, copying data between disks, and downloading files from a disk via SSH and SFTP.
* Note that "sdh" is reserved and unavailable during rescue.
```js
linode.rescueLinodeInstance({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body `object`
* devices [RescueDevices](#rescuedevices)
* linodeId **required** `integer`: ID of the Linode to rescue.
#### Output
* output `object`
### resizeLinodeInstance
Resizes a Linode you have the `read_write` permission to a different Type. If any actions are currently running or queued, those actions must be completed first before you can initiate a resize. Additionally, the following criteria must be met in order to resize a Linode:
* The Linode must not have a pending migration.
* Your Account cannot have an outstanding balance.
* The Linode must not have more disk allocation than the new Type allows.
* In that situation, you must first delete or resize the disk to be smaller.
```js
linode.resizeLinodeInstance({
"body": {
"type": ""
},
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* allow_auto_disk_resize `boolean`: Automatically resize disks when resizing a Linode. When resizing down to a smaller plan your Linode's data must fit within the smaller disk size.
* type **required** `string`: The ID representing the Linode Type.
* linodeId **required** `integer`: ID of the Linode to resize.
#### Output
* output `object`
### shutdownLinodeInstance
Shuts down a Linode you have permission to modify. If any actions are currently running or queued, those actions must be completed first before you can initiate a shutdown.
```js
linode.shutdownLinodeInstance({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to shutdown.
#### Output
* output `object`
### getLinodeStats
Returns CPU, IO, IPv4, and IPv6 statistics for your Linode for the past 24 hours.
```js
linode.getLinodeStats({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up.
#### Output
* output [LinodeStats](#linodestats)
### getLinodeStatsByYearMonth
Returns statistics for a specific month. The year/month values must be either a date in the past, or the current month. If the current month, statistics will be retrieved for the past 30 days.
```js
linode.getLinodeStatsByYearMonth({
"linodeId": 0,
"year": 0,
"month": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up.
* year **required** `integer`: Numeric value representing the year to look up.
* month **required** `integer`: Numeric value representing the month to look up.
#### Output
* output [LinodeStats](#linodestats)
### getLinodeTransfer
Returns a Linode's network transfer pool statistics for the current month.
```js
linode.getLinodeTransfer({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: ID of the Linode to look up.
#### Output
* output `object`
* billable `integer`: The amount of network transfer this Linode has used, in GB, past your monthly quota.
* quota `integer`: The amount of network transfer this Linode adds to your transfer pool, in GB, for the current month's billing cycle.
* used `integer`: The amount of network transfer used by this Linode, in bytes, for the current month's billing cycle.
### getLinodeVolumes
View Block Storage Volumes attached to this Linode.
```js
linode.getLinodeVolumes({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* linodeId **required** `integer`: ID of the Linode to look up.
#### Output
* output `object`
* data `array`
* items [Volume](#volume)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getKernels
Lists available Kernels.
```js
linode.getKernels({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [Kernel](#kernel)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getKernel
Returns information about a single Kernel.
```js
linode.getKernel({
"kernelId": ""
}, context)
```
#### Input
* input `object`
* kernelId **required** `string`: ID of the Kernel to look up.
#### Output
* output [Kernel](#kernel)
### getStackScripts
If the request is not authenticated, only public StackScripts are returned.
For more information on StackScripts, please read our guide: <a target="_top" href="https://linode.com/docs/platform/stackscripts/">Automate Deployment with StackScripts</a>.
```js
linode.getStackScripts({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [StackScript](#stackscript)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### addStackScript
Creates a StackScript in your Account.
```js
linode.addStackScript({
"body": null
}, context)
```
#### Input
* input `object`
* body **required**
* created `string`: The date this StackScript was created.
* deployments_active `integer`: Count of currently active, deployed Linodes created from this StackScript.
* deployments_total `integer`: The total number of times this StackScript has been deployed.
* description `string`: A description for the StackScript.
* id `integer`: The unique ID of this StackScript.
* images `array`: An array of Image IDs. These are the images that can be deployed with this Stackscript.
* items `string`
* is_public `boolean`: This determines whether other users can use your StackScript. **Once a StackScript is made public, it cannot be made private.**
* label `string`: The StackScript's label is for display purposes only.
* rev_note `string`: This field allows you to add notes for the set of revisions made to this StackScript.
* script `string`: The script to execute when provisioning a new Linode with this StackScript.
* updated `string`: The date this StackScript was last updated.
* user_defined_fields `array`: This is a list of fields defined with a special syntax inside this StackScript that allow for supplying customized parameters during deployment. See <a target="_top" href="https://www.linode.com/docs/platform/stackscripts/#variables-and-udfs">Variables and UDFs</a> for more information.
* items [UserDefinedField](#userdefinedfield)
* user_gravatar_id `string`: The Gravatar ID for the User who created the StackScript.
* username `string`: The User who created the StackScript.
#### Output
* output [StackScript](#stackscript)
### deleteStackScript
Deletes a private StackScript you have permission to `read_write`. You cannot delete a public StackScript.
```js
linode.deleteStackScript({
"stackscriptId": ""
}, context)
```
#### Input
* input `object`
* stackscriptId **required** `string`: The ID of the StackScript to look up.
#### Output
* output `object`
### getStackScript
Returns all of the information about a specified StackScript, including the contents of the script.
```js
linode.getStackScript({
"stackscriptId": ""
}, context)
```
#### Input
* input `object`
* stackscriptId **required** `string`: The ID of the StackScript to look up.
#### Output
* output [StackScript](#stackscript)
### updateStackScript
Updates a StackScript.
**Once a StackScript is made public, it cannot be made private.**
```js
linode.updateStackScript({
"stackscriptId": ""
}, context)
```
#### Input
* input `object`
* body [StackScript](#stackscript)
* stackscriptId **required** `string`: The ID of the StackScript to look up.
#### Output
* output [StackScript](#stackscript)
### getLinodeTypes
Returns collection of Linode Types, including pricing and specifications for each Type. These are used when [creating](/api/v4/linode-instances/#post) or [resizing](/api/v4/linode-instances-linode-id-resize/#post) Linodes.
```js
linode.getLinodeTypes(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [LinodeType](#linodetype)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getLinodeType
Returns information about a specific Linode Type, including pricing and specifications. This is used when [creating](/api/v4/linode-instances/#post) or [resizing](/api/v4/linode-instances-linode-id-resize/#post) Linodes.
```js
linode.getLinodeType({
"typeId": ""
}, context)
```
#### Input
* input `object`
* typeId **required** `string`: The ID of the Linode Type to look up.
#### Output
* output [LinodeType](#linodetype)
### getLongviewClients
Returns a paginated list of Longview Clients you have access to. Longview Client is used to monitor stats on your Linode with the help of the Longview Client application.
```js
linode.getLongviewClients({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [LongviewClient](#longviewclient)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createLongviewClient
Creates a Longview Client. This Client will not begin monitoring the status of your server until you configure the Longview Client application on your Linode using the returning `install_code` and `api_key`.
```js
linode.createLongviewClient({
"body": {}
}, context)
```
#### Input
* input `object`
* body **required** [LongviewClient](#longviewclient)
#### Output
* output [LongviewClient](#longviewclient)
### deleteLongviewClient
Deletes a Longview Client from your Account.
**All information stored for this client will be lost.**
This _does not_ uninstall the Longview Client application for your Linode - you must do that manually.
```js
linode.deleteLongviewClient({
"clientId": 0
}, context)
```
#### Input
* input `object`
* clientId **required** `integer`: The Longview Client ID to access.
#### Output
* output `object`
### getLongviewClient
Returns a single Longview Client you can access.
```js
linode.getLongviewClient({
"clientId": 0
}, context)
```
#### Input
* input `object`
* clientId **required** `integer`: The Longview Client ID to access.
#### Output
* output [LongviewClient](#longviewclient)
### updateLongviewClient
Updates a Longview Client. This cannot update how it monitors your server; use the Longview Client application on your Linode for monitoring configuration.
```js
linode.updateLongviewClient({
"body": {},
"clientId": 0
}, context)
```
#### Input
* input `object`
* body **required** [LongviewClient](#longviewclient)
* clientId **required** `integer`: The Longview Client ID to access.
#### Output
* output [LongviewClient](#longviewclient)
### getLongviewSubscriptions
Returns a paginated list of available Longview Subscriptions. This is a public endpoint and requires no authentication.
```js
linode.getLongviewSubscriptions({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [LongviewSubscription](#longviewsubscription)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getLongviewSubscription
Returns a single LongviewSubscription object. This is a public endpoint and requires no authentication.
```js
linode.getLongviewSubscription({
"subscriptionId": ""
}, context)
```
#### Input
* input `object`
* subscriptionId **required** `string`: The Longview Subscription to look up.
#### Output
* output [LongviewSubscription](#longviewsubscription)
### getManagedContacts
Returns a paginated list of Managed Contacts on your Account.
```js
linode.getManagedContacts({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [ManagedContact](#managedcontact)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createManagedContact
Creates a Managed Contact. A Managed Contact is someone Linode special forces can contact in the course of attempting to resolve an issue with a Managed Service.
```js
linode.createManagedContact({}, context)
```
#### Input
* input `object`
* body [ManagedContact](#managedcontact)
#### Output
* output [ManagedContact](#managedcontact)
### deleteManagedContact
Deletes a Managed Contact.
```js
linode.deleteManagedContact({
"contactId": 0
}, context)
```
#### Input
* input `object`
* contactId **required** `integer`: The ID of the contact to access.
#### Output
* output `object`
### getManagedContact
Returns a single Managed Contact.
```js
linode.getManagedContact({
"contactId": 0
}, context)
```
#### Input
* input `object`
* contactId **required** `integer`: The ID of the contact to access.
#### Output
* output [ManagedContact](#managedcontact)
### updateManagedContact
Updates information about a Managed Contact.
```js
linode.updateManagedContact({
"body": {},
"contactId": 0
}, context)
```
#### Input
* input `object`
* body **required** [ManagedContact](#managedcontact)
* contactId **required** `integer`: The ID of the contact to access.
#### Output
* output [ManagedContact](#managedcontact)
### getManagedCredentials
Returns a paginated list of Managed Credentials on your Account.
```js
linode.getManagedCredentials({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [ManagedCredential](#managedcredential)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createManagedCredential
Creates a Managed Credential. A Managed Credential is stored securely to allow Linode special forces to access your Managed Services and resolve issues.
```js
linode.createManagedCredential({}, context)
```
#### Input
* input `object`
* body
* id `integer`: This Credential's unique ID.
* label `string`: The unique label for this Credential. This is for display purposes only.
* last_decrypted `string`: The date this Credential was last decrypted by a member of Linode special forces.
* password `string`: The password to use when accessing the Managed Service.
* username `string`: The username to use when accessing the Managed Service.
#### Output
* output [ManagedCredential](#managedcredential)
### viewManagedSSHKey
Returns the unique SSH public key assigned to your Linode account's Managed service. If you [add this public key](https://linode.com/docs/platform/linode-managed/#adding-the-public-key) to a Linode on your account, Linode special forces will be able to log in to the Linode with this key when attempting to resolve issues.
```js
linode.viewManagedSSHKey(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`: A unique SSH public key that allows Linode's special forces to access a Managed server to respond to Issues.
* ssh_key `string`: The unique SSH public key assigned to your Linode account's Managed service.
### getManagedCredential
Returns a single Managed Credential.
```js
linode.getManagedCredential({
"credentialId": 0
}, context)
```
#### Input
* input `object`
* credentialId **required** `integer`: The ID of the Credential to access.
#### Output
* output [ManagedCredential](#managedcredential)
### updateManagedCredential
Updates the label of a Managed Credential. This endpoint does not update the username and password for a Managed Credential. To do this, use the Update Managed Credential Username and Password ([POST /managed/credentials/{credentialId}/update](https://developers.linode.com/api/docs/v4#operation/updateManagedCredentialUsernamePassword)) endpoint instead.
```js
linode.updateManagedCredential({
"body": {},
"credentialId": 0
}, context)
```
#### Input
* input `object`
* body **required** [ManagedCredential](#managedcredential)
* credentialId **required** `integer`: The ID of the Credential to access.
#### Output
* output [ManagedCredential](#managedcredential)
### deleteManagedCredential
Deletes a Managed Credential. Linode special forces will no longer have access to this Credential when attempting to resolve issues.
```js
linode.deleteManagedCredential({
"credentialId": 0
}, context)
```
#### Input
* input `object`
* credentialId **required** `integer`: The ID of the Credential to access.
#### Output
* output `object`
### updateManagedCredentialUsernamePassword
Updates the username and password for a Managed Credential.
```js
linode.updateManagedCredentialUsernamePassword({
"credentialId": 0
}, context)
```
#### Input
* input `object`
* body
* password `string`: The password to use when accessing the Managed Service.
* username `string`: The username to use when accessing the Managed Service.
* credentialId **required** `integer`: The ID of the Credential to update.
#### Output
* output `object`
### getManagedIssues
Returns a paginated list of recent and ongoing issues detected on your Managed Services.
```js
linode.getManagedIssues({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [ManagedIssue](#managedissue)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getManagedIssue
Returns a single Issue that is impacting or did impact one of your Managed Services.
```js
linode.getManagedIssue({
"issueId": 0
}, context)
```
#### Input
* input `object`
* issueId **required** `integer`: The Issue to look up.
#### Output
* output [ManagedIssue](#managedissue)
### getManagedLinodeSettings
Returns a paginated list of Managed Settings for your Linodes. There will be one entry per Linode on your Account.
```js
linode.getManagedLinodeSettings({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [ManagedLinodeSettings](#managedlinodesettings)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getManagedLinodeSetting
Returns a single Linode's Managed settings.
```js
linode.getManagedLinodeSetting({
"linodeId": 0
}, context)
```
#### Input
* input `object`
* linodeId **required** `integer`: The Linode ID whose settings we are accessing.
#### Output
* output [ManagedLinodeSettings](#managedlinodesettings)
### updateManagedLinodeSetting
Updates a single Linode's Managed settings.
```js
linode.updateManagedLinodeSetting({
"body": {},
"linodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** [ManagedLinodeSettings](#managedlinodesettings)
* linodeId **required** `integer`: The Linode ID whose settings we are accessing.
#### Output
* output [ManagedLinodeSettings](#managedlinodesettings)
### getManagedServices
Returns a paginated list of Managed Services on your Account. These are the services Linode Managed is monitoring and will report and attempt to resolve issues with.
```js
linode.getManagedServices(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [ManagedService](#managedservice)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createManagedService
Creates a Managed Service. Linode Managed will begin monitoring this service and reporting and attempting to resolve any Issues.
```js
linode.createManagedService({}, context)
```
#### Input
* input `object`
* body
* address `string`: The URL at which this Service is monitored.
* body `string`: What to expect to find in the response body for the Service to be considered up.
* consultation_group `string`: The group of ManagedContacts who should be notified or consulted with when an Issue is detected.
* created `string`: When this Managed Service was created.
* credentials `array`: An array of ManagedCredential IDs that should be used when attempting to resolve issues with this Service.
* items `integer`
* id `integer`: This Service's unique ID.
* label `string`: The label for this Service. This is for display purposes only.
* notes `string`: Any information relevant to the Service that Linode special forces should know when attempting to resolve Issues.
* region `string`: The Region in which this Service is located. This is required if address is a private IP, and may not be set otherwise.
* service_type `string` (values: url, tcp): How this Service is monitored.
* status `string` (values: disabled, pending, ok, problem): The current status of this Service.
* timeout `integer`: How long to wait, in seconds, for a response before considering the Service to be down.
* updated `string`: When this Managed Service was last updated.
#### Output
* output [ManagedService](#managedservice)
### deleteManagedService
Deletes a Managed Service. This service will no longer be monitored by Linode Managed.
```js
linode.deleteManagedService({
"serviceId": 0
}, context)
```
#### Input
* input `object`
* serviceId **required** `integer`: The ID of the Managed Service to access.
#### Output
* output `object`
### getManagedService
Returns information about a single Managed Service on your Account.
```js
linode.getManagedService({
"serviceId": 0
}, context)
```
#### Input
* input `object`
* serviceId **required** `integer`: The ID of the Managed Service to access.
#### Output
* output [ManagedService](#managedservice)
### updateManagedService
Updates information about a Managed Service.
```js
linode.updateManagedService({
"body": {},
"serviceId": 0
}, context)
```
#### Input
* input `object`
* body **required** [ManagedService](#managedservice)
* serviceId **required** `integer`: The ID of the Managed Service to access.
#### Output
* output [ManagedService](#managedservice)
### disableManagedService
Temporarily disables monitoring of a Managed Service.
```js
linode.disableManagedService({
"serviceId": 0
}, context)
```
#### Input
* input `object`
* serviceId **required** `integer`: The ID of the Managed Service to disable.
#### Output
* output [ManagedService](#managedservice)
### enableManagedService
Enables monitoring of a Managed Service.
```js
linode.enableManagedService({
"serviceId": 0
}, context)
```
#### Input
* input `object`
* serviceId **required** `integer`: The ID of the Managed Service to enable.
#### Output
* output [ManagedService](#managedservice)
### getIPs
Returns a paginated list of IP Addresses on your Account, excluding private addresses.
```js
linode.getIPs(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [IPAddress](#ipaddress)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### allocateIP
Allocates a new IPv4 Address on your Account. The Linode must be configured to support additional addresses - please [open a support ticket](/api/v4/support-tickets/#post) requesting additional addresses before attempting allocation.
```js
linode.allocateIP({
"body": null
}, context)
```
#### Input
* input `object`
* body **required** `object`
* linode_id **required** `integer`: The ID of a Linode you you have access to that this address will be allocated to.
* public **required** `boolean`: Whether to create a public or private IPv4 address.
* type **required** `string` (values: ipv4): The type of address you are requesting. Only IPv4 addresses may be allocated through this endpoint.
#### Output
* output [IPAddress](#ipaddress)
### getIP
Returns information about a single IP Address on your Account.
```js
linode.getIP({
"address": ""
}, context)
```
#### Input
* input `object`
* address **required** `string`: The address to operate on.
#### Output
* output [IPAddress](#ipaddress)
### updateIP
Sets RDNS on an IP Address. Forward DNS must already be set up for reverse DNS to be applied. If you set the RDNS to `null` for public IPv4 addresses, it will be reset to the default _members.linode.com_ RDNS value.
```js
linode.updateIP({
"body": {},
"address": ""
}, context)
```
#### Input
* input `object`
* body **required** [IPAddress](#ipaddress)
* address **required** `string`: The address to operate on.
#### Output
* output [IPAddress](#ipaddress)
### assignIPs
Assign multiple IPs to multiple Linodes in one Region. This allows swapping, shuffling, or otherwise reorganizing IPv4 Addresses to your Linodes. When the assignment is finished, all Linodes must end up with at least one public IPv4 and no more than one private IPv4.
```js
linode.assignIPs({
"body": null
}, context)
```
#### Input
* input `object`
* body **required** `object`
* assignments **required** `array`: The list of assignments to make. You must have read_write access to all IPs being assigned and all Linodes being assigned to in order for the assignments to succeed.
* items `object`
* address `string`: Ths IP Address for this assignment. Must be a IPv4 address you can access in the Region specified. May be a public or private address.
* linode_id `integer`: The ID of the Linode to assign this address to. The IP's previous Linode will lose this address, and must end up with at least one public address and no more than one private address once all assignments have been made.
* region **required** `string`: The ID of the Region in which these assignments are to take place. All IPs and Linodes must exist in this Region.
#### Output
* output `object`
### shareIPs
Configure shared IPs. A shared IP may be brought up on a Linode other than the one it lists in its response. This can be used to allow one Linode to begin serving requests should another become unresponsive.
```js
linode.shareIPs({
"body": null
}, context)
```
#### Input
* input `object`
* body **required** `object`
* ips **required** `array`: A list of IPs that will be shared with this Linode. When this is finished, the given Linode will be able to bring up these addresses in addition to the Linodes that these addresses belong to. You must have access to all of these addresses and they must be in the same Region as the Linode.
* items `string`
* linode_id **required** `integer`: The ID of the Linode that the addresses will be shared with.
#### Output
* output `object`
### getIPv6Pools
Displays the IPv6 pools on your Account.
```js
linode.getIPv6Pools({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [IPv6Pool](#ipv6pool)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getIPv6Ranges
Displays the IPv6 ranges on your Account.
```js
linode.getIPv6Ranges({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [IPv6Range](#ipv6range)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getNodeBalancers
Returns a paginated list of NodeBalancers you have access to.
```js
linode.getNodeBalancers({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [NodeBalancer](#nodebalancer)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createNodeBalancer
Creates a NodeBalancer in the requested Region. This NodeBalancer will not start serving requests until it is configured.
```js
linode.createNodeBalancer({
"body": null
}, context)
```
#### Input
* input `object`
* body **required** `object`
* client_conn_throttle [NodeBalancer/properties/client_conn_throttle](#nodebalancer/properties/client_conn_throttle)
* configs `array`: The ports to configure this NodeBalancer with on creation. Each config must have a unique port and at least one Node.
* items
* algorithm `string` (values: roundrobin, leastconn, source): What algorithm this NodeBalancer should use for routing traffic to backends.
* check `string` (values: none, connection, http, http_body): The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down.
* check_attempts `integer`: How many times to attempt a check before considering a backend to be down.
* check_body `string`: This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down.
* check_interval `integer`: How often, in seconds, to check that backends are up and serving requests.
* check_passive `boolean`: If true, any response from this backend with a `5xx` status code will be enough for it to be considered unhealthy and taken out of rotation.
* check_path `string`: The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
* check_timeout `integer`: How long, in seconds, to wait for a check attempt before considering it failed.
* cipher_suite `string` (values: recommended, legacy): What ciphers to use for SSL connections served by this NodeBalancer.
* id `integer`: This config's unique ID
* nodebalancer_id `integer`: The ID for the NodeBalancer this config belongs to.
* nodes_status `object`: A structure containing information about the health of the backends for this port. This information is updated periodically as checks are performed against backends.
* down `integer`: The number of backends considered to be "DOWN" and unhealthy. These are not in rotation, and not serving requests.
* up `integer`: The number of backends considered to be "UP" and healthy, and that are serving requests.
* port `integer`: The port this Config is for. These values must be unique across configs on a single NodeBalancer (you can't have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443.
* protocol `string` (values: http, https, tcp): The protocol this port is configured to serve.
* ssl_cert `string`: The PEM-formatted public SSL certificate (or the combined PEM-formatted SSL
* ssl_commonname `string`: The read-only common name automatically derived from the SSL certificate assigned to this NodeBalancerConfig. Please refer to this field to verify that the appropriate certificate is assigned to your NodeBalancerConfig.
* ssl_fingerprint `string`: The read-only fingerprint automatically derived from the SSL certificate assigned to this NodeBalancerConfig. Please refer to this field to verify that the appropriate certificate is assigned to your NodeBalancerConfig.
* ssl_key `string`: The PEM-formatted private key for the SSL certificate set in the `ssl_cert` field.
* stickiness `string` (values: none, table, http_cookie): Controls how session stickiness is handled on this port.
* nodes `array`: The NodeBalancer Nodes that serve this port. When creating a NodeBalancer this way, at least one Node is required per configured port.
* items [NodeBalancerNode](#nodebalancernode)
* label [NodeBalancer/properties/label](#nodebalancer/properties/label)
* region **required** `string`: The ID of the Region to create this NodeBalancer in.
#### Output
* output [NodeBalancer](#nodebalancer)
### deleteNodeBalancer
Deletes a NodeBalancer.
**This is a destructive action and cannot be undone.**
Deleting a NodeBalancer will also delete all associated Configs and Nodes, although the backend servers represented by the Nodes will not be changed or removed. Deleting a NodeBalancer will cause you to lose access to the IP Addresses assigned to this NodeBalancer.
```js
linode.deleteNodeBalancer({
"nodeBalancerId": 0
}, context)
```
#### Input
* input `object`
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
#### Output
* output `object`
### getNodeBalancer
Returns a single NodeBalancer you can access.
```js
linode.getNodeBalancer({
"nodeBalancerId": 0
}, context)
```
#### Input
* input `object`
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
#### Output
* output [NodeBalancer](#nodebalancer)
### updateNodeBalancer
Updates information about a NodeBalancer you can access.
```js
linode.updateNodeBalancer({
"body": {},
"nodeBalancerId": 0
}, context)
```
#### Input
* input `object`
* body **required** [NodeBalancer](#nodebalancer)
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
#### Output
* output [NodeBalancer](#nodebalancer)
### getNodeBalancerConfigs
Returns a paginated list of NodeBalancer Configs associated with this NodeBalancer. NodeBalancer Configs represent individual ports that this NodeBalancer will accept traffic on, one Config per port.
For example, if you wanted to accept standard HTTP traffic, you would need a Config listening on port 80.
```js
linode.getNodeBalancerConfigs({
"nodeBalancerId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
#### Output
* output `object`
* data `array`
* items [NodeBalancerConfig](#nodebalancerconfig)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createNodeBalancerConfig
Creates a NodeBalancer Config, which allows the NodeBalancer to accept traffic on a new port. You will need to add NodeBalancer Nodes to the new Config before it can actually serve requests.
```js
linode.createNodeBalancerConfig({
"nodeBalancerId": 0
}, context)
```
#### Input
* input `object`
* body [NodeBalancerConfig](#nodebalancerconfig)
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
#### Output
* output [NodeBalancerConfig](#nodebalancerconfig)
### deleteNodeBalancerConfig
Deletes the Config for a port of this NodeBalancer.
**This cannot be undone.**
Once completed, this NodeBalancer will no longer respond to requests on the given port. This also deletes all associated NodeBalancerNodes, but the Linodes they were routing traffic to will be unchanged and will not be removed.
```js
linode.deleteNodeBalancerConfig({
"nodeBalancerId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the config to access.
#### Output
* output `object`
### getNodeBalancerConfig
Returns configuration information for a single port of this NodeBalancer.
```js
linode.getNodeBalancerConfig({
"nodeBalancerId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the config to access.
#### Output
* output [NodeBalancerConfig](#nodebalancerconfig)
### updateNodeBalancerConfig
Updates the configuration for a single port on a NodeBalancer.
```js
linode.updateNodeBalancerConfig({
"body": {},
"nodeBalancerId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* body **required** [NodeBalancerConfig](#nodebalancerconfig)
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the config to access.
#### Output
* output [NodeBalancerConfig](#nodebalancerconfig)
### getNodeBalancerConfigNodes
Returns a paginated list of NodeBalancer nodes associated with this Config. These are the backends that will be sent traffic for this port.
```js
linode.getNodeBalancerConfigNodes({
"nodeBalancerId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the NodeBalancer config to access.
#### Output
* output `object`
* data `array`
* items [NodeBalancerNode](#nodebalancernode)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createNodeBalancerNode
Creates a NodeBalancer Node, a backend that can accept traffic for this NodeBalancer Config. Nodes are routed requests on the configured port based on their status.
```js
linode.createNodeBalancerNode({
"body": null,
"nodeBalancerId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* body **required**
* address `string`: The private IP Address where this backend can be reached. This _must_ be a private IP address.
* config_id `integer`: The NodeBalancer Config ID that this Node belongs to.
* id `integer`: This node's unique ID.
* label `string`: The label for this node. This is for display purposes only.
* mode `string` (values: accept, reject, drain, backup): The mode this NodeBalancer should use when sending traffic to this backend.
* nodebalancer_id `integer`: The NodeBalancer ID that this Node belongs to.
* status `string` (values: unknown, UP, DOWN): The current status of this node, based on the configured checks of its NodeBalancer Config.
* weight `integer`: Used when picking a backend to serve a request and is not pinned to a single backend yet. Nodes with a higher weight will receive more traffic.
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the NodeBalancer config to access.
#### Output
* output [NodeBalancerNode](#nodebalancernode)
### deleteNodeBalancerConfigNode
Deletes a Node from this Config. This backend will no longer receive traffic for the configured port of this NodeBalancer.
This does not change or remove the Linode whose address was used in the creation of this Node.
```js
linode.deleteNodeBalancerConfigNode({
"nodeBalancerId": 0,
"configId": 0,
"nodeId": 0
}, context)
```
#### Input
* input `object`
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the Config to access
* nodeId **required** `integer`: The ID of the Node to access
#### Output
* output `object`
### getNodeBalancerNode
Returns information about a single Node, a backend for this NodeBalancer's configured port.
```js
linode.getNodeBalancerNode({
"nodeBalancerId": 0,
"configId": 0,
"nodeId": 0
}, context)
```
#### Input
* input `object`
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the Config to access
* nodeId **required** `integer`: The ID of the Node to access
#### Output
* output [NodeBalancerNode](#nodebalancernode)
### updateNodeBalancerNode
Updates information about a Node, a backend for this NodeBalancer's configured port.
```js
linode.updateNodeBalancerNode({
"body": {},
"nodeBalancerId": 0,
"configId": 0,
"nodeId": 0
}, context)
```
#### Input
* input `object`
* body **required** [NodeBalancerNode](#nodebalancernode)
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the Config to access
* nodeId **required** `integer`: The ID of the Node to access
#### Output
* output [NodeBalancerNode](#nodebalancernode)
### rebuildNodeBalancerConfig
Rebuilds a NodeBalancer Config and its Nodes that you have permission to modify.
```js
linode.rebuildNodeBalancerConfig({
"body": null,
"nodeBalancerId": 0,
"configId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* configs `array`: Each config must have a unique port and at least one Node. Additionally:
* items
* algorithm `string` (values: roundrobin, leastconn, source): What algorithm this NodeBalancer should use for routing traffic to backends.
* check `string` (values: none, connection, http, http_body): The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down.
* check_attempts `integer`: How many times to attempt a check before considering a backend to be down.
* check_body `string`: This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down.
* check_interval `integer`: How often, in seconds, to check that backends are up and serving requests.
* check_passive `boolean`: If true, any response from this backend with a `5xx` status code will be enough for it to be considered unhealthy and taken out of rotation.
* check_path `string`: The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
* check_timeout `integer`: How long, in seconds, to wait for a check attempt before considering it failed.
* cipher_suite `string` (values: recommended, legacy): What ciphers to use for SSL connections served by this NodeBalancer.
* id `integer`: This config's unique ID
* nodebalancer_id `integer`: The ID for the NodeBalancer this config belongs to.
* nodes_status `object`: A structure containing information about the health of the backends for this port. This information is updated periodically as checks are performed against backends.
* down `integer`: The number of backends considered to be "DOWN" and unhealthy. These are not in rotation, and not serving requests.
* up `integer`: The number of backends considered to be "UP" and healthy, and that are serving requests.
* port `integer`: The port this Config is for. These values must be unique across configs on a single NodeBalancer (you can't have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443.
* protocol `string` (values: http, https, tcp): The protocol this port is configured to serve.
* ssl_cert `string`: The PEM-formatted public SSL certificate (or the combined PEM-formatted SSL
* ssl_commonname `string`: The read-only common name automatically derived from the SSL certificate assigned to this NodeBalancerConfig. Please refer to this field to verify that the appropriate certificate is assigned to your NodeBalancerConfig.
* ssl_fingerprint `string`: The read-only fingerprint automatically derived from the SSL certificate assigned to this NodeBalancerConfig. Please refer to this field to verify that the appropriate certificate is assigned to your NodeBalancerConfig.
* ssl_key `string`: The PEM-formatted private key for the SSL certificate set in the `ssl_cert` field.
* stickiness `string` (values: none, table, http_cookie): Controls how session stickiness is handled on this port.
* nodes `array`: The NodeBalancer Node(s) that serve this port. At least one Node is required per configured port.
* items [NodeBalancerNode](#nodebalancernode)
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
* configId **required** `integer`: The ID of the Config to access.
#### Output
* output [NodeBalancer](#nodebalancer)
### nodebalancers.nodeBalancerId.stats.get
Returns detailed statistics about the requested NodeBalancer.
```js
linode.nodebalancers.nodeBalancerId.stats.get({
"nodeBalancerId": 0
}, context)
```
#### Input
* input `object`
* nodeBalancerId **required** `integer`: The ID of the NodeBalancer to access.
#### Output
* output [NodeBalancerStats](#nodebalancerstats)
### getObjectStorageBuckets
Returns a paginated list of all Object Storage Buckets that you own.
This endpoint is available for convenience. It is recommended that instead you
use the more [fully-featured S3 API](https://docs.ceph.com/docs/mimic/radosgw/s3/serviceops/) directly.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receive breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.getObjectStorageBuckets(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [ObjectStorageBucket](#objectstoragebucket)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createObjectStorageBucket
Creates an Object Storage Bucket in the cluster specified. If the
bucket already exists and is owned by you, this endpoint will return a
`200` response with that bucket as if it had just been created.
This endpoint is available for convenience. It is recommended that instead you
use the more [fully-featured S3 API](https://docs.ceph.com/docs/mimic/radosgw/s3/bucketops/#put-bucket) directly.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receive breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.createObjectStorageBucket({}, context)
```
#### Input
* input `object`
* body `object`
* acl `string` (values: private, public-read, authenticated-read, public-read-write): The Access Control Level of the bucket using a canned ACL string. For more fine-grained control of ACLs, use the S3 API directly.
* cluster **required** `string`: The ID of the Object Storage Cluster where this bucket should be created.
* cors_enabled `boolean`: If true, the bucket will be created with CORS enabled for all origins. For more fine-grained controls of CORS, use the S3 API directly.
* label **required** `string`: The name for this bucket. Must be unique in the cluster you are creating the bucket in, or an error will be returned.
#### Output
* output [ObjectStorageBucket](#objectstoragebucket)
### deleteObjectStorageBucket
Removes a single bucket. While buckets containing objects _may_ be deleted by including the `force` option in the request, such operations will fail if the bucket contains too many objects. The recommended way to empty large buckets is to use the [S3 API to configure lifecycle policies](https://docs.ceph.com/docs/master/radosgw/bucketpolicy/#) that remove all objects, then delete the bucket.
This endpoint is available for convenience. It is recommended that instead you use the more [fully- featured S3 API](https://docs.ceph.com/docs/mimic/radosgw/s3/bucketops/#delete-bucket) directly.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with `/v4beta` instead of `/v4`, and be aware that this endpoint may receive breaking updates in the future. This notice will be removed when this endpoint is out of beta.
```js
linode.deleteObjectStorageBucket({
"clusterId": "",
"bucket": ""
}, context)
```
#### Input
* input `object`
* force `integer`: If false, this operation will fail if the bucket is not empty. If true, this operation will attempt to remove the bucket and its contents; very large buckets may still return an error and require object deletion manually or through object lifecycle management. See [the S3 API docs](https://docs.ceph.com/docs/mimic/radosgw/s3/bucketops/#delete-bucket) for details.
* clusterId **required** `string`: The ID of the cluster this bucket exists in.
* bucket **required** `string`: The bucket name.
#### Output
* output `object`
### getObjectStorageBucket
Returns a single Object Storage Bucket.
This endpoint is available for convenience. It is recommended that instead you
use the more [fully-featured S3 API](https://docs.ceph.com/docs/mimic/radosgw/s3/bucketops/#get-bucket) directly.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receive breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.getObjectStorageBucket({
"clusterId": "",
"bucket": ""
}, context)
```
#### Input
* input `object`
* clusterId **required** `string`: The ID of the cluster this bucket exists in.
* bucket **required** `string`: The bucket name.
#### Output
* output [ObjectStorageBucket](#objectstoragebucket)
### modifyObjectStorageBucketAccess
Allows changing basic Cross-origin Resource Sharing (CORS) and Access Control Level (ACL) settings.
Only allows enabling/disabling CORS for all origins, and/or setting canned ACLs.
For more fine-grained control of both systems, please use the S3 API directly.
This endpoint is available for convenience. It is recommended that instead you
use the more more [fully-featured S3 API](https://docs.ceph.com/docs/mimic/radosgw/s3/bucketops/#put-bucket-acl) directly.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receive breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.modifyObjectStorageBucketAccess({
"clusterId": "",
"bucket": ""
}, context)
```
#### Input
* input `object`
* body `object`
* acl `string` (values: private, public-read, authenticated-read): The Access Control Level of the bucket, as a canned ACL string. For more fine-grained control of ACLs, use the S3 API directly.
* cors_enabled `boolean`: If true, the bucket will be created with CORS enabled for all origins. For more fine-grained controls of CORS, use the S3 API directly.
* clusterId **required** `string`: The ID of the cluster this bucket exists in.
* bucket **required** `string`: The bucket name.
#### Output
* output `object`
### getObjectStorageBucketContent
Returns the contents of a bucket. The contents are paginated using a `marker`,
which is the name of the last object on the previous page. Objects may
be filtered by `prefix` and `delimiter` as well; see Query Parameters for more
information.
This endpoint is available for convenience. It is recommended that instead you
use the more [fully-featured S3 API](https://docs.ceph.com/docs/luminous/radosgw/s3/bucketops/#get-bucket) directly.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receive breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.getObjectStorageBucketContent({
"clusterId": "",
"bucket": ""
}, context)
```
#### Input
* input `object`
* marker `string`: The "marker" for this request, which can be used to paginate through large buckets. Its value should be the value of the `next_marker` property returned with the last page. Listing bucket contents *does not* support arbitrary page access. See the `next_marker` property in the responses section for more details.
* delimiter `string`: The delimiter for object names; if given, object names will be returned up to the first occurrence of this character. This is most commonly used with the `/` character to allow bucket transversal in a manner similar to a filesystem, however any delimiter may be used. Use in conjunction with `prefix` to see object names past the first occurrence of the delimiter.
* prefix `string`: Filters objects returned to only those whose name start with the given prefix. Commonly used in conjunction with `delimiter` to allow transversal of bucket contents in a manner similar to a filesystem.
* page_size `integer`: The number of items to return per page.
* clusterId **required** `string`: The ID of the cluster this bucket exists in.
* bucket **required** `string`: The bucket name.
#### Output
* output `object`
* data `array`: This page of objects in the bucket.
* items [ObjectStorageObject](#objectstorageobject)
### createObjectStorageObjectURL
Creates a pre-signed URL to access a single Object in a bucket. This
can be used to share objects, and also to create/delete objects by using
the appropriate HTTP method in your request body's `method` parameter.
This endpoint is available for convenience. It is recommended that instead you
use the more [fully-featured S3 API](https://docs.ceph.com/docs/mimic/radosgw/s3/)
directly.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receive breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.createObjectStorageObjectURL({
"clusterId": "",
"bucket": ""
}, context)
```
#### Input
* input `object`
* body `object`
* content_type `string`: The expected `Content-type` header of the request this signed URL will be valid for. If provided, the `Content-type` header _must_ be sent with the request when this URL is used, and _must_ be the same as it was when the signed URL was created. Required for all methods *except* "GET" or "DELETE".
* expires_in `integer`: How long this signed URL will be valid for, in seconds. If omitted, the URL will be valid for 3600 seconds (1 hour).
* method **required** `string`: The HTTP method allowed to be used with the pre-signed URL.
* name **required** `string`: The name of the object that will be accessed with the pre-signed URL. This object need not exist, and no error will be returned if it doesn't. This behavior is useful for generating pre-signed URLs to upload new objects to by setting the `method` to "PUT".
* clusterId **required** `string`: The ID of the cluster this bucket exists in.
* bucket **required** `string`: The bucket name.
#### Output
* output `object`
* url `string`: The signed URL to perform the request at.
### getObjectStorageClusters
Returns a paginated list of Object Storage Clusters that are available for
use. Users can connect to the clusters with third party clients to create buckets
and upload objects.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receiving breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.getObjectStorageClusters(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [ObjectStorageCluster](#objectstoragecluster)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getObjectStorageCluster
Returns a single Object Storage Cluster.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receiving breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.getObjectStorageCluster({
"clusterId": ""
}, context)
```
#### Input
* input `object`
* clusterId **required** `string`: The ID of the Cluster.
#### Output
* output [ObjectStorageCluster](#objectstoragecluster)
### getObjectStorageKeys
Returns a paginated list of Object Storage Keys for authenticating to
the Object Storage S3 API.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receiving breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.getObjectStorageKeys(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [ObjectStorageKey](#objectstoragekey)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createObjectStorageKeys
Provisions a new Object Storage Key on your account.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receiving breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.createObjectStorageKeys({}, context)
```
#### Input
* input `object`
* body `object`
* label `string`: The label for this keypair, for display purposes only.
#### Output
* output
* access_key `string`: This keypair's access key. This is not secret.
* id `integer`: This keypair's unique ID
* label `string`: The label given to this key. For display purposes only.
* secret_key `string`: This keypair's secret key. **Only returned on key creation**.
### deleteObjectStorageKey
Revokes an Object Storage Key. This keypair will no longer be usable by third-party clients.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receiving breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.deleteObjectStorageKey({
"keyId": 0
}, context)
```
#### Input
* input `object`
* keyId **required** `integer`: The key to look up.
#### Output
* output `object`
### getObjectStorageKey
Returns a single Object Storage Key provisioned for your account.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receiving breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.getObjectStorageKey({
"keyId": 0
}, context)
```
#### Input
* input `object`
* keyId **required** `integer`: The key to look up.
#### Output
* output [ObjectStorageKey](#objectstoragekey)
### updateObjectStorageKey
Updates an Object Storage Key on your account.
**Beta**: This endpoint is in beta. Please make sure to prepend all requests with
`/v4beta` instead of `/v4`, and be aware that this endpoint may receiving breaking
updates in the future. This notice will be removed when this endpoint is out of
beta.
```js
linode.updateObjectStorageKey({
"keyId": 0
}, context)
```
#### Input
* input `object`
* body [ObjectStorageKey](#objectstoragekey)
* keyId **required** `integer`: The key to look up.
#### Output
* output [ObjectStorageKey](#objectstoragekey)
### getProfile
Returns information about the current User. This can be used to see who is acting in applications where more than one token is managed. For example, in third-party OAuth applications.
This endpoint is always accessible, no matter what OAuth scopes the acting token has.
```js
linode.getProfile(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output [Profile](#profile)
### updateProfile
Update information in your Profile. This endpoint requires the "account:read_write" OAuth Scope.
```js
linode.updateProfile({
"body": {}
}, context)
```
#### Input
* input `object`
* body **required** [Profile](#profile)
#### Output
* output [Profile](#profile)
### getProfileApps
This is a collection of OAuth apps that you've given access to your Account, and includes the level of access granted.
```js
linode.getProfileApps({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [AuthorizedApp](#authorizedapp)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### deleteProfileApp
Expires this app token. This token may no longer be used to access your Account.
```js
linode.deleteProfileApp({
"appId": 0
}, context)
```
#### Input
* input `object`
* appId **required** `integer`: The authorized app ID to manage.
#### Output
* output `object`
### getProfileApp
Returns information about a single app you've authorized to access your Account.
```js
linode.getProfileApp({
"appId": 0
}, context)
```
#### Input
* input `object`
* appId **required** `integer`: The authorized app ID to manage.
#### Output
* output [AuthorizedApp](#authorizedapp)
### getDevices
Returns a paginated list of active TrustedDevices for your User. Browsers with an active Remember Me Session are logged into your account until the session expires or is revoked.
```js
linode.getDevices(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [TrustedDevice](#trusteddevice)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### revokeTrustedDevice
Revoke an active TrustedDevice for your User. Once a TrustedDevice is revoked, this device will have to log in again before accessing your Linode account.
```js
linode.revokeTrustedDevice({
"deviceId": 0
}, context)
```
#### Input
* input `object`
* deviceId **required** `integer`: The ID of the TrustedDevice
#### Output
* output `object`
### getTrustedDevice
Returns a single active TrustedDevice for your User.
```js
linode.getTrustedDevice({
"deviceId": 0
}, context)
```
#### Input
* input `object`
* deviceId **required** `integer`: The ID of the TrustedDevice
#### Output
* output [TrustedDevice](#trusteddevice)
### getProfileGrants
This returns a GrantsResponse describing what the acting User has been granted access to. For unrestricted users, this will return a 204 and no body because unrestricted users have access to everything without grants. This will not return information about entities you do not have access to. This endpoint is useful when writing third-party OAuth applications to see what options you should present to the acting User.
For example, if they do not have `global.add_linodes`, you might not display a button to deploy a new Linode.
Any client may access this endpoint; no OAuth scopes are required.
```js
linode.getProfileGrants(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output [GrantsResponse](#grantsresponse)
### getUserPreferences
View a list of user preferences tied to the OAuth client that generated
the token making the request. The user preferences endpoints allow
consumers of the API to store arbitrary JSON data, such as a user's font
size preference or preferred display name. User preferences are available
for each OAuth client registered to your account, and as such an account can
have multiple user preferences.
```js
linode.getUserPreferences(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`: A dictionary of user preferences.
### updateUserPreferences
Updates a user's preferences. These preferences are tied to the OAuth client that generated the token making the request. The user preferences endpoints allow consumers of the API to store arbitrary JSON data, such as a user's font size preference or preferred display name. An account may have multiple preferences. Preferences, and the pertaining request body, may contain any arbitrary JSON data that the user would like to store.
```js
linode.updateUserPreferences({
"body": {}
}, context)
```
#### Input
* input `object`
* body **required** `object`: Arbitrary JSON of your choosing.
#### Output
* output `object`: An object of user preferences.
### getSSHKeys
Returns a collection of SSH Keys you've added to your Profile.
```js
linode.getSSHKeys({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [SSHKey](#sshkey)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### addSSHKey
Adds an SSH Key to your Account profile.
```js
linode.addSSHKey({}, context)
```
#### Input
* input `object`
* body [SSHKeyRequest](#sshkeyrequest)
#### Output
* output [SSHKey](#sshkey)
### deleteSSHKey
Deletes an SSH Key you have access to.
**Note:** deleting an SSH Key will *not* remove it from any Linode or Disk that was deployed with `authorized_keys`. In those cases, the keys must be manually deleted on the Linode or Disk. This endpoint will only delete the key's association from your Profile.
```js
linode.deleteSSHKey({
"sshKeyId": 0
}, context)
```
#### Input
* input `object`
* sshKeyId **required** `integer`: The ID of the SSHKey
#### Output
* output `object`
### getSSHKey
Returns a single SSH Key object identified by `id` that you have access to view.
```js
linode.getSSHKey({
"sshKeyId": 0
}, context)
```
#### Input
* input `object`
* sshKeyId **required** `integer`: The ID of the SSHKey
#### Output
* output [SSHKey](#sshkey)
### updateSSHKey
Updates an SSH Key that you have permission to `read_write`.
```js
linode.updateSSHKey({
"body": {},
"sshKeyId": 0
}, context)
```
#### Input
* input `object`
* body **required** [SSHKey](#sshkey)
* sshKeyId **required** `integer`: The ID of the SSHKey
#### Output
* output [SSHKey](#sshkey)
### tfaDisable
Disables Two Factor Authentication for your User. Once successful, login attempts from untrusted computers will only require a password before being successful. This is less secure, and is discouraged.
```js
linode.tfaDisable(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
### tfaEnable
Generates a Two Factor secret for your User. TFA will not be enabled until you have successfully confirmed the code you were given with [tfa-enable-confirm](/api/v4/profile-tfa-enable-confirm/#post) (see below). Once enabled, logins from untrusted computers will be required to provide a TFA code before they are successful.
```js
linode.tfaEnable(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* expiry `string`: When this Two Factor secret expires.
* secret `string`: Your Two Factor secret. This is used to generate time-based two factor codes required for logging in. Doing this will be required to confirm TFA an actually enable it.
### tfaConfirm
Confirms that you can successfully generate Two Factor codes and enables TFA on your Account. Once this is complete, login attempts from untrusted computers will be required to provide a Two Factor code before they are successful.
```js
linode.tfaConfirm({
"body": null
}, context)
```
#### Input
* input `object`
* body **required** `object`
* tfa_code `string`: The Two Factor code you generated with your Two Factor secret. These codes are time-based, so be sure it is current.
#### Output
* output `object`
* scratch `string`: A one-use code that can be used in place of your Two Factor code, in case you are unable to generate one. Keep this in a safe place to avoid being locked out of your Account.
### getPersonalAccessTokens
Returns a paginated list of Personal Access Tokens currently active for your User.
```js
linode.getPersonalAccessTokens(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [PersonalAccessToken](#personalaccesstoken)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createPersonalAccessToken
Creates a Personal Access Token for your User. The raw token will be returned in the response, but will never be returned again afterward so be sure to take note of it. You may create a token with _at most_ the scopes of your current token. The created token will be able to access your Account until the given expiry, or until it is revoked.
```js
linode.createPersonalAccessToken({
"body": null
}, context)
```
#### Input
* input `object`
* body **required** `object`
* expiry `string`: When this token should be valid until. If omitted, the new token will be valid until it is manually revoked.
* label [PersonalAccessToken/properties/label](#personalaccesstoken/properties/label)
* scopes `string`: The scopes to create the token with. These cannot be changed after creation, and may not exceed the scopes of the acting token. If omitted, the new token will have the same scopes as the acting token.
#### Output
* output [PersonalAccessToken](#personalaccesstoken)
### deletePersonalAccessToken
Revokes a Personal Access Token. The token will be invalidated immediately, and requests using that token will fail with a 401. It is possible to revoke access to the token making the request to revoke a token, but keep in mind that doing so could lose you access to the api and require you to create a new token through some other means.
```js
linode.deletePersonalAccessToken({
"tokenId": 0
}, context)
```
#### Input
* input `object`
* tokenId **required** `integer`: The ID of the token to access.
#### Output
* output `object`
### getPersonalAccessToken
Returns a single Personal Access Token.
```js
linode.getPersonalAccessToken({
"tokenId": 0
}, context)
```
#### Input
* input `object`
* tokenId **required** `integer`: The ID of the token to access.
#### Output
* output [PersonalAccessToken](#personalaccesstoken)
### updatePersonalAccessToken
Updates a Personal Access Token.
```js
linode.updatePersonalAccessToken({
"body": {},
"tokenId": 0
}, context)
```
#### Input
* input `object`
* body **required** [PersonalAccessToken](#personalaccesstoken)
* tokenId **required** `integer`: The ID of the token to access.
#### Output
* output [PersonalAccessToken](#personalaccesstoken)
### getRegions
Lists the Regions available for Linode services. Not all services are guaranteed to be
available in all Regions.
```js
linode.getRegions(null, context)
```
#### Input
*This action has no parameters*
#### Output
* output `object`
* data `array`
* items [Region](#region)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getRegion
Returns a single Region.
```js
linode.getRegion({
"regionId": ""
}, context)
```
#### Input
* input `object`
* regionId **required** `string`: ID of the Region to look up.
#### Output
* output [Region](#region)
### getTickets
Returns a collection of Support Tickets on your Account. Support Tickets can be both tickets you open with Linode for support, as well as tickets generated by Linode regarding your Account.
This collection includes all Support Tickets generated on your Account, with open tickets returned first.
```js
linode.getTickets({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [SupportTicket](#supportticket)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createTicket
Open a Support Ticket.
Only one of the ID attributes (`linode_id`, `domain_id`, etc.) can be set on a single Support Ticket.
```js
linode.createTicket({}, context)
```
#### Input
* input `object`
* body [SupportTicketRequest](#supportticketrequest)
#### Output
* output [SupportTicket](#supportticket)
### getTicket
Returns a Support Ticket under your Account.
```js
linode.getTicket({
"ticketId": 0
}, context)
```
#### Input
* input `object`
* ticketId **required** `integer`: The ID of the Support Ticket.
#### Output
* output [SupportTicket](#supportticket)
### createTicketAttachment
Adds a file attachment to an existing Support Ticket on your Account. File attachments are used to assist our Support team in resolving your Ticket. Examples of attachments are screen shots and text files that provide additional information.
Note: Accepted file extensions include: .gif, .jpg, .jpeg, .pjpg, .pjpeg, .tif, .tiff, .png, .pdf, or .txt.
```js
linode.createTicketAttachment({
"body": null,
"ticketId": 0
}, context)
```
#### Input
* input `object`
* ticketId **required** `integer`: The ID of the Support Ticket.
#### Output
* output `object`
### closeTicket
Closes a Support Ticket you have access to modify.
```js
linode.closeTicket({
"ticketId": 0
}, context)
```
#### Input
* input `object`
* ticketId **required** `integer`: The ID of the Support Ticket.
#### Output
* output `object`
### getTicketReplies
Returns a collection of replies to a Support Ticket on your Account.
```js
linode.getTicketReplies({
"ticketId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* ticketId **required** `integer`: The ID of the Support Ticket.
#### Output
* output `object`
* data `array`
* items [SupportTicketReply](#supportticketreply)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createTicketReply
Adds a reply to an existing Support Ticket.
```js
linode.createTicketReply({
"body": null,
"ticketId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* description **required** `string`: The content of your reply.
* ticketId **required** `integer`: The ID of the Support Ticket.
#### Output
* output [SupportTicketReply](#supportticketreply)
### getTags
Tags are User-defined labels attached to objects in your Account, such as Linodes. They are used for specifying and grouping attributes of objects that are relevant to the User.
This endpoint returns a paginated list of Tags on your account.
```js
linode.getTags({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [Tag](#tag)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createTag
Creates a new Tag and optionally tags requested objects with it immediately.
**Important**: You must be an unrestricted User in order to add or modify Tags.
```js
linode.createTag({}, context)
```
#### Input
* input `object`
* body `object`
* domains `array`: A list of Domain IDs to apply the new Tag to. You must be allowed to `read_write` all of the requested Domains, or the Tag will not be created and an error will be returned.
* items `integer`
* label **required** `string`: The new Tag.
* linodes `array`: A list of Linode IDs to apply the new Tag to. You must be allowed to `read_write` all of the requested Linodes, or the Tag will not be created and an error will be returned.
* items `integer`
* nodebalancers `array`: A list of NodeBalancer IDs to apply the new Tag to. You must be allowed to `read_write` all of the requested NodeBalancers, or the Tag will not be created and an error will be returned.
* items `integer`
* volumes `array`: A list of Volume IDs to apply the new Tag to. You must be allowed to `read_write` all of the requested Volumes, or the Tag will not be created and an error will be returned.
* items `integer`
#### Output
* output [Tag](#tag)
### deleteTag
Remove a Tag from all objects and delete it.
**Important**: You must be an unrestricted User in order to add or modify Tags.
```js
linode.deleteTag({
"label": ""
}, context)
```
#### Input
* input `object`
* label **required** `string`
#### Output
* output `object`
### getTaggedObjects
Returns a paginated list of all objects you've tagged with the requested Tag. This is a mixed collection of all object types.
```js
linode.getTaggedObjects({
"label": ""
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* label **required** `string`
#### Output
* output `object`
* data `array`
* items `object`
* type `string`
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### getVolumes
Returns a paginated list of Volumes you have permission to view.
```js
linode.getVolumes({}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
#### Output
* output `object`
* data `array`
* items [Volume](#volume)
* page [PaginationEnvelope/properties/page](#paginationenvelope/properties/page)
* pages [PaginationEnvelope/properties/pages](#paginationenvelope/properties/pages)
* results [PaginationEnvelope/properties/results](#paginationenvelope/properties/results)
### createVolume
Creates a Volume on your Account. In order for this to complete successfully, your User must have the `add_volumes` grant. Creating a new Volume will start accruing additional charges on your account.
```js
linode.createVolume({
"body": {}
}, context)
```
#### Input
* input `object`
* body **required** `object`
* tags `array`: An array of Tags applied to this object. Tags are for organizational purposes only.
* items `string`
* config_id `integer`: When creating a Volume attached to a Linode, the ID of the Linode Config to include the new Volume in. This Config must belong to the Linode referenced by `linode_id`. Must _not_ be provided if `linode_id` is not sent. If a `linode_id` is sent without a `config_id`, the volume will be attached:
* label `string`: The Volume's label, which is also used in the `filesystem_path` of the resulting volume.
* linode_id `integer`: The Linode this volume should be attached to upon creation. If not given, the volume will be created without an attachment.
* region `string`: The Region to deploy this Volume in. This is only required if a linode_id is not given.
* size `integer`: The initial size of this volume, in GB. Be aware that volumes may only be resized up after creation.
#### Output
* output [Volume](#volume)
### deleteVolume
Deletes a Volume you have permission to `read_write`.
**Deleting a Volume is a destructive action and cannot be undone.**
Deleting stops billing for the Volume. You will be billed for time used within
the billing period the Volume was active.
```js
linode.deleteVolume({
"volumeId": 0
}, context)
```
#### Input
* input `object`
* volumeId **required** `integer`: ID of the Volume to look up.
#### Output
* output `object`
### getVolume
Get information about a single Volume.
```js
linode.getVolume({
"volumeId": 0
}, context)
```
#### Input
* input `object`
* page `integer`: The page of a collection to return.
* page_size `integer`: The number of items to return per page.
* volumeId **required** `integer`: ID of the Volume to look up.
#### Output
* output [Volume](#volume)
### updateVolume
Updates a Volume that you have permission to `read_write`.
```js
linode.updateVolume({
"body": null,
"volumeId": 0
}, context)
```
#### Input
* input `object`
* body **required**
* tags `array`: An array of Tags applied to this object. Tags are for organizational purposes only.
* items `string`
* created `string`: When this Volume was created.
* filesystem_path `string`: The full filesystem path for the Volume based on the Volume's label. Path is /dev/disk/by-id/scsi-0Linode_Volume_ + Volume label.
* id `integer`: The unique ID of this Volume.
* label **required** `string`: The Volume's label is for display purposes only.
* linode_id `integer`: If a Volume is attached to a specific Linode, the ID of that Linode will be displayed here.
* region [Region/properties/id](#region/properties/id)
* size `integer`: The Volume's size, in GiB.
* status `string` (values: creating, active, resizing, contact_support): The current status of the volume. Can be one of:
* updated `string`: When this Volume was last updated.
* linode_id
* region
* size
* volumeId **required** `integer`: ID of the Volume to look up.
#### Output
* output [Volume](#volume)
### attachVolume
Attaches a Volume on your Account to an existing Linode on your Account. In order for this request to complete successfully, your User must have `read_only` or `read_write` permission to the Volume and `read_write` permission to the Linode. Additionally, the Volume and Linode must be located in the same Region.
```js
linode.attachVolume({
"body": {},
"volumeId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* config_id `integer`: The ID of the Linode Config to include this Volume in. Must belong to the Linode referenced by `linode_id`. If not given, the last booted Config will be chosen.
* linode_id
* persist_across_boots `boolean`: Defaults to true, if false is provided, the Volume will not be attached to the Linode Config. In this case more than 8 Volumes may be attached to a Linode if a Linode has 16GB of RAM or more. The number of volumes that can be attached is equal to the number of GB of RAM that the Linode has, up to a maximum of 64. `config_id` should not be passed if this is set to false and linode_id must be passed. The Linode must be running.
* volumeId **required** `integer`: ID of the Volume to attach.
#### Output
* output [Volume](#volume)
### cloneVolume
Creates a Volume on your Account. In order for this request to complete successfully, your User must have the `add_volumes` grant. The new Volume will have the same size and data as the source Volume. Creating a new Volume will incur a charge on your Account.
```js
linode.cloneVolume({
"body": {
"label": ""
},
"volumeId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* label **required** [Volume/properties/label](#volume/properties/label)
* volumeId **required** `integer`: ID of the Volume to clone.
#### Output
* output `object`
### detachVolume
Detaches a Volume on your Account from a Linode on your Account. In order for this request to complete successfully, your User must have `read_write` access to the Volume and `read_write` access to the Linode.
```js
linode.detachVolume({
"volumeId": 0
}, context)
```
#### Input
* input `object`
* volumeId **required** `integer`: ID of the Volume to detach.
#### Output
* output `object`
### resizeVolume
Resize an existing Volume on your Account. In order for this request to complete successfully, your User must have the `read_write` permissions to the Volume.
* Volumes can only be resized up.
```js
linode.resizeVolume({
"body": {
"size": 0
},
"volumeId": 0
}, context)
```
#### Input
* input `object`
* body **required** `object`
* size **required** [Volume/properties/size](#volume/properties/size)
* volumeId **required** `integer`: ID of the Volume to resize.
#### Output
* output `object`
## Definitions
### Account
* Account `object`: Account object
* active_promotions `array`
* items `object`: A list of active promotions on your account. Promotions generally
* credit_monthly_cap `string`: The amount available to spend per month.
* credit_remaining `string`: The total amount of credit left for this promotion.
* description `string`: A detailed description of this promotion.
* expire_dt `string`: When this promotion's credits expire.
* image_url `string`: The location of an image for this promotion.
* summary `string`: Short details of this promotion.
* this_month_credit_remaining `string`: The amount of credit left for this month for this promotion.
* active_since `string`: The datetime of when the account was activated.
* address_1 `string`: First line of this Account's billing address.
* address_2 `string`: Second line of this Account's billing address.
* balance `number`: This Account's balance, in US dollars.
* balance_uninvoiced `number`: This Account's current estimated invoice in US dollars. This is not your final invoice balance. Bandwidth charges are not included in the estimate.
* capabilities `array`: A list of capabilities your account supports.
* items `string`
* city `string`: The city for this Account's billing address.
* company `string`: The company name associated with this Account.
* country `string`: The two-letter country code of this Account's billing address.
* credit_card `object`: Credit Card information associated with this Account.
* expiry `string`: The expiration month and year of the credit card.
* last_four `string`: The last four digits of the credit card associated with this Account.
* email `string`: The email address of the person associated with this Account.
* first_name `string`: The first name of the person associated with this Account.
* last_name `string`: The last name of the person associated with this Account.
* phone `string`: The phone number associated with this Account.
* state `string`: If billing address is in the United States, this is the State portion of the Account's billing address. If the address is outside the US, this is the Province associated with the Account's billing address.
* tax_id `string`: The tax identification number associated with this Account, for tax calculations in some countries. If you do not live in a country that collects tax, this should be `null`.
* zip `string`: The zip code of this Account's billing address.
### AccountSettings
* AccountSettings `object`: Account Settings object
* backups_enabled `boolean`: Account-wide backups default. If `true`, all Linodes created will automatically be enrolled in the Backups service. If `false`, Linodes will not be enrolled by default, but may still be enrolled on creation or later.
* longview_subscription `string`: The Longview Pro tier you are currently subscribed to. The value must a [Longview Subscription](/api/v4/longview-subscriptions) ID or `null`.
* managed `boolean`: Our 24/7 incident response service. This robust, multi-homed monitoring system distributes monitoring checks to ensure that your servers remain online and available at all times. Linode Managed can monitor any service or software stack reachable over TCP or HTTP. Once you add a service to Linode Managed, we'll monitor it for connectivity, response, and total request time.
* network_helper `boolean`: Enables network helper across all users by default for new Linodes and Linode Configs.
### AuthorizedApp
* AuthorizedApp `object`: An application you have authorized access to your Account through OAuth.
* created `string`: When this app was authorized.
* expiry `string`: When this app's access token expires. Please note that apps may still have active refresh tokens after this time passes.
* id `integer`: This authorization's ID, used for revoking access.
* label `string`: The name of the application you've authorized.
* scopes `string`: The OAuth scopes this app was authorized with. This defines what parts of your Account the app is allowed to access.
* thumbnail_url `string`: The URL at which this app's thumbnail may be accessed.
* website `string`: The website where you can get more information about this app.
### Backup
* Backup `object`: An object representing a Backup or snapshot for a Linode with Backup service enabled.
* configs `array`: A list of the labels of the Configuration profiles that are part of the Backup.
* items `string`
* created `string`: The date the Backup was taken.
* disks `array`: A list of the disks that are part of the Backup.
* items `object`
* filesystem [Disk/properties/filesystem](#disk/properties/filesystem)
* label `string`
* size `integer`
* finished `string`: The date the Backup completed.
* id `integer`: The unique ID of this Backup.
* label `string`: A label for Backups that are of type `snapshot`.
* status `string` (values: paused, pending, running, needsPostProcessing, successful, failed, userAborted): The current state of a specific Backup.
* type `string` (values: auto, snapshot): This indicates whether the Backup is an automatic Backup or manual snapshot taken by the User at a specific point in time.
* updated `string`: The date the Backup was most recently updated.
### CreditCard
* CreditCard `object`: An object representing the credit card information you have on file with Linode to make Payments against your Account.
* card_number **required** `string`: Your credit card number. No spaces or dashes allowed.
* expiry_month **required** `integer`: A value from 1-12 representing the expiration month of your credit card.
* expiry_year **required** `integer`: A four-digit integer representing the expiration year of your credit card.
### Device
* Device `object`: Device can be either a Disk or Volume identified by `disk_id` or `volume_id`. Only one type per slot allowed. Can be null.
* disk_id `integer`: The Disk ID, or `null` if a Volume is assigned to this slot.
* volume_id `integer`: The Volume ID, or `null` if a Disk is assigned to this slot.
### Devices
* Devices `object`: A dictionary of device disks to use as a device map in a Linode's configuration profile.
* sda [Device](#device)
* sdb [Device](#device)
* sdc [Device](#device)
* sdd [Device](#device)
* sde [Device](#device)
* sdf [Device](#device)
* sdg [Device](#device)
* sdh [Device](#device)
### Disk
* Disk `object`
* created `string`: When this Linode was created.
* filesystem `string` (values: raw, swap, ext3, ext4, initrd): The Disk filesystem can be one of:
* id `integer`: This Disk's ID which must be provided for all operations impacting this Disk.
* label `string`: The Disk's label is for display purposes only.
* size `integer`: The size of the Disk in MB.
* status `string` (values: ready, not ready, deleting): A brief description of this Disk's current state. This field may change without direct action from you, as a result of operations performed to the Disk or the Linode containing the Disk.
* updated `string`: When this Linode was last updated.
### DiskRequest
* DiskRequest `object`: Disk object request.
* authorized_keys `array`: A list of public SSH keys that will be automatically appended to the root user's `~/.ssh/authorized_keys` file.
* items `string`
* authorized_users `array`: A list of usernames that will have their SSH keys, if any, automatically appended to the root user's `~/.ssh/authorized_keys` file.
* items `string`
* filesystem [Disk/properties/filesystem](#disk/properties/filesystem)
* image `string`: An Image ID to deploy the Disk from. Official Linode Images start with `linode/ `, while your Images start with `private/`.
* label **required** [Disk/properties/label](#disk/properties/label)
* read_only `boolean`: If true, this Disk is read-only.
* root_pass `string`: This will set the root user's password on the newly-created Linode.
* size **required** `integer`
* stackscript_data `object`: This field is required only if the StackScript being deployed requires input
* stackscript_id `integer`: A StackScript ID that will cause the referenced StackScript to be run during
### Domain
* Domain `object`: A domain zonefile in our DNS system. You must own the domain name and tell your registrar to use Linode's nameservers in order for a domain in our system to be treated as authoritative.
* tags `array`: An array of tags applied to this object. Tags are for organizational purposes only.
* items `string`
* axfr_ips `array`: The list of IPs that may perform a zone transfer for this Domain. This is potentially dangerous, and should be set to an empty list unless you intend to use it.
* items `string`
* description `string`: A description for this Domain. This is for display purposes only.
* domain **required** `string`: The domain this Domain represents. Domain labels cannot be longer than 63 characters and must conform to [RFC1035](https://tools.ietf.org/html/rfc1035). Domains must be unique on Linode's platform, including across different Linode accounts; there cannot be two Domains representing the same domain.
* expire_sec `integer`: The amount of time in seconds that may pass before this Domain is no longer authoritative. Valid values are 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200 - any other value will be rounded to the nearest valid value.
* group `string`: The group this Domain belongs to. This is for display purposes only.
* id **required** `integer`: This Domain's unique ID
* master_ips `array`: The IP addresses representing the master DNS for this Domain.
* items `string`
* refresh_sec `integer`: The amount of time in seconds before this Domain should be refreshed. Valid values are 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200 - any other value will be rounded to the nearest valid value.
* retry_sec `integer`: The interval, in seconds, at which a failed refresh should be retried. Valid values are 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200 - any other value will be rounded to the nearest valid value.
* soa_email `string`: Start of Authority email address. This is required for master Domains.
* status `string` (values: disabled, active, edit_mode, has_errors): Used to control whether this Domain is currently being rendered.
* ttl_sec `integer`: "Time to Live" - the amount of time in seconds that this Domain's records may be cached by resolvers or other domain servers.
* type **required** `string` (values: master, slave): If this Domain represents the authoritative source of information for the domain it describes, or if it is a read-only copy of a master (also called a slave).
### DomainRecord
* DomainRecord `object`: A single record on a Domain.
* id `integer`: This Record's unique ID.
* name `string`: The name of this Record. This field's actual usage depends on the type of record this represents. For A and AAAA records, this is the subdomain being associated with an IP address.
* port `integer`: The port this Record points to.
* priority `integer`: The priority of the target host. Lower values are preferred.
* protocol `string`: The protocol this Record's service communicates with. Only valid for SRV records.
* service `string`: The service this Record identified. Only valid for SRV records.
* tag `string`: The tag portion of a CAA record. It is invalid to set this on other record types.
* target `string`: The target for this Record. This field's actual usage depends on the type of record this represents. For A and AAAA records, this is the address the named Domain should resolve to.
* ttl_sec `integer`: "Time to Live" - the amount of time in seconds that this Domain's records may be cached by resolvers or other domain servers. Valid values are 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200 - any other value will be rounded to the nearest valid value.
* type `string` (values: A, AAAA, NS, MX, CNAME, TXT, SRV, PTR, CAA): The type of Record this is in the DNS system. For example, A records associate a domain name with an IPv4 address, and AAAA records associate a domain name with an IPv6 address.
* weight `integer`: The relative weight of this Record. Higher values are preferred.
### ErrorObject
* ErrorObject `object`: An object for describing a single error that occurred during the processing of a request.
* field `string`: The field in the request that caused this error. This may be a path, separated by periods in the case of nested fields. In some cases this may come back as "null" if the error is not specific to any single element of the request.
* reason `string`: What happened to cause this error. In most cases, this can be fixed immediately by changing the data you sent in the request, but in some cases you will be instructed to [open a Support Ticket](/api/v4/support-tickets/#post) or perform some other action before you can complete the request successfully.
### Event
* Event `object`: A collection of Event objects. An Event is an action taken against an entity related to your Account. For example, booting a Linode would create an Event.
* action `string` (values: account_update, account_settings_update, backups_enable, backups_cancel, backups_restore, community_question_reply, community_like, credit_card_updated, disk_create, disk_delete, disk_update, disk_duplicate, disk_imagize, disk_resize, dns_record_create, dns_record_delete, dns_record_update, dns_zone_create, dns_zone_delete, dnz_zone_import, dns_zone_update, host_reboot, image_delete, image_update, ipaddress_update, lassie_reboot, lish_boot, linode_addip, linode_boot, linode_clone, linode_create, linode_delete, linode_update, linode_deleteip, linode_migrate, linode_migrate_datacenter, linode_migrate_datacenter_create, linode_mutate, linode_mutate_create, linode_reboot, linode_rebuild, linode_resize, linode_resize_create, linode_shutdown, linode_snapshot, linode_config_create, linode_config_delete, linode_config_update, longviewclient_create, longviewclient_delete, longviewclient_update, managed_disabled, managed_enabled, managed_service_create, managed_service_delete, nodebalancer_create, nodebalancer_delete, nodebalancer_update, nodebalancer_config_create, nodebalancer_config_delete, nodebalancer_config_update, nodebalancer_node_create, nodebalancer_node_delete, nodebalancer_node_update, oauth_client_create, oauth_client_delete, oauth_client_secret_reset, oauth_client_update, password_reset, payment_submitted, profile_update, stackscript_create, stackscript_delete, stackscript_update, stackscript_publicize, stackscript_revise, tag_create, tag_delete, tfa_disabled, tfa_enabled, ticket_attachment_upload, ticket_create, ticket_update, token_create, token_delete, token_update, user_create, user_update, user_delete, user_ssh_key_add, user_ssh_key_delete, user_ssh_key_update, vlan_attach, vlan_detach, volume_attach, volume_clone, volume_create, volume_delete, volume_update, volume_detach, volume_resize): The action that caused this Event. New actions may be added in the future.
* created `string`: When this Event was created.
* entity `object`: Detailed information about the Event's entity, including ID, type, label, and URL used to access it.
* id `integer`: The unique ID for an Event's entity.
* label `string`: The current label of this object. The label may reflect changes that occur with this Event.
* type `string` (values: account, backups, community, disks, domain, image, ipaddress, linode, longview, managed_service, nodebalancer, oauth_client, profile, stackscript, tag, ticket, token, user, user_ssh_key, volume): The type of entity that is being referenced by the Event.
* url `string`: The URL where you can access the object this Event is for. If a relative URL, it is relative to the domain you retrieved the Event from.
* id `integer`: The unique ID of this Event.
* percent_complete `integer`: A percentage estimating the amount of time remaining for an Event.
* rate `string`: The rate of completion of the Event. Only some Events will return rate; for example, migration and resize Events.
* read `boolean`: If this Event has been read.
* secondary_entity `object`: Detailed information about the Event's secondary entity, which provides additional information
* id `string`: The ID of the object that is the secondary entity.
* label `string`: The label of this object.
* type `string`: The type of entity that is being referenced by the Event.
* url `string`: The URL where you can access the object this Event is for. If a relative URL, it is relative to the domain you retrieved the Event from.
* seen `boolean`: If this Event has been seen.
* status `string` (values: failed, finished, notification, scheduled, started): The current status of this Event.
* time_remaining `string`: The estimated time remaining until the completion of this Event. This value is only returned for some in-progress migration events. For all other in-progress events, the `percent_complete` attribute will indicate about how much more work is to be done.
* username `string`: The username of the User who caused the Event.
### Grant
* Grant `object`: Represents the level of access a restricted User has to a specific resource on the Account.
* id `integer`: The ID of the entity this grant applies to.
* label `string`: The current label of the entity this grant applies to, for display purposes.
* permissions `string` (values: , read_only, read_write): The level of access this User has to this entity. If null, this User has no access.
### GrantsResponse
* GrantsResponse `object`: A structure representing all grants a restricted User has on the Account. Not available for unrestricted users, as they have access to everything without grants. If retrieved from the `/profile/grants` endpoint, entities to which a User has no access will be omitted.
* domain `array`: The grants this User has pertaining to Domains on this Account. There will be one entry per Domain on the Account.
* items [Grant](#grant)
* global `object`: A structure containing the Account-level grants a User has.
* account_access `string` (values: , read_only, read_write): The level of access this User has to Account-level actions, like billing information. A restricted User will never be able to manage users.
* add_domains `boolean`: If true, this User may add Domains.
* add_images `boolean`: If true, this User may add Images.
* add_linodes `boolean`: If true, this User may create Linodes.
* add_longview `boolean`: If true, this User may create Longview clients.
* add_nodebalancers `boolean`: If true, this User may add NodeBalancers.
* add_stackscripts `boolean`: If true, this User may add StackScripts.
* add_volumes `boolean`: If true, this User may add Volumes.
* cancel_account `boolean`: If true, this User may cancel the entire Account.
* longview_subscription `boolean`: If true, this User may manage the Account's Longview subscription.
* image `array`: The grants this User has pertaining to Images on this Account. There will be one entry per Image on the Account.
* items [Grant](#grant)
* linode `array`: The grants this User has pertaining to Linodes on this Account. There will be one entry per Linode on the Account.
* items [Grant](#grant)
* longview `array`: The grants this User has pertaining to Longview Clients on this Account. There will be one entry per Longview Client on the Account.
* items [Grant](#grant)
* nodebalancer `array`: The grants this User has pertaining to NodeBalancers on this Account. There will be one entry per NodeBalancer on the Account.
* items [Grant](#grant)
* stackscript `array`: The grants this User has pertaining to StackScripts on this Account. There will be one entry per StackScript on the Account.
* items [Grant](#grant)
* volume `array`: The grants this User has pertaining to Volumes on this Account. There will be one entry per Volume on the Account.
* items [Grant](#grant)
### IPAddress
* IPAddress `object`: An IP address that exists in Linode's system, either IPv4 or IPv6.
* address `string`: The IP address.
* gateway `string`: The default gateway for this address.
* linode_id `integer`: The ID of the Linode this address currently belongs to. For IPv4 addresses, this is by default the Linode that this address was assigned to on creation, and these addresses my be moved using the [/networking/ipv4/assign](/api/v4/networking-ipv-4-assign/#post) endpoint. For SLAAC and link-local addresses, this value may not be changed.
* prefix `integer`: The number of bits set in the subnet mask.
* public `boolean`: Whether this is a public or private IP address.
* rdns `string`: The reverse DNS assigned to this address. For public IPv4 addresses, this will be set to a default value provided by Linode if not explicitly set.
* region `string`: The Region this IP address resides in.
* subnet_mask `string`: The mask that separates host bits from network bits for this address.
* type `string` (values: ipv4, ipv6, ipv6/pool, ipv6/range): The type of address this is.
### IPAddressPrivate
* IPAddressPrivate `object`: A private IPv4 address that exists in Linode's system.
* address `string`: The private IPv4 address.
* gateway `string`: The default gateway for this address.
* linode_id `integer`: The ID of the Linode this address currently belongs to.
* prefix `integer`: The number of bits set in the subnet mask.
* public `boolean`: Whether this is a public or private IP address.
* rdns `string`: The reverse DNS assigned to this address.
* region `string`: The Region this address resides in.
* subnet_mask `string`: The mask that separates host bits from network bits for this address.
* type `string`: The type of address this is.
### IPAddressV6LinkLocal
* IPAddressV6LinkLocal `object`: A link-local IPv6 address that exists in Linode's system,.
* address `string`: The IPv6 link-local address.
* gateway `string`: The default gateway for this address.
* linode_id `integer`: The ID of the Linode this address currently belongs to.
* prefix `integer`: The network prefix.
* public `boolean`: Whether this is a public or private IP address.
* rdns `string`: The reverse DNS assigned to this address.
* region `string`: The Region this address resides in.
* subnet_mask `string`: The subnet mask.
* type `string`: The type of address this is.
### IPAddressV6Slaac
* IPAddressV6Slaac `object`: A SLAAC IPv6 address that exists in Linode's system.
* address `string`: The address.
* gateway `string`: The default gateway for this address.
* linode_id `integer`: The ID of the Linode this address currently belongs to.
* prefix `integer`: The network prefix.
* public `boolean`: Whether this is a public or private IP address.
* rdns `string`: The reverse DNS assigned to this address.
* region `string`: The Region this address resides in.
* subnet_mask `string`: The subnet mask.
* type `string`: The type of address this is.
### IPv6Pool
* IPv6Pool `object`: An object representing an IPv6 pool.
* prefix `integer`: The prefix length of the address, denoting which addresses can be assigned from this pool.
* range `string`: The IPv6 pool
* region `string`: A pool of IPv6 addresses that are routed to all of your Linodes in a single Region. Any Linode you own may bring up any address in this pool at any time, with no external configuration required.
### IPv6Range
* IPv6Range `object`: An object representing an IPv6 range.
* range `string`: The IPv6 range.
* region `string`: A range of IPv6 addresses routed to a single Linode in the given Region. Your Linode is responsible for routing individual addresses in the range, or handling traffic for all of the addresses in the range.
### ImagePrivate
* ImagePrivate `object`: Private Image object
* created `string`: When this Image was created.
* created_by `string`: The name of the User who created this Image.
* deprecated `boolean`: Whether or not this Image is deprecated. Will only be True for deprecated public Images.
* description `string`: A detailed description of this Image.
* expiry `string`: Only Images created automatically (from a deleted Linode; type=automatic) will expire.
* id `string`: The unique ID of this Image.
* is_public `boolean`: True if the Image is public.
* label `string`: A short description of the Image. Labels cannot contain special characters.
* size `integer`: The minimum size this Image needs to deploy. Size is in MB.
* type `string` (values: manual, automatic): How the Image was created. "Manual" Images can be created at any time. "Automatic" images are created automatically from a deleted Linode.
* vendor `string`: The upstream distribution vendor. `None` for private Images.
### ImagePublic
* ImagePublic `object`: Public Image object
* created `string`: When this Image was created.
* created_by `string`: The name of the User who created this Image, or "linode" for official Images.
* deprecated `boolean`: Whether or not this Image is deprecated. Will only be true for deprecated public Images.
* description `string`: A detailed description of this Image.
* expiry `string`: Only Images created automatically (from a deleted Linode; type=automatic) will expire.
* id `string`: The unique ID of this Image.
* is_public `boolean`: True if the Image is public.
* label `string`: A short description of the Image.
* size `integer`: The minimum size this Image needs to deploy. Size is in MB.
* type `string` (values: manual, automatic): How the Image was created. Manual Images can be created at any time. "Automatic" Images are created automatically from a deleted Linode.
* vendor `string`: The upstream distribution vendor. `None` for private Images.
### Invoice
* Invoice `object`: Account Invoice object
* date `string`: When this Invoice was generated.
* id `integer`: The Invoice's unique ID.
* label `string`: The Invoice's display label.
* subtotal `integer`: The amount of the Invoice before taxes in US Dollars.
* tax `integer`: The amount of tax levied on the Invoice in US Dollars.
* total `integer`: The amount of the Invoice after taxes in US Dollars.
### InvoiceItem
* InvoiceItem `object`: An InvoiceItem object.
* amount `integer`: The price, in US dollars, of the Invoice Item. Equal to the unit price multiplied by quantity.
* from `string`: The date the Invoice Item started, based on month.
* label `string`: The Invoice Item's display label.
* quantity `integer`: The quantity of this Item for the specified Invoice.
* tax `integer`: The amount of tax levied on this Item in US Dollars.
* to `string`: The date the Invoice Item ended, based on month.
* total `integer`: The price of this Item after taxes in US Dollars.
* type `string` (values: hourly, prepay, misc): The type of service, ether `prepay` or `misc`.
* unitprice `integer`: The monthly service fee in US Dollars for this Item.
### Kernel
* Kernel `object`: Linux kernel object
* architecture `string` (values: x86_64, i386): The architecture of this Kernel.
* id `string`: The unique ID of this Kernel.
* kvm `boolean`: If this Kernel is suitable for KVM Linodes.
* label `string`: The friendly name of this Kernel.
* pvops `boolean`: If this Kernel is suitable for paravirtualized operations.
* version `string`: Linux Kernel version.
* xen `boolean`: If this Kernel is suitable for Xen Linodes.
### Linode
* Linode `object`
* tags `array`: An array of tags applied to this object. Tags are for organizational purposes only.
* items `string`
* alerts `object`
* cpu `integer`: The percentage of CPU usage required to trigger an alert.
* io `integer`: The amount of disk IO operation per second required to trigger an alert. If the average disk IO over two hours exceeds this value, we'll send you an alert. If set to `0` (zero), this alert is disabled.
* network_in `integer`: The amount of incoming traffic, in Mbit/s, required to trigger an alert. If the average incoming traffic over two hours exceeds this value, we'll send you an alert. If this is set to `0` (zero), the alert is disabled.
* network_out `integer`: The amount of outbound traffic, in Mbit/s, required to trigger an alert. If the average outbound traffic over two hours exceeds this value, we'll send you an alert. If this is set to `0` (zero), the alert is disabled.
* transfer_quota `integer`: The percentage of network transfer that may be used before an alert is triggered. When this value is exceeded, we'll alert you. If this is set to `0` (zero), the alert is disabled.
* backups `object`: Information about this Linode's backups status. For information about available backups, see [/linode/instances/{linodeId}/backups](/api/v4/linode-instances-linode-id-backups).
* enabled `boolean`: If this Linode has the Backup service enabled. To enable backups, see [POST /linode/instances/{linodeId}/backups/enable](/api/v4/linode-instances-linode-id-backups-enable/#post).
* schedule `object`
* day `string` (values: Scheduling, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday): The day of the week that your Linode's weekly Backup is taken.
* window `string` (values: Scheduling, W0, W2, W4, W6, W8, W10, W12, W14, W16, W18, W20, W22): The window in which your backups will be taken, in UTC. A
* created `string`: When this Linode was created.
* group `string`: A deprecated property denoting a group label for this Linode.
* hypervisor `string` (values: kvm): The virtualization software powering this Linode.
* id `integer`: This Linode's ID which must be provided for all operations impacting this Linode.
* image
* ipv4 `array`: This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address
* items `string`
* ipv6 `string`: This Linode's IPv6 SLAAC addresses. This address is specific to a Linode, and may not be shared. If the Linode has not been assigned an IPv6 address, the return value will be `null`.
* specs `object`: Information about the resources available to this Linode.
* disk `integer`: The amount of storage space, in MB, this Linode has access to. A typical Linode will divide this space between a primary disk with an `image` deployed to it, and a swap disk, usually 512 MB. This is the default configuration created when deploying a Linode with an `image` through [POST /linode/instances](/api/v4/linode-instances/#post). While this configuration is suitable for 99% of use cases, if you need finer control over your Linode's disks, see the [/linode/instances/{linodeId}/disks](/api/v4/linode-instances-linode-id-disks) endpoints.
* memory `integer`: The amount of RAM, in MB, this Linode has access to. Typically a Linode will choose to boot with all of its available RAM, but this can be configured in a Config profile, see the [/linode/instances/{linodeId}/configs](/api/v4/linode-instances-linode-id-configs) endpoints and the LinodeConfig object for more information.
* transfer `integer`: The amount of network transfer this Linode is allotted each month.
* vcpus `integer`: The number of vcpus this Linode has access to. Typically a Linode will choose to boot with all of its available vcpus, but this can be configured in a Config Profile, see the [/linode/instances/{linodeId}/configs](/api/v4/linode-instances-linode-id-configs) endpoints and the LinodeConfig object for more information.
* status `string` (values: running, offline, booting, rebooting, shutting_down, provisioning, deleting, migrating, rebuilding, cloning, restoring): A brief description of this Linode's current state. This field may change without direct action from you. For instance, the status will change to "running"
* updated `string`: When this Linode was last updated.
* watchdog_enabled `boolean`: The watchdog, named Lassie, is a Shutdown Watchdog that monitors your Linode and will reboot it if it powers off unexpectedly. It works by issuing a boot job when your Linode powers off without a shutdown job being responsible.
* group `string`: A deprecated property denoting a group label for this Linode.
* label `string`: The Linode's label is for display purposes only. If no label is provided for a Linode, a default will be assigned.
* region [Region/properties/id](#region/properties/id)
* type [LinodeType/properties/id](#linodetype/properties/id)
### LinodeBase
* LinodeBase `object`: Common properties for Linode Request and Response objects.
* group `string`: A deprecated property denoting a group label for this Linode.
* label `string`: The Linode's label is for display purposes only. If no label is provided for a Linode, a default will be assigned.
* region [Region/properties/id](#region/properties/id)
* type [LinodeType/properties/id](#linodetype/properties/id)
### LinodeConfig
* LinodeConfig `object`
* comments `string`: Optional field for arbitrary User comments on this Config.
* devices **required** [Devices](#devices)
* helpers `object`: Helpers enabled when booting to this Linode Config.
* devtmpfs_automount `boolean`: Populates the /dev directory early during boot without udev. Defaults to false.
* distro `boolean`: Helps maintain correct inittab/upstart console device.
* modules_dep `boolean`: Creates a modules dependency file for the Kernel you run.
* network `boolean`: Automatically configures static networking.
* updatedb_disabled `boolean`: Disables updatedb cron job to avoid disk thrashing.
* id `integer`: The ID of this Config.
* kernel `string`: A Kernel ID to boot a Linode with. Defaults to "linode/latest-64bit".
* label **required** `string`: The Config's label is for display purposes only.
* memory_limit `integer`: Defaults to the total RAM of the Linode.
* root_device `string`: The root device to boot.
* run_level `string` (values: default, single, binbash): Defines the state of your Linode after booting. Defaults to `default`.
* virt_mode `string` (values: paravirt, fullvirt): Controls the virtualization mode. Defaults to `paravirt`.
### LinodeRequest
* LinodeRequest `object`: Common properties for creating and rebuilding Linodes.
* authorized_keys [DiskRequest/properties/authorized_keys](#diskrequest/properties/authorized_keys)
* authorized_users [DiskRequest/properties/authorized_users](#diskrequest/properties/authorized_users)
* booted `boolean`: This field defaults to `true` if the Linode is created with an Image or from a Backup.
* image [DiskRequest/properties/image](#diskrequest/properties/image)
* root_pass [DiskRequest/properties/root_pass](#diskrequest/properties/root_pass)
* stackscript_data [DiskRequest/properties/stackscript_data](#diskrequest/properties/stackscript_data)
* stackscript_id [DiskRequest/properties/stackscript_id](#diskrequest/properties/stackscript_id)
### LinodeStats
* LinodeStats `object`: CPU, IO, IPv4, and IPv6 statistics. Graph data, if available, is in "[timestamp, reading]" array format. Timestamp is a UNIX timestamp in EST.
* cpu `array`: Percentage of CPU used.
* items `array`
* items `number`
* io `object`: Input/Output statistics.
* io `array`: Block/s written.
* items `array`
* items `number`
* swap `array`: Block/s written.
* items `array`
* items `number`
* netv4 `object`: IPv4 statistics.
* in `array`: Input stats for IPv4, measured in bits/s (bits/second).
* items `array`
* items `number`
* out `array`: Output stats for IPv4, measured in bits/s (bits/second).
* items `array`
* items `number`
* private_in `array`: Private IPv4 input statistics, measured in bits/s (bits/second).
* items `array`
* items `number`
* private_out `array`: Private IPv4 output statistics, measured in bits/s (bits/second).
* items `array`
* items `number`
* netv6 `object`: IPv6 statistics.
* in `array`: Input stats for IPv6, measured in bits/s (bits/second).
* items `array`
* items `number`
* out `array`: Output stats for IPv6, measured in bits/s (bits/second).
* items `array`
* items `number`
* private_in `array`: Private IPv6 input statistics, measured in bits/s (bits/second).
* items `array`
* items `number`
* private_out `array`: Private IPv6 output statistics, measured in bits/s (bits/second).
* items `array`
* items `number`
* title `string`: The title for this data set.
### LinodeType
* LinodeType `object`: Returns collection of Linode types, including pricing and specifications for each type. These are used when [creating](/api/v4/linode-instances/#post) or [resizing](/api/v4/linode-instances-linode-id-resize/#post) Linodes.
* addons `object`: A list of optional add-on services for Linodes and their associated costs.
* backups `object`: Information about the optional Backup service offered for Linodes.
* price `object`: Cost of enabling Backups for this Linode Type.
* hourly `integer`: The cost (in US dollars) per hour to add Backups service.
* monthly `integer`: The cost (in US dollars) per month to add Backups service.
* class `string` (values: nanode, standard, dedicated, gpu, highmem): The class of the Linode Type. We currently offer five classes of Linodes:
* disk `integer`: The Disk size, in MB, of the Linode Type.
* gpus `integer`: The number of GPUs this Linode Type offers.
* id `string`: The ID representing the Linode Type.
* label `string`: The Linode Type's label is for display purposes only.
* memory `integer`: Amount of RAM included in this Linode Type.
* network_out `integer`: The Mbits outbound bandwidth allocation.
* price `object`: Cost in US dollars, broken down into hourly and monthly charges.
* hourly `integer`: Cost (in US dollars) per hour.
* monthly `integer`: Cost (in US dollars) per month.
* successor `string`: The Linode Type that a [mutate](/api/v4/linode-instances-linode-id-mutate/#post) will upgrade to for a Linode of this type. If "null", a Linode of this type may not mutate.
* transfer `integer`: The monthly outbound transfer amount, in MB.
* vcpus `integer`: The number of VCPU cores this Linode Type offers.
### LongviewClient
* LongviewClient `object`: A LongviewClient is a single monitor set up to track statistics about one of your servers.
* api_key `string`: The API key for this Client, used when configuring the Longview Client application on your Linode.
* apps `object`: The apps this Client is monitoring on your Linode. This is configured when you install the Longview Client application, and is present here for information purposes only.
* apache `boolean`: If True, the Apache Longview Client module is monitoring Apache on your server.
* mysql `boolean`: If True, the MySQL Longview Client modules is monitoring MySQL on your server.
* nginx `boolean`: If True, the Nginx Longview Client module is monitoring Nginx on your server.
* created `string`: When this Longview Client was created.
* id `integer`: This Client's unique ID.
* install_code `string`: The install code for this Client, used when configuring the Longview Client application on your Linode.
* label `string`: This Client's unique label. This is for display purposes only.
* updated `string`: When this Longview Client was last updated.
### LongviewSubscription
* LongviewSubscription `object`: A Longview Subscriptions represents a tier of Longview service you can subscribe to.
* clients_included `integer`: The number of Longview Clients that may be created with this Subscription tier.
* id `string`: The unique ID of this Subscription tier.
* label `string`: A display name for this Subscription tier.
* price `object`: Pricing information about this Subscription tier.
* hourly `number`: The hourly price, in US dollars, for this Subscription tier.
* monthly `number`: The maximum monthly price in US Dollars for this Subscription tier. You will never be charged more than this amount per month for this subscription.
### ManagedContact
* ManagedContact `object`: Information about someone Linode's special forces may contact in case an issue is detected with a manager service.
* email `string`: The address to email this Contact to alert them of issues.
* group `string`: A grouping for this Contact. This is for display purposes only.
* id `integer`: This Contact's unique ID.
* name `string`: The name of this Contact.
* phone `object`: Information about how to reach this Contact by phone.
* primary `string`: This Contact's primary phone number.
* secondary `string`: This Contact's secondary phone number.
* updated `string`: When this Contact was last updated.
### ManagedCredential
* ManagedCredential `object`: A securely-stored Credential that allows Linode's special forces to access a Managed server to respond to Issues.
* id `integer`: This Credential's unique ID.
* label `string`: The unique label for this Credential. This is for display purposes only.
* last_decrypted `string`: The date this Credential was last decrypted by a member of Linode special forces.
### ManagedIssue
* ManagedIssue `object`: An Issue that was detected with a service Linode is managing.
* created `string`: When this Issue was created. Issues are created in response to issues detected with Managed Services, so this is also when the Issue was detected.
* entity `object`: The ticket this Managed Issue opened.
* id `integer`: This ticket's ID
* label `string`: The summary for this Ticket.
* type `string` (values: ticket): The type of entity this is. In this case, it is always a Ticket.
* url `string`: The relative URL where you can access this Ticket.
* id `integer`: This Issue's unique ID.
* services `array`: An array of Managed Service IDs that were affected by this Issue.
* items `integer`
### ManagedLinodeSettings
* ManagedLinodeSettings `object`: Settings for a specific Linode related to Managed Services. There is one ManagedLinodeSettings object for each Linode on your Account.
* group `string`: The group of the Linode these Settings are for. This is for display purposes only.
* id `integer`: The ID of the Linode these Settings are for.
* label `string`: The label of the Linode these Settings are for.
* ssh `object`: The SSH settings for this Linode.
* access `boolean`: If true, Linode special forces may access this Linode over ssh to respond to Issues.
* ip `string`: The IP Linode special forces should use to access this Linode when responding to an Issue.
* port `integer`: The port Linode special forces should use to access this Linode over ssh to respond to an Issue.
* user `string`: The user Linode's special forces should use when accessing this Linode to respond to an issue.
### ManagedService
* ManagedService `object`: A service that Linode is monitoring as part of your Managed services. If issues are detected with this service, a ManagedIssue will be opened and, optionally, Linode special forces will attempt to resolve the Issue.
* address `string`: The URL at which this Service is monitored.
* body `string`: What to expect to find in the response body for the Service to be considered up.
* consultation_group `string`: The group of ManagedContacts who should be notified or consulted with when an Issue is detected.
* created `string`: When this Managed Service was created.
* credentials `array`: An array of ManagedCredential IDs that should be used when attempting to resolve issues with this Service.
* items `integer`
* id `integer`: This Service's unique ID.
* label `string`: The label for this Service. This is for display purposes only.
* notes `string`: Any information relevant to the Service that Linode special forces should know when attempting to resolve Issues.
* region `string`: The Region in which this Service is located. This is required if address is a private IP, and may not be set otherwise.
* service_type `string` (values: url, tcp): How this Service is monitored.
* status `string` (values: disabled, pending, ok, problem): The current status of this Service.
* timeout `integer`: How long to wait, in seconds, for a response before considering the Service to be down.
* updated `string`: When this Managed Service was last updated.
### NodeBalancer
* NodeBalancer `object`: Linode's load balancing solution. Can handle multiple ports, SSL termination, and any number of backends. NodeBalancer ports are configured with NodeBalancer Configs, and each config is given one or more NodeBalancer Node that accepts traffic. The traffic should be routed to the NodeBalancer's ip address, the NodeBalancer will handle routing individual requests to backends.
* tags `array`: An array of Tags applied to this object. Tags are for organizational purposes only.
* items `string`
* client_conn_throttle `integer`: Throttle connections per second. Set to 0 (zero) to disable throttling.
* created `string`: When this NodeBalancer was created.
* hostname `string`: This NodeBalancer's hostname, ending with _.nodebalancer.linode.com_
* id `integer`: This NodeBalancer's unique ID.
* ipv4 `string`: This NodeBalancer's public IPv4 address.
* ipv6 `string`: This NodeBalancer's public IPv6 address.
* label `string`: This NodeBalancer's label. These must be unique on your Account.
* region `string`: The Region where this NodeBalancer is located. NodeBalancers only support backends in the same Region.
* transfer `object`: Information about the amount of transfer this NodeBalancer has had so far this month.
* in `number`: The total outbound transfer, in MB, used for this NodeBalancer this month.
* out `number`: The total inbound transfer, in MB, used for this NodeBalancer this month.
* total `number`: The total transfer, in MB, used by this NodeBalancer this month.
* updated `string`: When this NodeBalancer was last updated.
### NodeBalancerConfig
* NodeBalancerConfig `object`: A NodeBalancer config represents the configuration of this NodeBalancer on a single port. For example, a NodeBalancer Config on port 80 would typically represent how this NodeBalancer response to HTTP requests.
* algorithm `string` (values: roundrobin, leastconn, source): What algorithm this NodeBalancer should use for routing traffic to backends.
* check `string` (values: none, connection, http, http_body): The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down.
* check_attempts `integer`: How many times to attempt a check before considering a backend to be down.
* check_body `string`: This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down.
* check_interval `integer`: How often, in seconds, to check that backends are up and serving requests.
* check_passive `boolean`: If true, any response from this backend with a `5xx` status code will be enough for it to be considered unhealthy and taken out of rotation.
* check_path `string`: The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
* check_timeout `integer`: How long, in seconds, to wait for a check attempt before considering it failed.
* cipher_suite `string` (values: recommended, legacy): What ciphers to use for SSL connections served by this NodeBalancer.
* id `integer`: This config's unique ID
* nodebalancer_id `integer`: The ID for the NodeBalancer this config belongs to.
* nodes_status `object`: A structure containing information about the health of the backends for this port. This information is updated periodically as checks are performed against backends.
* down `integer`: The number of backends considered to be "DOWN" and unhealthy. These are not in rotation, and not serving requests.
* up `integer`: The number of backends considered to be "UP" and healthy, and that are serving requests.
* port `integer`: The port this Config is for. These values must be unique across configs on a single NodeBalancer (you can't have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443.
* protocol `string` (values: http, https, tcp): The protocol this port is configured to serve.
* ssl_cert `string`: The PEM-formatted public SSL certificate (or the combined PEM-formatted SSL
* ssl_commonname `string`: The read-only common name automatically derived from the SSL certificate assigned to this NodeBalancerConfig. Please refer to this field to verify that the appropriate certificate is assigned to your NodeBalancerConfig.
* ssl_fingerprint `string`: The read-only fingerprint automatically derived from the SSL certificate assigned to this NodeBalancerConfig. Please refer to this field to verify that the appropriate certificate is assigned to your NodeBalancerConfig.
* ssl_key `string`: The PEM-formatted private key for the SSL certificate set in the `ssl_cert` field.
* stickiness `string` (values: none, table, http_cookie): Controls how session stickiness is handled on this port.
### NodeBalancerNode
* NodeBalancerNode `object`: A NodeBalancerNode represents a single backend serving requests for a single port of a NodeBalancer. Nodes are specific to NodeBalancer Configs, and serve traffic over their private IP. If the same Linode is serving traffic for more than one port on the same NodeBalancer, one NodeBalancer Node is required for each config (port) it should serve requests on. For example, if you have four backends, and each should response to both HTTP and HTTPS requests, you will need two NodeBalancerConfigs (port 80 and port 443) and four backends each - one for each of the Linodes serving requests for that port.
* address `string`: The private IP Address where this backend can be reached. This _must_ be a private IP address.
* config_id `integer`: The NodeBalancer Config ID that this Node belongs to.
* id `integer`: This node's unique ID.
* label `string`: The label for this node. This is for display purposes only.
* mode `string` (values: accept, reject, drain, backup): The mode this NodeBalancer should use when sending traffic to this backend.
* nodebalancer_id `integer`: The NodeBalancer ID that this Node belongs to.
* status `string` (values: unknown, UP, DOWN): The current status of this node, based on the configured checks of its NodeBalancer Config.
* weight `integer`: Used when picking a backend to serve a request and is not pinned to a single backend yet. Nodes with a higher weight will receive more traffic.
### NodeBalancerStats
* NodeBalancerStats `object`: Stats for this NodeBalancer.
* data `object`: The data returned about this NodeBalancers.
* connections `array`: An array of key/value pairs representing unix timestamp and reading for connections to this NodeBalancer.
* items `number`
* traffic `object`: Traffic statistics for this NodeBalancer.
* in `array`: An array of key/value pairs representing unix timestamp and reading for inbound traffic.
* items `number`
* out `array`: An array of key/value pairs representing unix timestamp and reading for outbound traffic.
* items `number`
* title `string`: The title for the statistics generated in this response.
### Notification
* Notification `object`: An important, often time-sensitive item related to your Account.
* body `string`: A full description of this Notification, in markdown format. Not all Notifications include bodies.
* entity `object`: Detailed information about the Notification.
* id `integer`: The unique ID of the Notification's entity, based on the entity type.
* label `string`: The current label for this Notification's entity.
* type `string`: The type of entity this is related to.
* url `string`: The URL where you can access the object this Notification is for. If a relative URL, it is relative to the domain you retrieved the Notification from.
* label `string`: A short description of this Notification.
* message `string`: A human-readable description of the Notification.
* severity `string` (values: minor, major, critical): The severity of this Notification. This field can be used to decide how prominently to display the Notification, what color to make the display text, etc.
* type `string` (values: migration_scheduled, migration_imminent, migration_pending, reboot_scheduled, outage, payment_due, ticket_important, ticket_abuse, notice, maintenance, promotion): The type of Notification this is.
* until `string`: If this Notification has a duration, this will be the ending time for the Event/action. For example, if there is scheduled maintenance for one of our systems, `until` would be set to the end of the maintenance window.
* when `string`: If this Notification is of an Event that will happen at a fixed, future time, this is when the named action will be taken. For example, if a Linode is to be migrated in response to a Security Advisory, this field will contain the approximate time the Linode will be taken offline for migration.
### OAuthClient
* OAuthClient `object`: A third-party application registered to Linode that users may log into with their Linode account through our authentication server at <a target="_top" href="https://login.linode.com">https://login.linode.com</a>. Using an OAuth Client, a third-party developer may be given access to some, or all, of a User's account for the purposes of their application.
* id `string`: The OAuth Client ID. This is used to identify the client, and is a publicly-known value (it is not a secret).
* label `string`: The name of this application. This will be presented to users when they are asked to grant it access to their Account.
* public `boolean`: If this is a public or private OAuth Client. Public clients have a slightly different authentication workflow than private clients. See the <a target="_top" href="https://oauth.net/2/">OAuth spec</a> for more details.
* redirect_uri `string`: The location a successful log in from <a target="_top" href="https://login.linode.com">https://login.linode.com</a> should be redirected to for this client. The receiver of this redirect should be ready to accept an OAuth exchange code and finish the OAuth exchange.
* secret `string`: The OAuth Client secret, used in the OAuth exchange. This is returned as `<REDACTED>` except when an OAuth Client is created or its secret is reset. This is a secret, and should not be shared or disclosed publicly.
* status `string` (values: active, disabled, suspended): The status of this application. `active` by default.
* thumbnail_url `string`: The URL where this client's thumbnail may be viewed, or `null` if this client does not have a thumbnail set.
### ObjectStorageBucket
* ObjectStorageBucket `object`: An Object Storage Bucket. This should be accessed primarily through the S3 API; [click here for more information](https://docs.ceph.com/docs/mimic/radosgw/s3/#api).
* cluster `string`: The ID of the Object Storage Cluster this bucket is in.
* created `string`: When this bucket was created.
* hostname `string`: The hostname where this bucket can be accessed. This hostname can be accessed through a browser if the bucket is made public.
* label `string`: The name of this bucket.
* objects `integer`: The number of objects in this bucket.
* region `string`: The ID of the Region this bucket exists in.
* size `integer`: The size of this bucket, in bytes.
### ObjectStorageCluster
* ObjectStorageCluster `object`: An Object Storage Cluster
* domain `string`: The base URL for this cluster, used for connecting with third-party clients.
* id `string`: The unique ID for this cluster.
* region `string`: The region where this cluster is located.
* static_site_domain `string`: The base URL for this cluster used when hosting static sites.
* status `string` (values: available, unavailable): This cluster's status.
### ObjectStorageKey
* ObjectStorageKey `object`: A keypair used to communicate with the Object Storage S3 API.
* access_key `string`: This keypair's access key. This is not secret.
* id `integer`: This keypair's unique ID
* label `string`: The label given to this key. For display purposes only.
* secret_key `string`: This keypair's secret key. **Only returned on key creation**.
### ObjectStorageObject
* ObjectStorageObject `object`: An Object in Object Storage, or a "prefix" that contains one or more objects when a `delimiter` is used.
* etag `string`: An MD-5 hash of the object. `null` if this object represents a prefix.
* is_truncated `boolean`: Designates if there is another page of bucket objects.
* last_modified `string`: The date and time this object was last modified. `null` if this object represents a prefix.
* name `string`: The name of this object or prefix.
* next_marker `string`: Returns the value you should pass to the `marker` query parameter to get the next page of objects. If there is no next page, `null` will be returned.
* owner `string`: The owner of this object, as a UUID. `null` if this object represents a prefix.
* size `integer`: The size of this object, in bytes. `null` if this object represents a prefix.
### PaginationEnvelope
* PaginationEnvelope `object`: An envelope for paginated response. When accessing a collection through a GET endpoint, the results are wrapped in this envelope which includes metadata about those results.
* data **required** `array`
* items `object`
* page **required** `integer`
* pages **required** `integer`
* results **required** `integer`
### PayPal
* PayPal `object`: An object representing the staging of a Payment via PayPal.
* cancel_url **required** `string`: The URL to have PayPal redirect to when Payment is cancelled.
* redirect_url **required** `string`: The URL to have PayPal redirect to when Payment is approved.
* usd **required** `string`: The payment amount in USD. Minimum accepted value of $5 USD. Maximum accepted value of $500 USD or credit card payment limit; whichever value is highest. PayPal's maximum transaction limit is $10,000 USD.
### PayPalExecute
* PayPalExecute `object`: An object representing an execution of Payment to PayPal to capture the funds and credit your Linode Account.
* payer_id **required** `string`: The PayerID returned by PayPal during the transaction authorization process.
* payment_id **required** `string`: The PaymentID returned from [POST /account/payments/paypal](/account-payments-paypal/#post) that has been approved with PayPal.
### Payment
* Payment `object`: Payment object response.
* date `string`: When the Payment was made.
* id `integer`: The unique ID of the Payment.
* usd `integer`: The amount, in US dollars, of the Payment.
### PaymentRequest
* PaymentRequest `object`: Payment object request.
* cvv `string`: CVV (Card Verification Value) of the credit card to be used for the Payment.
* usd **required** `string`: The amount in US Dollars of the Payment. The maximum credit card payment that can be made is $50,000 dollars.
### PersonalAccessToken
* PersonalAccessToken `object`: A Personal Access Token is a token generated manually to access the API without going through an OAuth login. Personal Access Tokens can have scopes just like OAuth tokens do, and are commonly used to give access to command-line tools like the Linode CLI, or when writing your own integrations.
* created `string`: The date and time this token was created.
* expiry `string`: When this token will expire. Personal Access Tokens cannot be renewed, so after this time the token will be completely unusable and a new token will need to be generated. Tokens may be created with "null" as their expiry and will never expire unless revoked.
* id `integer`: This token's unique ID, which can be used to revoke it.
* label `string`: This token's label. This is for display purposes only, but can be used to more easily track what you're using each token for.
* scopes `string`: The scopes this token was created with. These define what parts of the Account the token can be used to access. Many command-line tools, such as the <a target="_top" href="https://github.com/linode/linode-cli">Linode CLI</a>, require tokens with access to `*`. Tokens with more restrictive scopes are generally more secure.
* token `string`: The token used to access the API. When the token is created, the full token is returned here. Otherwise, only the first 16 characters are returned.
### Profile
* Profile `object`: A Profile represents your User in our system. This is where you can change information about your User. This information is available to any OAuth Client regardless of requested scopes, and can be used to populate User information in third-party applications.
* authorized_keys `array`: The list of SSH Keys authorized to use Lish for your User. This value is ignored if `lish_auth_method` is "disabled."
* items `string`
* email `string`: Your email address. This address will be used for communication with Linode as necessary.
* email_notifications `boolean`: If true, you will receive email notifications about account activity. If false, you may still receive business-critical communications through email.
* ip_whitelist_enabled `boolean`: If true, logins for your User will only be allowed from whitelisted IPs. This setting is currently deprecated, and cannot be enabled.
* lish_auth_method `string` (values: password_keys, keys_only, disabled): What methods of authentication are allowed when connecting via Lish. "keys_only" is the most secure if you intend to use Lish, and "disabled" is recommended if you do not intend to use Lish at all.
* referrals `object`: Information about your status in our referral program.
* code `string`: Your referral code. If others use this when signing up for Linode, you will receive account credit.
* completed `integer`: The number of completed signups with your referral code.
* credit `integer`: The amount of account credit in US Dollars issued to you through the referral program.
* pending `integer`: The number of pending signups with your referral code. You will not receive credit for these signups until they are completed.
* total `integer`: The number of users who have signed up with your referral code.
* url `string`: Your referral url, used to direct others to sign up for Linode with your referral code.
* restricted `boolean`: If true, your User has restrictions on what can be accessed on your Account. To get details on what entities/actions you can access/perform, see [/profile/grants](/api/v4/profile-grants).
* timezone `string`: The timezone you prefer to see times in. This is not used by the API, and is for the benefit of clients only. All times the API returns are in UTC.
* two_factor_auth `boolean`: If true, logins from untrusted computers will require Two Factor Authentication. See [/profile/tfa-enable](/api/v4/profile-tfa-enable/#post) to enable Two Factor Authentication.
* uid `integer`: Your unique ID in our system. This value will never change, and can safely be used to identify your User.
* username `string`: Your username, used for logging in to our system.
### Region
* Region `object`: An area where Linode services are available.
* capabilities `array`: A list of capabilities of this region.
* items `string`
* country `string`: The country where this Region resides.
* id `string`: The unique ID of this Region.
### RescueDevices
* RescueDevices `object`
* sda [Device](#device)
* sdb [Device](#device)
* sdc [Device](#device)
* sdd [Device](#device)
* sde [Device](#device)
* sdf [Device](#device)
* sdg [Device](#device)
### SSHKey
* SSHKey `object`: A credential object for authenticating a User's secure shell connection to a Linode.
* created `string`: The date this key was added.
* id `integer`: The unique identifier of an SSH Key object.
* label `string`: A label for the SSH Key.
* ssh_key `string`: The public SSH Key, which is used to authenticate to the root user of the Linodes you deploy.
### SSHKeyRequest
* SSHKeyRequest `object`: An object consisting of a user identified name as the `label` and the generated key as the `ssh-key`.
* label `string`: A label for the key.
* ssh_key `string`: The public SSH Key, which is used to authenticate to the root user of the Linodes you deploy.
### StackScript
* StackScript `object`: A StackScript enables you to quickly deploy a fully-configured application in an automated manner.
* created `string`: The date this StackScript was created.
* deployments_active `integer`: Count of currently active, deployed Linodes created from this StackScript.
* deployments_total `integer`: The total number of times this StackScript has been deployed.
* description `string`: A description for the StackScript.
* id `integer`: The unique ID of this StackScript.
* images `array`: An array of Image IDs. These are the images that can be deployed with this Stackscript.
* items `string`
* is_public `boolean`: This determines whether other users can use your StackScript. **Once a StackScript is made public, it cannot be made private.**
* label `string`: The StackScript's label is for display purposes only.
* rev_note `string`: This field allows you to add notes for the set of revisions made to this StackScript.
* script `string`: The script to execute when provisioning a new Linode with this StackScript.
* updated `string`: The date this StackScript was last updated.
* user_defined_fields `array`: This is a list of fields defined with a special syntax inside this StackScript that allow for supplying customized parameters during deployment. See <a target="_top" href="https://www.linode.com/docs/platform/stackscripts/#variables-and-udfs">Variables and UDFs</a> for more information.
* items [UserDefinedField](#userdefinedfield)
* user_gravatar_id `string`: The Gravatar ID for the User who created the StackScript.
* username `string`: The User who created the StackScript.
### SupportTicket
* SupportTicket `object`: A Support Ticket opened on your Account.
* attachments `array`: A list of filenames representing attached files associated with this Ticket.
* items `string`
* closable `boolean`: Whether the Support Ticket may be closed.
* closed `string`: The date and time this Ticket was closed.
* description `string`: The full details of the issue or question.
* entity `object`: The entity this Ticket was opened for.
* id `integer`: The unique ID for this Ticket's entity.
* label `string`: The current label of this entity.
* type `string`: The type of entity this is related to.
* url `string`: The URL where you can access the object this event is for. If a relative URL, it is relative to the domain you retrieved the entity from.
* gravatar_id `string`: The Gravatar ID of the User who opened this Ticket.
* id `integer`: The ID of the Support Ticket.
* opened `string`: The date and time this Ticket was created.
* opened_by `string`: The User who opened this Ticket.
* status `string` (values: closed, new, open): The current status of this Ticket.
* summary `string`: The summary or title for this Ticket.
* updated `string`: The date and time this Ticket was last updated.
* updated_by `string`: The User who last updated this Ticket.
### SupportTicketReply
* SupportTicketReply `object`: An object representing a reply to a Support Ticket.
* created `string`: The date and time this Ticket reply was created.
* created_by `string`: The User who submitted this reply.
* description `string`: The body of this Support Ticket reply.
* from_linode `boolean`: If set to true, this reply came from a Linode employee.
* gravatar_id `string`: The Gravatar ID of the User who created this reply.
* id `integer`: The unique ID of this Support Ticket reply.
### SupportTicketRequest
* SupportTicketRequest `object`: An object representing a created Support Ticket - a question or issue and request for help from the Linode support team.
* description **required** `string`: The full details of the issue or question.
* domain_id `integer`: The ID of the Domain this ticket is regarding, if relevant.
* linode_id `integer`: The ID of the Linode this ticket is regarding, if relevant.
* longviewclient_id `integer`: The ID of the Longview client this ticket is regarding, if relevant.
* nodebalancer_id `integer`: The ID of the NodeBalancer this ticket is regarding, if relevant.
* summary **required** `string`: The summary or title for this SupportTicket.
* volume_id `integer`: The ID of the Volume this ticket is regarding, if relevant.
### Tag
* Tag `object`: A tag that has been applied to an object on your Account. Tags are currently for organizational purposes only.
* label `string`: A Label used for organization of objects on your Account.
### Transfer
* Transfer `object`: An object representing your network utilization for the current month, in Gigabytes.
* billable `integer`: The amount of your transfer pool that is billable this billing cycle.
* quota `integer`: The amount of network usage allowed this billing cycle.
* used `integer`: The amount of network usage you have used this billing cycle.
### TrustedDevice
* TrustedDevice `object`: A trusted device object represents an active Remember Me session with <a target="_top" href="https://login.linode.com">login.linode.com</a>.
* created `string`: When this Remember Me session was started. This corresponds to the time of login with the "Remember Me" box checked.
* expiry `string`: When this TrustedDevice session expires. Sessions typically last 30 days.
* id `integer`: The unique ID for this TrustedDevice
* last_authenticated `string`: The last time this TrustedDevice was successfully used to authenticate to <a target="_top" href="https://login.linode.com">login.linode.com</a>.
* last_remote_addr `string`: The last IP Address to successfully authenticate with this TrustedDevice.
* user_agent `string`: The User Agent of the browser that created this TrustedDevice session.
### User
* User `object`: A User on your Account. Unrestricted users can log in and access information about your Account, while restricted users may only access entities or perform actions they've been granted access to.
* email `string`: The email address for this User, for account management communications, and may be used for other communications as configured.
* restricted `boolean`: If true, this User must be granted access to perform actions or access entities on this Account. See [/account/users/{username}/grants](/api/v4/account-users-username-grants) for details on how to configure grants for a restricted User.
* ssh_keys `array`: A list of SSH Key labels added by this User. These are the keys that will be deployed if this User is included in the `authorized_users` field of a [create Linode](/api/v4/linode-instances/#post), [rebuild Linode](/api/v4/linode-instances-linode-id-rebuild/#post), or [create Disk](/api/v4/linode-instances-linode-id-disks/#post) request.
* items `string`
* username `string`: This User's username. This is used for logging in, and may also be displayed alongside actions the User performs (for example, in Events or public StackScripts).
### UserDefinedField
* UserDefinedField `object`: A custom field defined by the User with a special syntax within a StackScript. Derived from the contents of the script.
* default `string`: The default value. If not specified, this value will be used.
* example **required** `string`: An example value for the field.
* label **required** `string`: A human-readable label for the field that will serve as the input prompt for entering the value during deployment.
* manyOf `string`: A list of acceptable values for the field in any quantity, combination or order.
* name **required** `string`: The name of the field.
* oneOf `string`: A list of acceptable single values for the field.
### Volume
* Volume `object`: A Block Storage Volume associated with your Account.
* tags `array`: An array of Tags applied to this object. Tags are for organizational purposes only.
* items `string`
* created `string`: When this Volume was created.
* filesystem_path `string`: The full filesystem path for the Volume based on the Volume's label. Path is /dev/disk/by-id/scsi-0Linode_Volume_ + Volume label.
* id `integer`: The unique ID of this Volume.
* label **required** `string`: The Volume's label is for display purposes only.
* linode_id `integer`: If a Volume is attached to a specific Linode, the ID of that Linode will be displayed here.
* region [Region/properties/id](#region/properties/id)
* size `integer`: The Volume's size, in GiB.
* status `string` (values: creating, active, resizing, contact_support): The current status of the volume. Can be one of:
* updated `string`: When this Volume was last updated.
| 38.470588 | 1,933 | 0.730857 | eng_Latn | 0.978134 |
dac92ed51ebf6b8e45f8f1b26bb734a1da1c533b | 2,556 | md | Markdown | packages/color-hooks/README.md | sendevman/rctvertex | ad040179e8f24c9e328f910b666a6c66e0408401 | [
"MIT"
] | 1,324 | 2019-05-25T19:16:04.000Z | 2022-03-12T21:30:58.000Z | packages/color-hooks/README.md | sghall/react-vertex | 461e8a9e1ba1c02317c7ced69022b248cdd89c61 | [
"MIT"
] | 10 | 2019-05-29T01:36:47.000Z | 2022-02-17T21:11:09.000Z | packages/color-hooks/README.md | sendevman/rctvertex | ad040179e8f24c9e328f910b666a6c66e0408401 | [
"MIT"
] | 31 | 2019-05-26T00:50:18.000Z | 2019-12-21T22:51:06.000Z | ## `@react-vertex/color-hooks`
[](https://github.com/sghall/react-vertex/blob/master/packages/color-hooks/LICENSE)
[](https://www.npmjs.com/package/@react-vertex/color-hooks)
[](https://bundlephobia.com/result?p=@react-vertex/color-hooks)
### [Documentation and Examples](https://react-vertex.com)
Hooks and utility functions for converting colors to WebGL friendly formats.
##### Install via npm:
```js
npm install @react-vertex/color-hooks
```
##### Importing:
```js
import {
useHex,
convertHex,
useRgb,
convertRgb,
} from '@react-vertex/color-hooks'
```
#### `useHex(hex, noAlpha?)` => `Array`
#### `convertHex(hex, noAlpha?)` => `Array`
Convert hex colors to WebGL friendly format. Exported as a hook (`useHex`) and a utility function (`convertHex`).
###### Arguments:
`hex`: String hex color.
`noAlpha (optional)`: Boolean indicating if you want the alpha value in the array.
###### Returns:
`array`: An array of numbers between 0 and 1. A four element array by default and three elements if the `noAlpha` parameter is used.
###### Example Usage:
```js
import {
useHex,
convertHex,
} from '@react-vertex/color-hooks'
const [r, g, b, a] = useHex('#fff')
// [1, 1, 1, 1]
const clearColor = useHex('#0006')
// [0, 0, 0, 0.4]
convertHex('#4183c4')
// [0.2549019607843137, 0.5137254901960784, 0.7686274509803922, 1]
convertHex('#4183c4', true) // Drop the alpha by passing true as a second param
// [0.2549019607843137, 0.5137254901960784, 0.7686274509803922]
gl.clearColor(...convertHex('#323334'))
```
#### `useRgb(rgb, noAlpha?)` => `Array`
#### `convertRgb(rgb, noAlpha?)` => `Array`
Convert rgb colors to WebGL friendly format. Exported as a hook (`useRgb`) and a utility function (`convertRgb`).
###### Arguments:
`rgb`: String rgb color e.g. `'rgb(40, 42, 54)'` or `'rgba(40, 42, 54, 75%)'`.
`noAlpha (optional)`: Boolean indicating if you want the alpha value in the array.
###### Returns:
`array`: An array of numbers between 0 and 1. A four element array by default and three elements if the `noAlpha` parameter is used.
###### Example Usage:
```js
import {
useRgb,
convertRgb,
} from '@react-vertex/color-hooks'
const [r, g, b, a] = useRgb('rgb(255, 255, 255)');
// [1, 1, 1, 1]
const clearColor = convertRgb('rgb(255, 0, 255)', true)
// [1, 0, 1]
```
| 26.625 | 169 | 0.679969 | eng_Latn | 0.584313 |
dac935db931ba67ac2225abb295c1fa4fe96f7bb | 56 | md | Markdown | README.md | nguyen-nhat/firebase-learn | 49cc86ec8eb9b4c8f3bbc8d61c9058437ddb9fed | [
"MIT"
] | null | null | null | README.md | nguyen-nhat/firebase-learn | 49cc86ec8eb9b4c8f3bbc8d61c9058437ddb9fed | [
"MIT"
] | null | null | null | README.md | nguyen-nhat/firebase-learn | 49cc86ec8eb9b4c8f3bbc8d61c9058437ddb9fed | [
"MIT"
] | null | null | null | # firebase-learn
Code environment for learning Firebase
| 18.666667 | 38 | 0.839286 | eng_Latn | 0.664973 |
daca8e34d996836ebadf202ab9b74aea29232590 | 23 | md | Markdown | docs/API/Structure_Generation/adsorption.md | aced-differentiate/auto_cat | eeaea6b3e3f117565e1479d5c5c1cb9d830f8526 | [
"MIT"
] | null | null | null | docs/API/Structure_Generation/adsorption.md | aced-differentiate/auto_cat | eeaea6b3e3f117565e1479d5c5c1cb9d830f8526 | [
"MIT"
] | null | null | null | docs/API/Structure_Generation/adsorption.md | aced-differentiate/auto_cat | eeaea6b3e3f117565e1479d5c5c1cb9d830f8526 | [
"MIT"
] | null | null | null | ::: autocat.adsorption
| 11.5 | 22 | 0.73913 | eng_Latn | 0.481435 |
dacac3617dcab78193c5a5238e218f8e568d2988 | 1,531 | md | Markdown | content/participants/ttjc@AbhijeetNandvikar/index.md | thesyedsufiyan/teamtanay.jobchallenge.dev | 135cddec479aed1c7e5e5afb9b35949aaf5de36b | [
"MIT"
] | 1 | 2020-04-21T18:41:38.000Z | 2020-04-21T18:41:38.000Z | content/participants/ttjc@AbhijeetNandvikar/index.md | thesyedsufiyan/teamtanay.jobchallenge.dev | 135cddec479aed1c7e5e5afb9b35949aaf5de36b | [
"MIT"
] | null | null | null | content/participants/ttjc@AbhijeetNandvikar/index.md | thesyedsufiyan/teamtanay.jobchallenge.dev | 135cddec479aed1c7e5e5afb9b35949aaf5de36b | [
"MIT"
] | null | null | null | ---
title: Abhijeet Nandvikar
type: "participant"
name: "Abhijeet Nandvikar"
portfolio: "https://abhijeet-portfolio.netlify.com/"
github-link: "https://github.com/AbhijeetNandvikar"
linkedin-link: "https://www.linkedin.com/in/abhijeet-nandvikar-724b7818b/"
looking-for: "internship"
description: "I am good at HTML/CSS/JS, learning react"
---
Hi, I am Abhijeet Nandvikar. I live in Mumbai. I am third year engineering student studying computer engineering at Atharva College.
### introduction
I am intrested in web development and I make websites for local business.
## why are you taking this challenge?
I am taking this challenege to expand my knowledge by working on projects learning new stuffs from mentors and gain new skills.
## something interesting about you?
I love doing yoga.
### help I need?
I want to learn about backend stuff.
### how to contact me?
- [Twitter](https://twitter.com/AbhijeetNandvi1)
- [LinkedIn](https://www.linkedin.com/in/abhijeet-nandvikar-724b7818b/)
### projects
I have made a website for a local business(Manjul Joshi Photography). Also I have made some basic projects.
My projects:
#### Xpense App (PWA)
_description_ This is progressive web app created for writting your daily expenses.
_stack_ Made using HTML/CSS/JS for frontend and Firebase for backend.
_hosted link_ https://xpense-app-d4794.web.app/index.html
_github link_ https://github.com/AbhijeetNandvikar/Xpense-App-PWA-
### blogs
I will start sharing my blogs with live links after I finish writing them.
| 26.859649 | 132 | 0.764206 | eng_Latn | 0.925809 |
dacbd67c6c23191f30433ac42f72e3f785169248 | 1,021 | md | Markdown | _listings/viddler/viddler-users-getplayerbranding-get-postman.md | streamdata-gallery-organizations/viddler | 3f3361654233abdb0b84c57f49b71f244327b86c | [
"CC-BY-3.0"
] | null | null | null | _listings/viddler/viddler-users-getplayerbranding-get-postman.md | streamdata-gallery-organizations/viddler | 3f3361654233abdb0b84c57f49b71f244327b86c | [
"CC-BY-3.0"
] | null | null | null | _listings/viddler/viddler-users-getplayerbranding-get-postman.md | streamdata-gallery-organizations/viddler | 3f3361654233abdb0b84c57f49b71f244327b86c | [
"CC-BY-3.0"
] | null | null | null | {
"info": {
"name": "Viddler API Users GetPlayerBranding",
"_postman_id": "3c1bb7b5-1511-4529-9ee3-3003f13e72dc",
"description": "Returns your player branding configuration.",
"schema": "https://schema.getpostman.com/json/collection/v2.0.0/"
},
"item": [
{
"name": "Viddler",
"item": [
{
"id": "9b3d08f6-8f6e-4868-9582-a7b8ab4a9143",
"name": "users-getplayerbranding",
"request": {
"url": "http://api.viddler.com/api/v2/viddler.users.getPlayerBranding?sessionid=%7B%7D",
"method": "GET",
"body": {
"mode": "raw"
},
"description": "Returns your player branding configuration."
},
"response": [
{
"status": "OK",
"code": 200,
"name": "Response_200",
"id": "41daa56c-4ae7-4e82-a22f-8088eed5715d"
}
]
}
]
}
]
} | 29.171429 | 101 | 0.46523 | yue_Hant | 0.284171 |
b57e0e8191322cc5b6e48b3f07d2cebea858d438 | 24 | md | Markdown | README.md | alexwu1009/History-of-Price-Gold- | 5956d5e997ee5b7972bd6c4a04a544f6aefffecc | [
"MIT"
] | null | null | null | README.md | alexwu1009/History-of-Price-Gold- | 5956d5e997ee5b7972bd6c4a04a544f6aefffecc | [
"MIT"
] | null | null | null | README.md | alexwu1009/History-of-Price-Gold- | 5956d5e997ee5b7972bd6c4a04a544f6aefffecc | [
"MIT"
] | null | null | null | # History-of-Price-Gold
| 12 | 23 | 0.75 | yue_Hant | 0.69538 |
b57ea43646433de1ed6da908bef76919d6e8e3be | 105 | md | Markdown | Packs/SplunkPy/ReleaseNotes/1_1_3.md | diCagri/content | c532c50b213e6dddb8ae6a378d6d09198e08fc9f | [
"MIT"
] | 799 | 2016-08-02T06:43:14.000Z | 2022-03-31T11:10:11.000Z | Packs/SplunkPy/ReleaseNotes/1_1_3.md | diCagri/content | c532c50b213e6dddb8ae6a378d6d09198e08fc9f | [
"MIT"
] | 9,317 | 2016-08-07T19:00:51.000Z | 2022-03-31T21:56:04.000Z | Packs/SplunkPy/ReleaseNotes/1_1_3.md | diCagri/content | c532c50b213e6dddb8ae6a378d6d09198e08fc9f | [
"MIT"
] | 1,297 | 2016-08-04T13:59:00.000Z | 2022-03-31T23:43:06.000Z |
#### Integrations
##### SplunkPy
- Fixed an issue where ***fetch-incidents*** would miss some incidents. | 26.25 | 71 | 0.695238 | eng_Latn | 0.97904 |
b57f7375535853db07d2c59d401bca4fb8b821a0 | 128 | md | Markdown | sample3.md | thase/thase.github.com | c28539a61c8b1e698b0fdb0e6a69748af527eb2d | [
"MIT"
] | null | null | null | sample3.md | thase/thase.github.com | c28539a61c8b1e698b0fdb0e6a69748af527eb2d | [
"MIT"
] | null | null | null | sample3.md | thase/thase.github.com | c28539a61c8b1e698b0fdb0e6a69748af527eb2d | [
"MIT"
] | null | null | null | ---
layout: page
title: "Sample3"
description: ""
category: [SmartPlayer, rendition]
tags: [abc,def]
---
{% include JB/setup %}
| 14.222222 | 34 | 0.664063 | eng_Latn | 0.795047 |
b57fa30eaa15f7fffadff164d31a9ba4c9a411c2 | 218 | md | Markdown | _watches/M20210514_025441_TLP_2.md | Meteoros-Floripa/meteoros.floripa.br | 7d296fb8d630a4e5fec9ab1a3fb6050420fc0dad | [
"MIT"
] | 5 | 2020-05-19T17:04:49.000Z | 2021-03-30T03:09:14.000Z | _watches/M20210514_025441_TLP_2.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | null | null | null | _watches/M20210514_025441_TLP_2.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | 2 | 2020-05-19T17:06:27.000Z | 2020-09-04T00:00:43.000Z | ---
layout: watch
title: TLP2 - 14/05/2021 - M20210514_025441_TLP_2T.jpg
date: 2021-05-14 02:54:41
permalink: /2021/05/14/watch/M20210514_025441_TLP_2
capture: TLP2/2021/202105/20210513/M20210514_025441_TLP_2T.jpg
---
| 27.25 | 62 | 0.784404 | eng_Latn | 0.051354 |
b5800aa0ccb5355194590b31375692eee1f42d78 | 821 | md | Markdown | content/user/new_user_topics/home_in_middle.md | torvista/documentation | 28ba0a1bad888a9061be7b437fb886b4c01a6abf | [
"MIT"
] | 4 | 2018-08-30T14:46:28.000Z | 2020-07-16T11:57:56.000Z | content/user/new_user_topics/home_in_middle.md | torvista/documentation | 28ba0a1bad888a9061be7b437fb886b4c01a6abf | [
"MIT"
] | 181 | 2016-04-25T14:06:12.000Z | 2022-03-06T10:15:49.000Z | content/user/new_user_topics/home_in_middle.md | torvista/documentation | 28ba0a1bad888a9061be7b437fb886b4c01a6abf | [
"MIT"
] | 25 | 2016-04-25T05:29:25.000Z | 2021-09-21T20:01:06.000Z | ---
title: How do I remove the word "Home" in the middle column?
description: Removing the home breadcrumb
category: new_user_topics
weight: 10
---
On some pages, to the right of the categories sidebox, the word "Home" (or perhaps "Home > some-category-name") appears above the page content.
These are called the *breadcrumbs* (think Hansel and Gretel). They show where you are and how to get back to previous locations. You can either turn them off completely or you can turn them off only on the main page. Although breadcrumbs may look a little odd on your home page, they can very useful to your users as they go deeper into your site.
To turn them off, go to [Admin > Configuration > Layout settings](/user/admin_pages/configuration/configuration_layoutsettings/) and set *Define Breadcrumb Status* to 0.
| 58.642857 | 350 | 0.768575 | eng_Latn | 0.999492 |
b58036fa054c4e94046520003687decf8ae55bb7 | 1,894 | md | Markdown | docs/filecoin/drand.md | DeveloperAlly/launchpad | e195c1474e104dad960f85c71065721602c04434 | [
"MIT"
] | 9 | 2022-01-31T22:36:37.000Z | 2022-03-23T07:51:41.000Z | docs/filecoin/drand.md | DeveloperAlly/launchpad | e195c1474e104dad960f85c71065721602c04434 | [
"MIT"
] | 12 | 2022-01-28T12:08:33.000Z | 2022-03-30T14:00:02.000Z | docs/filecoin/drand.md | DeveloperAlly/launchpad | e195c1474e104dad960f85c71065721602c04434 | [
"MIT"
] | 13 | 2022-01-27T11:19:08.000Z | 2022-03-28T02:01:08.000Z | ---
description: Distributed, Unpredictable, Publicly-Verifiable, and Decentralized Randomness Generator
---
## Drand
Drand is a distributed, bias-resistant, unpredictable, and publicly verifiable randomness generator that is key to the Filecoin implementation in how it provides unpredictable, decentralized and publicly verifiable random values for the blockchain. [Learn more about how Drand works in the docs](https://drand.love/docs/overview/#how-drand-works)
#### Drand: Distributed, Bias Resistant, Unpredictable and Publicly Verifiable Randomness | Nicolas Gailly
Drand uses [cryptographic methods](https://drand.love/docs/cryptography/#setup-phase), collective public keys, and a private key share of a collective private key to generate randomness in a distributed manner.
{% embed url="https://www.youtube.com/watch?v=ydwW2HFFxNI" %}
#### [drand - The Distributed Randomness Beacon | ResNetLabs On Tour – Nicolas GAILLY](https://research.protocol.ai/tutorials/resnetlab-on-tour/modular-p2p-stack/)
drand is a distributed randomness beacon. It provides publicly-verifiable, unpredictable, and bias-resistant random numbers as a public service. In this module, we’ll walk through::
* Threshold Cryptography & Randomness
* Distributed Key Generation in drand
* The Setup and Randomness Generation Phases
* The League of Entropy
{% embed url="https://www.youtube.com/watch?v=NNfaQ__UFCE" %}
## Drand Resources
* The [drand website](https://drand.love/)
* [Spec](https://spec.filecoin.io/libraries/drand/)
* [Github Repos](https://github.com/drand)
* Article – [Researchers from Protocol Labs Explain how the Drand or Distributed Randomness Project can Help with Cybersecurity, Election Audits](https://www.crowdfundinsider.com/2020/08/165618-researchers-from-protocol-labs-explain-how-the-drand-or-distributed-randomness-project-can-help-with-cybersecurity-election-audits/)
| 57.393939 | 346 | 0.789335 | eng_Latn | 0.837015 |
b5809bb8c393a8dd59487a5efa8c34321b045ab6 | 345 | md | Markdown | README.md | magemello/magemello.github.io | 9d1bf81b7113eb8fecc4c1c8b9fd06e48a3cb4cb | [
"Apache-2.0"
] | null | null | null | README.md | magemello/magemello.github.io | 9d1bf81b7113eb8fecc4c1c8b9fd06e48a3cb4cb | [
"Apache-2.0"
] | null | null | null | README.md | magemello/magemello.github.io | 9d1bf81b7113eb8fecc4c1c8b9fd06e48a3cb4cb | [
"Apache-2.0"
] | null | null | null | #Mario Romano - Online Portfolio
- Link: http://magemello.github.io/
#What I used to make it
- http://startbootstrap.com/template-overviews/freelancer/
- https://github.com/Aerolab/blockrain.js
- https://github.com/cristurm/nyan-cat
- https://github.com/konpa/devicon
- http://codepen.io/P233/pen/lGewF
- Plus javascript, Html, CSS and Love
| 24.642857 | 58 | 0.742029 | yue_Hant | 0.781348 |
b582c87fcf4395e431598ecfa0a863954b834ae1 | 22 | md | Markdown | README.zh-CN.md | BernardTolosajr/marmot | 97fc01f758569aa063220a136f397e88d65f003e | [
"MIT"
] | null | null | null | README.zh-CN.md | BernardTolosajr/marmot | 97fc01f758569aa063220a136f397e88d65f003e | [
"MIT"
] | null | null | null | README.zh-CN.md | BernardTolosajr/marmot | 97fc01f758569aa063220a136f397e88d65f003e | [
"MIT"
] | null | null | null | # Marmot
coming soon
| 5.5 | 11 | 0.727273 | eng_Latn | 0.979833 |
b5860a2d0919af41aca3357384f4678c31057b20 | 63 | md | Markdown | README.md | Taras2010/Bird | aeff1edbfe6ef7444b603aa4082425d8de848616 | [
"MIT"
] | 1 | 2021-03-28T16:59:48.000Z | 2021-03-28T16:59:48.000Z | README.md | Taras2010/GoITeensfrontend5-Symak | aeff1edbfe6ef7444b603aa4082425d8de848616 | [
"MIT"
] | null | null | null | README.md | Taras2010/GoITeensfrontend5-Symak | aeff1edbfe6ef7444b603aa4082425d8de848616 | [
"MIT"
] | null | null | null | # GoITeens-frontend5-Symak
Це є файл на домашнє завдання !!!!
| 21 | 34 | 0.730159 | ukr_Cyrl | 0.969325 |
b58643ea350a0e6e69f586d52a78ee8dc2954b17 | 1,771 | md | Markdown | README.md | audinue/refresh | 25b0b61af40141f8c70dcae0e3850626225b1819 | [
"MIT"
] | null | null | null | README.md | audinue/refresh | 25b0b61af40141f8c70dcae0e3850626225b1819 | [
"MIT"
] | null | null | null | README.md | audinue/refresh | 25b0b61af40141f8c70dcae0e3850626225b1819 | [
"MIT"
] | null | null | null | # Refresh
Write this...
```html
<script src="https://audinue.github.io/refresh/refresh.min.js"></script>
<script>
var name = 'John'
</script>
<p>Name: <input value="{name}" oninput="name=this.value"></p>
<p>Hello {name}!</p>
```
And you get this...
Visit the [playground](https://audinue.github.io/refresh/playground.html) to learn more.
## Usage
Copy and paste the following code to your HTML page:
```html
<script src="https://audinue.github.io/refresh/refresh.min.js"></script>
```
Or through [GitCDN](https://github.com/schme16/gitcdn.xyz)
```html
<script src="https://gitcdn.link/repo/audinue/refresh/master/refresh.min.js"></script>
```
## Notes
- Call `refresh()` to update the DOM outside of HTML.
- `<p align="{align}">Hello {name}!</p>`
- `this` refers to the owning element.
- `<tag for="value[, key] in expression"></tag>` creates new scope.
- `<tag if="expression"></tag>`, `<tag else-if="expression"></tag>` and `<tag else></tag>`
- `<tag class-map="class: expression[; class: expression]*"></tag>`
- `safe-*` for edge-cases like `<input type="number" safe-value="{foo}">`
- Two way data binding:
- `value-source="expression"` also works for `<select>` for WebKit only.
- `checked-source="expression"` accepts boolean, array and other.
- `text-source="expression"` for content-editable elements.
- `template="name(parameters)"` and `apply="name(arguments)"`
- `autofocus` works well with `if`.
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-138735077-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-138735077-1');
</script>
| 30.016949 | 90 | 0.669678 | yue_Hant | 0.333907 |
b586792f995f17d90faa9ab27e88f611fa4ed514 | 571 | md | Markdown | articles/internet-peering/includes/delete.md | changeworld/azure-docs.hu-hu | f0a30d78dd2458170473188ccce3aa7e128b7f89 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/internet-peering/includes/delete.md | changeworld/azure-docs.hu-hu | f0a30d78dd2458170473188ccce3aa7e128b7f89 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/internet-peering/includes/delete.md | changeworld/azure-docs.hu-hu | f0a30d78dd2458170473188ccce3aa7e128b7f89 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: fájl belefoglalása
titleSuffix: Azure
description: fájl belefoglalása
services: internet-peering
author: prmitiki
ms.service: internet-peering
ms.topic: include
ms.date: 11/27/2019
ms.author: prmitiki
ms.openlocfilehash: 0ed2137d1fd7a3c207db3ec49590a61f00b5fd99
ms.sourcegitcommit: aee08b05a4e72b192a6e62a8fb581a7b08b9c02a
ms.translationtype: MT
ms.contentlocale: hu-HU
ms.lasthandoff: 01/09/2020
ms.locfileid: "75774275"
---
Ebben az időszakban a megszüntetés nem támogatott a portál [vagy a PowerShell](mailto:[email protected]) használatával.
| 30.052632 | 133 | 0.833625 | hun_Latn | 0.808052 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.