text:
# unleash-client-clojure

[![Clojars Project](https://img.shields.io/clojars/v/unleash-client-clojure.svg)](https://clojars.org/unleash-client-clojure)
[![Coverage Status](https://coveralls.io/repos/github/AppsFlyer/unleash-client-clojure/badge.svg?branch=master)](https://coveralls.io/github/AppsFlyer/unleash-client-clojure?branch=master)

A Clojure library wrapping [unleash java client](https://github.com/Unleash/unleash-client-java)

## Usage

### Getting feature toggles

```clojure
(require '[unleash-client-clojure.unleash :as u]
         '[unleash-client-clojure.builder :as b])
;; a simple client
(def unleash (u/build (b/app-name "app-name") (b/unleash-api "http://unleash.herokuapp.com/api/")))
;; simple toggle
(u/enabled? unleash "Bit")
;; toggle with context
(require '[unleash-client-clojure.context :as c])
(def user-context (c/build (c/user-id "user-id")))
(u/enabled? unleash "toggle-name" user-context false)
;; more configuration can be passed by using the functions in the builder namespace
(require '[unleash-client-clojure.builder :as b])
(def unleash (u/build "app-name" "instance-id" "http://unleash.herokuapp.com/api/" (b/environment "staging") (b/fetch-toggles-interval 15)))
```

### Variant support

```clojure
(require '[unleash-client-clojure.variant :as v])
(u/get-variant unleash "DemoVariantWithPayload")
(let [x (u/get-variant unleash "DemoVariantWithPayload")]
  [(v/get-name x)
   (v/get-type x)
   (v/variant-enabled? x)
   (v/get-value x)])
```

### Advanced client config

```clojure
;; the builder namespace supports passing builder confgurations as functions
(require '[unleash-client-clojure.builder :as b])
(def unleash (u/build
               (b/app-name "app-name")
               (b/unleash-api "http://unleash.herokuapp.com/api/")
               (b/environment "staging")
               (b/fetch-toggles-interval 1)))
;; see the builder namespace for more available options
```

### Subscriber support

```clojure
;; one a subscriber can be pased to the client builder by passing
(b/subscriber my-subscriber)
;; the subscriber namespace has functions to help you build a subsriber
(require '[unleash-client-clojure.subscriber :as s])
;; pass a map with the keys [:on-error :on-event :toggle-evaluated
;; :toggles-fetched :client-metrics :client-registered :toggles-backed-up
;; :toggle-backup-restored] and callbacks you want to register.
;; any missing key defaults to no-op
;; this is a very noisy example:
(def unleash
  (u/build
    (b/app-name "app-name")
    (b/unleash-api "http://unleash.herokuapp.com/api/")
    (b/subscriber
      (s/build {:on-event println})))
```

#### TODO:

- [ ] Integration testing

repository: avirogalsky/unleash-client-clojure

gha_language: Clojure

repo_name: avirogalsky/unleash-client-clojure


text:
# PixelDraw
Paint Software that lets you draw geometrical patterns.
Language: Processing

# Screenshot
![Alt text](https://github.com/svr8/PixelDraw/blob/master/Screenshot.PNG "Sample shapes")

license: MIT

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
This game began with code from JumpJump by [user Greggman](http://github.com/greggman).

JumpJump is a sample game for the [HappyFunTimes party games system](http://greggman.github.io/HappyFunTimes).

Asset Attribution for the original assets
-----------

Bird

Name:Nooks

Link: http://forums.tigsource.com/index.php?topic=9353.0

Bricks

Name: SpiderDave

Link: http://opengameart.org/content/bricks-tilable


text:
# Changelog

All notable changes to `laravel-licenser` will be documented in this file.

### 4.0.1
- Fixed deallocation issue

### 4.0.0
- Deallocation logic

### 3.5.7
- Added flags to command

### 3.5.6
- Fixed console output errors

### 3.5.5
- Fixed type error for the `choice` function

### 3.5.4
- One day I'll get the file paths correct everytime all the time.

### 3.5.3
- Fixed config file path in provider (again)

### 3.5.2
- Fixed wrong config file in provider

### 3.5.1
- Now publishes the config file

### 3.5.0
- Added `license:update` Command

### 3.4.0
- Added `__toString()` method

### 3.3.0
- Added a getter for the owner of the license

### 3.2.2
- Fixed passing the correct parameters for the success function

### 3.2.1
- Fixed creating default entries in the database

### 3.2.0
- Added an 'success' function to License

### 3.1.0
- Added an 'error' function to License

### 3.0.0
- Added abstract name function

### 2.0.1
- Fixed abstract function definitions

### 2.0.0
- Changed 'HasLicenses' Api

### 1.1.0
- Can now automatically add licenses when checking if there are any available

### 1.0.2
- Fixed adding or subtracting licenses by 0

### 1.0.1
- Added publish option for older versions of Laravel.
- Fixed setting a new value for the license amount.
- Fixed Typo with LicenseException

### 1.0.0
- Initial release and connected with packagist.

gha_language: PHP

gha_license_id: MIT


text:
# Security Policy

## Supported Versions

We are only actively supporting 5.2.x right now.  If for some reason you need a patch to a previous version please open an issue with the specifics and we will see if we can accomodate you.

| Version | Supported          |
| ------- | ------------------ |
| 5.2.x   | :white_check_mark: |
| 5.1.x   | :x:                |
| 5.0.x   | :x:                |
| < 5.0   | :x:                |

## Reporting a Vulnerability

If you notice a vulnerability please open an issue here in Github with a link to the CVE

repository: boostchicken/spring-data-dynamodb

branch_name: refs/heads/develop

gha_language: Java

repo_name: boostchicken/spring-data-dynamodb


text:
# Important
## We are only writing/persisting on slave machine
## so, backup operation should be done on slave machine

# RDB + AOF together

With AOF, the process is a little bit more involved. When Redis starts, it looks at the AOF log as the primary source of information because it has always the newest data available. The problem is that if we only have a RDB snapshot and no AOF log (or we have a log but it has been affected by the accident so we cannot use it), Redis would still use the AOF log as the only data source. And since the log is missing (same as empty), it would not load any data at all and create a new empty snapshot file.

The following solution takes advantage of the fact that you can recreate the AOF log from the current dataset even if the AOF mode is currently disabled.

Similar to the RDB only, without AOF section, take down the server, delete any snapshots and logs and finally copy the backup dump.rdb file.
```
$ sudo rm -f dump.rdb appendonly.aof
$ sudo cp /backup/dump.rdb .
$ sudo chown redis:redis dump.rdb

```

Now the interesting part. Go to the configuration file (/etc/redis/redis.conf) and disable AOF:

`appendonly no`
Next, start the Redis server and issue the BGREWRITEAOF command:
```
$ sudo monit start redis-server
$ redis-cli BGREWRITEAOF

```

It might take some time, you can check the progress by looking at the aof_rewrite_in_progress value from the info command (0 - done, 1 - not yet):

`$ redis-cli info | grep aof_rewrite_in_progress`
Once it's done, you should see a brand new appendonly.aof file. Next, stop the server, turn the AOF back on and start the server again.

Now you might be asking why we don't just backup the AOF log. The answer is that you could but the AOF logs tend to get really large and we don't usually want to waste disk space.

## redis_backup.sh is in the same directory

# Edit crontab

# Do BGSAVE, every 15 mins, 5 mins before backup
10,25,40,55 * * * *  redis-cli bgsave

# Every 15 mins
0,15,30,45 * * * * /root/backup.sh >> /var/log/redis-backup.log

repository: f/koding

gha_language: CoffeeScript

repo_name: f/koding


text:
![logo](https://raw.githubusercontent.com/SelfhostedPro/Yacht/master/readme_media/Yacht_logo_1_dark.png "templates")

[![Docker Hub Pulls](https://img.shields.io/docker/pulls/selfhostedpro/yacht?color=%2341B883&label=Docker%20Pulls&logo=docker&logoColor=%2341B883&style=for-the-badge)](https://hub.docker.com/r/selfhostedpro/yacht)
[![Docker Image Size](https://img.shields.io/docker/image-size/selfhostedpro/yacht/vue?color=%2341B883&label=Image%20Size&logo=docker&logoColor=%2341B883&style=for-the-badge)](https://hub.docker.com/r/selfhostedpro/yacht)
[![Open Collective](https://img.shields.io/opencollective/all/selfhostedpro.svg?color=%2341B883&logoColor=%2341B883&style=for-the-badge&label=Supporters&logo=open%20collective)](https://opencollective.com/selfhostedpro "please consider helping me by either donating or contributing")

## Yacht

Yacht is a container management UI with a focus on templates and 1-click deployments.

**I'm currently rewriting the backend in Typescript as an attempt to have a language that more people would contribute to. You can follow development of that [here](https://github.com/SelfhostedPro/yacht-api).**

**Please note, that while we are rewriting the back end. The Yacht.sh website is outdated on its instructions, please visit https://dev.yacht.sh for now. The main Yacht.sh site will be updated with the new release.**

## Demo:

![Tempaltes](https://raw.githubusercontent.com/SelfhostedPro/Yacht/master/readme_media/Yacht-Demo.gif "templates")

## Installation:

Currently only linux has been verified as working but we are open to the idea of supporting windows eventually as well.

**Keep in mind, this is an alpha so the risk of data loss is real and it may not be stable**

Installation documentation can be found [here](https://dev.yacht.sh/docs/Installation/Install).

Check out the getting started guide if this is the first time you've used Yacht: https://dev.yacht.sh/docs/Installation/Getting_Started

**Yacht is also available via the DigitalOcean marketplace:**

[![DigitalOcean](https://raw.githubusercontent.com/SelfhostedPro/Yacht/master/readme_media/do-btn-blue.svg)](https://marketplace.digitalocean.com/apps/yacht?refcode=b68dee19dbf6)

**We can also be found on Linode**

[`<img src="https://www.linode.com/wp-content/uploads/2021/01/Linode-Logo-Black.svg" width="200" >`](https://www.linode.com/marketplace/apps/selfhostedpro/yacht/)

## Features So Far:

* Vuetify UI Framework
* Basic Container Management
* Template Framework
* Easy Template Updating
* Centralized settings for volume management and similar QOL functionality.
* Docker-Compose Compatibility
* Advanced Container Management (Edit/Modify)

## Planned Features:

* Container Monitoring
* Easy access to container interfaces
* User Management
* Scheduled Jobs

*If you want something that's not planned please open a feature request issue and we'll see about getting it added.*

## Templating:

Currently Yacht is compatible with portainer templates. You'll add a template url in the "Add Template" settings. The the template will be read, separated into apps, and imported into the database. The apps associated with the templates are linked via a db relationship so when the template is removed, so are the apps associated with it. We store the template url as well so we can enable updating templates with a button press.

We recommend starting with:

```
https://raw.githubusercontent.com/SelfhostedPro/selfhosted_templates/yacht/Template/template.json
```

In templates you are able to define variables (starting with `!`) to have them automatically replaced by whatever variable the user has set in their server settings (ie. `!config` will be replaced by `/yacht/AppData/Config` by default).

## Notes for ARM devices

If you're on arm and graphs aren't showing up add the following to your cmdline.txt:

```
cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1
```

## Supported Environment Variables

You can utilize the following environment variables in Yacht. None of them are mandatory.

| Variable     | Description                                                                                |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| PUID         | Set userid that the container will run as.                                                                                |
| PGID         | Set groupid that the container will run as.                                                                                |
| SECRET_KEY   | Setting this to a random string ensures you won't be logged out in between reboots of Yacht.                                                                                |
| ADMIN_EMAIL  | This sets the email for the default Yacht user.                                                                                |
| DISABLE_AUTH | This disables authentication on the backend of Yacht. It's not recommended unless you're using something like Authelia to manage authentication.                                        |
| DATABASE_URL | If you want to have Yacht use a database like SQL instead of the built in sqlite on you can put that info here in the following format:`postgresql://user:password@postgresserver/db` |
| COMPOSE_DIR  | This is the path inside the container which contains your folders that have docker compose projects. (*compose tag only*)                                                             |

## Notes for installing Docker and Yacht on WSL2 platform under Windows

If you’re running under WSL2 inside Windows, because of the difference in how permissions are handled. Your essentially inside of a Linux machine accessing a Windows file system. You will need to run after installation before adding the Yacht container:

```
$ sudo usermod -aG docker $USER
```

Additional information about this can be found in the [Post-installation steps for Linux](https://docs.docker.com/engine/install/linux-postinstall/)

## Update button not working?

*If the built in update button isn't working for you try the following command:*

```
docker run --rm -d -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower:latest --cleanup --run-once <container-name>
```

## License

[MIT License](LICENSE.md)

repository: SelfhostedPro/Yacht

gha_language: Vue

repo_name: SelfhostedPro/Yacht


text:
# jsoncv
[Link to the project](https://jsoncv.aran.site)
Store your CV in JSON and don't look back!

Head over to the link above and paste in the JSON below. Sections can have any title, each subsection must have a title subtitle and description. It's simple and flexible.

```
{

    "author": {
        "name": "Aran Long",
        "role": "Hacker, Maker, Comp Sci"
    },
   "sections": {
        "experience": [
            {
                "title": "InventiveCogs",
                "subtitle": "Technical Consultant, Sep 2016 - Present",
                "description": "Developed internal maps microservice using Node, Python, PostgreSQL, OSM, ZMQ, EC2. Designing internal AWS microservices architecture. Reduced requirement for real world testing through development of mock GPS replay system."
            },
            {
                "title": "Autodesk",
                "subtitle": "C++ Software Engineer, Summer 2016",
                "description": "Rebuilt core XML abstract library, resulting in 100% backend UNIX compatibility. Implemented error checking into macro scripting."
            },
            {
                "title": "University of Birmingham",
                "subtitle": "Student Ambassador / Robotics Outreach, Nov 2015 - Sep 2016",
                "description": "Led insight days on the basics of robotics in local schools. Gave talks and tours to incoming students."
            }
        ],
        "achievements": [
        	{
        		"title": "Junction",
        		"subtitle": "Helsinki, Finland, November 2016",
        		"description": "Awarded the Deezer prize for the development of a virality focussed bus stop game. Built using a microservices approach. Aran built the motion tracking microservice, using Python, Flask, SocketIO and OpenCV. "
        	},
            {
                "title": "Brumhack",
                "subtitle": "Birmingham, UK, November 2016",
                "description": "Awarded the first-place prize for developing ‘See’, a computer vision powered web application to help the blind see. Built using HTML, SCSS, JQuery, Clarifai, Microsoft Azure Cognitive."
            },
            {
                "title": "HackUPC",
                "subtitle": "Barcelona, Spain, October 2016",
                "description": "Awarded best use of Amazon AWS for developing ‘notifi.click’, a no cost notification system built using a microservices architecture on AWS and Amazon Dash buttons."
            },
            {
                "title": "Gadget Show",
                "subtitle": "Various, UK, Summer 2016",
                "description": "Developed, with a team of 10, a speed dating chatbot that featured on the UK TV show. I built the data entry stack and architected the project"
            },
            {
                "title": "Cisco",
                "subtitle": "Heathrow, UK, October 2015",
                "description": "Awarded the first-place prize for developing 'Permission Cloud'. A Blockchain based IOT permissions management system developed in collaboration with Barclays"
            }
        ]
    }
}
```

repository: AranScope/jsoncv

repo_name: AranScope/jsoncv


text:
[![Build Status](https://secure.travis-ci.org/airking05/go-exchange-chart-fetcher.png?branch=master)](http://travis-ci.org/airking05/go-exchange-chart-fetcher)
[![Coverage Status](https://coveralls.io/repos/airking05/go-exchange-chart-fetcher/badge.svg?branch=master)](https://coveralls.io/r/airking05/go-exchange-chart-fetcher?branch=master)
[![GoDoc](https://godoc.org/github.com/airking05/go-exchange-chart-fetcher?status.svg)](https://godoc.org/github.com/airking05/go-exchange-chart-fetcher)
[![license](https://img.shields.io/badge/license-MIT-4183c4.svg)](https://github.com/airking05/go-exchange-chart-fetcher/blob/master/LICENSE)

Go-exchange-chart-fetcher is a small server for "Fetching CryptoCurrency Data", implemented by golang.
It's pretty much stable server.

# What is this :

- this is a tool for fetching chart data.
- the data can be used for machine learning or so...

|        	| Poloniex       	| Hitbtc          	| Bitflyer     	| Binance 	| Zaif 	|
|--------	|----------------	|-----------------	|--------------	|---------	|------	|
| ID     	| 1              	| 2               	| 3            	|         	|      	|
| Status 	| Done(99 paris) 	| Done(421 paris) 	| Done(1 pair) 	|         	|      	|

![fetched_data](https://i.imgur.com/Qt4gUf9.png)

# How to Install :

```bash
go get github.com/airking05/go-exchange-chart-fetcher
```

# How to Use :

```Go
package main

import(
	"github.com/jinzhu/gorm"
	"github.com/airking05/go-exchange-chart-fetcher/models"
	"github.com/airking05/go-exchange-chart-fetcher/server"
)

// declare exchanges you want to fetch
var ExchangeIDs = []models.ExchangeID{
	models.Bitflyer,
	models.Poloniex,
	models.Hitbtc,
}

func main() {
// setup DB
    dbConf := "mysql:mysql@tcp(localhost:3306)/chart_fetcher?charset=utf8&parseTime=True&loc=UTC"
    db, err := gorm.Open("mysql", dbConf)
    if err != nil {
        panic("failed to connect db")
    }
    db.AutoMigrate(&models.Chart{})

// then start server!
    server := server.NewServer(ExchangeIDs, db)
    server.Run()
}
```

# running server

```bash
2018-02-04T18:50:40.918+0900	INFO	go-exchange-chart-fetcher/main.go:51	starting chart_server...
2018-02-04T18:50:40.918+0900	INFO	go-exchange-chart-fetcher/server.go:31	checking currecy pairs updates
2018-02-04T18:50:40.918+0900	INFO	go-exchange-chart-fetcher/server.go:192	starting chart writer...
2018-02-04T18:50:41.136+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Bitflyer] BTC/JPY
2018-02-04T18:50:41.136+0900	INFO	go-exchange-chart-fetcher/server.go:31	checking currecy pairs updates
2018-02-04T18:50:41.781+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Poloniex] CLAM/BTC
2018-02-04T18:50:41.781+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Poloniex] BTCD/XMR
2018-02-04T18:50:41.781+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Poloniex] BTCD/BTC
2018-02-04T18:50:41.781+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Poloniex] ETH/USDT
2018-02-04T18:50:41.781+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Poloniex] ETH/BTC
....
2018-02-04T18:59:08.583+0900	INFO	go-exchange-chart-fetcher/server.go:31	checking currecy pairs updates
2018-02-04T18:59:09.105+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Hitbtc] DOGE/USD
2018-02-04T18:59:09.105+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Hitbtc] DOGE/ETH
2018-02-04T18:59:09.105+0900	INFO	go-exchange-chart-fetcher/server.go:69	starting pair watcher [Hitbtc] COV/BTC
....
```

repository: simhaonline/go-exchange-chart-fetcher

repo_name: simhaonline/go-exchange-chart-fetcher


text:
Android Fragments
=================

An android app demo that showcases the Fragment lifecycle. There are two activities, `MainActivity.java` and `FragmentA.java`.
Using the logcat and Toast, this app shows the user when each callback is called.

Introduction:
---
The android fragment lifecycle includes the following callbacks: `onAttach()`, `onCreate()`, `onCreateView()`, `onViewCreated()`,
`onStart()`, `onResume()`, `onPause()`, `onStop()`, `onDestroyView()`, `onDetach()` and `onDestroy()`.

onAttach()
---
Called when a fragment is first attached to its context. onCreate() will be called after this.

onCreate()
----
This method is called to do initial creation of the fragment.

onCreateView()
---
Creates and returns the view hierarchy associated with the fragment.

onViewCreated()
---
Called immediately after onCreateView() has returned, but before any saved state has been restored in to the view.

onStart()
---
This method makes the fragment visible to the user.

onResume()
---
Called when the fragment is visible to the user and actively running.

onPause()
---
This method is called when the fragment is no longer interacting with the user either because its activity is being paused or
a fragment operation is modifying it in the activity.

onStop()
---
This method is called when the fragment is no longer visible to the user either because its activity is being stopped or a fragment operation is modifying it in the activity.

onDestroyView()
---
This method allows the fragment to clean up resources associated with its View.

onDetach()
---
Called immediately prior to the fragment no longer being associated with its activity.

onDestroy()
---
Called to do final cleanup of the fragment's state.

About this repo
===

Run this app in Android Studio.

You can view the logcat logs by opening the logcat(Alt+6) in Android Studio while your android device is running the app and connected to your computer.

Then type "LifeCycle" in logcat searchbar to get only messages relating to the app, or else, logcat will display all the messages generated by the device or emulator.

When you look at the actual phone screen, you can see that the toasts for each respective callback.

You can learn more about fragment lifecycle [here](https://developer.android.com/guide/fragments/lifecycle)!

repository: HeinKhantZaw/HuaweiAndroidTraining

branch_name: refs/heads/main

repo_name: HeinKhantZaw/HuaweiAndroidTraining


text:
# Installation
> `npm install --save @types/chartist`

# Summary
This package contains type definitions for Chartist (https://github.com/gionkunz/chartist-js).

# Details
Files were exported from https://www.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/chartist

Additional Details
 * Last updated: Fri, 09 Jun 2017 14:51:29 GMT
 * Dependencies: none
 * Global values: Chartist

# Credits
These definitions were written by Matt Gibbs <https://github.com/mtgibbs>, Simon Pfeifer <https://github.com/psimonski>.

repository: SaifRehman/angular-app

repo_name: SaifRehman/angular-app


text:
# Changelog

## v1.0.0

- rename acp to qush
- everything is functionnal

### v1.0.1

- (fix) the flag -P prompted the default preset instead of the local preset in sub directories of a project

### v1.0.2

- (fix) errors were not properly sequenced
- (fix) correction of some grammatical errors

### v1.0.3

- (fix) Unix compatibility

### v1.0.4

- remove "For UNIX user" section in README

### v1.0.5

- add logo

### v1.0.6

- (fix) pull detection to prevent a push

### v1.0.7

- add logo in cli with the command qush alone

### v1.0.8

- update logo design
- refactor code
- add version number to alone command
- move changelog to his own file

### v1.0.9

- (fix) preset showed a fatal git error if the command was not in a repository
- (fix) version 1.0.8 due to a functionnal programming error (rightIO(null) instead of rightIO(constVoid) or right(null))
- remove first break line for each commands

### v1.1.0

- (fix) more information website was pointing to the old github repository instead of qush
- complete refont of the qush config file system

repository: dylandoamaral/qush

gha_language: TypeScript

repo_name: dylandoamaral/qush


text:
# Bunyan-dynamo-example
A small example application to help you understand and play around with how bunyan-dynamo works.

## Getting Started

Navigate to the example folder and install the application's dependencies.

```bash
npm install
```

Start the application using the npm start script.

```bash
npm start
```

> Note that the environment variables ```APP_NAME``` and ```PORT``` have been set by the start script in the package.json file.

repository: ssmereka/bunyan-dynamo

gha_language: JavaScript

repo_name: ssmereka/bunyan-dynamo


text:
# Code conventions

- [POSIX shell](#posix-shell)
- [Go](#go)
- [Directory and file conventions](#directory-and-file-conventions)
- [Testing conventions](#testing-conventions)

## POSIX shell

- [Style guide](https://google.github.io/styleguide/shell.xml)

## Go

- [Go Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments)
- [Effective Go](https://golang.org/doc/effective_go.html)
- Know and avoid [Go landmines](https://gist.github.com/lavalamp/4bd23295a9f32706a48f)
- Comment your code.
  - [Go's commenting conventions](http://blog.golang.org/godoc-documenting-go-code)
  - If reviewers ask questions about why the code is the way it is, that's a sign that comments might be helpful.
- Command-line flags should use dashes, not underscores
- Naming
  - Please consider package name when selecting an interface name, and avoid redundancy. For example, `storage.Interface` is better than `storage.StorageInterface`.
  - Do not use uppercase characters, underscores, or dashes in package names.
  - Please consider parent directory name when choosing a package name. For example, `pkg/controllers/autoscaler/foo.go` should say `package autoscaler` not `package autoscalercontroller`.
    - Unless there's a good reason, the `package foo` line should match the name of the directory in which the `.go` file exists.
    - Importers can use a different name if they need to disambiguate.

## Directory and file conventions

- Avoid general utility packages. Packages called "util" are suspect. Instead, derive a name that describes your desired function. For example, the utility functions dealing with waiting for operations are in the `wait` package and include functionality like `Poll`. The full name is `wait.Poll`.
- All filenames should be lowercase.
- All source files and directories should use underscores, not dashes.
  - Package directories should generally avoid using separators as much as possible. When package names are multiple words, they usually should be in nested subdirectories.

## Testing conventions

Please refer to [TESTING.md](../../tests/TESTING.md) document.

gha_language: Go


text:
# nodejs-express-ssl
Boiler Plate Template for NodeJS & Express Apps w/ SSL Support

Use this as a starting point for your NodeJS Express Apps.

**Requirements**
1. SSL Certificate ([LetsEncrypt](http://letsencrypt.com/))

**Installation**
1. ``git clone https://github.com/brandonkovacs/nodejs-express-ssl``
2. ``npm install``

**Usage**
1. Set Environment Variables (See Below)
2) ``node index.js``

**Environment Variables**
* ``export PORT=8080``
* ``export SSL_KEY=/path/to/privkey.pem``
* ``export SSL_CERT=/path/to/certificate.pem``

repository: brandonkovacs/nodejs-express-ssl

repo_name: brandonkovacs/nodejs-express-ssl


text:
#
powerlifting-site

Uses API to populate instagram, name and wilks

# Development
1. Install NodeJs on your computer. After installing NodeJs, open up terminal and type in the following command to clone this project repository.

    ````
    git clone https://github.com/KillytheBid/Powerlifting-Site.git
    ````
2. After cloning this project reposity, get inside this project folder by typing the following command.

    ````
    cd powerlifting-site
    ````
3. Once we are inside the project folder, install project dependencies by typing the following commands below.

    ````
    npm install
    ````

4. After installing dependencies, use the following commands to start your dev server.

    ````
    npm run dev
    ````
5. After starting the server, you can open up a browser and visit at following link.

   ````
   http://localhost:3000
   ````

# License

MIT © [wajeht](https://github.com/wajeht)
[KillyTheBid](https://github.com/KillyTheBid)

repository: KillytheBid/Powerlifting-Site

gha_language: Python

repo_name: KillytheBid/Powerlifting-Site


text:
# CITE-seq-Count
A python package that allows to count antibody TAGS from a [CITE-seq](https://www.nature.com/articles/nmeth.4380) and/or [cell hashing](https://www.biorxiv.org/content/early/2017/12/21/237693) experiment.

Here is a website referencing the wetlab protocols needed https://cite-seq.com/

Installation
-------------------------------------------

```
pip install CITE-seq-Count
```

For more details on how to run it, please [click here](https://github.com/Hoohm/CITE-seq-Count/wiki/Running-the-script)


text:
---
---

```python
import sys

t = int( sys.argv[1] )

n = int( sys.argv[2] )

print("This is the %d times table." % t)

for i in range(1, n+1):
    t_times_i = t * i

    print("%d times %d equals %d" % (i, t, t_times_i))
```

# [Previous](../arguments) [Next](../arguments)