text:
# javaformatter-cli

[![Build Status](https://travis-ci.org/jrialland/javaformatter-cli.svg)](https://travis-ci.org/jrialland/javaformatter-cli)

This project evolved from a Quick and dirty commandline tool that formatted java source code to something more evoluted.

It scans source code directories and beautifies/formats/transforms the files it can, I add support for new tools when I them.

Disclaimer : The tool is made to fit the settings I like and the way I code. It works by convention, not by configuration.

Beautifier
----------

* java : Uses the  Eclipse code java formatter (and its default behavior by default) on all .java files
* xml : beautifies xml using the javax.xml.transform api on xml, xhtml, svg files
* css : beautifies using js-beautify (https://github.com/beautify-web/js-beautify) on every .css files
* html : beautifies using js-beautify (.html only)
* js, json :  beautifies using js-beautify (.js, .json files)

Header in java files
--------------------

- It can also add a commented text header at the beginning of java files (copyright infos, etc...) -> See -H option

Transpilers
-----------

It also features some extra tasks :
* coffeeScript 1.10 compilation (http://coffeeescript.org/) (turning .coffee into .coffee.js)
* compass compiler (http://compass-style.org/) (detect files named compass.rb as configuration file and run them)
* freemarker : runs freemarker on all files with the .ftl extension
* css/js minifier : if the file has ".minify" in its name, the file is minified and into .min

An example :
 If you want to have some coffeeScript files that need to be minified :
```
MyFirstFile.coffeee
MySecondFile.coffee
```

Create a file named all.minify.coffee.ftl with the following content :
```
<#include "MyFirstFile.coffee" parse=false>
<#include "MySecondFile.coffee" parse=false>
```

The compilation mechanism will apply this way :

1) The .ftl extension means that freemarker will be executed, producing a file named all.minify.coffee
2) The .coffee extension will trigger the coffeeScript compiler, and produce the all.minify.js
3) The fact that there is .minify in the name will run jsmin, and produce all.min.js

By specifying the file names properly, the following chain will trigger each time :
    * merging several files into one
    * compiling coffeeScript into javascript
    * minifying the javascript

```sh
#download the formatter script
curl https://cdn.rawgit.com/jrialland/javaformatter-cli/master/javaformatter.sh > javaformatter

#allow to run it
chmod +x javaformatter

#will cleanup the current dir
./javaformatter src/main/java
```

repository: jrialland/javaformatter-cli

gha_language: Java

repo_name: jrialland/javaformatter-cli


text:
# Directory of Open Access Books
The Directory of Open Access Books (DOAB) is a directory of open-access peer reviewed scholarly books.
Its aim is to increase discoverability of books. Currently, there are two requirements to take part in DOAB:
* Academic books in DOAB shall be available under an Open Access license (such as a Creative Commons license)
* Academic books in DOAB shall be subjected to independent and external peer review prior to publication
Data is downloaded from a csv file.

```eval_rst
+--------------------------+---------+
| Summary                  |         |
+==========================+=========+
| Average runtime          | 15m     |
+--------------------------+---------+
| Average download size    | 50MB    |
+--------------------------+---------+
| Harvest Type             | API     |
+--------------------------+---------+
| Harvest Frequency        | Weekly  |
+--------------------------+---------+
| Runs on remote worker    | False   |
+--------------------------+---------+
| Catchup missed runs      | False   |
+--------------------------+---------+
| Table Write Disposition  | Append  |
+--------------------------+---------+
| Update Frequency         | Daily   |
+--------------------------+---------+
| Credentials Required     | No      |
+--------------------------+---------+
```

## Schedule
The csv is updated daily and this telescope is scheduled to harvest the data weekly.

## Results
There are two tables containing data related to this telescope:
  * The main table which contains all the up-to-date DOAB data.
  * A partitioned table, where each partition contains the data of one run. The table is partitioned by the ingestion time.

If there are any edited or deleted entries, the old versions of these entries will first be deleted from the main table
(using a MERGE statement) after which the updated versions are appended to this table.

## Latest schema
``` eval_rst
.. csv-table::
   :file: ../schemas/doab_latest.csv
   :width: 100%
   :header-rows: 1
```

branch_name: refs/heads/main

extension: md

gha_language: Python

license_type: permissive


text:
## Simple Example demonstrating Ajax Implementation using Perl
Originally published: 2007-03-11 07:37:16
Last updated: 2007-03-11 07:37:16
Author: Rajkumar Jain

In the example below, we have a table containing Student names and Marks. Every row has an Edit button, by which user can edit the information for that row. We have used Microsoft Access as the Database to keep things very simple.  In order to run the below example code you will have to create a table by the name “Student” in MS Access”. It should have the following columns.

Column Name	 Data type
Sl_No(Primary Key)	Number
Name	Text
Marks	Number

Also you need to create a DSN by the name “mydsn” pointing to the Access DB.

The basic logic here used in the example is that we have two separate rows for View and Edit (for every Student). Initially we hide the Edit row (by using style="display:none") and display the View Row(by using style="display:block").  When the user clicks on the “Edit” button, the View row becomes hidden and the Edit row is displayed. We have used JavaScript to toggle between the rows. Below is the code snippet used in files (AjaxExample.pl and student.js).

license: MIT

branch_name: refs/heads/master

gha_license_id: MIT


text:
# React Native Uber Interface

A project made with React native, using the best practices.

## Installation

Clone the repo.

Use the package manager [yarn](https://yarnpkg.com/lang/en/docs/install/) or [npm](https://www.npmjs.com/get-npm) to install the dependencies.

run

```bash
yarn
```

or

```bash
npm install
```

## Requirements

These aplication requires you to obtain an API key for the [Android
SDK](https://developers.google.com/maps/documentation/android-sdk/signup) before run it.

## Usage

1. Specify your Google Maps API Key:

   Add your API key to your env file: (`./env`):
    ```
      // Environment variables

      API_KEY='Your Google maps API Key Here'
    ```
2. In your terminal:

   To run on Android:
    ```
      react-native run-android
    ```
    To run on IOS:
    ```
      react-native run-ios
    ```
3. If you are using simulator, set your gps through debug menus or using        external applications (eg fake gps).

## Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

## License

[MIT](https://choosealicense.com/licenses/mit/)

repository: GleidsonDaniel/UberInterface

repo_name: GleidsonDaniel/UberInterface


text:
# DEPRECATED NSURLSession-PromiseKit

PromiseKit 3.0 has [categories](https://github.com/mxcl/PromiseKit/blob/master/Categories/Foundation/NSURLSession%2BPromise.swift) that allow using NSURLSession with promises. Use that instead of this pod.

## Author

Jonas Schmid<EMAIL_ADDRESS>
## License

NSURLSession-PromiseKit is available under the MIT license. See the LICENSE file for more info.

repository: jschmid/NSURLSession-PromiseKit

gha_language: Objective-C

repo_name: jschmid/NSURLSession-PromiseKit


text:
# designernewsbot

Telegram bot that posts new hot stories from Designer News to [telegram channel](https://telegram.me/designer_news)

## Backend

Bot runs on a small [Hetzner cloud](https://hetzner.cloud/?ref=gy7R6jM4nx5J) machine

[Old version](https://github.com/phil-r/designernewsbot/tree/old-python-version) of this bot was written in python and was running on [Google App Engine](https://cloud.google.com/appengine/)

## Designer News API

Bot uses [Designer News API](https://github.com/DesignerNews/dn_api_v2)

It loads [top stories](https://www.designernews.co/api/v2/stories) every minute and posts any story that reached _10+_ score

## Behance API

Bot uses [Behance API](https://www.behance.net/dev)

## Dribbble API

Bot uses [Unofficial Dribble API](https://github.com/phil-r/dribbble-top)

## Telegram API

Bot uses [Telegram Bot API](https://core.telegram.org/bots/api) to post messages to the [telegram channel](https://telegram.me/designer_news) with [sendMessage](https://core.telegram.org/bots/api#sendmessage) request

## URL shortening

Bot uses internal shortener

## How to run your own `designernewsbot`

- Clone this project
- Run `yarn` to install dependencies
- Run `yarn migrate:dev` to create a databse and apply migrations
- Register your bot via [BotFather](https://telegram.me/BotFather)
- Rename `.env.example` to `.env` and
  - replace `YOUR_TELEGRAM_BOT_TOKEN` with your bot token
  - replace `YOUR_BEHANCE_TOKEN` with your behance token
- Possibly you'll want to create your own channel and your bot as an admin. Also change `@designer_news` in `src/helpers.ts` to your channel id

## Local development

To run server locally you can run `yarn dev`

## See also

- [hackernewsbot](https://github.com/phil-r/hackernewsbot)
- [asciifacesbot](https://github.com/phil-r/asciifacesbot)

repository: phil-r/designernewsbot

repo_name: phil-r/designernewsbot


text:
### [CVE-2006-2219](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2219)
![](https://img.shields.io/static/v1?label=Product&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)

### Description

phpBB 2.0.20 does not verify user-specified input variable types before being passed to type-dependent functions, which allows remote attackers to obtain sensitive information, as demonstrated by the (1) mode parameter to memberlist.php and the (2) highlight parameter to viewtopic.php that are used as an argument to the htmlspecialchars or urlencode functions, which displays the installation path in the resulting error message.

### POC

#### Reference
- http://securityreason.com/securityalert/837

#### Github
No PoCs found on GitHub currently.

repository: trickest/cve

gha_language: HTML

repo_name: trickest/cve


text:
# fill-array [![NPM version](https://badge.fury.io/js/fill-array.svg)](http://badge.fury.io/js/fill-array)

> Fill an array to the given length by repeating its elements. This is a very fast implementation.

## Install with [npm](npmjs.org)

```bash
npm i fill-array --save
```

## Usage

```js
var fill = require('fill-array');

fill(['a', 'b', 'c'], 10);
//=> ['a','b','c','a','b','c','a','b','c','a']
```

## Run tests

Install dev dependencies:

```bash
npm i -d && npm test
```

## Contributing
Pull requests and stars are always welcome. For bugs and feature requests, [please create an issue](https://github.com/jonschlinkert/fill-array/issues)

## Author

**Jon Schlinkert**

+ [github/jonschlinkert](https://github.com/jonschlinkert)
+ [twitter/jonschlinkert](http://twitter.com/jonschlinkert)

## License
Copyright (c) 2015, Jon Schlinkert.
Released under the MIT license

***

_This file was generated by [verb](https://github.com/assemble/verb) on January 26, 2015._

repository: jonschlinkert/fill-array

repo_name: jonschlinkert/fill-array


text:
# date_time_now

Shows how to use [xtd::date_time::now](https://gammasoft71.github.io/xtd/reference_guides/latest/classxtd_1_1date__time.html#ad94505e74efe9f353836901eda9230ed) property.

# Sources

[src/date_time_now.cpp](src/date_time_now.cpp)

[CMakeLists.txt](CMakeLists.txt)

# Build and run

Open "Command Prompt" or "Terminal". Navigate to the folder that contains the project and type the following:

```cmake
xtdc run
```

# Output

```
en_US
   Local date and time: Sun Jan  2 09:50:36 2022, local
   UTC date and time: Sun Jan  2 08:50:36 2022, utc

en_GB
   Local date and time: Sun  2 Jan 09:50:36 2022, local
   UTC date and time: Sun  2 Jan 08:50:36 2022, utc

fr_FR
   Local date and time: Dim  2 jan 09:50:36 2022, local
   UTC date and time: Dim  2 jan 08:50:36 2022, utc

de_DE
   Local date and time: So  2 Jan 09:50:36 2022, local
   UTC date and time: So  2 Jan 08:50:36 2022, utc

ru_RU
   Local date and time: воскресенье,  2 января 2022 г. 09:50:36, local
   UTC date and time: воскресенье,  2 января 2022 г. 08:50:36, utc
```


text:
# Overview

## Local Environment

| Tool                                         | Purpose                                                                       |
|----------------------------------------------|-------------------------------------------------------------------------------|
| [Gradle]( https://gradle.org)                | Used to run unit tests, package the JPI, and publish the plugin               |
| [Just](https://github.com/casey/just)        | A task runner. Used here to automate common commands used during development. |
| [Docker](https://www.docker.com/get-started) | Used to build the documentation for local preview                             |

## Learn More

| Topic                                         | Description                                                     |
|-----------------------------------------------|-----------------------------------------------------------------|
| [Running Tests](./running-tests.md)           | Learn how to run JTE's test suite                               |
| [Building the Plugin](./building.md)          | Learn how to build the JTE JPI                                  |
| [Linting](./linting.md)                       | Learn about JTE's code linting                                  |
| [Running A Local Jenkins](./local-jenkins.md) | Learn how to run a local Jenkins for manual integration testing |
| [Publishing A Release](releasing.md)          | Learn how to publish a JTE release                              |

repository: hosnify/templating-engine-plugin

repo_name: hosnify/templating-engine-plugin


text:
# Contributing to Surfliner

We would love your help to make Surfliner products better.

By participating in this project, you agree to abide by the [UC Principles of
Community][principles].

## Overview

### Project Structure

The Surfliner project is structured as a monorepo. If this is a new
concept to you, please read the [monorepo documentation][monorepo] as well as
this [comparison of monorepo versus multirepo][mono-vs-multi] configuration.

This results in a _project_ which we call Surfliner, and multiple _products_
which will live in the monorepo. Examples of _products_ are `starlight` and
`lark`.

Please note the difference between our use of _project_ and _product_ as we use
this language throughout our documentation.

### Branching Strategy

We are using a [trunk-based][trunk] branching strategy. In short, this means we
have a running `master` branch, `feature` branches for new work, and tagged
releases.

If you are coming from a [gitflow][gitflow] strategy, you'll note that your
feature branches will always merge back into `master` as opposed to `develop`.

## Contributing Tasks

* Reporting Issues
* Making Changes
* Documenting Code
* Committing Changes
* Submitting Changes
* Reviewing and Merging Changes

### Reporting Issues

If you would like to submit a request for a new feature, or a change to an
existing feature of a Surfliner product, we ask that you submit that request to
our [Aha! instance][aha].

If you are reporting a bug, or are a developer or stakeholder working directly
on a Sprint, you may create issues in GitLab as needed.

If you create a ticket directly in GitLab, please make sure you add a
[label][labels] for the product the ticket is related to. For example,
`starlight` or `lark`.

### Making Changes

If you are not a Surfliner team member, you should fork the repository.

* Create a topic branch from master `git branch feature/my-feature master`
* Checkout your new branch `git checkout feature/my-feature`
* Setup your development environment as documented for the project
* Run the test suite to confirm you have a working starting point
* Make sure you have added test coverage and documentation for your changes
* Run the _whole_ test suite to ensure nothing has been accidentally broken

### Documenting Code

* All new public methods, modules, and classes should include inline documentation in [YARD](http://yardoc.org/).
  * Documentation should seek to answer the question "why does this code exist?"
* Document private / protected methods as desired.
* If you are working in a file with no prior documentation, do try to document as you gain understanding of the code.
  * If you don't know exactly what a bit of code does, it is extra likely that it needs to be documented. Take a stab at it and ask for feedback in your merge request. You can use the 'Blame' button in GitLab to identify the original developer of the code and @mention them in your comment.
  * This work greatly increases the usability of the code base and supports the on-ramping of new committers.
  * We will all be understanding of one another's time constraints in this area.
* [Getting started with YARD](http://www.rubydoc.info/gems/yard/file/docs/GettingStarted.md)

Here is a basic example of a documented method using YARD:
```ruby
# Converts the object into textual markup given a specific format.
#
# @param format [Symbol] the format type, `:text` or `:html`
# @return [String] the object converted into the expected format.
def to_format(format = :html)
  # format the object
end
```

### Committing Code

* Make commits that are logical and representative of a complete chunk of work.
* See ["How to Write a Git Commit Message"][commit] by Chris Beams
* Use commit prefixes for the product you are working on. Example: `git commit
  -m "starlight: add missing indexing documentation"`
* If your commit will fix or close an existing issue in GitLab, you can
  reference the issue number in the commit message. Example: `Fixes #21`. See
the [GitLab automatic issue closing page][issue-closing] for more information
and examples.
* Consider creating a [default commit template][commit-template] to make this
  process easier for you.
* Make sure you have added the necessary tests for your changes.
* Run _all_ the tests to assure nothing else was accidentally broken.
* When you are ready to submit a merge request

### Submitting Changes

If you are coming from primarily working in GitHub, one difference to note with
GitLab is that *Pull Requests* are now called *Merge Requests*, but they are
functionally the same.

Please read the following GitLab documentation to familiarize yourself with the
process of creating and managing a merge request:

* [How to create a merge request][merge]
* [Merge requests overview][merge-overview]

Checklist:
* Make sure your branch is up to date with `master`
    * `git checkout master`
    * `git pull --rebase`
    * `git checkout <your-branch>`
    * `git rebase master`
    * It is a good idea to run your tests again.
* If you have multiple commits in your branch, consider whether squashing some
  of those commits together would improve their logical grouping. See [Squashing
commits with rebase][rebase] for more information.

### Reviewing and Merging Changes

We are using GitLab's [AutoDevOps CI/CD platform][devops] for running a variety
of automated checks. A few of these checks will be required to pass in order for
a merge request to be reviewed:

* Build
* Lint
* Test

When all of the required checks pass, then any of the active _product_ team
members may review and merge the code.

We **require** at least one _product_ team member approve the merge request,
though if there are specific people on the team you would like to review your
merge request, such as domain experts, UI/UX contributors, of members of other
_product_ teams, feel free to `@mention` or add them as an Assignee.

See the [Merge Request][merge] documentation for more details on how to assign
someone to review your MR.

It is a goal of the project to not let more than 24 hours go by without a new
Merge Request receiving a review from at least one _product_ team member. This
helps keep the cadence of code submission and review quick enough that Merge
Requests quickly end up in `master` and deployed. If you have not received a
review on your MR within this time frame, please reference the MR during daily
stand up and request a review, if you have not already done so via the user
interface as described above.

#### Things to Consider When Reviewing

First, the person contributing the code is putting themselves out there. Be mindful of what you say in a review.

* Ask clarifying questions
* State your understanding and expectations
* Provide example code or alternate solutions, and explain why

This is your chance for a mentoring moment of another developer. Take time to give an honest and thorough review of what has changed. Things to consider:

  * Does the commit message explain what is going on?
  * Does the code changes have tests? _Not all changes need new tests, some changes are refactorings_
  * Do new or changed methods, modules, and classes have documentation?
  * Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
  * Does the description of the new/changed specs match your understanding of what the spec is doing?
  * Did the CI pipeline complete successfully?

If you are uncertain about the proposed changes in the Merge Request, please
provide this very valuable feedback by asking questions. It benefits the entire
team if Merge Requests are used as an opportunity to share knowledge. It is a
goal of the project to try and minimize silos of expertise. Please feel
comfortable using a Merge Request review as an opportunity to help us all meet
that goal!

If, however, you find after this dialog that you are uncertain in approving the
Merge Request, feel free to bring other contributors into the conversation by
assigning them as a reviewer or mentioning the issue in Slack or daily stand up.

#### Code Style

We attempt to follow consistent code styles throughout the project. Information about our style guide is at
[`.styles`][styles], and normally takes the form of configuration for automated linters. Suggestions for changes
to the style guide are welcome as _stand-alone_ merge requests suggesting the appropriate changes. Please describe
the motivation for the change in your commit message.

For Ruby, we have a project-wide `rubocop` configuration at [`.styles/rubocop_surfliner.yml`][rubocop].
To run automated style checks, do `bundle exec rubocop` from any product directory.

For Shell scripts, we use [Shellcheck][shellcheck].
Shellcheck can be integrated into your editor, or ran directly on the command line with the `shellcheck` binary.

[aha]: https://ucsurfliner.ideas.aha.io/
[commit-template]: https://thoughtbot.com/blog/better-commit-messages-with-a-gitmessage-template
[commit]: https://chris.beams.io/posts/git-commit/
[devops]: https://docs.gitlab.com/ee/topics/autodevops/
[gitflow]: https://nvie.com/posts/a-successful-git-branching-model/
[issue-closing]: https://docs.gitlab.com/ee/user/project/issues/automatic_issue_closing.html
[labels]: https://docs.gitlab.com/ee/user/project/labels.html#creating-labels
[merge-overview]: https://docs.gitlab.com/ee/user/project/merge_requests/index.html
[merge]: https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html
[mono-vs-multi]: http://www.gigamonkeys.com/mono-vs-multi/
[monorepo]: https://trunkbaseddevelopment.com/monorepos/
[principles]: https://ucnet.universityofcalifornia.edu/working-at-uc/our-values/principles-of-community.html
[rebase]: https://docs.gitlab.com/ee/workflow/gitlab_flow.html#squashing-commits-with-rebase
[rubocop]: ./.styles/rubocop_surfliner.yml
[shellcheck]: https://www.shellcheck.net/
[styles]: ./.styles
[trunk]: https://trunkbaseddevelopment.com/

repository: surfliner/surfliner-mirror

gha_language: CSS

repo_name: surfliner/surfliner-mirror


text:
# TJCTF 2020

## Difficult Decryption

> 100
>
> We intercepted some communication between two VERY important people, named Alice and Bob. Can you figure out what the encoded message is?
>
> Written by saisree
>
> [intercepted.txt](intercepted.txt)

Tags: _crypto_ _discrete-log_

## Summary

Weak crypto, nothing more than a discrete log solve.

## Analysis

From [intercepted.txt](intercepted.txt):

```
Alice:

Modulus:<PHONE_NUMBER>03692092263984889813697016406
Base: 5
Base ^ A % Modulus:<PHONE_NUMBER>03461569340683568996607232345
-----
Bob:

Here's my Base ^ B % Modulus:<PHONE_NUMBER>3702450233149901853450417505
-----
Alice:

Here's the encoded message:
12259991521844666821961395299843462461536060465691388049371797540470

I encoded it using this Python command:

message ^ (pow(your_key, A,modulus))

Your_key is Base ^ B % Modulus.
After you decode the message, it will be a decimal number. Convert it to hex.
You know what to do after that.
```

To decrypt, just provide `A` to `message ^ (pow(your_key, A,
modulus))` where `your_key` is provided from Bob as `76405255723702450233149901853450417505`.

To get `A`, just use your favorite discrete log function.

## Solve

```python
#!/usr/bin/python3

from sympy.ntheory.residue_ntheory import discrete_log

M=491988559103692092263984889813697016406
P=232042342203461569340683568996607232345
B=5
A=discrete_log(M,P,B)
message =<PHONE_NUMBER>1844666821961395299843462461536060465691388049371797540470
bobkey =<PHONE_NUMBER>3702450233149901853450417505

text = bytes.fromhex(hex(pow(bobkey, A, M) ^ message)[2:]).decode('ASCII')
print(text)
```

One-liner, if you're into brevity:

```
python3 -c "print(bytes.fromhex(hex(pow(76405255723702450233149901853450417505,__import__('sympy.ntheory.residue_ntheory').discrete_log(491988559103692092263984889813697016406,232042342203461569340683568996607232345,5),491988559103692092263984889813697016406) ^<PHONE_NUMBER>1844666821961395299843462461536060465691388049371797540470)[2:]).decode('ASCII'))"
```

This runs in less than one second and outputs:

```
tjctf{Ali3ns_1iv3_am0ng_us!}
```

repository: datajerk/ctf-write-ups

repo_name: datajerk/ctf-write-ups


text:
# IW-Spring-17
WellVision -- Independent work Spring 17

Abstract:

WellVision is a software a tool for researchers and policymakers to apply various analyses to
existing oil and gas well databases. WellVision was built as a modular, plug-and-play framework
that supports the development of analysis modules in any language. Well data is stored in a local
database and accessed through a standardized data model. Two initial modules for estimating
methane emissions were developed as the initial WellVision analyses. These analyses were used to
create emissions estimates for well data sets from West Virginia and Pennsylvania.


text:
---
layout: post
permalink: /fireshell-fiercely-quick-front-end-boilerplate-and-workflows/
title: FireShell, fiercely quick front-end boilerplate and workflows
path: 2013-09-15-fireshell-fiercely-quick-front-end-boilerplate-and-workflows.md
tags:
- Library
- Opinion
- JavaScript
---

Built for the modern developer. For teams and the individual, encouraging a better workflow. JavaScript task running, build processes, autominification and file concatenation, wrapped with an enhanced HTML5 boilerplated framework.

FireShell is something I've been working on over the last few weeks, but is the result of years worth of experience and wanting to enhance the workflow for teams and front-end development. FireShell is one little package that does exactly this.

  Visit Site
  Download
  Fork

check out the video below for a full overview on getting started with FireShell, or check out the site.

The main three aspects of FireShell include:

### HTML5 Boilerplated
A cutting edge take on the HTML5 boilerplate with some HTML5 semantics and WAI-ARIA roles for baseline semantic markup and web accessibility.

### Sass OOCSS setup
CSS structure for small projects and scaling big, a fantastic setup to get your Object-Orientated CSS scaling. Ships with fully adaptive folder hierarchies.

### Grunt.js
Compiling Sass/SCSS, concatenating JavaScript files, connecting to a localhost server and live file reloads and injection. Auto-minification for production.

### Features
* HTML5 framework, WAI-ARIA roles and HTML5 semantics
* Baseline HTML5 features, DNS prefetching, responsive meta
* Encourages one-file CSS/JS in the view (HTML) for performance
* Includes jQuery CDN and relative fallback
* Includes Modernizr and HTML5 Shiv
* Google Universal Analytics snippet
* Open source workflow with Grunt.js running on Node.js
* A grunt.command file for double-click command-line execution
* Automatic Grunt dependency installation, directory relocation and grunt tasks
* Dynamically appended copyright for JS/CSS
* Livereloading the browser and file injection upon changes
* Annotated Gruntfile.js for extending
* Built-in build script for auto-minification of CSS and JavaScript files for production
* Pre-setup Sass/SCSS files and folders for baseline project structure and imports
* Includes .editorconfig for consistent coding styles in IDEs
* Standard .gitignore to ignore minified files and standard ignorables such as .DS_Store
* JSHint .jshintrc file for configuring JavaScript linting
* No superfluous code comments


text:
# keepass2-passwordmodifiedcolumn

**KeePass 2.x plugin to show the time a password was last modified.**

**This functionality is now built into KeePass as of 2.36, however this is maintained for users that cannot upgrade.**

**Download plgx from [here](https://github.com/andrew-schofield/keepass2-passwordmodifiedcolumn/raw/master/PasswordModifiedColumn.plgx).**

**Mono users can download the dlls from [here](https://github.com/andrew-schofield/keepass2-passwordmodifiedcolumn/tree/master/mono).**

## Usage

* Enable the custom column. If history entries are available for an entry they will be used to calculated a password last modified date.

## How it works

Unfortunately KeePass doesn't keep track of when individual fields are modified in an entry, it just stores an overall `Last Modified` date for the whole entry. This poses a problem if you want to work out when a password was last changed.

Luckily KeePass stores history entries whenever a modification is made. These can be used to work out when a password was last changed by comparing the passwords in the history entries.

* If there are no history entries we have to assume that the `Last Modified ` date of the entry is the last time the password was changed.
* If the password is the same in all the history entries and the current entry then we assume the modification date of the earliest history entry is the last time the password was changed.
* Otherwise we start from the current entry and work backwards through the history looking for the first time the password changed and use the later of two entries which have different passwords.

This should give accurate results if you maintain the history for each entry, however if you prune the history it will only be accurate as far back as there is history data.

## Notes

* Sorting does not work currently due to this not being available to custom columns.

## Donate

keepass2-passwordmodifiedcolumn is developed entirely in my own time. If you wish to support development you can donate via paypal here.

[![Donate](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=S2DVYTS47PX4S)

## Copyright

© 2017 Andrew Schofield


text:
Warning!
========

This repository is currently not maintained and after knowing much better the OpenEXR format, there is a lot of missing features that shall have been supported:
- No support for displayWindow
- No support for chromaticities

If you want to use the proper tool, I recommend using OpenImageIO tools: https://openimageio.readthedocs.io/en/v<IP_ADDRESS>/oiiotool.html

So, take this repo with a grain of salt, an example on how to read OpenEXR images using the OpenEXR library, not as the state of the art.

OpenEXR converter
=================

These tools are simple utilities to convert images files from OpenEXR to PNG 8bit sRGB files and TIFF to OpenEXR.

Checking out the repository
===========================

```
git clone git@github.com:yama-chan/openexr-converter.git
git submodule update --init --recursive
```

Compilation
===========

Dependencies
------------
You need to install OpenEXR to compile the tool:
* libopenexr
* libtiff

### Ubuntu 16.04 LTS

```
sudo apt install libopenexr-dev libtiff5-dev
```

### Arch Linux

```
sudo pacman -S openexr libtiff
```

### Compilation
In order to compile in a folder build the tool, do:

```
mkdir build
cd build
cmake ..
make
```

After compilation,
* `exr-png` will be created in `src/exr-png` folder.
* `tiff-exr` will be created in `src/tiff-exr` folder.

To install, do:

```
sudo make install
```

Usage
=====

OpenEXR to PNG
--------------

```
exr-png  [-g <real>] [-a] -o <string> -i <string> [--] [--version]
		 [-h]
```

Where:

```
   -g <real>,  --gamma <real>
     Set the gamma correction (default sRGB)

   -a,  --ignore-alpha
     Ignore alpha channel

   -o <string>,  --output <string>
     (required)  Set file to save to

   -i <string>,  --input <string>
     (required)  Set file to convert

   --,  --ignore_rest
     Ignores the rest of the labeled arguments following this flag.

   --version
     Displays version information and exits.

   -h,  --help
     Displays usage information and exits.
```

TIFF to OpenEXR
---------------

```
tiff-exr <input_tiff_file> <output_exr_file>
```

repository: afichet/openexr-converter

repo_name: afichet/openexr-converter


text:
## Build a custom version

### Dependencies for building a custom version of iOSBadge:

* [Ruby](http://www.ruby-lang.org/en/downloads/) ( [Ruby version manager](https://rvm.io/rvm/install/) )
* [Node.js](http://nodejs.org/) ( [Node version manager](https://github.com/creationix/nvm) )
* [Compass](http://compass-style.org/) ( `gem install compass` ) *
* [Grunt](http://gruntjs.com/) ( `npm install grunt -g` ) *

\* add `sudo` in front of the command if needed

### How to build & contribute

1. Make sure that you have [Grunt](http://gruntjs.com/) installed.
2. In terminal move to iOSBadge folder and run `npm install` to install all dependencies.
3. Make all Javascript changes in Coffeescript file(s), CSS changes in SCSS file(s). Make your changes only to files located inside the `src` folder.
4. run `grunt` to build iOSBadge
5. Make sure that all changes are valid and open a pull request

You can use the `iosbadge.scss` file located in `src/iosbadge/scss` folder to add your custom themes and sizes.

All Javascript changes should be written in Coffeescript to `iosbadge.coffee` file located in `src/iosbadge/coffee` folder.

Run `grunt` after your changes to build your custom version.

### Building and running unit tests

Source files for jasmine tests can be found inside `src/test` folder.

You can build and run unit tests by running `grunt test` in the plugin folder in terminal.

### API documentation

Plugin API documentation can be found inside the `docs` folder.

repository: akennedy/iOSBadge

repo_name: akennedy/iOSBadge


text:
# Skin Sense: A Skin Cancer Detection App

![Branch master](https://img.shields.io/badge/branch-master-brightgreen.svg?style=flat-square)

## Problem Statement
Skin Cancer is the most common cancer and is often
ignored by people at an early stage. An estimated
178,560 cases of melanoma will be diagnosed in the
U.S. in 2018. If melanoma is recognized and treated
early, it is almost always curable, but if it is not, the
cancer can advance and spread to other parts of the
body, where it becomes hard to treat and can be fatal.

## Solution
Melanoma, if treated early, could be cured. Our
application, with 84.7% accuracy is capable
enough to classify Melanoma skin cancer even at
an early stage remotly. One can easily classify
the type of cancer as Melanoma or not and can
take actions accordingly.

## Technology Stack
+ TensorFlow - Google's DeepLearning
Framework

+ Model Architecture Inception v3
(mobilenet_100_224)

+ Android Studio

+ Google Maps API

+ Firebase - Google's Mobile and Web App
Development Framework

## Features
+ Offline data storage for statistical analysis and expertise
consultancy

+ Offline Classification

+ Google authentication with email verification

+ In app Hospital finder

## Screenshots

## Special Mentions
Stood first among the 70 teams in Hitsathon V2.0 (Hindustan University Hackathon)

## Team Members:
Team Scary Bugs:

+ [Tanay Toshniwal](https://github.com/tanaytoshniwal)
+ [Arnab Ray](https://github.com/arnabuchiha)
+ [Ritvik Jain](https://github.com/Ritvikjain)
+ [Rajnish Raj](https://github.com/ShadowRajnsih)

Show some love ❤ and Star ⭐ the Repository to support the project.

repository: arnabuchiha/SkinSense

repo_name: arnabuchiha/SkinSense


text:
# kindle-pdf-scraper
Node.js/Puppeteer scraper able to download given book from Kindle Cloud Reader as PDF.

Scraper performs following actions in Kindle Cloud Reader:
- log into the app
- set page layout in the app
- press next-page button for each page and download each page as PDF with `page.pdf` interface

This process was implemented in 02/2021. It is possible that this implementation will need to be adjusted in the future.

Due to lack of Node.js PDF libraries the merging was implemented with Python 3/PyPDF2.

___

## Prerequisities
- Node.js, npm cli
- Puppeteer ^7.0.1 with built-in Chromium
- argparse ^2.0.1
- Python 3, PyPDF2 package (for PDF merging)

___

## Usage
`npm install`

`node scrape.js -url "https://read.amazon.com/?asin=XXXXXXXXXX" -email<EMAIL_ADDRESS>-pwd "d7nkb1!3423j" -pages 200 -path "./my-book/" -fs 0 -pm 1 -pc "white"`

```
optional arguments:
  -h, --help            show this help message and exit
  -url URL              URL of given book in Kindle Cloud Reader (required)
  -email EMAIL          Amazon login email (required)
  -pwd PASSWORD         Amazon login password (required)
  -pages NO. PAGES      Number of pages (from beginning) to scrape (required)
  -path SAVE PATH       Absolute/relative path to save PDF files (required)
  -fs [FONTSIZE], --fontSize [FONTSIZE]
                        Font size of text 0/1/2/3/4 (default 2)
  -pm [PAGEMARGIN], --pageMargin [PAGEMARGIN]
                        PDF page margins 0/1/2/3/4 (default 1)
  -pc [PAGECOLOR], --pageColor [PAGECOLOR]
                        PDF page color white/sepia/black (default white)
 ```

 `python merge.py -path ./my-book/ -fr 1 -to 200 -name final.pdf -l 200`

 ```
 usage: merge.py [-h] -path PATH -fr FR -to TO -name NAME [-l [LEFT]] [-r [RIGHT]] [-t [TOP]] [-b [BOTTOM]]

Merge given scraped PDF pages into single PDF book

optional arguments:
  -h, --help            show this help message and exit
  -path PATH            Path to scraped PDF pages with name pattern \d+/pdf (REQUIRED)
  -fr FR                Number of first PDF page to merge (REQUIRED)
  -to TO                Number of last PDF page to merge (REQUIRED)
  -name NAME            Name of final PDF file (REQUIRED)
  -l [LEFT], --left [LEFT]
                        Crop left margin of all pages (px) (default 0)
  -r [RIGHT], --right [RIGHT]
                        Crop right margin of all pages (px) (default 0)
  -t [TOP], --top [TOP]
                        Crop top margin of all pages (px) (default 0)
  -b [BOTTOM], --bottom [BOTTOM]
                        Crop bottom margin of all pages (px) (default 0)
 ```

 ___

 ## Recommendations
 Kindle Cloud Reader makes it difficult to render text on PDF pages. For that reason it is recommended to set up PDF layout first. Start with changing these parameters:
 - font size (-fs) and page margin (-pm) arguments
 - browser viewport : change `defaultViewport` values of `chromeOptions` object in the constructor

 If PDF layout is still not sufficient enough, continue with changing `printOptions` object in the constructor.

 ___

 ## Known issues
 - browser sometimes looses track of `iframe` with page content (`this.sel.iframe` selector). It was not possible to reproduce the error

repository: uelel/kindle-pdf-scraper

repo_name: uelel/kindle-pdf-scraper


text:
# tick-collections

`TickMap` & `TickSet` are subclasses of `Map` and `Set` whose contents are cleared every tick. Useful for eg memoization based on highly volatile data.

Their interfaces are identical to the classes they extend. Their only practical difference is to schedule an immediate `clear` whenever they receive state, such that they will be empty again at the next tick.

### Install

#### [from npm](https://www.npmjs.com/package/tick-collections)

```sh
npm i tick-collections
```

#### or grab the UMD module from a CDN

```html
<script src="https://cdn.rawgit.com/barneycarroll/tick-collections/1.0.2/umd.js"></script>
```

### Import

#### as ES6 modules

```javascript
import { TickMap } from 'tick-collections'
```

The NPM package caters for automatic ES6 module resolution via `jsnext:main` & `module`. If you're not using a compliant ES6 module resolver (Rollup or Webpack, at the time of writing), simply point to the ES6 source file explicitly: `import { TickMap } from 'tick-collections/es6'`.

#### or using your favourite UMD method

```javascript
const { Map } = require( 'tick-collections' ) // CommonJS!

define( [ 'tick-collections' ], ( { Set } ) => { /**/ } ) // AMD!

true === ( window.Map === Map ) // Browser!
```

This package depends upon compliant native implementations of `class`, `Map` & `Set` - without `class` extension, neither native or any of the popular collection shims can be robustly or uniformly patched. `Promise.resolve` is used internally to clear collections on subsequent ticks of state being set - the internals have no opinion on whether that's a shim or not but obviously if you cannot depend on a runtime guarantee of next tick clearing if the runtime is incapable of reliably queuing tasks to execute in the next tick ;)

repository: barneycarroll/tick-collections

repo_name: barneycarroll/tick-collections


text:
# Cookies

To make this site work properly, we sometimes place small data files called cookies on your device. Most big websites do this too.

### What are cookies?

A cookie is a small text file that a website saves on your computer or mobile device when you visit the site. It enables the website to remember your actions and preferences (such as login, language, font size and other display preferences) over a period of time, so you don’t have to keep re-entering them whenever you come back to the site or browse from one page to another.

### How do we use cookies?

We use cookies only to determine whether or not you are logged into your user account. These cookies are deleted when you end your browser session, unless you check "Remember me" when you log in -- if you do that, we will create a cookie that identifies you for the next two weeks and keeps you from having to log in again.

### How to control cookies

You can control and/or delete cookies as you wish – for details, see <https://aboutcookies.org>. You can delete all cookies that are already on your computer and you can set most browsers to prevent them from being placed. If you do this, however, you may have to manually adjust some preferences every time you visit a site and some services and functionalities may not work.

repository: mdheller/rletters

gha_license_id: NOASSERTION

repo_name: mdheller/rletters


text:
# airbnb-ct

AirBnB analysis - Cape Town, South Africa

    This notebook is using data from Inside Airbnb. The goal is to investigate the data and find out more information about    the AirBnb landscape in Cape Town where I live.

    View Medium Post

## Table of Contents

* [About the Project](#about-the-project)
  * [Built With](#built-with)
* [Getting Started](#getting-started)
  * [Prerequisites](#prerequisites)
* [Usage](#usage)
* [Contributing](#contributing)
* [License](#license)
* [Contact](#contact)
* [Acknowledgements](#acknowledgements)

## About The Project

Airbnb is very popular and of course, in Cape Town we often wonder about the density of listings because its very expensive to rent as a local. So I decided to check out this data and investigate the foundational aspects of this landscape.

Some key questions / areas of investigation I hade were:

(1) Listings Dataset:
What does the price distribution look like in Cape Town & for specific Areas?
What is the difference in pricing between the property types?
What is the difference in pricing between areas / wards ?
How many hosts have multiple listings and where are they?
What is the difference between superhosts and normal hosts pricing?

(2) Reviews Dataset:
What are the reviews like for Cape Town hosts, good or bad?
How does demand fluctuate for AirBnb in Cape Town?
Is there the expected seasonality with seasons?
Is there higher demand with less seasonality in certain areas?

(3) Price Prediction:
As a new host, if you try to charge above market price for a listing, then renters will select more affordable alternatives which are similar. If you set price too low, you will miss out on potential revenue as well.

The k nearest neighbours results were not incredible, but lay a decent foundation to build upon.

It would be great to extend this to specific areas in the data, and also build out some more powerful models with more features.

Also, there is a Boat & Cave listing in Cape Town that was found!

### Built With

* [AWS Sagemaker Notebook](https://aws.amazon.com/sagemaker/)
* [Pandas](https://pandas.pydata.org/)
* [Numpy](https://numpy.org/)
* [Seaborn](https://seaborn.pydata.org/)
* [sklearn](https://scikit-learn.org/stable/)
* [python](https://www.python.org/download/releases/3.0/)

## Getting Started

To get a local copy up and running follow these simple example steps.
* Go fetch the listings and reviews datasets (for the city of your choice) from [insideairbnb](http://insideairbnb.com/get-the-data.html)
* [Cape Town Reviews Data](http://data.insideairbnb.com/south-africa/wc/cape-town/2020-04-26/visualisations/reviews.csv)
* [Cape Town Listings Data] (http://data.insideairbnb.com/south-africa/wc/cape-town/2020-04-26/visualisations/listings.csv)
* Download the jupyter notebook from this repository, connect up the datasets loading cell to wherever you host your data ( I hosted mine on a s3 bucket in amazon)
* [Notebook Link](https://github.com/forbesg-repo/airbnb-ct/blob/master/airbnb-ct.ipynb)
* Run through the notebook and have fun!

### Prerequisites

Knowledge of python 3 and other libraries listed above.

## Usage

I wrote a post on medium about my findings, you can read that here:

* [Medium Article](https://medium.com/@forbesg/listing-an-airbnb-in-cape-town-this-analysis-will-make-you-understand-the-landscape-3a928862b931)

## Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are **greatly appreciated**.

1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3.  Push to the Branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request

## License

Distributed under the MIT License. See `LICENSE` for more information.

## Contact

Gareth Forbes -<EMAIL_ADDRESS>
Project Link: [Medium](https://medium.com/@forbesg/listing-an-airbnb-in-cape-town-this-analysis-will-make-you-understand-the-landscape-3a928862b931)

## Acknowledgements
* [Jeff Hale](https://towardsdatascience.com/scale-standardize-or-normalize-with-scikit-learn-6ccc7d176a02)
* [Rahul Gupta](https://medium.com/analytics-vidhya/identifying-most-important-amenities-affecting-the-price-of-airbnb-3a34af7e4a38)
* [Ankit Peshin, Sarang Gupta, Ankita Agrawal](http://www.columbia.edu/~sg3637/airbnb_final_analysis.html)

repository: forbesg-repo/airbnb-ct

repo_name: forbesg-repo/airbnb-ct


text:
# Change Log

## [1.1.1] - 2023-05-30

### Changed

- Loosen `seg_seg` dependency requirement to include `0.1.x` and `1.x`

## [1.1.0] - 2022-05-02

### Added

- Add Vincenty's Inverse Formula Distance (thanks @Cameron-Kurth)

## [1.0.0] - 2021-11-24

### Added

- `project/3` - Projects a given distance in a given direction away from a point
- `angle_to/2` - Returns direction from one point to another
- `min_coterminal_angle/1` - Coterminal angle closest to 0 for the given angle
- `min_positive_coterminal_angle/1` - Smallest positive coterminal angle for the given angle
- `angular_difference/2` - Angular difference between two angles

### Changed

- Update CI to use Github Actions instead of travis-ci
- Update dependencies

repository: pkinney/distance

gha_language: Elixir

repo_name: pkinney/distance


text:
# Getting started

These sections should provide you with all the information needed to install the `@polkadot/api` package, understand the structure of the interfaces and allow you to start using it. For existing users this really should be titled "Things I wish I knew before I started using the api" - it really aims to close the gap to allow anybody to get to grips with using the packages.

## What this is not

This is not line-by-line documentation of all the existing function calls available, nor it is tied to a specific chain. (Although the examples do refer to the base Polkadot & Substrate chains). There will be some things in the API that are probably not covered, which brings us to the next point...

## Help us help others

If you spot gaps in the information provided, or are uncertain about any specific area, please do [log an issue](https://github.com/polkadot-js/api/issues) or if you are that way inclined, make a pull-request. We really want to have good documentation in these areas and allow people to be productive right from the start.

## Ready? Steady? Go!

If you already have a good grasp on the API and are just looking for a specific answer, you may want to take a look at the [Frequently Asked Questions](FAQ.md). With all that said, let's get started... [What should be installed, and how should we do it?](install.md)

repository: usetech-llc/api

repo_name: usetech-llc/api


text:
# Repository Technical Specs

These specifications describe technical aspects about this app. In particular, they discuss how the repository is organized, technical standards, etc.

## Technical overview

This app is built using a MERN stack: [Express.js](https://expressjs.com/) on [Node.js](https://nodejs.org), [MongoDB](https://www.mongodb.com/) (via [Mongoose](http://mongoosejs.com/)), and [React](https://facebook.github.io/react/).

We are running our apps on Google Cloud Platform, using Google App Engine. Builds and pull requests are tested and deployed via Travis.

## Some technical comments

+ This project is open to people from a variety of technical levels! So don't be afraid to try to contribute and, if you have questions, ask for help. (Also, React is not as complicated as it might seem at first!)

## Other technical information

+ [The structure of the database](DATABASE.md)
+ [The API backend](API.md)

### Notes for non-experts

+ .jsx are just javascript files which also allow React components (things that look like -- but are not quite -- standard html). If you know javascript, you should be able to understand them!

+ Javascript is fairly straightforward syntactically. However, one of the trickiest parts is that it is run typically asynchronously, which can be confusing. Understanding that makes a big difference in being able to read and write javascript effectively.

+ To learn React, if you know javascript, I suggest you go to the Facebook documents. Start with (the tutorial)[https://facebook.github.io/react/tutorial/tutorial.html] and then do (the Quickstart)[https://facebook.github.io/react/docs/installation.html]. These give a good overview of the framework.

## Repository organization

### Sources

The repository organization is as follows:

```
├──server/                      the Express backend for serving
│  │                            static files and servicing
│  │                            the API
│  ├──routes/                   API routes
│  │  ├── index.js              main routes
│  │  ├── ...
│  ├──models/                   data models for API
│  │  ├── db.js                 connect to the mongo DB
│  │  ├── ...
│  ├──controllers/              backend API
│  │  ├── ...
│  ├──common/                   support files used in multiple
│  │  ├── ...
sections
│  │  ├── ...
│  ├──server.js                 starting point for backend
│  ├──config-server.json        server config file; see below
├──src/                         client files for React
│  ├──App.jsx                   client starting point
│  ├──credentials-client.jsx    hold client credentials
│  ├── ...
├──static/                      static files
│  ├──index.html                shell for the client for React
│  ├── ...
├──scripts/                     scripts, other content not intended to be run on the server
│  ├── ...
```

### Compiled code

The following additional files are generated by compiling the source:
```
├── dist-server/          transpiled version of server/
│   ├── ...
├── dist-scripts/         transpiled version of scripts/
│   ├── ...
├── static/
│   ├── app.bundle.js     compiled client code from src
│   ├── vendor.bundle.js  compiled client code from node_modules
```

## Conventions

### REST API structure

+ For rest API endpoints, use spinal case, i.e. "this-style", not "thisStyle" or "this_style".

### Javascript syntax

+ Use ES2015 syntax on both the server and client-side (including modules). Babel will be used to transpile code for wider compatibility with older browsers

### React

+ React component class should be their own files

### JSON

We will (tentatively) follow the [Google JSON Style Guide](https://google.github.io/styleguide/jsoncstyleguide.xml).

### Linting

The code is linted via ESLint to follow the [Airbnb javascript guide](https://github.com/airbnb/javascript). For contributors: running eslint (after you have run `npm install` in the main directory to install dependencies) is as easy as running `npm run lint` in the main directory.

### Variable/property names

+ Variables/properties holding Mongo ObjectID's should end in "Id"; e.g. a variable holding the ObjectID for a User document could be called `userId`. Other variables should instead end in "IdOt" (i.e. other ID); e.g., the variable that holds the Facebook ID of the user is called `userIdOt` not `userId` or `fBUserId`.

### State names

In the code, state names will be given as the 2-letter lowercase postal abbreviation

## Development

To develop the code base, do the following:

1. [Install mongodb](https://docs.mongodb.com/manual/administration/install-community/).
1. Follow [these Github instructions](https://help.github.com/articles/fork-a-repo/) to fork this repo to your account
1. In the repo directory, install the dependencies by running
    $ npm install
1. [Set up configuration variables](#configuration-variables)
1. Copy server/credentials-template.js to server/credentials.js and edit it. For example, try changing `'mongodb://'` to `'mongodb://localhost/atibroadcastapp'`.
1. Make sure mongo is running.
1. Start the app via:

    $ npm run dev-all

The app should automatically detect changes to your code and recompile. The development server will listen on port 8000.
1. Give your Google account the appropriate priveleges on the local install. To do this, first make sure that the file "dist-scripts/addUser.js" is executable by running `chmod -x dist-scripts/addUser.js`. Then, to add a user, run `dist-scripts/addUser.js LOGINEMAIL FIRSTNAME LASTNAME` for each user.

[Note that, to post message, you will first need to set a Facebook access token by running the "Update Access Token" option with the appoporiate Facebook user.]

### Configuration variables

The following configuration variables are recognized:

variable name | (R)equired or default value | description
---- | ---- | ----
port | 8080 | port on which server will be run
fb\_appsecretid | R | Facebook App secret
fb\_broadcastuserid | R | Facebook broadcast user ID
mongo\_connectionstring | R | connection string for mongo
cookiesecret | R | salt for cookies
google\_oauthsecret | R | Google client secret (currently not used)
google\_apikey | R | Google API key, used, e.g., for geolocation of groups
arcgis\_clientid | R | client ID for arcgis
arcgis\_clientsecret | R | client secret for arcgis
allowed\_states | null | which states will be allowed when refreshing groups. can be either an array of state abbreviation or JSON that parses to such an array. if null, all states are allowed.

*Note: config.js will automatically define the additional variable is_gae, which is true if the instance is run on GAE*

Note that all variables are lowercase and separate using underscores.

Because it is easiest to store configuration variables in different places in different environments, configuration variables are checked for in several places in the following order:
1. As argument (e.g. `node dist-server/server.js --port 40 --fb_appsecretid fjlj34`)
2. As an environmental variable
3. From the file server/config-server.json
4. From Google App Engine project metadata (if being run on Google App Engine)

gha_language: JavaScript


text:
# graphql-proxy-poc

The purpose of the code in this repository was to explore a means of accelerating the aggregation
of  gRPC services written in Java into a front facing GraphQL proxy for use within a React UI.
Complicating the work was an existing GraphQL server written in go that needed to continue resolving
the existing types. The solution also needed to allow for new data resolvers to be written directly in
Java.

## Contents

* `stub-org-service` is a made up gRPC service written in Java and only used for the purposes of
showing queries being forwarded and handled by an actual gRPC service.

* `proxy` is the actual GraphQL server implementation that attempts to solve the goals stated above.

## Approach

The gRPC integration was already part of a Google project, rejoiner.

The first approaches created a generic `PassthruDataFetcher` and then registered that on different
GraphQL types. While easy to understand, this approach would result in each instance of `PassthruDataFetcher`
calling the go GraphQL service since types could be loaded in parallel.

Pulling apart the query needed to happen at a lower level in the communication stack, namely before the
`graphql-java` library had mapped the query types into DataFetcher instances. Building a custom `QueryInvoker`
that leveraged the `Parser` and `AstPrinter` allowed me to determine which elements of the query were
handled by the go GraphQL server and which needed to be resolved locally. With that information, I was then
able to issue a new HTTP request to the go server async and allow the `graphql-java` server to resolve all
the internal bits.

Difficulty also occurs in merging the results back, specifically the `data` element. The best approach seems
to be turning the `data` Object into two Maps and then merging the maps into a single result.

## Findings

This approach does work but had a few downsides. First, it depends on the `Parser` class which is flagged
as an internal API. Each upgrade to `graphql-java` may require revisiting and fixing the custom `QueryInvoker`.
Additionally, the inbound request is parsed twice. Being able to provide filters to the query resolution process
or at least having callbacks would be a welcome design change to enable this kind of use case.

GraphQL fragments are also a pain to deal with. This highlights the need to maintain the custom `QueryInvoker` as
the GraphQL syntax is evolved and changed. Restricting the query syntax to basic types and avoiding constructs
like fragments and variables may also be used to avoid needing to maintain parity with the spec.

## Recommendation

Given that the go GraphQL server does not contain a large amount of data handling logic at this time, I would avoid
using a proxy in front of the server. Any GraphQL proxy is going to be aware of the schemas involved and have an
implementation aware of the language specification. It makes more sense to port the go code over to Java is one wishes
to leverage rejoiner for gluing the gRPC services together.

repository: dhable/graphql-proxy-poc

repo_name: dhable/graphql-proxy-poc


text:
# L-System

This page explores fractals defined with the [Lindenmayer](https://en.wikipedia.org/wiki/L-system) grammar.

The grammar is recursive and supports drawing, moving and turning .

Each step is named by a single letter
- "[" means save the drawing state ( location and current angle )
- "]" restores the state
- "-" means turn left
- "+" means turn right
- W, X, Y & Z move the current location (no drawing) forward based on the current angle, then recursively call steps W, X, Y or Z.
- A, B ... V draw a line forward at the current angle, then recursively call the step

Use the presets to see example grammars.

[Demo Website](https://rcorbish.ydns.eu/l-system/index.html)

### Warning

Do not set recursion depth too large, depending on the rules you define you may run out of memory.

## Licence

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or
distribute this software, either in source code form or as a compiled
binary, for any purpose, commercial or non-commercial, and by any
means.

In jurisdictions that recognize copyright laws, the author or authors
of this software dedicate any and all copyright interest in the
software to the public domain. We make this dedication for the benefit
of the public at large and to the detriment of our heirs and
successors. We intend this dedication to be an overt act of
relinquishment in perpetuity of all present and future rights to this
software under copyright law.

IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to <http://unlicense.org/>

license: Unlicense

repository: rcorbish/l-system

repo_name: rcorbish/l-system


text:
# QMK Toolbox

This is a collection of useful tools packaged into one app. This is a pretty recent development, but is looking to replace the QMK Flasher.

# Flashing

Supporting following bootloaders:
 - DFU (Atmel, LUFA) via dfu-programmer (http://dfu-programmer.github.io/)
 - Caterina (Arduino, Pro Micro) via avrdude (http://nongnu.org/avrdude/)
 - Halfkay (Teensy, Ergodox EZ) via teensy_loader_cli (https://pjrc.com/teensy/loader_cli.html)
 - STM32 (ARM) via dfu-util (http://dfu-util.sourceforge.net/)
 - BootloadHID (Atmel, ps2avrGB, CA66) via bootloadHID (https://www.obdev.at/products/vusb/bootloadhid.html)

If there's an interest in any others, they can be added if their commands are known.

# HID Listening

Also listens to HID ascii from usage page 0xFF31 (compatible with the hid_listen provided by PJRC) - connects automatically and to all sources available.

# Installation

## Dependencies

### Windows
When using the QMK Toolbox on Windows, please install the mandatory drivers first. You can get [the latest release here](https://github.com/qmk/qmk_driver_installer/releases)

### macOS
If you're using [homebrew](http://brew.sh/), you can use the following commands:

    brew tap osx-cross/avr
    brew tap PX4/homebrew-px4
    brew update
    brew install avr-gcc
    brew install dfu-programmer
    brew install gcc-arm-none-eabi
    brew install avrdude

## Download

A Windows and macOS version are available, and you can get [the latest release here](https://github.com/qmk/qmk_toolbox/releases).

For Homebrew users, it is also available as a Cask:

```
$ brew tap homebrew/cask-drivers
$ brew cask install qmk-toolbox
```


text:
# One Morning, You Wake Up and Find Yourself(sort of) in Charge
by [David Demaree (@ddemaree)](http://www.twitter.com/ddemaree)

|Cohort             |Age|
|-------------------|---|
|Entire US Workforce|42 |
|All programmers    |38 |
|StackOverflow users|30 |
|Google employees   |29 |

##### Most seem to leave exclusively 'programming' later, into a leadership/management role.

### Programming moves into:
* Mastery
* Mentorship
* Management

#### …all three of these seem to lead to being 'in charge'. Or…
* in control
* responsible

## Sort of 'in charge'.
* Power & Control: The least important part of things. Your ability to actually use this is incredibly constrained.
* Saying things worth following. Your words end up having much more impact.
* Being a force multiplier. You make others be more impactful, and what you do has a lot more impact.
* Helping good collaboration happen. You have to work at this, it takes real skill, but it's very valuable to…

#### Getting things done you can't get done alone.
* Going from *writing code* to **helping others write code.**

### Communication Patterns
* Have some empathy.(or fake it by asking questions)
* Apply metaphors liberally. lolol.
* KISS: DO IT EVERY TIME.
* Don't waste time. Don't provide more information than is needed. Think about *what the other person needs to hear*. You don't have to say everything right now, they can ask questions later. They'll ask followup questions if they need to. Say the minimum you need to say, they'll ask a question that'll force you to answer it precisely.

### Improve your support stack
* Testing tools & practices
* Development environment & tools
* developer interfaces to your app
* deployment process
* docs & style guides

### Giving Great Code Review
* Use pull requests
* Join the right conversations
* Uphold standards(constructively)
* Nitpick(appropriately)
* Above all, be helpful

### Beware of Process Overhead
* Collective Process Ownership
* Lots of Guidelines, Few Rules
* Garbage collection, not enforcement: This is not about enforcing compliance, it's about helping fixes and guiding, great for backlog decisions and cleaning. Be very permissive about what you let in on the backlog, but make course corrections
* Have tools follow process
* Meetings are Tools

### Remember it's not about you
* Separate taste from judgment
* Watch out for biases
* "Feeling" productive can be bullshit
* When in doubt, talk about it

## Investment strategies for your political capitol

### Get in on grown-up meetings
Get in on discussions with those above the engineers

### Ask lots of questions. (Remember the empathy?)
There's a lot related to your job that isn't your job and you otherwise wouldn't hear about.

### Learn to take the long view.
When you're at a higher level, when you're architecting the system, you need to think a bit ahead of your project just so you can mitigate and head off problems, especially since you know the direction of the business because you know things the Engineers don't.

### Learn to sell your ideas.
Talk about benefits, costs, etc.

### Learn to think bigger(but realistically)
Think up to the bound of what your team is capable of. Know your limits, but get to them too.

### When the time comes, ask for the job you're(probably) already doing
You've been coordinating the team, knowing your stuff, putting your opinion out and being right. So ask for it. Be proper about it, get the pay and title and position you deserve

## A leader's first responsibility is to make sure your team has whatever it needs to be AWESOME
Make sure your team has what they need to do their best work.

# One More Thing
Wear sunscreen. Hahahahahahahahahahahaah

# Have fun.

Stress isn't fun. It doesn't work. It doesn't help your team. Love your job, love your work, love your product.

Why work hard on your stuff if you aren't enjoying it? This is important. Put yourself in places where you believe in what you're doing, and enjoy it.

### Get to know yourself.
What actually interests you? What do you ACTUALLY want to do?

## You want to get here:
* Something you love
* Something you're good at
* Something the world needs

Get between those three. Get in the center. Jeff Veen came up with this.

### go.dem.mx/wcr2013/flowbook

If you don't have to work hard at something, you stop enjoying it. But, if you can't ever get good at it, you just get really frustrated and drop it.

You want to find a good **Flow**: Giving yourself a challenge, getting better, and finding new challenges. Keep growing, keep becoming the next most valuable, find the next most interesting thing.

# What are the things you want to DO with your next 20 years?


text:
# PyCHIP8
This is a project where I implemented CHIP-8 emulator using Python 3.
## Table of content
<!-- TOC -->
- [PyCHIP8](#pychip8)
- [Table of content](#table-of-content)
- [Installation](#installation)
- [Running](#running)
- [Changing key mapping](#changing-key-mapping)
<!-- /TOC -->

## Installation
To install this emulator you will need Python 3.7 with pip package. Using virtual environment in recommended but not necessary
1. Download this repository (using download button or use git clone command)
1. (Optional) Create virtual environment by running ``` virtualenv venv ```
1. (Optional) Activate virtual environment by running ```venv\Scripts\activate``` (Windows)  or ```source venv/bin/activate```(Linux)
1. Run ```pip install -r requirements.txt ```

## Running

To run this emulator you have to have valid CHIP-8 ROM file. There are many sources you can get them from and one example is [this github repository](https://github.com/dmatlack/chip8/tree/master/roms)

Running PyCHIP8 emulator is done by running ```python PyCHIP8.py --rom <path_to_file>``` command
## Changing key mapping
To change key mapping in this emulator you have to change PyCHIP8/conf.py file. In this file there is python dictionary named KEY_MAPPING, change values in it to customize key mapping to your preferences.

CHIP-8 uses 4x4 keyboard and each key has its address in memory. To help you visualize this I`ve created table below. Each cell represents key, and value in the cell is address specified in KEY_MAPPING key.

|  |  |  |  |
| --- | --- | --- | --- |
| 0x0 | 0x1 | 0x2 | 0x3 |
| 0x4 | 0x5 | 0x6 | 0x7 |
| 0x8 | 0x9 | 0xA | 0xB |
| 0xC | 0xD | 0xE | 0xF |
|  |  |  |  |

This is the current key mapping

|  |  |  |  |
| --- | --- | --- | --- |
| 1 | 2 | 3 | 4 |
| q | w | e | r |
| a | s | d | f |
| z | x | c | v |
|  |  |  |  |

Because this emulator uses pygame for keyboard support, you will have to use pygame constants to define keys, to find specific keys visit [this site](https://www.pygame.org/docs/ref/key.html)


text:
[![version](https://img.shields.io/github/release/cybercongress/cyber-wiki-index.svg?style=flat-square)](https://github.com/cybercongress/cyber-wiki-index/releases/latest)
[![CircleCI](https://img.shields.io/circleci/project/github/cybercongress/cyber-wiki-index.svg?style=flat-square)](https://circleci.com/gh/cybercongress/cyber-wiki-index/tree/master)
[![license](https://img.shields.io/badge/License-Cyber-brightgreen.svg?style=flat-square)](https://github.com/cybercongress/cyber-wiki-index/blob/master/LICENSE)
[![LoC](https://tokei.rs/b1/github/cybercongress/cyber-wiki-index)](https://github.com/cybercongress/cyber-wiki-index)
[![contributors](https://img.shields.io/github/contributors/cybercongress/cyber-wiki-index.svg?style=flat-square)](https://github.com/cybercongress/cyber-wiki-index/graphs/contributors)
[![discuss](https://img.shields.io/badge/Join%20Us%20On-Telegram-2599D2.svg?style=flat-square)](https://t.me/fuckgoogle)
[![contribute](https://img.shields.io/badge/contributions-welcome-orange.svg?style=flat-square)](https://github.com/cybercongress/cyber-wiki-index/blob/master/CONTRIBUTING.md)

[://cyber](https://github.com/cybercongress/cyberd) wiki index
==================

  - [Installation](#installation)
  - [Usage](#usage)
  - [Issues](#issues)
  - [Contributing](#contributing)
  - [Changelog](#changelog)

## Installation

## Usage

### Submit links
Basically, there are two main functions provided by `cyber-wiki` tool.
The first one is to parse wiki titles and submit links between keywords and wiki pages.
```
submit-links-to-cyber /home/user/enwiki-latest-all-titles --address=cli_acc_y0y
```

Here, **enwiki-latest-all-titles** is titles file obtained from
 [official Wiki dumps](https://dumps.wikimedia.org/enwiki/latest/enwiki-latest-all-titles-in-ns0.gz).

> Note: Uses only local cyber node.

> Note: Submit links do not add duras to ipfs.

### Uploading duras to IPFS
Also, `cyber-wiki` has separate command `upload-duras-to-ipfs` to upload files to local IPFS.
All duras are collected under single root unixfs directory.
```
upload-duras-to-ipfs /home/user/enwiki-latest-all-titles
```
> Note: We already upload duras.
They can be downloaded and pined on yor local node by **Qmdwsryu8HskLzBspzPwJbL8UZ1ZPZF8VemtW1ja1GMXGp** hash.

## Issues

If you have any problems with or questions about search, please contact us through a
 [GitHub issue](https://github.com/cybercongress/cyber-wiki-index/issues).

## Contributing

You are invited to contribute new features, fixes, or updates, large or small; We are always thrilled to receive pull
 requests, and do our best to process them as fast as We can. You can find detailed information in our
 [contribution guide](./docs/contributing/contributing.md).

## Changelog

Stay tuned with our [Changelog](./CHANGELOG.md).

  Built by
  cyber•Congress and
  contributors

repository: asadovka/cyber-wiki-index

repo_name: asadovka/cyber-wiki-index


text:
##  A/R Register Listing for a Specified Record (ARREG.R2)

<PageHeader />

**Form Details**
[ Form Details ](ARREG-R2-1/README.md)

**Purpose**
The ARREG.R2 procedure is used to print a listing of all Accounts Receivable
register transactions for a selected record, such as an AR, SHIP or CASH
record.

**Frequency of Use**
This report should be run as a check of all transactions which have been
created for a specific record. It can be run as required to audit the activity
of a record.

**Prerequisites**
Accounts Receivable register transactions are created automatically by the system through the [ AR.E ](../../../../rover/AP-OVERVIEW/AP-ENTRY/ACCT-CONTROL/ACCT-CONTROL-3/AR-E) , [ CASH.E ](../../../../rover/AP-OVERVIEW/AP-ENTRY/ACCT-CONTROL/ACCT-CONTROL-1/ar-e/AR-E-1/CASH-E) , [ SHIP.P1 ](../../../../rover/AP-OVERVIEW/AP-ENTRY/ACCT-CONTROL/ACCT-CONTROL-1/comm-e/SHIP-P1) and [ ARR.P1 ](../../../../rover/AP-OVERVIEW/AP-ENTRY/ACCT-CONTROL/ACCT-CONTROL-1/ar-e/AR-E-4/AR-F2/ARR-P1) procedures.

**Data Fields**

**Acct Number** The General Ledger account number.
**Acct Description** The description as is appears in the GLCHART file.
**Reg Id** The record id of the ARREG entry.
**Date** The date for which the register entry was made.
**Amount** The total amount of the register record.
**Procedure** The procedure which caused this register record to occur (e.g. [ AR.E ](../../../../rover/AP-OVERVIEW/AP-ENTRY/ACCT-CONTROL/ACCT-CONTROL-3/AR-E) , [ CASH.E ](../../../../rover/AP-OVERVIEW/AP-ENTRY/ACCT-CONTROL/ACCT-CONTROL-1/ar-e/AR-E-1/CASH-E) , etc.).
**Record Id** The record id which caused this register record to occur (e.g.
AR id, Cash number, etc.).

<badge text= "Version 8.10.57" vertical="middle" />

<PageFooter />

repository: zumasys/docs

repo_name: zumasys/docs


text:
## Dryad :o:

|          |                        |
| -------- | ---------------------- |
| title    | Dryad                  |
| status   | 10                     |
| section  | Workflow-Orchestration |
| keywords | Workflow-Orchestration |

Dryad is a general-purpose distributed execution engine for
coarse-grain data-parallel applications. Dryad was created with the
objective of automatically managing scheduling, distribution, fault
tolerance etc. Dryad concentrates on the throughput instead of latency
and it assumes that a private data centre is
used [@www-DryadIntro].  It creates a dataflow graph by using
computational 'vertices' and communication 'channels'. The
computational vertices are written using C++ base classes and
objects. During runtime, the dataflow graph is parallelized by
distributing the vertices across multiple processor cores on the same
computer or different physical computers connected by a network. The
Dryad runtime handles this scheduling without any explicit
intervention. The data flow from one vertex to another is realized by
TCP/IP streams, shared memory, or temporary files. In the directed
acyclic graph created by Dryad, each vertex is a program and the edges
represent data channels. Each graph is represented as G = (VG, EG, IG,
OG), where VG is a sequence of vertices with EG directed edges and two
sets IG is a subset of VG and OG is a subset of VG that indicate the
input and output vertices respectively [@DryadPaper]. Other
technologies used for the same purpose as Dryad include Map Reduce,
MPI etc.

gha_language: Jupyter Notebook


text:
# Attachments

Attachments are binary data files that can be attachment to an `RxDocument`, like a file that is attached to an email.

Using attachments instead of adding the data to the normal document, ensures that you still have a good **performance** when querying and writing documents, even when a big amount of data, like an image file has to be stored.

- You can store string, binary files, images and whatever you want side by side with your documents.
- Deleted documents automatically loose all their attachments data.
- Not all replication plugins support the replication of attachments.
- Attachments can be stored encrypted.

Internally, attachments in RxDB are stored and handled similar to how [CouchDB, PouchDB](https://pouchdb.com/guides/attachments.html#how-attachments-are-stored) does it.

## Add the attachments plugin

To enable the attachments, you have to add the `attachments` plugin.

```ts
import { addRxPlugin } from 'rxdb';
import { RxDBAttachmentsPlugin } from 'rxdb/plugins/attachments';
addRxPlugin(RxDBAttachmentsPlugin);
```

## Enable attachments in the schema

Before you can use attachments, you have to ensure that the attachments-object is set in the schema of your `RxCollection`.

```javascript

const mySchema = {
    version: 0,
    type: 'object',
    properties: {
        // .
        // .
        // .
    },
    attachments: {
        encrypted: true // if true, the attachment-data will be encrypted with the db-password
    }
};

const myCollection = await myDatabase.addCollections({
    humans: {
        schema: mySchema
    }
});
```

## putAttachment()

Adds an attachment to a `RxDocument`. Returns a Promise with the new attachment.

```javascript
const attachment = await myDocument.putAttachment(
    {
        id,     // (string) name of the attachment like 'cat.jpg'
        data,   // (string|Blob) data of the attachment
        type    // (string) type of the attachment-data like 'image/jpeg'
    }
);
```

## getAttachment()

Returns an `RxAttachment` by its id. Returns `null` when the attachment does not exist.

```javascript
const attachment = myDocument.getAttachment('cat.jpg');
```

## allAttachments()

Returns an array of all attachments of the `RxDocument`.

```javascript
const attachments = myDocument.allAttachments();
```

## allAttachments$

Gets an Observable which emits a stream of all attachments from the document. Re-emits each time an attachment gets added or removed from the RxDocument.

```javascript
const all = [];
myDocument.allAttachments$.subscribe(
    attachments => all = attachments
);
```

## RxAttachment

The attachments of RxDB are represented by the type `RxAttachment` which has the following attributes/methods.

### doc

The `RxDocument` which the attachment is assigned to.

### id

The id as `string` of the attachment.

### type

The type as `string` of the attachment.

### length

The length of the data of the attachment as `number`.

### digest

The hash of the attachments data as `string`.

NOTICE: The digest is NOT calculated by RxDB, instead it is calculated by the RxStorage. The only guarantee is that the digest will change when the attachments data changes.

### rev

The revision-number of the attachment as `number`.

### remove()

Removes the attachment. Returns a Promise that resolves when done.

```javascript
const attachment = myDocument.getAttachment('cat.jpg');
await attachment.remove();
```

## getData()

Returns a Promise which resolves the attachment's data as `Blob`. (async)

```javascript
const attachment = myDocument.getAttachment('cat.jpg');
const blob = await attachment.getData();
```

## getStringData()

Returns a Promise which resolves the attachment's data as `string`.

```javascript
const attachment = await myDocument.getAttachment('cat.jpg');
const data = await attachment.getStringData();
```

# Attachment compression

Storing many attachments can be a problem when the disc space of the device is exceeded.
Therefore it can make sense to compress the attachments before storing them in the [RxStorage](./rx-storage.md).
With the `attachments-compression` plugin you can compress the attachments data on write and decompress it on reads.
This happens internally and will now change on how you use the api.

```ts
import {
    wrappedAttachmentsCompressionStorage
} from 'rxdb/plugins/attachments-compression';

import { getRxStorageIndexedDB } from 'rxdb-premium/plugins/storage-indexeddb';

// create a wrapped storage with attachment-compression.
const storageWithAttachmentsCompression = wrappedAttachmentsCompressionStorage({
    storage: getRxStorageIndexedDB()
});

const db = await createRxDatabase<RxStylechaseCollections>({
    name: 'mydatabase',
    storage: storageWithAttachmentsCompression
});

// set the compression mode at the schema level
const mySchema = {
    version: 0,
    type: 'object',
    properties: {
        // .
        // .
        // .
    },
    attachments: {
        compression: 'deflate'  // <- Specify the compression mode here. Atm only 'deflate' mode is available.
    }
};

/* ... create your collections as usual and store attachments in them. */

```

repository: pubkey/rxdb

gha_language: TypeScript

repo_name: pubkey/rxdb


text:
# API Specs

All API calls are done will the following conventions described below.

Input
=====

* API calls are made with the endpoint prefix at - /api/
* When appropriate Results can be paginated with the parameters offset and count (defaulting to 0 and -1, respectively if not present)
* Parameters specified in the POST body will override those specified as URL query params.

Output
======
* Where possible http status codes will be used to denote return statuses.
* Body of the message will be in JSON unless the output format is specified
(either or via Accept header or via a "format" query parameter or POST
parameter in that order of precedence)

API is divided into following sections:

## Teams API
Handles team management.

## Users API
Handles user management, settings and auths.

## Channels API
Channel management and control

## Messages API
Message sending, recetion, creation, updates, notification etc

repository: wislr/backbone

repo_name: wislr/backbone


text:
# VK Hack 2018

Backend part of mobile app

## API

Here are some tips to get you started with the backend of the app.

### Map

This application provides you with models, views, etc. for working with different objects, related to pets,
e.g. grooming salons, cash boxes, etc.

#### PetPoint

`PetPoint` contains following fields:
* `name` - name of the point
* `type` - one of the point types (see [constants](app/map/constants.py) for better understanding)
* `address` - string, which contains full address of the point
* `location` - contains address as `lon/lat` pair (see [this](app/utils/fields.py) for better understanding)
* `site` - website of the point
* `extra` - any additional information, that can be useful

API provides one way of communicating:
1. `/api/map/map/` accepts `GET` requests and designed to list and retrieves `PetPoint` objects;
in order to retrieve some particular object specify its `{{id}}`;
also it is possible to filter results by `type`

### Pets

This application provides you with models, views, etc. for working with animal shelter's pets.

#### Pet

`Pet` contains following fields:
* `name` - name of the pet
* `type` - one of the pet types (see [constants](app/map/constants.py) for better understanding)
* `photo` - photo of the pet (see [this](app/utils/fields.py) for better understanding)
* `age` - age of the pet
* `info` - any additional information, that can be useful

API provides two ways of communicating:
1. `/api/pets/pets/` accepts `GET` requests and designed to list and retrieves `PetPoint` objects;
in order to retrieve some particular object specify its `{{id}}`;
also it is possible to filter results by `type`
2. `/api/pets/similar/` displays form, which gets picture and give back vector of cosine distances to pictures,
stored in the database

#### FakePet

`FakePet` contains following field:
* `photo` - photo of the pet (see [this](app/utils/fields.py) for better understanding)

This model is used to store pictures of pets uploaded by users.

### Users

This application provides you with models, views, etc. for working with users' data.

#### UserData

`UserData` contains following fields:
* `vk_id` - id of user at [vk.com](https://vk.com)
* `photo` - link to users' photo (see [this](app/utils/fields.py) for better understanding)
* `first_name` - first name of the user (taken from [vk.com](https://vk.com))
* `second_name` - last name of the user (taken from [vk.com](https://vk.com))
* `level` - level of the user
* `experience` - current experience of the user
* `coins` - users' coins
* `donated` - total values of users' donations

API provides three ways of communicating:
1. `/api/users/users/` accepts `POST` requests and designed to create `UserData` objects
2. `/api/users/users/{{id}}` accepts `GET`, `PATCH`,
`PUT` requests and designed to retrieve and modify `UserData` objects
3. `/api/users/users/leaderboard` accepts `GET` requests and designed to show users in order,
specified by `ordering` keyword, which can either be `level` or `donated`


text:
# chatty

A real-time chat app built with React and WebSockets.

![Chatty in action](https://github.com/jonathandannel/chatty/blob/master/docs/demo.gif?raw=true)

## Features

- Name changes
- Colors assigned to each user
- Active user count
- Conditional class highlighting on new messages

## Dependencies

`npm` and `nodejs` are required to run this app.

### Client

- react
- babel
- webpack
- eslint
- node-sass
- sockjs

### WebSocket Server

- express
- ws
- uuid

## Getting Started

- In the root directory, run `npm install` to install client-side dependencies.
- In the `chat_server` directory, run `npm install` again to install WebSocket dependencies. Run `node server.js` to start the WS server.
- Back in the parent directory, run `npm start` and head to localhost:3000 in your browser.

## To Do

- Sidebar displaying names of active users
- Allow users to embed images/video
- Fluid UI/UX & transitions
- Server broadcast on user connect/disconnect


text:
---
name: Task
about: Create a technical task that needs doing.
title: 'Task: ...'
labels: "task"
assignees: ''
---
# ❕ Problem Statement

<!-- Clearly describe what the problem this tech task is attempting to address. -->

# 💬 Task Description

<!-- A clear and concise description of the task. -->

# 👩🔧 Technical Design Notes

<!-- Provide any technical design notes here. -->

# 🤝 Relationships

- Other Related Issues: #xxx, #yyy

gha_language: Shell


text:
# BeanRate.com
## Codeup Capstone

## To Do:

A. (sudo npm install -g bower)
B. bower install chartist --save

##Site Plan:
LEMP+J stack

	Name: Bean Rate

	Template: Agency (http://startbootstrap.com/template-overviews/agency/)

	Functionality?
    	re: BeerAdvocate for coffee

     Users:
        1. user
        2. admin
        3. top rater

        as guest:
            view coffees/ reviews
            view roasters
            view regions

        as user:
        	guest privileges + :
            Create User:
                avatar/pic
                username/email
                password/conf.
                (log in with Facebook/Twitter/LinkedIn)****

            Add a coffee:
                see: BA site, use Angular, verify does not exist first
                add a roaster

            	Add a roaster:
            		w/in create coffee form (Angular, w/ dropdown)

        		Require: add a review!

    		Add a review to coffee:
    			Angular create form
				Flavor notes (wheel/pie chart) ie: http://wrapbootstrap.com/preview/WB0519204

		http://shop.colectivocoffee.com/products/black-and-tan
		https://gionkunz.github.io/chartist-js/

			confirm account w/ email

		as admin:
			guest & user privileges + :
			manage all reviews, users, coffees, and roasters
			verify all roaster info on create (auto-generate email to dev)
			verify coffee info on create (auto-generate email to dev)
			update roaster info as necessary (button/link on page)

    Coffees:
        show:
        name
        belong to one Roaster
        belong to one Region (sourced)
        price (per oz.?)/(bag size)
        score (avg.)
        pDev
        description
        photo?

          -Reviews:
                rating
                rDev
                sub-scores
                    many scores (belong to reviews)
                sort by (recent, high, low, top raters)
                username
                user avatar
                date
                brew parameters (accordion/drop-down)
                    -grind
                    -weight coffee
                    -weight water
                    -brew time
                    -brew equipment
                    -roast date

    Roaster:
        db:has many coffees
        Name Address City State Zip Phone
        Website Map Twitter-handle
        **send email on create
        Coffees
        Count (# of reviews)
        Average rating (all coffees)
        show each avg rating for each coffee

    Regions:
        db:has many coffees
        Map (image or lat/lon)
        description
        display some coffees (table)
           links to coffee show and roaster show

    Home:
    	carousel?
    	create account button/ small section
    	contact us

    	starting point: http://ironsummitmedia.github.io/startbootstrap-agency/
    		full page carousel-y thing
    		make "services smaller"
    		3 boxes with links to indexes (region, roaster, coffee) where "portfolio is"
    		team section w/ small bio/links/etc.
    		[footer]

DB structure:

    users table
    	-id
    	-username
    	-email
    	-password
    	-confirmation -- use binary 1/0, y/n or code?
        -role
        -img_url (nullable)
        -created_at
        -updated_at
        -remember token

    reviews table
    	-id
    	-coffee_id
    	-roaster_id
    	-user_id
    	-review
    	(critera:)
    		-aroma
    		-flavor
    		-aftertaste
    		-balance
    		(overall average of these?)
		-roast
		-body
		-acidity

		-price (nullable)
		-bag size (nullable)

    	-created_at
    	-updated_at

	flavor_review table [pivot]
		-review_id
		--flavor_id (2 are primary key)

	flavor table
		-id
		-flavor_category_id
		-name

	flavor_category table
		-id
		-name

	coffees table
		-id
		-user_id
		-name
		-roaster_id
		-region_id
		-roaster_notes (textarea)
        -active
		-link [top user or admin only] (nullable)
		-process (nullable)
		-elevation (nullable)
		-img_url (nullable)

    roasters table
    	-id
  		-user_id
    	-name
    	-address
    	-city
    	-state
    	-zip
    	-description
    	-link
    	-img_url
    	-twitter (nullable)
    	-facebook (nullable)
    	-instagram (nullable)

    regions table
    	-id
    	-region
    	-description
    	-img_url

    parameters table
        -id
        -review_id
        -grind (nullable)
        -wt_water (nullable)
        -wt_coffee (nullable)
        -brew_time (nullable)
        -brewer (nullable)
        -method (textarea) (nullable)
        -roast_date (nullable)
        -temp_water (nullable)

Classes:

    User
    	has many Review
        has many Coffee
        has many Roaster
        has Role
        has many Invitation

    Review
    	belongs to User
    	belongs to many Flavor
    	belongs to Coffee
        has Parameter

    FlavorCategory
    	has many Flavor

    Flavor
    	belongs to many Review
    	belongs to FlavorCategory

    Coffee
    	has many Review
        belongs to Roaster
    	belongs to Region
        belongs to User

    Roaster
    	has many Coffee
        belongs to User

    Region
    	has many Coffee

    Parameter
        belongs to Review

    Role
        belongs to User

    Invitation
        belongs to User

startup new project: https://gist.github.com/dgcollier/7bf95080656f996de2df

## Laravel PHP Framework

[![Build Status](https://travis-ci.org/laravel/framework.svg)](https://travis-ci.org/laravel/framework)
[![Total Downloads](https://poser.pugx.org/laravel/framework/downloads.svg)](https://packagist.org/packages/laravel/framework)
[![Latest Stable Version](https://poser.pugx.org/laravel/framework/v/stable.svg)](https://packagist.org/packages/laravel/framework)
[![Latest Unstable Version](https://poser.pugx.org/laravel/framework/v/unstable.svg)](https://packagist.org/packages/laravel/framework)
[![License](https://poser.pugx.org/laravel/framework/license.svg)](https://packagist.org/packages/laravel/framework)

Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Laravel attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

Laravel aims to make the development process a pleasing one for the developer without sacrificing application functionality. Happy developers make the best code. To this end, we've attempted to combine the very best of what we have seen in other web frameworks, including frameworks implemented in other languages, such as Ruby on Rails, ASP.NET MVC, and Sinatra.

Laravel is accessible, yet powerful, providing powerful tools needed for large, robust applications. A superb inversion of control container, expressive migration system, and tightly integrated unit testing support give you the tools you need to build any application with which you are tasked.

## Official Documentation

Documentation for the entire framework can be found on the [Laravel website](http://laravel.com/docs).

### Contributing To Laravel

**All issues and pull requests should be filed on the [laravel/framework](http://github.com/laravel/framework) repository.**

### License

The Laravel framework is open-sourced software licensed under the [MIT license](http://opensource.org/licenses/MIT)


text:
![Skywriter](https://github.com/pimoroni/skywriter-hat/blob/master/skywriter-logo.png)

This repository contains libraries and examples for the Pimoroni Skywriter boards.

Compatible with:

* Skywriter - https://shop.pimoroni.com/products/skywriter?variant=1047423445
* Skywriter HAT - https://shop.pimoroni.com/products/skywriter-hat?variant=1002848445

## Installing Software

### One-line Installer

We've created a super-easy installation script that will install all pre-requisites and get your HAT up and running in a jiffy. To run it fire up Terminal which you'll find in Menu -> Accessories -> Terminal on your Raspberry Pi desktop like so:

![Finding the terminal](terminal.jpg)

In the new terminal window type the following and follow the instructions:

```
curl -sS get.pimoroni.com/skywriter | bash
```

### From PyPi (Stable)

Install `smbus`:

```
sudo apt install python3-smbus
```

Enable i2c:

```
sudo raspi-config nonint do_i2c 0
```

Install the library:

```
python3 -m pip install skywriter
```

### From Source (Unstable/Latest)

Install `smbus`:

```
sudo apt install python3-smbus
```

Enable i2c:

```
sudo raspi-config nonint do_i2c 0
```

Install the library:

```
git clone https://github.com/pimoroni/skywriter-hat
cd skywriter-hat/python/library
python3 setup.py install
```

## Documentation & Support

* Function reference - http://docs.pimoroni.com/skywriter/
* GPIO Pinout - https://pinout.xyz/pinout/skywriter_hat
* Get help - http://forums.pimoroni.com/c/support

## Skywriter to Pi Connection

You can use a full-sized Skywriter board with your Raspberry Pi and our library by mimicking the connections that the HAT users. They are as follows:

Skywriter  | Raspberry Pi
-----------|--------------
GND        | GND
TRFR       | GPIO 27
RESET      | GPIO 17
SCL        | GPIO 3 / SCL
SDA        | GPIO 2 / SDA
VCC        | 3V

repository: pimoroni/skywriter-hat

repo_name: pimoroni/skywriter-hat


text:
Azure Blob CLI is a tool that makes managing Azure Blobs and Containers on the fly easy. It is an **unofficial** and prunned version of azure-cli built ontop of Laravel Zero.

To learn more about laravel zero, visit [link](http://laravel-zero.com/).

------

## Screenshots

<img src="https://i.imgur.com/hFdcUUb.gif" title="source: imgur.com" />

## Getting Started

To make this a cinch, add your Azure Account Name and Storage Key as `AZURE_STORAGE_NAME` and `AZURE_STORAGE_KEY` values in the .env.sample file. Then rename .env.sample to .env.

### Command Syntax

```
php azure-blob-cli {command}
```
## Features

- List Containers
  ```
  php azure-blob-cli containers
  ```
- Create Container
  ```
  php azure-blob-cli create-container {container-name}
  ```
- Delete Container
  ```
  php azure-blob-cli delete-container {container-name}
  ```
- Download Blobs
  ```
  php azure-blob-cli explore {container-name}
  ```
## License

Azure Blob Cli is an open-source software licensed under the [MIT license](https://github.com/emugabi/azure-blob-cli/blob/stable/LICENSE.md).

repository: emugabi/azure-blob-cli

repo_name: emugabi/azure-blob-cli