text:
# CPostgreSQL

This package is a system module wrapper for *libpq* – the official C library for PostgreSQL –, which must be installed separately before using it in Swift projects.

_Note: the database itself does not need to be running, only the header and library files matter._

Choose one of the following options:

## macOS: Install PostgreSQL via Homebrew (preferred)

1. Visit the https://brew.sh to install Homebrew if it isn't already installed.
1. Run the following command:

    ```
    brew install postgresql pkg-config
    ```

## macOS alternative: Install PostgreSQL with Postgres.app

1. Download Postgres.app from [postgresapp.com](https://postgresapp.com).
1. Create a [pkgConfig](https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageDescriptionV4.md#pkgconfig) file at `/usr/local/lib/pkgconfig/libpq.pc`
with the following content:

    ```
    path=/Applications/Postgres.app/Contents/Versions/latest
    Cflags: -I${path}/include
    Libs: -L${path}/lib -lpq
    ```
1. Adjust the path as necessary.

## macOS alternative: Install PostgreSQL with the EnterpriseDB installer

1. Download and run the installer from [enterprisedb.com](https://www.enterprisedb.com/downloads/postgres-postgresql-downloads#macosx).
1. Create a [pkgConfig](https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageDescriptionV4.md#pkgconfig) file at `/usr/local/lib/pkgconfig/libpq.pc`
with the following content:

    ```
    path=/Library/PostgreSQL/10
    Cflags: -I${path}/include
    Libs: -L${path}/lib -lpq
    ```
1. Adjust the version number (`10` in the example) to match the installed version.

## Linux: Install PostgreSQL via apt-get

Execute the following commands as the superuser:

```
apt-get update
apt-get upgrade
apt-get install postgresql postgresql-contrib
```

repository: vvkaghera/apiSwiftCode

repo_name: vvkaghera/apiSwiftCode


text:
# node-hackrf

Control a HackRF device (e.g. Jawbreaker, HackRF One, or Rad1o) from node

This is a low-level binding to `libhackrf`. If you'd like a nice stream interface, try [`hackrf-stream`](https://github.com/mappum/hackrf-stream).

```
npm install hackrf
```

## API

#### `var devices = hackrf()`

Returns an array containing information about the connected HackRF devices. If no devices are connected, an empty array will be returned.

#### `var device = devices.open(index)`

Opens and returns the device in the array of devices with index `index`.

#### `device.getVersion()`

Returns the `hackrf` firmware version.

#### `device.setFrequency(hz, [callback])`

Set the frequency. `hz` should be an integer

#### `device.setBandwidth(hz, [callback])`

Set the bandwidth. `hz` should be an integer

#### `device.setSampleRate(hz, [callback])`

Set the sample rate. `hz` should be an integer

#### `device.setLNAGain(val)`

Set the lna gain. Should be between `0-40`

#### `device.setVGAGain(val)`

Set the vna gain. Should be between `0-62`

#### `device.setTxGain(val)`

Set the tx gain. Should be between `0-47`

#### `device.startRx(onrx)`

Receive data. `onrx` is called with `(data, cb)`.

``` js
device.startRx(function (data, cb) {
  console.log('read', data)
  cb() // done
})
```

#### `device.stopRx([callback])`

Stop receiving data.

#### `device.startTx(ontx)`

Transmit data. `ontx` is called with `(data, cb)`.
You should write the data you want to send to `data`.

``` js
device.startTx(function (data, cb) {
  for (var i = 0; i < data.length; i++) data[i] = 127
  cb() // write the data
})
```

#### `device.stopTx([callback])`

Stop transmitting data.

#### `device.close([callback])`

Release the resources for the device (allowing it to be used by another process).

## License

MIT

license: MIT

repository: gavintw/node-hackrf

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: gavintw/node-hackrf


text:
---
layout: page
title: "Scenes"
comments: false
sharing: false
footer: false
---

## Any Level from Easy to Hard
### A subclass of CCScene

These objects can represent menus, levels, cutscenes or any kind of screen. Their main purpose is to encapsulate functionality (like mini apps) and as stages in the game workflow. They are composed by one or more layers, stacked one behind another.

A single level of your game will be a scene and will contain one of more layers, with each layer containing one or more sprites.

## Subclassing

In order to present the Layers on the screen you need to subclass the Scene class, which is accomplished by the following:

``` ruby
class MyScene < Joybox::Core::Scene

end
```

## Initialization

Create a new instance of a Scene:

``` ruby
scene = MyScene.new

# Present the Scene on the screen
director << scene
```

## Transitioning to a Scene

### First Scene Loaded

To load the first scene within your application:

``` ruby
scene = MenuScene.new

director.run_with_scene(scene)
```

### Transitioning from a Scene to another Scene

From within a scene you can easily transition to another scene with the following:

``` ruby
second_scene = MySecondScene.new

director << second_scene
```

## Set Up & Tear Down

A scene has two methods to assist with setup and teardown of your scene:

* `on_enter` - when the scene has already been initialized and will be presented by the director.

* `on_exit` - when the scene is going to no longer be presented by the director

``` ruby
def on_enter
  # Initialize Layers and other logic
end

def on_exit
  # Perform any state clean if needed
end
```

For more information, see: [CCScene Class Reference](http://www.cocos2d-iphone.org/api-ref/2.0.0/interface_c_c_scene.html)

repository: kfatehi/Joybox-Documentation

extension: markdown

repo_name: kfatehi/Joybox-Documentation


text:
##UX DESIGNER;WHO IS? AND WHAT IT ENTAILS?

A UX Designer is focused on all aspects of a product's development, including design, usability, funcion, and even branding and marketing. Their work touches the entire end-to-end journey of a user's interaction with a product, and includes identifying new opportunities for the product and business.
What does a UX designer do?

 Responsibilities often include:

-Consulting with clients to understand their goals and explaining research results

-Conducting usability testing

-Creating wireframes, storyboards, sitemaps and screen flows

*Creating product prototypes

*Developing personas and usage scenarios

*Analyzing user feedback and activity, and iterating to enhance the user experience

*Assisting with content development

*Conducting competitor and customer analysis

repository: TOBECHI-GH/rename-fork

branch_name: refs/heads/main

gha_license_id: MIT

repo_name: TOBECHI-GH/rename-fork


text:
AzureSpeed
==========

www.azurespeed.com source code

##How To Run
1. Open AzureSpeed.sln in Visual Studio 2015
2. Replace storage accounts and keys in AzureSpeed.WebUI\App_Data\setting.json
3. Run AdminConsole to initialize storage account, make sure it's laoding correct settings.json in step 2
4. You are all set, enjoy!

repository: SquirrelAssassin/speed

repo_name: SquirrelAssassin/speed


text:
---
description: How to setup ACL
---

# Setup

In this section, setup of the ACL package is covered. It goes without saying, you should have some prior knowledge about how to work with Laravel's [Authorization](https://laravel.com/docs/9.x/authorization), before attempting to use this package's components.

[[TOC]]

## Register Service Provider

Register `AclServiceProvider` inside your `config/app.php`.

```php
return [

    // ... previous not shown ... //

    /*
    |--------------------------------------------------------------------------
    | Autoloaded Service Providers
    |--------------------------------------------------------------------------
    */

    'providers' => [

        \Aedart\Acl\Providers\AclServiceProvider::class

        // ... remaining services not shown ... //
    ],
];
```

## Publish Assets (optional)

Run `vendor:publish` to publish this package's configuration.

```shell
php artisan vendor:publish
```

After the command has completed, you should see `config/acl.php` in your application.

### Publish Assets for Athenaeum Core Application

If you are using the [Athenaeum Core Application](../../core), then run the following command to publish assets:

```shell
php {your-cli-app} vendor:publish-all
```

## Configuration

Inside the `config/acl.php` file, you can change configuration for this package.

### Using your own models

By default, this package's Eloquent models are used when interacting the various ACL components. To this this, simply state the class paths of your own models, in the `models` setting.

::: tip Note
If you choose to use your own models, then please make sure that they extend this package's Eloquent models - _otherwise you will experience unexpected behavior_.
:::

```php
<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Models
    |--------------------------------------------------------------------------
    */

    'models' => [

        'user' => \App\Models\User::class,

        'role' => \App\Models\Acl\Role::class,

        'permission' => \App\Models\Acl\Permission::class,

        'group' => \App\Models\Acl\Permissions\Group::class
    ],

    // ... remaining not shown
];
```

## The `HasRoles` trait

Your Eloquent `User` model must make use of the `HasRoles` trait. This will ensure that users can be assigned roles and thereby be granted permissions.

```php
<?php

namespace App\Models;

use Aedart\Acl\Traits\HasRoles;
use Illuminate\Foundation\Auth\User as Authenticatable;

class User extends Authenticatable
{
    use HasRoles;
}

```

## Migrate the database

Once you have configured the ACL components to your liking, you must migrate the database, so that the various tables can be installed.

```shell
php artisan migrate
```

::: tip Note
The current version of this package does not publish it's database migration files. They are loaded directly via `AclServiceProvider`, when the `artisan migrate` command is executed.
:::

## Define permissions for Gate

To ensure that Laravel's Authorisation Gate component is able to distinguish between which permission a user is granted or not, you must define these in your application's `\App\Providers\AuthServiceProvider` class.
This can easily be accomplished via the ACL `Registrar` component's `define()` method.

```php
<?php

namespace App\Providers;

use Aedart\Acl\Traits\RegistrarTrait;
use App\Models\User;
use Illuminate\Contracts\Auth\Access\Gate;
use Illuminate\Foundation\Support\Providers\AuthServiceProvider as ServiceProvider;

class AuthServiceProvider extends ServiceProvider
{
    use RegistrarTrait;

    // ... previous not shown ...

    public function boot(Gate $gate)
    {
        $this->registerPolicies();

        $this->getRegistrar()->define($gate);
    }
}
```

### When acl tables are missing...

::: warning CI environment
If you have a [CI](https://en.wikipedia.org/wiki/Continuous_integration) environment, you might experience a _"missing permissions table"_ failure, when installing a fresh instance of the application.
This will happen when the `AuthServiceProvider`'s `boot()` is invoked, before migrations are installed.

A possible solution for this, is to safely ignore the `QueryException`. E.g.:

```php
use Aedart\Utils\Str;
use Illuminate\Database\QueryException;

try {
    $this->getRegistrar()->define($gate);
} catch(QueryException $e) {
    // Ignore exception - BUT ONLY IF it concerns missing permissions table!
    // Otherwise, re-throw the exception...
    if (!Str::contains($e->getMessage(), [
        'could not find driver (SQL: select * from `permissions`)',
        'relation "permissions" does not exist'
    ])) {
        throw $e;
    }
}
```

This issue can be very frustrating. Yet, this package dares not assume how to deal missing with migrations or boot order of your service providers.
:::

## Onward

You should now be ready to start working with the ACL components. In the upcoming sections, how to create permissions, roles, granting & revoking permissions ...etc, is covered in details.

repository: aedart/athenaeum

gha_language: PHP

repo_name: aedart/athenaeum


text:
## Course Materials

### Node.js
- [install Node.js & NPM](https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions)

### Webpack
Install webpack locally using
```bash
npm i -D webpack webpack-cli
```
- [Base configuration](https://webpack.js.org/concepts/#entry)
- [build mode](https://webpack.js.org/concepts/mode/)
- [webpack-serve](https://github.com/webpack-contrib/webpack-serve)

### Eslint
- [Official Docs](https://eslint.org/docs/user-guide/getting-started)
- [Airbnb preset](https://www.npmjs.com/package/eslint-config-airbnb)

### Babel
- [Usage Guide](https://babeljs.io/docs/en/usage)
- [babel-preset-env](https://babeljs.io/docs/en/babel-preset-env)

### App API
- [cart.school.pdffillers.com](http://cart.school.pdffillers.com/api/orders)

### Plugins & Loaders
- [html-webpack-plugin](https://github.com/jantimon/html-webpack-plugin)
- [babel-loader](https://github.com/babel/babel-loader)
- [ejs-loader](https://github.com/okonet/ejs-loader)
- [mini-css-extract-plugin](https://github.com/webpack-contrib/mini-css-extract-plugin)
- [css-loader](https://github.com/webpack-contrib/css-loader)
- [serviceworker-webpack-plugin](https://www.npmjs.com/package/serviceworker-webpack-plugin)
### Etc.
- [code smell](https://en.wikipedia.org/wiki/Code_smell)
- [web app manifest](https://developers.google.com/web/fundamentals/web-app-manifest/)
- [lessons & screencasts](https://drive.google.com/drive/u/1/folders/1e2YviXy0DFXTCTD-uD4Vwv0XtKsE7C9F)

### Cart App API
#### Get orders by user Id
For userId = 1
```
GET http://cart.school.pdffillers.com/api/orders?id=1
```
#### Get User data by user Id
For userId = 1
```
GET http://cart.school.pdffillers.com/api/users/1
```

repository: pdffiller/js-react-school-tasks

path: /Web App Basics/Links.md

gha_language: HTML

repo_name: pdffiller/js-react-school-tasks


text:
# Ubiquitous Language
A language structured around the domain model and used by all team members to connect all the activities of the team with the software. (Eric Evans)

## Definitions
This is a list of words and definitions of the language.

### class FQN
The class Fully Qualified Name is mostly given as a string. It refers to a file with an absolute namespace. But no \ is prepended before the Namespace.

```php
$fqn1 = "Webforge\Code\Test\Base";
$fqn2 = "stdClass";
$fqn3 = "Doctrine\ORM\Mapping";
```
This is equivalent to the return value from get_class()

### class name
The class Name is the name of the class without its namespace. Its distinct from an FQN.

```php
$fqn1 = "Webforge\Code\Test\Base";
$className1 = 'Base';

$fqn2 = "stdClass";
$className2 = 'stdClass';

$fqn3 = "Doctrine\ORM\Mapping";
$className2 = 'Mapping';
```

### Package
the term is used as used in composer. A package is a collection of class files and scripts or binaries that represent a common context. A Package can be a kind of library, or application, or something else. On github one repository would be considered as a package.

repository: webforge-labs/webforge-common

repo_name: webforge-labs/webforge-common


text:
---
title: "\n\t\t\t\tBest Mac Pro Memory\t\t"
date: 2010-08-30 00:00:00 Z
categories:
- jim
author<EMAIL_ADDRESS>comments: true
excerpt: "\n\t\t\t\t\t\t"
layout: post
link: https://jim.am/best-mac-pro-memory/
wordpress_id: 5476
---

Wow. I’ve already written about how I think that dropping almost 3 large for computer RAM on Mac Pros right now is just flushing money down the toilet. If I know one thing when it comes to ram prices, especially for the Mac Pro RAM Prices and it’s this:

[![Cheap Apple Mac Pro](http://www.jim.am/wp-content/uploads/2010/08/Screen-shot-2011-03-25-at-12.44.53-PM.png)](http://www.amazon.com/gp/product/B003ZR4M6I/ref=as_li_ss_tl?ie=UTF8&tag=ramseeker-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B003ZR4M6I)

**[Cheapest Mac Pro](http://www.amazon.com/gp/product/B003ZR4M6I/ref=as_li_ss_tl?ie=UTF8&tag=ramseeker-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B003ZR4M6I)**

**RAM Prices for Mac Pro will drop over time**. Even with the newer 1333 MHz RAM for the Mac Pros it was only about a week ago or so that you would have to pay just a touch under $3,000 for Mac Pro 64GB but as I write this the ram prices drop and drop – especially for the bigger chips such as 64GB as there’s more room for price drops. Let’s say a 4gb memory upgrade module drops in price of ten dollars. It’s possible. If you do the math you save ten dollars for 4GB so you’ll save $160 assuming the same discount on the larger Mac Pro Memory Kit. Now, technically you’d need 8x8GB to get to 64Gb so my example is flawed from the start but not really. With few exceptions, 1gb costs ten bucks than 2gb will cost twenty and 4gb will be at $40. There might be a small ‘pricing discount’ to get you to buy ram and the 4GB chip might have a price of $39, but we’re splitting hairs.

Let’s have a look at today’s prices for Mac Pro. And these are the Best Mac Pro Memory Prices at time of writing so you should always check for current Apple Mac Pro RAM Prices as your mileage may vary. ![:)](http://www.jim.am/wp-includes/images/smilies/simple-smile.png)

[![best mac pro ram prices](http://www.jim.am/wp-content/uploads/2010/08/Screen-shot-2010-08-30-at-4.23.43-PM.png)](http://www.jim.am/memory/Mac_Pro_RAM_Upgrade_Kits_DDR3_1333_with_4GB_RAM-32gb/)

As you will see, the [8gb Mac Pro  RAM costs $272.](http://www.jim.am/memory/Mac_Pro_RAM_Upgrade_Kits_DDR3_1333_with_4GB_RAM-8gb/) The price for [16GB Mac Pro RAM](http://www.jim.am/memory/Mac_Pro_RAM_Upgrade_Kits_DDR3_1333_with_4GB_RAM-16gb/)? about double at $556, and double again for [32gb of RAM for Mac Pro ](http://www.jim.am/memory/Mac_Pro_RAM_Upgrade_Kits_DDR3_1333_with_4GB_RAM-32gb/)(actually it seems you pay a bit of a premium for the bigger ram for Mac Pro in this example)

Anyway, the [best price for Apple Mac Pro RAM](http://www.jim.am#lowest) is what you can afford really as the Mac Pros offer loads of options for memory upgrades and this chart is just a sampling of  the memory upgrade possibilities. With  the new 2010 Apple Mac Pro machines you can use 2GB, 4GB, or even 8GB to get to the maximum memory configurtation at the best price that suits your needs and also considering your specific Mac Pro models as some still take the older 1066 DDR RAM and to make things even more confusing not all Mac Pro’s will use the Max RAM of 64GB. It’s a good place to start to see what specific Mac Pro you have and what Mac Pro processor speed and then do some research on Mac Pro RAM Prices from there.

If you need any help with finding the **[best Mac Pro RAM Upgrade,](http://www.jim.am)** feel free to contact me. It’s why I’m here.

repository: ramseeker/sidey

repo_name: ramseeker/sidey


text:
# GitHub Explorer

GitHub client with the v4 GraphQL API using [Apollo Client](https://www.apollographql.com/client/) and CSS Grid.

![preview](https://user-images.githubusercontent.com/2513462/36777146-7c7e9fac-1cbc-11e8-8229-6ecedf73c7c7.gif)

## Development

* copy `token.sample.js` and name `token.js`. Insert a GitHub API token with the following scopes [https://developer.github.com/v4/guides/forming-calls/#authenticating-with-graphql](https://developer.github.com/v4/guides/forming-calls/#authenticating-with-graphql).
* `yarn start` / `npm start`
* built with [create-react-app](https://github.com/facebook/create-react-app)

repository: WooodHead/github-explorer

repo_name: WooodHead/github-explorer


text:
# Flutter Test `pre-commit`

[`pre-commit`](https://pre-commit.com) hook for running Flutter unit tests

Add the following in your `.pre-commit-config.yaml`:
```yaml
- repo: https://github.com/dluksza/flutter-test-pre-commit
  rev: "master"
  hooks:
    - id: flutter-test
```

## Testing nested Flutter project

By default `flutter test` is run in repository root, this should work for most of the cases.
When your Flutter project is nested somewhere in git repository or you have multiple modules
add `args` parameter to the hook configuration containing list of paths to the Flutter
projects, eg.:

```yaml
  hooks:
    - id: flutter-test
      args: [ module1, module2 ]
```

## Acknowledgements

[Charles Crete](https://github.com/Cretezy/) for creating `flutter-format-pre-commit`

repository: dluksza/flutter-test-pre-commit

repo_name: dluksza/flutter-test-pre-commit


text:
#Use Repository Specific User Config

The following commands will ensure that Git will explicitly ask you to set `user.name` and `user.email` on a per-repository basis.

```sh
# Requires you to set user.name and email per repository
git config --global user.useConfigOnly true

# Remove email address from global config
git config --global --unset-alluser.email
```

**context**: I learned this because I have multiple github accounts and I want to make sure I commit using the right username and email address per repository.

**note**: There are other possible ways to achieve this behavior but this is the one that works most conveniently for Git v2.8 and above (see [source](https://orrsella.com/2013/08/10/git-using-different-user-emails-for-different-repositories/))

repository: jbfrrr/til

repo_name: jbfrrr/til


text:
[![Build Status](https://travis-ci.org/damakahindi/bucket-list-api.svg?branch=master)](https://travis-ci.org/damakahindi/bucket-list-api)
[![Coverage Status](https://coveralls.io/repos/github/damakahindi/bucket-list-api/badge.svg?branch=master)](https://coveralls.io/github/damakahindi/bucket-list-api?branch=master)

# bucket-list-api
This is a  bucket-list API that allows users of the API to manages buckets, session and add users.

## Dependencies
* Mongoose
* Node
* Postman

## Installation

1. Install [**Node JS**](https://nodejs.org/en/).
1. Create a Mongo DB there [**MLab**](https://mlab.com/) .
1. Clone the [**repository here**](https://github.com/andela-ekahindi/doc-api.git) or download the zip file of the project. Unzip it.
1. [**cd**] into the root of the *bucket-list-api project directory**.
1. Run `npm install` on the terminal.

## Tests

Run `MONGODB_URI=mongodb://<user>:<user>@<userURL>.mlab.com:1237/name-of-mlab-mongo-db npm test` on the terminal while within the **project root directory**.

## Usage
### Starting
In the project root, run `MONGODB_URI=mongodb://<user>:<user>@ds1234.mlab.com:1237/name-of-mlab-mongo-db npm start`.
### Routes
* #### users

  * ##### create
  `POST`
  `http://<IP_ADDRESS>:5000/api/user`

* #### sections
  * ##### create
  `POST`
  `http://<IP_ADDRESS>:5000/api/section`

  * ##### update
  `PUT`
  `http://<IP_ADDRESS>:5000/api/section/:id`

  * ##### delete
  `DELETE`
  `http://<IP_ADDRESS>:5000/api/section/:id`

  * ##### get one
  `GET`
  `http://<IP_ADDRESS>:5000/api/section/:id`

  * ##### get documets belonging to a particular user
  `GET`
  `http://<IP_ADDRESS>:5000/api/user/:id/section`

* #### buckets

* ##### create
  `POST`
  `http://<IP_ADDRESS>:5000/api/bucket`

  * ##### update
  `PUT`
  `http://<IP_ADDRESS>:5000/api/bucket/:id`

  * ##### delete
  `DELETE`
  `http://<IP_ADDRESS>:5000/api/bucket/:id`

  * ##### get one
  `GET`
  `http://<IP_ADDRESS>:5000/api/bucket/:id`

  * ##### get documets belonging to a particular user
  `GET`
  `http://<IP_ADDRESS>:5000/api/user/:id/bucket`

**NB** Make sure all tests pass before testing the api with POSTman.

## Models

Three models are defined: `Bucket`, `User` and `Section`.

## Testing

Testing is achieved through use of `supertest`, `mocha` and `chai` packages. `supertest` is used to make requests to the api and `mocha` is the testing framework test and `chai` is the exception library.

## Express Routes

Api endpoints were created using `express` router. To access them on a http client, run `node index.js` on your terminal. The routes are defined under `server/routes`.

license MIT 😄 😄

repository: damakahindi/bucket-list-api

gha_language: JavaScript

repo_name: damakahindi/bucket-list-api


text:
# Cryptostictis cupressi Guba, 1961 SPECIES

#### Status
SYNONYM

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
Monograph of Monochaetia and Pestalotia 47 (1961)

#### Original name
Cryptostictis cupressi Guba, 1961

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Ascomycota/Sordariomycetes/Xylariales/Amphisphaeriaceae/Lepteutypa/Lepteutypa cupressi/ Syn. Cryptostictis cupressi/README.md

repo_name: mdoering/backbone


text:
# Hardware Notes

This is a collection of one-off notes and useful things to know about the DC26 badge hardware-wise, most of which was reverse engineered from the firmware dump as well as board schematics and datasheets.

## ICs

The entire board runs at 3.3V.

The main microcontroller is a [PIC32MM0256GPM048](http://ww1.microchip.com/downloads/en/DeviceDoc/60001387c.pdf) with no code protection.

The U7 microcontroller is a [PIC12F508](http://ww1.microchip.com/downloads/en/DeviceDoc/41236E.pdf) in 8-pin SOIC package with code protection enabled; only something like the first 32 bytes are readable which makes firmware dumping useless.

The U4 microcontroller is a [PIC10F200](http://ww1.microchip.com/downloads/en/DeviceDoc/40001239F.pdf) in 6-pin SOT-23 package (likely with code protection enabled), masquerading as a 74LVC1G57 configurable multifunction logic gate. By default it is configured to operate as a 2 input AND gate, but by feeding it a hex string on GP0 (see below), it will swap modes to become a 2 input XOR gate until the next power cycle.

The LED controller is an [IS31FL3236](http://www.issi.com/WW/pdf/31FL3236.pdf) 36 channel I2C constant current LED sink driver.

## Hardware Puzzles

There are four hardware puzzles on the DEFCON26 badge. They correspond to the following:

1. Short the C11 capacitor on the PCB to stop the LED from blinking. Solves the E on human badges.

2. Feed 0xFEEDB0B0DEADBEEF to U4 LSB first (this can be done in software).

3. Desolder U7 and resolder it rotated 180 degrees.

4. Generate a magnetic field next to the hall effect sensor (location will vary based on badge type - on human badges it is behind the subway car on the bottom right). Changes some flavor text, unknown what else it does.

## Useful U4/U7/PIC32 pin mappings

The PIC32, U4 and U7 are all connected with SPI-like wiring. These are prime locations to attach a logic analyzer to analyze the data going in and out of the microcontrollers for LFSR analysis.

Note that for the PIC12F508 (U7), the pin assignments are when the chip is unflipped.

| Function           | PIC32MM0256GPM048 | PIC12F508 | PIC10F200 |
| ------------------ | ----------------- | --------- | --------- |
| RST                | RC4               | GP5       |           |
| CLK                | RB0               | GP1       | GP1       |
| MOSI (PIC32 -> U4) | RB1               |           | GP0       |
| MOSI (U7 -> U4)    | RC0               | GP0       | GP3       |
| MISO (U4 -> PIC32) | RC2               |           | GP2       |

Note that U4 has two inputs in XOR mode, one from the PIC32 (the bitstring to be decoded) and one from U7 (its LFSR output). U4 MISO is also connected to the LED next to U4 (the robot head on a human badge).

## Notes on U4/U7/PIC32 SPI

All microcontrollers run off of the same clock signal, which is generated in software by the PIC32.

Before any encoding/decoding operation is done, the PIC32 will hold RST high to reset U7 (note that this does not reset U4), then drive the clock once before it feeds U4 with input.

To make U4 switch to XOR mode, 0xFEEDB0B0DEADBEEF must be fed to U4 least significant bit first while driving the clock. This will look like you are feeding F77D B57B 0D0D B77F if interpreting as MSB first.

## Puzzle 2 (robot head) notes

Feeding Bobo (the robot head) only works properly in the v2 firmware.

Bobo can be fed by using the buttons in the arcade/control rooms. - corresponds to a 0 while + corresponds to a 1.

Using - or + will drive the shared U4/U7 input clock as well as set the appropriate bit for U4's MISO.

In addition, once 0xFEEDB0B0DEADBEEF has been inputted, the PIC32 will hold U7's reset line high for about 1 second. The user can then perform a decoding operation with -/+, getting the output by observing the LEDs.

## Other useful PIC32 pins

RA4 and RA2 can control the C11 LED. Holding RA2 high (also known as CTRL1 in debug menu) will cause the LED to stop blinking, and holding RA4 high (CTRL0) will cause the LED to turn on.

RB1 (CTRL2) can be held high to toggle the U4 LED, which also seems to solve puzzle 2 (If it is working correctly).

Hall effect sensor (puzzle 4) is triggered by RD0 being pulled high.

## Other pin mappings

All following mappings are output channels on the LED controller (IS31FL3236).

Out16 corresponds to the middle blinking terminal on the human badge.

Out22 corresponds to the bottom blinking terminal on the human badge.

Out27/28/29 correspond to the RGB channels of the O on the human badge.

This will probably not be that useful except for when analyzing the firmware, to know the relative positions of the LED data in the I2C write buffer.


text:
# How to Validate an OBO ontology using Obo Metadata Ontology schema

## Steps

### Step 1: Obtain the sqlite version of the ontology

Currently the sqlite version of ontologies are not distributed alongside them in OBO

You can either

 - (a) make the sqlite file yourself, see [INCATools/semantic-sql](https://github.com/INCATools/semantic-sql)
 - (b) get a ready-made download from the [s3 bucket](https://s3.amazonaws.com/bbop-sqlite/)

The second option is likely easiest.

For example:

```bash
wget https://s3.amazonaws.com/bbop-sqlite/uberon.db
```

### Step 2: Install oaklib

```bash
pip install oaklib
```

Check your install works:

```bash
runoak --help
```

### Step 3: Validate an individual ontology

```bash
runoak -i sqlite:uberon.db validate
```

This will stream yaml output. The output is linkml objects using the SHACL Validation vocabulary

```
type: https://w3id.org/shacl/MinCountConstraintComponent
severity: ERROR
subject: CARO:0000003
predicate: rdfs:label
info: Missing slot (label) for CARO:0000003

type: https://w3id.org/shacl/MinCountConstraintComponent
severity: ERROR
subject: CARO:0000006
predicate: rdfs:label
info: Missing slot (label) for CARO:0000006
```

### Step 3 (alternative): Validate multiple ontologies

```bash
runoak validate-multiple db/*.db -o obo-validation.tsv
```

## Caveats

Currently only the following are implemented:

* MinCountConstraintComponent checks (required or recommended)
* MaxCountConstraintComponent checks
* DeprecatedPropertyComponent
* DatatypeConstraintComponent: basic type checks (literal vs object) DOES NOT YET CHECK SPECIFIC LITERAL TYPE
* ClosedConstraintComponent

## Using your own schema

TODO: add an option to pass in your own yaml file

## How this works

The Python API is described here:

 - [ValidatorInterface](https://incatools.github.io/ontology-access-kit/interfaces/validator.html)

Currently there is only one implementation, the SqlDatabase implementation

The validation is driven entirely by a [LinkML](https://linkml.io) schema

Currently this schema lives within this repo, but the goal is to have it live outside and be imported

- [linkml generated docs](https://incatools.github.io/ontology-access-kit/datamodels/ontology-metadata/index.html)
- source: [src/oaklib/datamodels/ontology_metadata.yaml](https://github.com/INCATools/ontology-access-kit/blob/main/src/oaklib/datamodels/ontology_metadata.yaml)

Different implementations are free to use this in different ways

The SqlDatabase implementation attempts to do this in a performant way doing whole-database predicate-based queries

Validation results use the [Validator Datamodel](https://incatools.github.io/ontology-access-kit/datamodels/validation), which reuses many URIs from SHACL

## Analysis

See notebooks folder in [https://github.com/cmungall/obo-metadata](https://github.com/cmungall/obo-metadata)

repository: INCATools/ontology-access-kit

gha_language: Jupyter Notebook

repo_name: INCATools/ontology-access-kit


text:
#Humpback Road Map
##Where to from here?

Humpback is quickly evolving and so is the web around us.  We want to build a platform that will last
and that includes making some future proofing changes to Humpback.

When Humpback was started, angular was getting pretty old and angular 2 was way way to new, but many of
us agree with the concepts of angular 2, which is where we think humpback will move to.

###Typescript
We want to completely convert the humpback platform over to Typescript.

###Angular 2
We want rebuild all the Humpback modules to tightly integrate with the angular 2 methodology to make
development even quicker and resuable.

###Barnacles
Humpback currently uses installable hooks called Barnacles.  We want to standardize a way to create and
use these.  Possiblly even make a market place for them.

###Pipelines
It's not a secret that devs have a lot of choices when it comes to their pipeline.  Wether that's AWS, Gcloud, Heroku, etc.
We would love to make prekitted pipelines that make deploying humpback a breeze on these platforms and allow for
continuous integration and deployment. Heck, why not add some Hubot stuff in there?

##The Choice is up to you!
Even when I started Humpback I was never under the illusion that I was the best at this.  I knew it was ambitious
and I would have to really count on the OS community to feel the same pains as me and want to work together to
solve them.  So the call is up to all of us now.


text:
## Intro

This class is a drop in way to add sharing with facebook and twitter to your iOS apps. Other methods to share
can/will be added later. If you have a method you want to add, please fork the project, add your code and send us a pull request!

## Setup

#### Add and Setup Facebook SDK

Adding the facebook sdk is well documented [here](https://developers.facebook.com/docs/mobile/ios/build/), but I'll give you a quick outline.

1. Create an app on facebook at [https://developers.facebook.com/apps](https://developers.facebook.com/apps).
2. Add facebook-ios-sdk files to your project.
3. Add necessary code to your app delegate files, detailed [here](https://developers.facebook.com/docs/mobile/ios/build/#implementsso).
4. Make sure you remember to setup your info.plist file for Facebook SSO.

#### Add and Setup Twitter

1. Include the twitter framework in your project by adding the iOS5 Twitter framework in xcode.
2. That's all.

#### Add ShareMachine Files

1. Copy the ShareMachine.h and ShareMachine.m files to your project.
2. Change the constants in the ShareMachine.h file to reflect your facebook_app_id, and the various links/messages you want your users to share.
3. Create an instance of ShareMachine in your viewController with the initWithDelegate method. The delegate is probably the view controller. You also need to call the share methods somehow. In this example we'll use a simple UIButton (created from within Interface Builder) that will share to facebook.

		ViewController.h

		#import "ShareMachine.h"

		@interface ViewController : UIViewController <BonoboShareMachineDelegate>

		@property (nonatomic, strong) ShareMachine* shareMachine;

		@end
<br>

		ViewController.m

		@implementation ViewController

		@synthesize shareMachine;

		-(void)viewDidLoad {
			self.shareMachine = [[ShareMachine alloc] initWithDelegate:self];
		}

		-(IBAction)onShareFacebookButtonTap:(id)sender {
			[self.shareMachine shareWithFacebook];
		}

		@end

4. There are also delegate methods you can implement in the viewController if you want to do something specific when the share is finished or if the share errors out.

		ViewController.m

		@implementation ViewController

		@synthesize shareMachine;

		-(void)viewDidLoad {
			self.shareMachine = [[ShareMachine alloc] initWithDelegate:self];
		}

		-(IBAction)onShareFacebookButtonTap:(id)sender {
			[self.shareMachine shareWithFacebook];
		}

		-(void)didFinishSharing {
			// Do some stuff when the share action has been completed
		}

		-(void)didFailToShareWithError:(NSError *)error {
			// Do some stuff if the share action fails with
			// an error (Error only works for facebook at the
			// moment. Twitter will always return didFinishSharing).
		}

		@end

## Fork that junk yo!

We are always happy to see pull requests for the following things:

- Bug fixes
- New sharing methods
- Any other change that makes the code faster, cleaner, DRYer or better in any other way.

## Requirements

Right now this code is written for iOS5+ and it uses ARC (Automatic Reference Counting).

## License

Copyright (C) 2012 Bonobo [info<EMAIL_ADDRESS>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS 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.

repository: Bonobolabs/ShareMachine

repo_name: Bonobolabs/ShareMachine


text:
# Bee Functional testing framework

### Test Suite
Bunch of tests, that lay down in the subfolder (recursively) with `suite.ini` file. `suite.ini` is basic ini-file, that consists of one section `default`, and a number of fields:
* `core`
* `description` - Test Suite description
* `script` - shebang file to start bee with
* disables:
    * `disabled` - tests that must be skipped
    * `release_disabled` - tests that must be skipped when Bee has been builded with `Release`
    * `valgrind_disabled` - tests that must be skipped when Valgrind is enabled
* `lua_libs` - paths for lua files, that should be copied into the folder, where server is started (delimited with the space, e.g. `lua_libs=lua/1.lua lua/2.lua`)
* `long_run` - mark tests as long, enabled only with `--long` option (delimited with the space, e.g. `long_run=t1.test.lua t2.test.lua`)

Field `core` must be one of:
* `bee` - Test-Suite for Functional Testing
* `app` - Another functional Test-Suite
* `unit` - Unit-Testing Test Suite

### Test
Each test consists of files `*.test(.lua|.py)?`, `*.result`, and may have skip condition file `*.skipcond`.
On first run (without `.result`) `.result` is generated from output.
Each run, in the beggining, `.skipcond` file is executed. In the local env there's object `self`, that's `Test` object. If test must be skipped - you must put `self.skip = 1` in this file. Next, `.test(.lua|.py)?` is executed and file `.reject` is created, then `.reject` is compared with `.result`. If something differs, then 15 last string of this diff file are printed and `.reject` file is saving in the folder, where `.result` file is. If not, then `.reject` is deleted.

#### Python
Files: `<name>.test.py`, `<name>.result` and `<name>.skipcond`(optionaly).
Environment:
* `sql` - `DbConnection` class. Convert our subclass of SQL into IProto query and then decode it. Print into `.result` in YAML. Examples:
    * `sql("select * from t<space> where k<key>=<string|number>[ limit <number>]")`
    * `sql("insert into t<space> values ([<string|number> [, <string|number>]*])")`
    * `sql("delete from t<space> where k<key>=<string|number>")`
    * `sql("call <proc_name>([string|number]*)")`
    * `sql("update t<space> set [k<field>=<string|number> [, k<field>=<string|number>]*] where k<key>=<string|number>"")`
    * `sql("ping")`
* `admin` - `AdminConnection` - simply send admin query on admin port (LUA), then, receive answer. Examples
    * `admin('db.info')`

**Example:**
```python
import os
import time

from lib.admin_connection import AdminConnection
from lib.bee_server import BeeServer

master = server
admin("db.info.lsn") # equivalent to master.admin("db.info.lsn") and server.admin(...)
sql("select * from t0 where k0=1")
replica = BeeServer()
replica.script = 'replication/replica.lua'
replica.vardir = os.path.join(server.vardir, "replica")
replica.deploy()
master.admin("db.insert(0, 1, 'hello')")
print('sleep_1')
time.sleep(0.1)
print('sleep_finished')
print('sleep_2')
admin("require('fiber').sleep(0.1)")
print('sleep_finished')
replica.admin("db.select(0, 0, 1)")
con2 = AdminConnection('localhost', server.admin.port)
con2("db.info.lsn")
replica.stop()
replica.cleanup(True)
con2.disconnect()
```

**Result:**
```yaml
db.info.lsn
---
- null
...
select * from t0 where k0=1
---
- error:
    errcode: ER_NO_SUCH_SPACE
    errmsg: Space '#0' does not exist
...
db.insert(0, 1, 'hello')
---
- error: '[string "return db.insert(0, 1, ''hello'')"]:1: attempt to call field ''insert''
    (a nil value)'
...
sleep_1
sleep_finished
sleep_2
require('fiber').sleep(0.1)
---
...
sleep_finished
db.select(0, 0, 1)
---
- error: '[string "return db.select(0, 0, 1)"]:1: attempt to call field ''select''
    (a nil value)'
...
db.info.lsn
---
- null
...
```

#### Lua
Files: `<name>.test.lua`, `<name>.result` and `<name>.skipcond`(optionaly).
Tests interact only with `AdminConnection`. Supports some preprocessor functions (eg `delimiter`)

**Delimiter example:**
```
db.schema.space.create('temp')
t1 = db.space.temp
t1:create_index('primary', { type = 'hash', parts = {1, 'num'}, unique = true})
t1:insert{0, 1, 'hello'}
--# setopt delimiter ';'
function test()
    return {1,2,3}
end;
test(
);
--# setopt delimiter ''
test(
);
test

```

**Delimiter result:**
```
db.schema.space.create('temp')
---
- index: []
  on_replace: 'function: 0x40e4fdf0'
  temporary: false
  id: 512
  engine: memtx
  enabled: false
  name: temp
  field_count: 0
- created
...
t1 = db.space.temp
---
...
t1:create_index('primary', { type = 'hash', parts = {1, 'num'}, unique = true})
---
...
t1:insert{0, 1, 'hello'}
---
- [0, 1, 'hello']
...
--# setopt delimiter ';' -- !!COMMENTARY - delimiter is changed to ';\n'
function test()
    return {1,2,3}
end;
---
...
test(
);
---
- - 1
  - 2
  - 3
...
--# setopt delimiter '' -- !!COMMENTARY - delimiter is changed back - to '\n'
test(
---
- error: '[string "test( "]:1: unexpected symbol near ''<eof>'''
...
);
---
- error: '[string "); "]:1: unexpected symbol near '')'''
...
test
---
- 'function: 0x40e533b8'
...
```

##### Preprocessor description
prefix `--#` means that this line must processed to preprocessor

__Base directives:__
* `--# setopt delimiter '<delimiter>'` - Sets delimiter to <delimiter>\n

__Server directives:__
* `--# create server <name> with ...` - Create server with name <name>, where `...` may be:
    * `script = '<path>'` - script to start
    * `rpl_master = <server>` - replication master server name
* `--# start server <name>` - Run server <name>
* `--# stop server <name> ` - Stop server <name>
* `--# cleanup server <name> ` - Cleanup (basically after server has been stopped)

__Connection directives:__
* `--# create connection <name-con> to <name-serv>` - create connection named <name-con> to <name-serv> server
* `--# drop connection <name>` - Turn connection <name> off and delete it
* `--# set connection <name>` - Set connection <name> to be main, for next commands

__Filter directives:__
* `--# push filter '<regexp_from>' to '<regexp_to>'` - e,g, `--# push filter 'listen: .*' to 'listen: <uri>'`

__Set variables:__
* `--# set variables '<variable_name>' to '<where>'` - execute `<variable_name> = *<where>` where *<where> is value of where. Where must be
    * `<server_name>.admin` - admin port of this server
    * `<server_name>.master` - listen port of master of this replica
    * `<server_name>.listen` - listen port of this server

repository: cosmic-fibre/bee

repo_name: cosmic-fibre/bee


text:
## Specifications
| Behaviour | Input | Output |
| :---------------- | :---------------: | ------------------: |
| Display all categories | **On page load** | List of various categiroes is displayed on landing page |
| Display pitch from a pitch category | **Click on category** | Redirected to a page with a list of pitches from the category |
| Display the pitch | **On page load** | Each pitch displays the title, content, posted by, on |
| Comment the pitch | **Comment** | Redirected to the sign-in page |
|Profile| **On page load**|The logged in user is able to view their profile-pic, bio, pitches posted and edit their profile|
| Edit profile | **Edit profile** | Redirects the user to a page to update their bio and upload a profile-pic|

repository: GeGe-K/Pitcher-App

repo_name: GeGe-K/Pitcher-App


text:
---
title: Biodesign for the Real-World
layout: project
tagline: "Prototyping bacteria-based Arsenic detection sensors"
description: "We explore prototypes of hardware, software, and wetware in the design of a practical water quality sensors."
permalink: /biodesign
klass: hardware
images: images/biodesign.png
links:
  - icon: home
    url: http://biodesign.cc
  - icon: wikipedia
    url: http://wiki.biodesign.cc
  - icon: github
    url: https://github.com/BioDesignRealWorld
hidden: true
---

BIODESIGN for the REAL WORLD is a transdisciplinary and collaborative research
project addressing water quality with partners in Switzerland,
[(Art)ScienceBLR](http://artscienceblr.org/) in India, and
[Lifepatch](http://lifepatch.org/) in Indonesia.

BIO-DESIGN for the REAL WORLD explores how biology and biotechnology can be designed within social contexts.

As a powerful technological medium after industrial and digital revolutions,
implementation and design solutions for biology and biotechnology must reflect
a diversity of voices to be meaningful in society, not only to be guided by
concerns of a few.

We are interested in
* Real world problems
* Horizontal exchange
* Open and transdisciplinary approach

Read more about our interests, funding, press on the [biodesign wiki](http://wiki.biodesign.cc),


text:
# library-api

## Migrations

```bash
flask db init
flask db migrate
flask db upgrade
```

## Launch (Houston fasten your seat belts, we are going to fly!)

```bash
python run.py
```

## Docker

```bash
docker-compose up --build
```

![Library UML Schema](https://cdn1.bbcode0.com/uploads/2021/7/15/2a85255ed61dfaed5c48b1a3881d90d9-full.jpg)

repository: nightlyds/library-api

repo_name: nightlyds/library-api


text:
---
layout: post
title:  "Glyphicons for Bootstrap"
description: "Glyphicons for Bootstrap"
date:   2013-08-30 12:40:47
categories: bootstrap
tags: [bootstrap]
---

# Glyphicons for Bootstrap

The official Bootstrap icon font, featuring 160 glyphs from [Glyphicons](http://glyphicons.com), ready for use in any Bootstrap project. Includes support for IE8+.

To get started, check out [http://glyphicons.getbootstrap.com](http://glyphicons.getbootstrap.com)!

### Bugs and feature requests

Have a bug or a feature request? [Please open a new issue](https://github.com/twitter/bootstrap/issues). Before opening any issue, please search for existing issues and read the [Issue Guidelines](https://github.com/necolas/issue-guidelines), written by [Nicolas Gallagher](https://github.com/necolas/).

### Contributing

Please read through our guidelines for contributing to Bootstrap. Included are directions for opening issues, coding standards, and notes on development. All HTML and CSS should conform to the [Code Guide](http://github.com/mdo/code-guide), maintained by [Mark Otto](http://github.com/mdo).

### Community

Keep track of development and community news.

* Follow [@twbootstrap on Twitter](http://twitter.com/twbootstrap).
* Read and subscribe to the [The Official Twitter Bootstrap Blog](http://blog.getbootstrap.com).
* Have a question that's not a feature request or bug report? [Ask on the mailing list.](http://groups.google.com/group/twitter-bootstrap)
* Chat with fellow Bootstrappers in IRC. On the `irc.freenode.net` server, in the `##twitter-bootstrap` channel.

### Versioning

For transparency and insight into our release cycle, and for striving to maintain backward compatibility, bootstrap-glyphicons will be maintained under the Semantic Versioning guidelines as much as possible.

Releases will be numbered with the following format:

`<major>.<minor>.<patch>`

And constructed with the following guidelines:

* Breaking backward compatibility bumps the major (and resets the minor and patch)
* New additions without breaking backward compatibility bumps the minor (and resets the patch)
* Bug fixes and misc changes bumps the patch

For more information on SemVer, please visit [http://semver.org/](http://semver.org/).

### Authors

**Mark Otto**

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

### Copyright and license

Copyright 2013 Mark Otto, Inc under [the MIT license](LICENSE).

gha_language: CSS


text:
# cookiecutter-restful-elastalk

This is a [cookiecutter](https://cookiecutter.readthedocs.io/en/latest/) template designed to help you get started with your [Flask-RESTPlus](https://flask-restplus.readthedocs.io/en/stable/) API project.

## Project Features

The project you create from this template has a few features to be aware of including:

* a [Flask-RESTPlus](https://flask-restplus.readthedocs.io/en/stable/) project framework.
* the [elastalk](https://pypi.org/project/elastalk/) library which has some utilities you can use to talk to [Elasticsearch](https://www.elastic.co/products/elastic-stack)
* [pytest](https://docs.pytest.org/en/latest/) unit tests
* a documentation project based on [Sphinx](http://www.sphinx-doc.org/en/master/usage/quickstart.html)

## Getting Started

### Prerequisites

Here are the things you need to install the software and how to install them...

```bash
pip install cookiecutter
```

### Using the Template

#### Step One: Build the project.
You can build a project directly from the github repository.

```bash
cookiecutter https://github.com/Geo-Comm/cookiecutter-restful-elastalk
```

#### Run the `make` Targets

The template contains a cookiecutter [post-generate hook](http://cookiecutter.readthedocs.io/en/latest/advanced/hooks.html) that will attempt to do the following using targets in the project's [Makefile](https://www.gnu.org/software/make/):

You may want to go about this differently according to your processes, but if you want to create a virtual environment for the project, install the dependencies, and set up the comman-line application, you can use the `make` targets defined in the project like so.

There are several other `make` targets so have a look at the `Makefile` if you're interested.

```bash
cd <project-name>
make venv
make install
make build
```

#### Run the Command-Line App

If you have performed the steps above, you should now be able to run the application by the project name.

```bash
<project-name> --help
```

If you get the template help message, you're ready to start building.

## Project Features

The project you create from this template has a few features to be aware of including:

* a [click](http://click.pocoo.org/5/) application to get you going;
* [pytest](https://docs.pytest.org/en/latest/) unit tests; and
* a documentation project based on [Sphinx](http://www.sphinx-doc.org/en/master/usage/quickstart.html).

## Resources

Would you like to learn more?  Check out the links below!

* [Cookiecutter Project Documentation](https://cookiecutter.readthedocs.io/en/latest/)
* [Cookiecutter: Project Templates Made Easy](https://www.pydanny.com/cookie-project-templates-made-easy.html)
* [Flask-RESTPlus](https://flask-restplus.readthedocs.io/en/stable/)
* [pytest](https://docs.pytest.org/en/latest/)
* [Sphinx](http://www.sphinx-doc.org/en/master/usage/quickstart.html)

## Authors

* **Pat Daburu** - *Initial work* - [github](https://github.com/patdaburu)

See also the list of [contributors](https://github.com/patdaburu/cookiecutter-gc-cli/graphs/contributors) who participated in this project.

## License

Copyright (c) 2018-2019 Pat Daburu

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS 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.

repository: patdaburu/cookiecutter-restful-elastalk

gha_language: Python

repo_name: patdaburu/cookiecutter-restful-elastalk


text:
---
id: 17726
title: Audrey Lamy
date: 2021-04-07T20:01:16+00:00
author: Laima
layout: post
guid: https://ukdataservers.com/audrey-lamy/
permalink: /04/07/audrey-lamy/
---

* some text
{: toc}

## Who is Audrey Lamy

Stage and screen star most well known for her long-running role as Marion on the television series Scènes de ménages. She has also appeared in films like Beauty and the Beast (2014) and Polisse.

## Prior to Popularity

Her first acting role was in the 2004 telemovie Milady and the Three Musketeers.

## Random data

A successful stage actress, she spent five years performing her award-winning one-woman show Dernières avant Vegas.

## Family & Everyday Life of Audrey Lamy

Born to Michèle and Michel Lamy, she has one sister, Alexandra.

## People Related With Audrey Lamy

She joined Vincent Cassel and Lea Seydoux in the cast of 2014’s Beauty and the Beast.


text:
# Panorama Orchestration & Azure Virtual WAN
Secure Azure Virtual WAN traffic with Palo Alto Networks VM-Series firewalls.  Please see the [Deployment Guide](https://github.com/wwce/azure-arm-virtual-wan/blob/main/GUIDE.pdf) for more information.

## Overview

This build illustrates how to secure Azure Virtual WAN traffic with VM-Series scale sets. The build is broken down into 5 Parts.  Depending on existing Azure resources, certain parts may not be required.

- **Part 1.** Create Virtual WAN & Virtual Hub

- **Part 2.** Connect VM-Series Inbound Scale Set to the Virtual Hub

- **Part 3.** Connect VM-Series Outbound Scale Set to the Virtual Hub

- **Part 4.** Peer Local VNET to VM-Series Outbound VNET

- **Part 5.** Connect Spoke VNET to Virtual Hub

### Architecture

The build shows two types of traffic flows through a Virtual WAN hub.

1.  Internet inbound traffic through a VM-Series scale set to directly connected hub virtual network (vwan-spoke)
    - Additional scale sets can be added throughout different Azure regions to achieve a globally scalable inbound security edge.
2.  East-West traffic through a VM-Series scale set from a vwan-spoke to a locally peered virtual network
    - This design can be integrated into larger infrastructures that have regional hub and spoke architectures.  The VM-Series in each regional hub VNET, can secure ingress traffic coming from virtual WAN hubs.
    - This can design can also be applied for traffic between ExpressRoute and VNET connections.

### Prerequisites

The following items are required prior to launching the build.

1.  A active Azure subscription with appropriate permissions and resource allocation quota.
2.  Panorama
    - PAN-OS 10.0 or greater
    - Azure Plugin 3.0 or greater
3.  Inbound & Outbound VM-Series scale set within a dedicated VNETs.

**If you do not have the VM-Series deployed, please see [Deployment Guide](https://github.com/wwce/azure-arm-virtual-wan/blob/main/GUIDE.pdf) for how-to.**

##  Guide

####  Part 1:  Create Virtual WAN & Virtual Hub

In this part, a Virtual WAN is created with a virtual hub.  The hub will be used in Parts 2 and 3 to direct traffic from connected spokes to the security VNETs.  If you already have a virtual hub, you can skip this step and proceed to part 2.

[![Deploy To Azure](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/1-CONTRIBUTION-GUIDE/images/deploytoazure.svg?sanitize=true)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fwwce%2Fazure-virtual-wan-connect%2Fmain%2Fpart1_wan.json)

####  Part 2:  Connect Inbound VM-Series Scale Set to the Virtual Hub
Connects an existing security VNET that contains a VM-Series inbound scale set to the virtual hub created in part 1.

[![Deploy To Azure](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/1-CONTRIBUTION-GUIDE/images/deploytoazure.svg?sanitize=true)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fwwce%2Fazure-virtual-wan-connect%2Fmain%2Fpart2_connect_inbound.json)

####  Part 3:  Connect Outbound VM-Series Scale Set to the Virtual Hub
Connects an existing security VNET that contains a VM-Series outbound scale set to the virtual hub created in part 1.

[![Deploy To Azure](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/1-CONTRIBUTION-GUIDE/images/deploytoazure.svg?sanitize=true)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fwwce%2Fazure-virtual-wan-connect%2Fmain%2Fpart3_connect_outbound.json)

####  Part 4:  Peer Local VNET to VM-Series Outbound VNET
Creates a spoke VNET that is peered (via vNet Peering) to the outbound VM-Series VNET.  A route table is created to direct all traffic from the spoke VNET to the outbound firewall's interal load balancer.  A route is also added to the virtual hub's route table.  This route will direct virtual WAN traffic destined to the spoke VNET through the outbound VM-Series VNET connection that was created in part 3.

[![Deploy To Azure](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/1-CONTRIBUTION-GUIDE/images/deploytoazure.svg?sanitize=true)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fwwce%2Fazure-virtual-wan-connect%2Fmain%2Fpart4_create_peer_spoke.json)

####  Part 5:  Connect Spoke VNET to Virtual Hub
Creates a spoke VNET that is directly connected to the virtual hub created in part 1.  This VNET is used to demonstrate/test internet inbound traffic through the inbound VM-Series and also lateral traffic through the outbound VM-Series its local spoke.

[![Deploy To Azure](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/1-CONTRIBUTION-GUIDE/images/deploytoazure.svg?sanitize=true)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fwwce%2Fazure-virtual-wan-connect%2Fmain%2Fpart5_create_vhub_spoke.json)

repository: wwce/azure-arm-virtual-wan

repo_name: wwce/azure-arm-virtual-wan


text:
# MakersBnB

[![Build Status](https://travis-ci.com/ShinyVerse/MakersBnB.svg?branch=master)](https://travis-ci.com/ShinyVerse/MakersBnB)
[![Coverage Status](https://coveralls.io/repos/github/ShinyVerse/MakersBnB/badge.svg)](https://coveralls.io/github/ShinyVerse/MakersBnB)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

This repository is a clean clone of AirBnB which has been implemented by creating a remote API and a separate front end. We created this as a first team project at [Makers Academy](makers.tech), over the course of five days.

## Installation

To clone the project to your local machine run

```sh
git clone https://github.com/shinyverse/makersbnb
```

Next, install all the dependencies using npm:

```sh
npm install
```

### Testing
To run the tests, run:
```sh
npm run test_coverage
```
This runs `nyc` and `jasmine` and will also generate a coverage report locally.

### Usage

Before the front end can be used, the API must be run and hosted. To run the API on your `localhost` run `node api.js`, which will load the api to `http://localhost:3000`. You can choose to host this through `ngrok`, if you like.

Next, go to the `src/inferface.js` file and change the `RootURL` on line 1:
```javascript
let rootURL = 'http://localhost:3000'
```
To open the front end, run `node frontend.js`.

## Technologies
The remote API has been built using Node.js with Express.js for the routing and Mongoose for integration with the MongoDB database. The `Connection` class uses the Mongoose `Schema` constructor to structure the database. The Schema themselves are quite simple:

```javascript
var mongoose = require('mongoose');

const userSchema = new mongoose.Schema({
  name: String,
  email: String,
  password: String
});
```

The front end is powered by jQuery and Express.js. There is an `APIConnection` class in the `src` folder, through which all the other classes access the API. Throughout the front end we used Javascript's `Promise` class to deal with the asynchronicity of API calls. Checking which listings the user has uploaded requires two `then` uses:

```javascript

ListingHandler.prototype.queryOwnListings = function(owner_id) {
  let listings = this.queryListings();
  let output = []
  return listings.then((res, rej) => {        // first then
      for (i = 0; i < res.length; i += 1) {
        if (res[i].owner_id === owner_id) {
          output.push(res[i])
        }
      }
    }).then(() => {                           // second then
      return output
    })
}
```

Lastly, out front end has been very nicely styled with CSS, and is compatible with mobile screens as well as desktop:

![Front Page](images/frontpage.png)

## MVP User stories

We started with a list of five user stories which represented our minimum viable product, all of which have been implemented.

### User authentication
```
As a user
I can sign up
So that I have a unique profile
```
```
As  signed up user
I can sign in
So that I can access my profile
```
### Users can post listings
```
As a signed in user
I can post a listing
So that other users can see it
```
### Users can manage bookings
```
As a signed in user
I can request to book a listing
So that I can stay at a property
```
```
As a signed in user
I can see the bookings I have made
So that I know where I am due to be staying
```

## Team
 - [Laura Jackson](https://github.com/shinyverse)
 - [Cristina María Ocaña Manzano](https://github.com/cristinaocanamanzano)
 - [Andres Faraone-Pirie](https://github.com/afaraone)
 - [Cameron Whitehead](https://github.com/camjw)

## License
This repo is licensed under the MIT license.

## Contributing
We did not have time to:
- Implement password encryption with `bcryptjs`.
- Implement listing images.
- Implement many other features, including payment with [Stripe](https://stripe.com).

If anyone wants to implement these features, or others, we would be happy to receive a pull request.

repository: ShinyVerse/MakersBnB

repo_name: ShinyVerse/MakersBnB


text:
It features an (incomplete) SWI-Prolog foreign language
interface, a utility class that makes it easy querying with Prolog and also a
Pythonic interface.

Since PySWIP uses SWI-Prolog as a shared library and ctypes to access it, it
doesn't require compilation to be installed.

Note that this version of PySWIP is slightly incompatible with 0.1.x versions.

Requirements:
-------------

* Python 2.3 and higher.
* ctypes 1.0 and higher.
* SWI-Prolog 5.6.x and higher (most probably other versions will also work).
* libpl as a shared library.
* Works on Linux and Win32, should work for all POSIX.

Example (Using Prolog):
-----------------------

    >>> from pyswip import Prolog
    >>> prolog = Prolog()
    >>> prolog.assertz("father(michael,john)")
    >>> prolog.assertz("father(michael,gina)")
    >>> list(prolog.query("father(michael,X)"))
    [{'X': 'john'}, {'X': 'gina'}]
    >>> for soln in prolog.query("father(X,Y)"):
    ...     print soln["X"], "is the father of", soln["Y"]
    ...
    michael is the father of john
    michael is the father of gina

Since version 0.1.3 of PySWIP, it is possible to register a Python function as a
Prolog predicate through SWI-Prolog's foreign language interface.

Example (Foreign Functions):
----------------------------

    from pyswip import Prolog, registerForeign

    def hello(t):
        print "Hello,", t
    hello.arity = 1

    registerForeign(hello)

    prolog = Prolog()
    prolog.assertz("father(michael,john)")
    prolog.assertz("father(michael,gina)")
    list(prolog.query("father(michael,X), hello(X)"))

Outputs:
    Hello, john
    Hello, gina

Since version 0.2, PySWIP contains a 'Pythonic' interface which allows writing
predicates in pure Python (*Note that interface is experimental.*)

Example (Pythonic interface):
-----------------------------

    from pyswip import Functor, Variable, Query

    assertz = Functor("assertz", 2)
    father = Functor("father", 2)

    call(assertz(father("michael","john")))
    call(assertz(father("michael","gina")))

    X = Variable()
    q = Query(father("michael",X))
    while q.nextSolution():
        print "Hello,", X.value
    q.closeQuery()

Outputs:
    Hello, john
    Hello, gina

The core functionality of ``Prolog.query`` is based on Nathan Denny's public
domain prolog.py found at
http://www.ahsc.arizona.edu/~schcats/projects/docs/prolog-0.2.0.html

Install
-------

Please see ``INSTALL`` for detailed instructions.

repository: AngryLawyer/pyswip

repo_name: AngryLawyer/pyswip


text:
---
title: Configuration

description:
weight: 1900
doctypes: [""]
toc: true
---

This document describes how to configure the NGINX App Protect module
> Check out the complete [NGINX Ingress Controller with App Protect example resources on GitHub](https://github.com/nginxinc/kubernetes-ingress/tree/v2.0.3/examples/appprotect).

## Global Configuration

The NGINX Ingress Controller has a set of global configuration parameters that align with those available in the NGINX App Protect module. See [ConfigMap keys](/nginx-ingress-controller/configuration/global-configuration/configmap-resource/#modules) for the complete list. The App Protect parameters use the `app-protect*` prefix.

> Check out the complete [NGINX Ingress Controller with App Protect example resources on GitHub](https://github.com/nginxinc/kubernetes-ingress/tree/v2.0.3/examples/appprotect).

## Enable App Protect for an Ingress Resource

You can enable and configure NGINX App Protect on a per-Ingress-resource basis. To do so, you can apply the [App Protect annotations](/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/#app-protect) to each desired resource.

## App Protect Policies

You can define App Protect policies for your Ingress resources by creating an `APPolicy` [Custom Resource](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/).

 > **Note**: The fields `policy.signature-requirements[].minRevisionDatetime` and `policy.signature-requirements[].maxRevisionDatetime` are not currently supported.

 > **Note**: [The Advanced gRPC Protection for Unary Traffic](/nginx-app-protect/configuration/#advanced-grpc-protection-for-unary-traffic) only supports providing an `idl-file` inline. The fields `policy.idl-files[].link`, `policy.idl-files[].$ref`, and
 `policy.idl-files[].file` are not supported. The IDL file should be provided in field `policy.idl-files[].contents`. The value of this field can be base64 encoded. In this case the field `policy.idl-files[].isBase64` should be set to `true`.

To add any [App Protect policy](/nginx-app-protect/policy/#policy) to an Ingress resource:

1. Create an `APPolicy` Custom resource manifest.
2. Add the desired policy to the `spec` field in the `APPolicy` resource.

   > **Note**: The relationship between the Policy JSON and the resource spec is 1:1. If you're defining your resources in YAML, as we do in our examples, you'll need to represent the policy as YAML. The fields must match those in the source JSON exactly in name and level.

  For example, say you want to use the [DataGuard policy](/nginx-app-protect/policy/#policy/data-guard) shown below:

  ```json
  {
      "policy": {
          "name": "dataguard_blocking",
          "template": { "name": "POLICY_TEMPLATE_NGINX_BASE" },
          "applicationLanguage": "utf-8",
          "enforcementMode": "blocking",
          "blocking-settings": {
              "violations": [
                  {
                      "name": "VIOL_DATA_GUARD",
                      "alarm": true,
                      "block": true
                  }
              ]
          },
          "data-guard": {
              "enabled": true,
              "maskData": true,
              "creditCardNumbers": true,
              "usSocialSecurityNumbers": true,
              "enforcementMode": "ignore-urls-in-list",
              "enforcementUrls": []
          }
      }
  }
  ```

  You would create an `APPolicy` resource with the policy defined in the `spec`, as shown below:

  ```yaml
  apiVersion: appprotect.f5.com/v1beta1
  kind: APPolicy
  metadata:
    name: dataguard-blocking
  spec:
    policy:
      name: dataguard_blocking
      template:
        name: POLICY_TEMPLATE_NGINX_BASE
      applicationLanguage: utf-8
      enforcementMode: blocking
      blocking-settings:
        violations:
        - name: VIOL_DATA_GUARD
          alarm: true
          block: true
      data-guard:
        enabled: true
        maskData: true
        creditCardNumbers: true
        usSocialSecurityNumbers: true
        enforcementMode: ignore-urls-in-list
        enforcementUrls: []
  ```

  > Notice how the fields match exactly in name and level. The Ingress Controller will transform the YAML into a valid JSON App Protect policy config.

## App Protect Logs

You can set the [App Protect log configurations](/nginx-app-protect/troubleshooting/#app-protect-logging-overview) by creating an `APLogConf` [Custom Resource](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/).

To add the [App Protect log configurations](/nginx-app-protect/configuration/#security-logs) to an Ingress resource:

1. Create an `APLogConf` Custom Resource manifest.
2. Add the desired log configuration to the `spec` field in the `APLogConf` resource.

   > **Note**: The fields from the JSON must be presented in the YAML *exactly* the same, in name and level. The Ingress Controller will transform the YAML into a valid JSON App Protect log config.

For example, say you want to [log state changing requests](/nginx-app-protect/configuration/#security-log-configuration-file) for your Ingress resources using App Protect. The App Protect log configuration looks like this:

```json
{
    "filter": {
        "request_type": "all"
    },
    "content": {
        "format": "default",
        "max_request_size": "any",
        "max_message_size": "5k"
    }
}
```

You would define that config in the `spec` of your `APLogConf` resource as follows:

```yaml
apiVersion: appprotect.f5.com/v1beta1
kind: APLogConf
metadata:
  name: logconf
spec:
  filter:
    request_type: all
  content:
    format: default
    max_request_size: any
    max_message_size: 5k
```
## App Protect User Defined Signatures

You can define App Protect [User Defined Signatures](https://docs.nginx.com/nginx-app-protect/configuration/#user-defined-signature-definitions) for your Ingress resources by creating an `APUserSig` [Custom Resource](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/).

 > **Note**: The field `revisionDatetime` is not currently supported.

> **Note**: `APUserSig` resources increase the reload time of NGINX Plus compared with `APPolicy` and `APLogConf` resources. Refer to [NGINX Fails to Start or Reload](/nginx-ingress-controller/app-protect/troubleshooting/#nginx-fails-to-start-or-reload) for more information.

To add the [User Defined Signatures](https://docs.nginx.com/nginx-app-protect/configuration/#user-defined-signature-definitions) to an Ingress resource:

1. Create an `APUserSig` Custom resource manifest.
2. Add the desired User defined signature to the `spec` field in the `APUserSig` resource.

   > **Note**: The fields from the JSON must be presented in the YAML *exactly* the same, in name and level. The Ingress Controller will transform the YAML into a valid JSON App Protect User Defined signature. There is no need to reference the user defined signature resource in the ingress resource.

For example, say you want to create the following user defined signature:

```json
{  "softwareVersion": "15.1.0",
    "tag": "Fruits",
    "signatures": [
      {
      "name": "Apple_medium_acc",
      "rule": "content:\"apple\"; nocase;",
      "signatureType": "request",
      "attackType": {
         "name": "Brute Force Attack"
      },
      "systems": [
         {"name": "Microsoft Windows"},
         {"name": "Unix/Linux"}
                     ],
      "risk": "medium",
      "accuracy": "medium",
      "description": "Medium accuracy user defined signature with tag (Fruits)"
      }
   ]
}
```

You would add that config in the `spec` of your `APUserSig` resource as follows:

```yaml
apiVersion: appprotect.f5.com/v1beta1
kind: APUserSig
metadata:
  name: apple
spec:
  signatures:
  - accuracy: medium
    attackType:
      name: Brute Force Attack
    description: Medium accuracy user defined signature with tag (Fruits)
    name: Apple_medium_acc
    risk: medium
    rule: content:"apple"; nocase;
    signatureType: request
    systems:
    - name: Microsoft Windows
    - name: Unix/Linux
  softwareVersion: 15.1.0
  tag: Fruits
```

repository: gamunu/kubernetes-ingress

repo_name: gamunu/kubernetes-ingress


text:
VueJS - Environment Setup
Advertisements
 Previous Page Next Page
There are many ways to install VueJS. Some of the ways on how to carry out the installation are discussed ahead.

Using the <script> tag directly in HTML file
<html>
   <head>
      <script type = "text/javascript" src = "vue.min.js"></script>
   </head>
   <body></body>
</html>
Go to the home site https://vuejs.org/v2/guide/installation.html of VueJS and download the vue.js as per need. There are two versions for use - production version and development version. The development version is not minimized, whereas the production version is minimized as shown in the following screenshot. Development version will help with the warnings and debug mode during the development of the project.

Installation
Using CDN
We can also start using VueJS file from the CDN library. The link https://unpkg.com/vue will give the latest version of VueJS. VueJS is also available on jsDelivr (https://cdn.jsdelivr.net/npm/vue/dist/vue.js) and cdnjs (https://cdnjs.cloudflare.com/ajax/libs/vue/2.4.0/vue.js).

We can host the files at our end, if required and get started with VueJS development.

Using NPM
For large scale applications with VueJS, it is recommended to install using the npm package. It comes with Browserify and Webpack along with other necessary tools, which help with the development. Following is the command to install using npm.

npm  install vue
Using CLI Command Line
VueJS also provides CLI to install the vue and get started with the server activation. To install using CLI, we need to have CLI installed which is done using the following command.

npm install --global vue-cli
CLI Command Line
Once done, it shows the CLI version for VueJS. It takes a few minutes for the installation.

+<EMAIL_ADDRESS>added 965 packages in 355.414s
Following is the command to create the project using Webpack.

vue init webpack myproject
Select Command Prompt
To get started, use the following command.

cd myproject
npm install
npm run dev
Command Prompt
NPM
Once we execute npm run dev, it starts the server and provides the url for display to be seen in the browser which is as shown in the following screenshot.

Welcome to VueJS
The project structure using CLI looks like the following.

repository: jmmedel/VueJs-Guide

repo_name: jmmedel/VueJs-Guide


text:
This project that I have started, is part of my main project. Here at C-programming, I will teach how to program using C language.
I am currently following this book:
Computer Science(A structured programming approach using C) by Behrouz A. Forouzan & Richard F. Gilberg.

The way I will be conducting my website is quiet simple:
1. I will provide examples, and leave rest upto the reader.
As having "strong will" is one essential attribute for success.
2. I will not dive too much in texts, but will definetly provide resources when possible or refer to appropriate books name, etc.
3. Most important, and most ambitious part of my website is to develop a system that can capture the user enter code and compile it and give you results on your end.(But as I said, this will take lot of time.)
4. I will teach you how to setup C compiler on your system, mostly preferred windows, as I do not own a Mac.

How to use my website resources:
Go through examples and retype them on your system, and run them and see where mistakes have occured. Or type them on provided website space(once the feature is made available). If you feel confident, then read the problem description and jump right into coding and test them with given testcases.

Please not, that the project is in its infact stage, and need lot of work. I am doing my best to speed up as fast I can, but being a Computer Engineering undergrad student I have other academic commitments too. Please be patient with me.

repository: asheemchhetri/C-programming

repo_name: asheemchhetri/C-programming


text:
# SeleniumTests

This is a sample test project based on STF (SeleniumTestsFramework).
To know more about STF please refer
STF [How-To guide](http://www.seleniumtests.com/2013/10/announcing-selenium-tests-automation.html)

This test suite also include tests for android mobile site, android app and ios test as well, hence you must set up Appium before executing tests. Refer [Appium Beginners Tutorials](http://www.seleniumtests.com/p/appium-tutorial.html) before running test else mobile site and mobile app tests would fail

If you use SauceLabs then you can pass Sauce Lab URL to execuete test on desired browser/app. Have a look at testng.xml for more details

You can clone this project and run tests as

```mvn clean test```

Once test execution is over then you would find step by step report of all the test steps under -

```<path to your cloned directory>/seleniumtests/target/surefire-reports/SeleniumTestReport.html```

Have a question or feature request for STF? post it in [Testing Forum](http://www.seleniumtests.com/p/testing-forum.html) :-)


text:
# Kubernetes toolbox

[![Container image on Quay](https://quay.io/repository/shelman/ktoolbox/status "Docker Repository on Quay")](https://quay.io/repository/shelman/ktoolbox)

Launch a shell in a semi-persistent pod on a cluster, with automatic expiration when idle.

When running `ktoolbox` it will check if an existing toolbox pod is running,
then exec into it and start a bash shell. If the pod does not exist, or has
exited, the script will (re)create it before proceeding.

The default maximum idle time before exiting is 180 minutes, but can be
customized using the `-i` flag.

```% ktoolbox
 _______          _ _                              Node: gke-myproject-cluster-nodes-df48b632-bcb2
|__   __|        | | |                          Host IP: <IP_ADDRESS>
   | | ___   ___ | | |__   _____  __      Pod Namespace: default
   | |/ _ \ / _ \| | '_ \ / _ \ \/ /           Pod Name: toolbox-dln
   | | (_) | (_) | | |_) | (_) >  <              Pod IP: <IP_ADDRESS>
   |_|\___/ \___/|_|_.__/ \___/_/\_\    Service Account: default

default/toolbox-dln:~$
```

## Installation

Copy [the ktoolbox script](https://raw.githubusercontent.com/dln/ktoolbox/master/ktoolbox)
somewhere within your `$PATH` and make it executable. Enjoy!

### One line system-wide install:
```
sudo curl -L https://git.io/JeCE4 -o /usr/local/bin/ktoolbox && sudo chmod +x /usr/local/bin/ktoolbox
```

## Usage

```
  ktoolbox [-c image] [-i max_idle_mins] [-n namespace] [-N name] [cmd...]
    -h                 Display this help message.
    -f                 Force recreation of toolbox pod even if running.
    -N NAME            Use given container name instead of the default (toolbox-$USER).
                       Can also be set using KTOOLBOX_NAME environment variable.
    -n NAMESPACE       Use given namespace instead of context default.
                       Can also be set using KTOOLBOX_NAMESPACE environment variable.
    -i MAX_IDLE_MINS   Max idle time in minutes before exiting. 180 mins by default.
                       Can also be set using KTOOLBOX_MAX_IDLE_MINS environment variable.
    -c IMAGE           Override default container image (dlneintr/toolbox:latest).
                       Can also be set using KTOOLBOX_IMAGE environment variable.
```

## Customizing the container
The default container image contains various useful utilities, but may be customized to taste.
Any image may be used as long as it has `bash` and `curl` installed, since
these are used in the entrypoint script to handle expiration.

Easiest is to make a custom Dockerfile like this:

```
FROM quay.io/shelman/ktoolbox
RUN sudo apk add -U --no-cache memcached redis
```

You can override the image used by ktoolbox with either the `-c` flag or,
more conveniently, by setting the `KTOOLBOX_IMAGE` environment variable.

## Extra tooling
To keep the image size down, the default container has only a few basics installed.
However, it includes a few convenience scripts to afford download and installation
of more tools.

Included installers:

- `install-gcloud.sh` -- Installs [Google Cloud SDK](https://cloud.google.com/sdk)

repository: dln/ktoolbox

gha_language: Shell

repo_name: dln/ktoolbox


text:
# PyGame-KeyHook
[![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/Sigmanificient/PyGame-KeyHook/badges/quality-score.png?b=main)](https://scrutinizer-ci.com/g/Sigmanificient/PyGame-KeyHook/?branch=main)
[![Build Status](https://scrutinizer-ci.com/g/Sigmanificient/PyGame-KeyHook/badges/build.png?b=master)](https://scrutinizer-ci.com/g/Sigmanificient/MyJohnCracker/build-status/master)
![Lines of code](https://img.shields.io/tokei/lines/github/Sigmanificient/PyGame-KeyHook)
![GitHub repo size](https://img.shields.io/github/repo-size/Sigmanificient/PyGame-KeyHook)

A pygame key hook program that show to key you pressing in realtime at the bottom right of your screen

repository: Sigmanificient/PyGame-KeyHook

repo_name: Sigmanificient/PyGame-KeyHook


text:
> [Go to French version](/fr/Règlements/Décrets,%20ordonnances%20et%20règlements%20statutaires/2009/15.md)

# Regulations Adding Perfluorooctane Sulfonate and Its Salts to the Virtual Elimination List

**SOR/2009-15**

Enabling authorities:
- [PERFLUOROOCTANE SULFONATE VIRTUAL ELIMINATION ACT](/en/Acts/Statutes%20of%20Canada/2008/c.%2013.md)

Date registered: 13 January 2009

----------

The Minister of the Environment and the Minister of Health, pursuant to subsection 3(1) of the [Perfluorooctane Sulfonate Virtual Elimination Act](/en/Acts/Statutes%20of%20Canada/2008/c.%2013.md)[a], hereby make the annexed Regulations Adding Perfluorooctane Sulfonate and Its Salts to the Virtual Elimination List.

a: S.C. 2008, c. 13

Ottawa, December 7, 2008

JIM PRENTICE
*Minister of the Environment*

Ottawa, January 9, 2009

LEONA AGLUKKAQ
*Minister of Health*

## Addition

**1** Perfluorooctane sulfonate and its salts are added to column 1 of the [Virtual Elimination List](/en/Regulations/Statutory%20Orders%20and%20Regulations/2006/298.md)[1], compiled under subsection 65(2) of the [Canadian Environmental Protection Act, 1999](/en/Acts/Statutes%20of%20Canada/1999/c.%2033.md)[2].

1: SOR/2006-298

2: S.C. 1999, c. 33

## Coming into Force

**2** These Regulations come into force on the day on which they are registered.

repository: TravisMadill/CanadianLaws

path: /en/Regulations/Statutory Orders and Regulations/2009/15.md

repo_name: TravisMadill/CanadianLaws


text:
# Welcome to the Cosmos Docs!

![cosmonaut reading the cosmos docs in space](./graphics/cosmos-docs.jpg)

Cosmos is a decentralized network of independent parallel blockchains, each powered by classical BFT consensus algorithms like Tendermint.

The first blockchain in the Cosmos Network is the Cosmos Hub, whose native token is the Atom. Cosmos is a permission-less network, meaning that anybody can build a blockchain on it.

Cosmos can interoperate with multiple other applications and cryptocurrencies. By creating a new zone, you can plug any blockchain system into the Cosmos hub and pass tokens back and forth between those zones, without the need for an intermediary.

## Quick Start

- [Getting started with the SDK](./sdk/core/intro.md)
- [SDK Examples](../examples)
- [Join the testnet](./getting-started/join-testnet.md#run-a-full-node)

## Edit the Documentation

See [this file](./DOCS_README.md) for details of the build process and
considerations when making changes.

## Version

This documentation is built from the following commit:

repository: beyondprotocol/cosmos-sdk

branch_name: refs/heads/develop

repo_name: beyondprotocol/cosmos-sdk


text:
# Polynya_EGU_TC
Codes to reproduce the results of Heuzé and Lemos (subm 2020), under revision for The Cryosphere.

-----

To reproduce section 3.1 (reference polynya dates from NSIDC):

1- produce your own longitude and latitude grid adapted to your NSIDC data, or use lat_nsidc.dat and lon_nsidc.dat;

2- use get_polynya_dates.m and/or edge_sic.m on already downloaded NSIDC sea ice concentration data.

------

To reproduce section 3.2 (criterion determination by comparing years with / without polynya):

1- apply cloud filter, produce human-readable dates, and put all APP images into one matrix per band using prepare_APP.m;

2- the geographical and temporal tests of section 3.2 are all in find_criterion_APP.m.

------

To reproduce appendix A (cloud mask validation), use in this order:

1- readmodis.py then cloud_from_MYD35.m on already downloaded MYD35_L2 data;

2- cloud_from_APP.m on already downloaded APP data;

3- comparecloudmasks.m on the output generated by steps 1 and 2.


text:
Project Implementation Description & Explanation
=========

Keyboard Shortcuts
--------------------
---
- Press "r" to start/stop audio recording.
- Press "z" to download zip containing audio files.
- Press "t" to fetch TTS audio files.

Project Implementation Description & Explanation
--------------------
---
- People want to interact with the content of a recorded video presentation more directly if the recording included the semantic structure of the content rather than just raster images.
- For example, viewers may copy and paste the text from the slides, click on links, give feedback, and jump to logical segments.
- By creating a system to record and playback video-like content and audio playback with the semantic meaning intact via HTML will meet this need.
- The implementation will include adding features to a recorded video presentation with audio playback such as copy and paste text from the slides, clicking on links, giving feedback, and jumping to logical segments.
- The video presentation is going to record audio and video for later playback with the use of the audio-slideshow reveal.js plugin by rajgoel on GitHub.

How to Create an HTML Slide
--------------------
---

"Video" Slideshow Presentation Player

Created/Presented by: Mark Neitzel

Major: Bachelors of Science in Computer Science

Advisor: Dr. Hayes

Source Code Repository
--------------------
---
- Source Code Repository

path: /Documents/Project Implementation Description & Explanation.md


text:
# Consul.conf

![Version](https://img.shields.io/badge/version-1.0-lightgrey.svg?style=flat)
[![Docker pulls](https://img.shields.io/docker/pulls/lukaszlach/consul-conf.svg?label=docker+pulls)](https://hub.docker.com/r/lukaszlach/consul-conf)
[![Donate PayPal](https://img.shields.io/badge/donate-PayPal-yellow.svg?style=flat)](https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=lach@php5.pl&lc=US&item_name=Consul.conf&no_note=0&cn=&curency_code=USD&bn=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted)

**Consul.conf** provides responsive web interface for managing configuration of your services in [Consul](https://www.consul.io/) key-value storage through beautiful and customizable dashboards built with [Material Design for Bootstrap](https://mdbootstrap.com/) and [Phalcon Framework](https://github.com/phalcon/cphalcon).

![](https://user-images.githubusercontent.com/5011490/36346134-0b77573a-1439-11e8-81be-722b0e89f2a6.png)

**Consul.conf** is [easy to install](#install) and [integrate](#quick-guide) as only creating one single key in Consul key-value is required to introduce your first dashboard. All already existing fields will be visible inside the web interface and can only use some customization.

- **Standalone** - distributed as a lightweight Docker image, installable with automated script.
- **[Different field types](docs/CUSTOMIZE.md#customizing-field)** - as different types of information require different types of fields, choose either [text](docs/CUSTOMIZE.md#text), [select](docs/CUSTOMIZE.md#select) or [checkbox](docs/CUSTOMIZE.md#checkbox).
- **[Look-and-feel](docs/CUSTOMIZE.md)** - [customize your dashboards](docs/CUSTOMIZE.md#customizing-dashboard) by changing color, icon or hiding unconfigured fields. Much more can be done when [customizing fields](docs/CUSTOMIZE.md#customizing-field) you can also pass default value, read-only or hidden flag.
- **Responsive** - works fine on tablet and mobile phone.
- **Stateless** - dashboards and fields are stored in Consul key-value, meaning Consul.conf can be run on your local machine or any server having access to Consul API and it will be able to fetch all your dashboards and customizations. It also works well with any [existing key structure it finds](#integrate).
- **[Event notifications](docs/CONFIGURE.md#notifications)** - send message to [Slack](docs/CONFIGURE.md#slack) or [HipChat](docs/CONFIGURE.md#hipchat) channel when event happens, for example user logs in or changes the value of a field on dashboard.
- **[Basic](docs/CONFIGURE.md#basic) and [LDAP](docs/CONFIGURE.md#ldap) authorization** support.
- **[HTTPs](docs/CONFIGURE.md#https)** support.

## Install

![](https://img.shields.io/badge/docker-17.05+-lightgrey.svg?style=flat)
![](https://img.shields.io/badge/docker--compose-3+-lightgrey.svg?style=flat)

Use automated install script that pulls Docker image, creates directory structure and configuration files and installs start/stop commands for you, by executing below command. If you prefer to do it manually - proceed with [usage instructions](#run-manually), Docker image will be downloaded automatically on first usage.

```bash
export CONSUL_CONF_VERSION=1.0
curl -L "https://raw.githubusercontent.com/lukaszlach/consul-conf/$CONSUL_CONF_VERSION/install" | bash
```

You will see "Consul.conf installed and running" message after installation is done, configuration directory `/etc/consul-conf` holds `consul-conf.conf` that allows you to modify settings. Installation process also adds `consul-conf-start` and `consul-conf-stop` management commands.

> On default settings Consul.conf listens on port 8080.

You can use the same commands to upgrade (or downgrade) Consul.conf, all your configuration values, dashboards and fields will be preserved. Just change `CONSUL_CONF_VERSION` to desired version.

Read the [Troubleshooting Guide](docs/TROUBLESHOOTING.md) in case of problems with connecting to Consul HTTP API or running the Docker image.

### Install examples

Optionally you can install example fully customized dashboards by executing below command. Script expects Consul HTTP API on `http://localhost:8500`, you can change it with `CONSUL_API_URL` environment variable.

```bash
curl -L "https://raw.githubusercontent.com/lukaszlach/consul-conf/$CONSUL_CONF_VERSION/install-examples" | bash
```

## Quick guide

Below examples expect Consul API available on `localhost:8500` and Consul.conf listening on `localhost:8080`. See all different ways you can [store new value inside Consul key-value storage](docs/CONSUL.md#storing-values-in-key-value-storage).

### Step 1. Create dashboard

```bash
# create dashboard under "project/" base path
curl -X PUT -d '{"name": "Example dashboard", "color": "deep-purple"}' \
    http://localhost:8500/v1/kv/project/.dashboard/.config
```

### Step 2. Create field

```bash
# set value for "project/key" path
curl -X PUT -d 'value' \
    http://localhost:8500/v1/kv/project/key

# create dashboard field for "project/key" path
curl -X PUT -d '{"name": "Example key", "icon": "rocket"}' \
    http://localhost:8500/v1/kv/project/.dashboard/key
```

### Step 3. See how it looks like

Visit [http://localhost:8080](http://localhost:8080), you will see a dashboard list with your newly added "Example dashboard" already available. On the dashboard itself you can see "Example key", change it's value and save in Consul key-value storage.

You can now configure your projects basing on the value of `project/key` key in Consul key-value storage and use Consul.conf to handle and propagate it's changes.

![](https://user-images.githubusercontent.com/5011490/36344842-7e7550ac-1420-11e8-86a4-843d2dce816a.png)

Dashboard list: http://localhost:8080/d

![](https://user-images.githubusercontent.com/5011490/36344862-031ef6e6-1421-11e8-9227-78c881142534.png)

Example dashboard: http://localhost:8080/d/project

## Customize

Consul.conf allows customizing dashboards and fields by setting their name, description and look-and-feel attributes like color or icon.

See separate document on how to [create and customize dashboards and fields](docs/CUSTOMIZE.md).

## Configure

Consul.conf is configured using `/etc/consul-conf/consul-conf.conf` file which is used by `docker-compose.yml` file from the same directory to start and stop the service, environment variables are passed automatically. This file has simple `FIELD=value` structure, all lines starting with `#` are ignored.

> If you are running Docker image manually, you need to pass environment variables manually as well.

See separate document for [list of currently recognized configuration options](docs/CONFIGURE.md).

## Integrate

Consul.conf works easily with any existing key structure it finds, it mainly looks for `.dashboard/.config` key when scanning for dashboards. When such key is found, even with empty JSON object inside - it's base path will be visible inside the web UI as separate dashboard.

By default all existing keys will be visible and editable using text inputs, even when no corresponding field configuration key is present in Consul key-value storage. All found nested keys are also rendered.

## Monitor

Docker container logs all important events with details - all entries include username of logged in user and his IP address. Access logs from nginx are also passed, although limited to non-GET requests. Some environment variables' values are hidden in logs, mostly these holding credentials, ACL tokens etc.

You can view logs by executing `docker logs consul_conf -f` but it is recommended to forward them to external aggregator like syslog.

Example log output:

```
[2018-02-16T20:57:45+00:00] [uid=admin, ip=<IP_ADDRESS>] Logged in
<IP_ADDRESS> - - [16/Feb/2018:20:57:45 +0000] "POST /login HTTP/1.1" 200 5

[2018-02-16T20:58:57+00:00] [uid=admin, ip=<IP_ADDRESS>] Stored project/string-key=value
[2018-02-16T20:58:57+00:00] [uid=admin, ip=<IP_ADDRESS>] Stored project/select-key=option3
[2018-02-16T20:58:57+00:00] [uid=admin, ip=<IP_ADDRESS>] Stored project/checkbox-key=true
<IP_ADDRESS> - - [16/Feb/2018:20:58:57 +0000] "POST /d/project/config HTTP/1.1" 200 14
```

## Troubleshooting

[Troubleshooting guide](docs/TROUBLESHOOTING.md) is available in separate document.

## Build from source

```bash
git clone https://github.com/lukaszlach/consul-conf.git consul-conf/
cd consul-conf/
# build consul-conf:dev Docker image
make DOCKER_IMAGE_TAG=dev
```

## Run manually

You can use `docker-compose-example.yml` found in this repository as a base for your configuration and call `docker-compose up -d` to run it.

Although, if you still want to use raw `docker` command:

```bash
# minimal example
docker run -d \
    -p 8080:80 \
    -v /etc/consul-conf:/etc/consul-conf \
    -e CONSUL_API_URL=http://consul.service.consul:8500 \
    --name consul_conf \
    lukaszlach/consul-conf:latest

# complex example
docker run -d \
    -p 8080:80 \
    -v /etc/consul-conf:/etc/consul-conf \
    -e HTTPS_PORT=443 \
    -e HTTP_ALLOW=<IP_ADDRESS>/0 \
    -e CRYPT_KEY=A3oj5abcadegkfgj2Vh \
    -e CONSUL_API_URL=http://consul.service.consul:8500 \
    -e CONSUL_ACL_TOKEN=custom-acl-token \
    -e BASIC_AUTH=admin:admin \
    -e LDAP_ENABLED=1 \
    -e LDAP_URL=ldaps://ldap.service.consul:636 \
    -e LDAP_ATTR_UID=uid \
    -e LDAP_BIND_DN=ou=users,ou=team,dc=company \
    -e NOTIFY_HIPCHAT=1 \
    -e HIPCHAT_API=https://hipchat.server.com/ \
    -e HIPCHAT_ROOM=123 \
    -e HIPCHAT_TOKEN=XTlyCeYH8rFhgjA4sJ8tu8UBnYhrmFOTPr5gM3J0 \
    -e NOTIFY_SLACK=1 \
    -e SLACK_ROOM=consul-conf \
    -e SLACK_URL=https://hooks.slack.com/services/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 \
    --name consul_conf \
    lukaszlach/consul-conf:latest
```

## Licence

MIT License

Copyright (c) 2018 Łukasz Lach<EMAIL_ADDRESS>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS 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.

repository: bngopale/consul-conf

repo_name: bngopale/consul-conf