text:
# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).

## [Unreleased](../../releases/tag/X.Y.Z)

## [5.0.1](../../releases/tag/5.0.1) - 2023-07-30

### Fixed

- Changed order of installing additional pip packages ([#166](../../issues/166))

## [5.0.0](../../releases/tag/5.0.0) - 2023-05-20

### Changed

- Docker Compose V1 is EOL and this role will no longer support that in general.
- Changed name of `docker_compose_no_pip` to `docker_compose_pip`, default set to `false`.
- `docker_compose` is `true` and `docker_compose_pip` is `false`, it will only create symbolic links (`docker-compose`) for backward compatibility. Docker compose CLI plugin is installed by default now.

### Removed

- Removed variables `docker_compose_no_pip_detect_version` and `docker_compose_no_pip_version`
- Removed Debian 8 bug tweaks.

### Internal

- Updated Vagrantfile for testing to works with AlmaLinux 9 as controller.
- Investigate impact of Docker Compose V2 ([#147](../../issues/147))

## [4.0.0](../../releases/tag/4.0.0) - 2022-12-05

### Changed

- Bumped minimal Ansible version to 5.0.0

## Fixed

- Unsupported parameters for (ansible.legacy.command) module: warn ([#160](../../issues/160))

## [3.8.0](../../releases/tag/3.8.0) - 2022-10-22

## Added

- Add Linux Mint 21 support. [@alexander-danilenko] ([#156](../../issues/156))
- Abort if podman in detected in the system

## Internal

- Added manuel test related to Docker SDK and PiP
- Added test of docker-compose not using PiP and auto detect version in regression suite

## [3.7.2](../../releases/tag/3.7.2) - 2022-04-24

## Fixed

- Docker daemon environment variables not set when SysVinit is used ([#152](../../issues/152))

## [3.7.1](../../releases/tag/3.7.1) - 2022-04-24

## Fixed

- Upgrade of docker-compose fails when fetching latest version from Github API ([#151](../../issues/151))
- Service module fail on WSL2 with Ubuntu 20.04 ([#150](../../issues/150))

## [3.7.0](../../releases/tag/3.7.0) - 2022-02-05

## Added

- Support for CentOS Stream 8

## Internal

- Update of test configuration.
- Updated Docker CE support matrix.

## [3.6.1](../../releases/tag/3.6.1) - 2021-12-29

## Fixed

- Fix broken Linux Mint 19 + 20 ([#144](../../pull/144))

## Internal

- Minor refactoring of test configuration.

## [3.6.0](../../releases/tag/3.6.0) - 2021-11-07

## Added

- Added support for Rocky Linux 8

## Fixed

- Docker restart fails after OPA authz plugin installation on Ubuntu 20.04 ([#143](../../issues/143))
- Docker plugin install seems to be missing "item.args" ([#142](../../issues/142))

## Internal

- Rocky Linux 8 included in regressiontesting.

## [3.5.0](../../releases/tag/3.5.0) - 2021-10-30

### Added

- Add support for RHEL7 ppc64le architecture [@DimaShmu] ([#140](../../issues/140))

## [3.4.1](../../releases/tag/3.4.1) - 2021-08-09

### Fixed

- Error when creating docker-compose symlink when file is present at path

## [3.4.0](../../releases/tag/3.4.0) - 2021-06-28

### Changed

- Add support to upgrade/downgrade docker-compose (binary version) ([#138](../../issues/138))
- Bumped minimum Ansible version to 2.10 in role meta information

### Fixed

- Bumped docker-compose version from 1.29.1 to 1.29.2 (`docker_compose_no_pip_version`)
- Failed execution during removal of Docker CE and related files

### Internal

- Restructure of test cases
- Bumped Ansible version to 2.10.7 meaning regression testing is no longer done on versions below 2.10

## [3.3.2](../../releases/tag/3.3.2) - 2021-04-17

### Fixed

- Python docker version 5 Drops support for Python 2 ([#136](../../issues/136))
- Bumped non-Python version of docker-compose from 1.27.4 to 1.29.1
- Fixed Ansible linting warnings related to rule 208

### Internal

- Bumped ansible version to 2.9.20 which is used for regression testing

## [3.3.1](../../releases/tag/3.3.1) - 2021-02-21

### Fixed

- Version 3.3.0 forces pip upgrades on RHEL8 ([#135](../../issues/135))

### Changed

- Cleaned out old compatibility check related to Debian 7

## [3.3.0](../../releases/tag/3.3.0) - 2021-02-16

### Added

- Add support for AlmaLinux 8 ([#133](../../issues/133))

### Fixed

- PiP upgrade no longer works for Python 2 ([#134](../../issues/134))

## [3.2.1](../../releases/tag/3.2.1) - 2020-12-21

### Changed

- Bumped docker-compose version to 1.27.4

## [3.2.0](../../releases/tag/3.2.0) - 2020-11-16

### Changed

- Review code around Docker plugin handling ([#132](../../issues/132))

### Fixed

- Docker daemon is not restarted on configuration change when already started. Fixed by changes in #132.

### Internal

- Readme file in tests directory updated
- Updated tests to use Ansible 2.9.15

## [3.1.2](../../releases/tag/3.1.2) - 2020-11-07

### Fixed

- Centos8: Issues when trying to install plugins ([#131](../../issues/131))

## [3.1.1](../../releases/tag/3.1.1) - 2020-10-23

### Fixed

- WSL2: Failing to check docker daemon status ([#127](../../issues/127))

## [3.1.0](../../releases/tag/3.1.0) - 2020-10-09

### Changed

- Pip install on RHEL 7 and 8 ([#125](../../issues/125))

### Fixed

- Fails on RHEL 7 because $releasever is set to 7Server ([#126](../../issues/126))
- Tasks related to removal uses yum instead of dnf for RHEL 8 ([#124](../../issues/124))

## [3.0.0](../../releases/tag/3.0.0) - 2020-10-07

### Changed

- Support for Ansible 2.8 dropped, increased to 2.9. Future changes might break compatibility.
- containerd for CentOS/RHEL 8 update to version 1.2.13-3.2
- Experimental switch `docker_x_redhat_centos_8_workaround` now defaults to `no`
  since it seems to now be available in CentOS/RHEL 8 repo: https://github.com/docker/for-linux/issues/873

### Fixed

- RHEL8 install fails due to missing docker-ce-edge repository ([#123](../../issues/123))

### Removed

- Remove handling of deprecated variable docker_pkg_name ([#85](../../issues/85))
- Remove handling of deprecated variable docker_enable_ce_edge ([#83](../../issues/83))

## [2.7.0](../../releases/tag/2.7.0) - 2020-08-09

### Changed

- Update default docker-compose version to 1.26.2
- Changed `docker_x_ssl_match_hostname` to true and detection if missing

### Fixed

- No module named shutil_get_terminal_size ([#121](../../issues/121))

### Added

- Add missing audit rules which are defined in CIS Docker Benchmark 1.2.0 ([#120](../../issues/120))

## [2.6.6](../../releases/tag/2.6.6) - 2020-07-19

### Fixed

- No package matching '' is available ([#119](../../issues/119))

## [2.6.5](../../releases/tag/2.6.5) - 2020-07-04

### Fixed

- Missing dependency zipp for installed docker-compose using PiP ([#112](../../issues/112))

## [2.6.4](../../releases/tag/2.6.4) - 2020-06-27

### Changed

- Updated default docker-compose version to 1.26.0

## [2.6.3](../../releases/tag/2.6.3) - 2020-05-02

### Changed

- Minimum supported Ansible version increased to 2.8.
- Update default docker-compose version to 1.25.5 ([#114](../../issues/114))
- Improve/Refactor handling related to postinstall steps and PiP ([#115](../../issues/115))

### Fixed

- Fix python3 reference in tasks/postinstall.yml ([#117](../../issues/117))

### Internal

- Improved testing to get it more stable when reboots are required
- Docker run throws error on Fedora 31 ([#116](../../issues/116))

## [2.6.2](../../releases/tag/2.6.2) - 2019-12-04

### Fixed

- Docker CE package fails to install on CentOS 8 ([#110](../../issues/110))

## [2.6.1](../../releases/tag/2.6.1) - 2019-08-13

### Fixed

- EPEL repo shall not be installed when docker_setup_repos is false

## [2.6.0](../../releases/tag/2.6.0) - 2019-08-10

### Added

- Add support to disable setup of apt/dnf/apt repos ([#109](../../issues/109))

## [2.5.2](../../releases/tag/2.5.2) - 2019-08-02

### Fixed

- Error in apt_repository on Ubuntu 19.04 (Disco Dingo) ([#108](../../issues/108))
- 19.03 fails on Fedora 28 - write /proc/self/attr/keycreate: permission denied ([#107](../../issues/107))
- Ubuntu 17.10 Artful is not handled correctly ([#104](../../issues/104))
- Updated default value for docker-compose version to 1.24.1

### Internal

- Added automated test for Ubuntu 19.04 Disco Dingo
- Removed Ubuntu 14.04 Trusty Tahr from automated tests
- Updated tests to not use deprecated configuration which was now removed in 19.03 ([#105](../../issues/105))

## [2.5.1](../../releases/tag/2.5.1) - 2019-07-16

### Fixed

- Major version comparison fails for some tasks due to non-numeric value ([#103](../../issues/103))
- Docker compose fails on Debian 10 (Buster) ([#102](../../issues/102))

## [2.5.0](../../releases/tag/2.5.0) - 2019-07-14

### Added

- Added initial basic support for Raspbian

### Fixed

- Migrating from with_X to loop ([#100](../../issues/100))
- Install of authz plugins does not update daemon config ([#99](../../issues/99))
- Failure on Fedora 30 ([#93](../../issues/93))

### Internal

- Updated experimental CIS test.

## [2.4.1](../../releases/tag/2.4.1) - 2019-06-06

### Fixed

- RHEL: subscription-manager uses network when docker_network_access is set to false ([#98](../../issues/98))

## [2.4.0](../../releases/tag/2.4.0) - 2019-06-05

### Added

- Experimental configuration (`docker_network_access`) to not access network during run

### Changed

- Many deprecation warnings in Ansible 2.8 ([#94](../../issues/94))
- Improve handling of Python 3 ([#95](../../issues/95))
- RHEL: handling repos NOT via subscription-manager ([#96](../../issues/96))
- Role name changed due to automatic conversion of hyphen to underscore in Ansible Galaxy

### Fixed

- api.github.com limits on number of requests causes the request to fail ([#87](../../issues/87))
- RHEL, role fails to remove "pre-docker-ce" packages ([#92](../../issues/92))
- Install of Docker SDK fails on RHEL (not supported by this role) ([#97](../../issues/97))

### Internal

- Preparations for doing automated tests with RHEL 7
- Increase Ansible version to 2.6.16
- Preparations for better handling of Python 3 in test suites
- Removed Debian 7 Wheezy from tests due to APT repository EOLs etc

## [2.3.0](../../releases/tag/2.3.0) - 2019-03-11

### Fixes

- APT repository setup fails on Debian Buster 10 ([#88](../../issues/88))

### Added

- Added `postinstall` tag

### Changed

- Deprecation warning about filters in Ansible 2.5 ([#40](../../issues/40))

### Internal

- Updated regression test baseline to Ansible 2.5
- Refactored setup of repository to reduce number of skipped tasks
- Refactored distribution check tasks
- Added regression tests

## [2.2.0](../../releases/tag/2.2.0) - 2019-02-10

### Added

- Support removal of Docker CE packages and related configuration ([#82](../../issues/82))
- Replace docker_pkg_name with docker_version ([#86](../../issues/86))

### Deprecated

- Variable `docker_remove_pre_ce` will be removed in future major release ([#80](../../issues/80))
- Variable `docker_pkg_name` will be removed in future major release ([#86](../../issues/86))

## [2.1.1](../../releases/tag/2.1.1) - 2019-02-01

### Fixed

- Changing Docker repository channel does not work ([#79](../../issues/79))

## [2.1.0](../../releases/tag/2.1.0) - 2019-01-19

### Added

- Initial support for installation of Docker plugins ([#78](../../issues/78))

### Internal

- Some adjustments to what is included in regression test suite
- Devicemapper regression tests fail with Docker 18.09 ([#69](../../issues/69))
- Docker CE matrix added to see distribution support

## [2.0.0](../../releases/tag/2.0.0) - 2019-01-03

### Added

- Improve use of --check ([#72](../../issues/72))
- Add more advanced options to control PiP package installation ([#73](../../issues/73))
- Flag to disable compatibility and distribution checks
- python-pip-whl is required in Debian 8 to install via PiP

### Changed

- Docker 18.09 fails to create containers when MountFlags=slave is set ([#76](../../issues/76))

### Fixed

- Non-systemd environment variables are not correctly set since version 1.11.0 of this role ([#74](../../issues/74))
- Some variables lives on between plays which cause unexpected behavior ([#75](../../issues/75))
- docker-compose does not work with sudo ([#77](../../issues/77))

### Internal

- Refactored automated tests to now execute Ansible from separate node due to issues
  with VirualBox guest additions from time to time.
- Fixed issues reported by Ansible-lint

## [1.11.3](../../releases/tag/1.11.3) - 2018-12-11

### Fixed

- python-pip is always installed ([#71](../../issues/71))

## [1.11.2](../../releases/tag/1.11.2) - 2018-12-11

### Fixed

- docker_compose_no_pip only works in Ansible 2.7 or later ([#68](../../issues/68))
- Pip not installed before use of pip module ([#70](../../issues/70))

## [1.11.1](../../releases/tag/1.11.1) - 2018-12-03

### Fixed

- Docker compose is installed via PiP even when docker_compose_no_pip is set to true ([#68](../../issues/68))

## [1.11.0](../../releases/tag/1.11.0) - 2018-12-01

### Added

- Identify systemd support even in check mode ([#66](../../issues/66))

### Internal

- Ansible-lint with Ansible Galaxy rules report problems ([#67](../../issues/67))
- Fixed issues with missing Fedora images at vagrantup.com

## [1.10.0](../../releases/tag/1.10.0) - 2018-11-05

### Added

- Add support for Debian 7 (Wheezy) ([#64](../../issues/64))

### Fixed

- Docker startup fails in Fedora 28 because it cannot find pvcreate ([#58](../../issues/58))
- LVM2 package is required to be installed when devicemapper is used ([#61](../../issues/61))
- docker-compose won't install ([#62](../../issues/62))
- Revisit install of docker-compose ([#63](../../issues/63))

### Internal

- Testing: Snapshotting used during testing by `test.sh` to speed up by avoiding unnecessary installs of Ansible and guest additions
- Add Fedora distributions to test suite ([#57](../../issues/57))
- Fails to install VirtualBox guest additions on Fedora 29 beta ([#59](../../issues/59))
- Replace currently used Vagrant boxes during testing with more official boxes ([#60](../../issues/60))

## [1.9.0](../../releases/tag/1.9.0) - 2018-10-24

### Added

- Add support to allow users to be added to the docker group ([#53](../../issues/53))
- Add support to select different Docker repository channels ([#55](../../issues/55))

### Deprecated

- Variable `docker_enable_ce_edge` will be removed because Docker no longer provide edge releases ([#54](../../issues/54))

## [1.8.0](../../releases/tag/1.8.0) - 2018-10-14

### Added

- Add support to install Docker Ansible module dependencies ([#48](../../issues/48))
- Add support to install packages after install via PiP or OS package manager ([#49](../../issues/49))

### Internal

- Testing: Improved structure in `vagrant_config.yml` for `test.sh`
- Testing: Improved `test.sh` with better limit functionality

### Fixed

- auditd is installed even if docker_enable_audit set to false ([#50](../../issues/50))
- Cannot use dm.directlvm_device in Debian 8 ([#51](../../issues/51))
- Update repository cache fails on Fedora ([#52](../../issues/52))

## [1.7.2](../../releases/tag/1.7.2) - 2018-09-27

### Fixed

- Python 3 forward compatibility ([#47](../../issues/47))

## [1.7.1](../../releases/tag/1.7.1) - 2018-07-08

### Fixed

- Ansible Galaxy linting report error during import  ([#45](../../issues/45))
- null written to /etc/docker/daemon.json ([#46](../../issues/46))

## [1.7.0](../../releases/tag/1.7.0) - 2018-07-08

### Added

- Add support to add environment variables to Docker daemon ([#43](../../issues/43))
- Add support to add systemd configuration options to Docker service ([#44](../../issues/44))

### Fixed

- systemctl daemon-reload is not run when toggling docker_enable_mount_flag_fix ([#39](../../issues/39))
- Role is not idempotent for Ubuntu and Debian distributions ([#41](../../issues/41))
- Cannot set hosts in daemon.json because of arguments to dockerd in Ubuntu/Debian ([#42](../../issues/42))

## [1.6.0](../../releases/tag/1.6.0) - 2018-06-07

### Changed

- Deprecation warning about include in Ansible 2.4 ([#12](../../issues/12))

## [1.5.0](../../releases/tag/1.5.0) - 2018-05-02

### Added

- Add tags to either install or just configure Docker ([#37](../../issues/37))

## [1.4.0](../../releases/tag/1.4.0) - 2018-04-14

### Added

- Introduce flag to disable mount flag fix and addition of compatibility check [@jamiejackson] ([#35](../../issues/35))

## [1.3.2](../../releases/tag/1.3.2) - 2018-02-07

### Fixed

- RedHat: breaks when rhel-7-server-rt-beta-rpms isn't listed; check [@jamiejackson] ([#29](../../issues/29))

## [1.3.1](../../releases/tag/1.3.1) - 2018-02-01

### Fixed

- Install failed on CentOS because of newly added RedHat support ([#28](../../issues/28))

## [1.3.0](../../releases/tag/1.3.0) - 2018-01-28

### Added

- Support for RedHat [@jamiejackson] ([#26](../../issues/26))

## [1.2.0](../../releases/tag/1.2.0) - 2017-12-08

### Added

- Add support to specify specific Docker version ([#21](../../issues/21))
- Support for Linux Mint ([#24](../../issues/24))

## [1.1.0](../../releases/tag/1.1.0) - 2017-11-06

### Added

- Add support to ensure Docker is not upgraded ([#17](../../issues/17))
- Support for Ubuntu and Debian ([#20](../../issues/20))

### Changed

- Refactoring of tasks ([#19](../../issues/19))

### Fixed

- /proc/sys/fs/may_detach_mounts does not exists in all kernel 3.10 versions ([#18](../../issues/18))
- auditd does not apply all rules after reboot because of rule errors ([#16](../../issues/16))

## [1.0.1](../../releases/tag/1.0.1) - 2017-10-22

### Fixed

- Kernel parameter fs.may_detach_mounts is necessary even if mount flag is set to slave ([#13](../../issues/13))

## [1.0.0](../../releases/tag/1.0.0) - 2017-10-17

### Removed

- Removed support to setup devicemapper using container-storage-setup ([#10](../../issues/10))

## [0.4.3](../../releases/tag/0.4.3) - 2017-09-26

### Fixed

- MountFlags "slave" helps to prevent "device busy" errors on RHEL/CentOS 7.3 kernels [@jgagnon1] ([#11](../../issues/11))

## [0.4.2](../../releases/tag/0.4.2) - 2017-08-13

### Fixed

- Docker fails to setup subgid and subuid in CentOS 7.3.1611 ([#9](../../issues/9))

### Deprecated

- Functionallity related to `docker_setup_devicemapper`. Similar support now available in Docker v17.06.

## [0.4.1](../../releases/tag/0.4.1) - 2017-07-21

### Fixed

- Missing docker.service.d directory ([#6](../../issues/6))

## [0.4.0](../../releases/tag/0.4.0) - 2017-06-30

### Added

- Add configuration option for adding audit rules for Docker compliant with CIS 1.13 ([#5](../../issues/5))

## [0.3.0](../../releases/tag/0.3.0) - 2017-06-28

### Added

- Add configuration support to enable Docker CE Edge versions ([#3](../../issues/3))
- Add simple support to setup devicemapper using container-storage-setup ([#4](../../issues/4))

## [0.2.0](../../releases/tag/0.2.0) - 2017-05-25

### Fixed

- Task "Configure Docker daemon" fails because of missing directory ([#2](../../issues/2))

### Added

- Add support to specify daemon.json file to copy ([#1](../../issues/1))

## [0.1.0](../../releases/tag/0.1.0) - 2017-05-01

### Added

- Support to remove pre Docker CE versions
- Basic configuration support for Docker daemon

repository: haxorof/ansible-role-docker-ce

gha_language: Shell

repo_name: haxorof/ansible-role-docker-ce


text:
# DoseOxygenSUV
## Dose modification factor (DMF)

Plot of dose modification factor against pO2 for k=2.5 mmHg and OERmax = 3.0.

![Alt text](https://github.com/isachpaz/DoseOxygenSUV/blob/main/dmf.png?raw=true "Dose modification plot")

license: MIT

repository: isachpaz/DoseOxygenSUV

branch_name: refs/heads/main

extension: md

license_type: permissive

repo_name: isachpaz/DoseOxygenSUV


text:
# \<paper-lipsum\> [![Published on webcomponents.org](https://img.shields.io/badge/webcomponents.org-published-blue.svg)](https://beta.webcomponents.org/element/AmruthPillai/paper-lipsum)
The Dummy Text Generator Web Component

## Introduction

`paper-lipsum` is a web component created using Polymer to let your display dummy blocks of text on your website using just one tag, instead of having to copy paste the whole block from a website.
It's as easy as 1-2-3.

Take a look at the Documentation & Demo

## Web Component Demo

```html
<paper-lipsum></paper-lipsum>
```

## Installation

Make sure you have Node/NPM and Bower installed. Then, run this command:

```
bower install --save AmruthPillai/paper-lipsum
```

Import the `webcomponents.js` script to your webpage, if you haven't already:

```
<script src="bower_components/webcomponentsjs/webcomponents-lite.js"></script>
```

Then, import the paper-lipsum component to your webpage:

```
<link rel="import" href="bower_components/paper-lipsum/paper-lipsum.html">
```

That's all you need to start using the `<paper-lipsum>` tag. Magical, isn't it?

## Usage

All you need to do to get some dummy text is:

```
<paper-lipsum></paper-lipsum>
```

I'm not kidding... that's it! (I'm starting to sound like I'm overselling this component, aren't I?)

But of course, there are a few other ways to manipulate this text too... like displaying a certain number of words:

```
<paper-lipsum words="200"></paper-lipsum>
```

You can check this out in action on the GitHub demo page: https://amruthpillai.github.io/paper-lipsum/

## Contributing
1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3.  Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Build

### Install the Polymer-CLI

First, make sure you have the [Polymer CLI](https://www.npmjs.com/package/polymer-cli) installed. Then run `polymer serve` to serve your application locally.

You can serve the built versions by giving `polymer serve` a folder to serve
from:

```
$ polymer serve build/bundled
```

### Running Tests

```
$ polymer test
```

Your application is already set up to be tested via [web-component-tester](https://github.com/Polymer/web-component-tester). Run `polymer test` to run your application's test suite locally.

## License

MIT License

Copyright (c) 2016 Amruth Pillai

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.

branch_name: refs/heads/master


text:
# Merlin

## Context

After you have built a model with high-quality training data and the perfect algorithm, it’s time to apply it to make predictions and serve the outcome for future decision making.
For many data scientists, model training can be done easily within their Jupyter notebook. However, things become trickier when it comes to productionizing the model to serve real traffic, which is engineering intensive. There are many tools available, but learning when and how to use them requires a lot of exploration, which can be a headache.

## User Flow

![User flow](./diagrams/user_flow.drawio.svg)

1. **Deploy a model**

    We want to make the deployment experience as seamless as possible, directly from Jupyter notebook. With the Merlin SDK, we can now upload the model and trigger the deployment pipeline, by simply calling a few functions in the notebook. Alternatively, Merlin UI supports the same, with just 1 click.

2. **Setup serving endpoint**

    Once the model is deployed with an auto-generated HTTP endpoint, you can then specify the serving model version in the console. Give it a minute and your model will automagically be able to serve prediction.

3. **Evaluate and iterate**

    The Merlin UI allows you to deploy and track different model versions and tag any version to run experiment easily. All model artifacts are synchronized into MLflow Tracking, which can be used to track and compare the model performance.

## Concepts

**Project**: Project represents a namespace for a collection of model. For example, a project could be food Recommendations, driver allocation, ride pricing, etc.

**Model**: Every model is associated with one (and only one) project and model endpoint. Model also can have zero or more model versions. In the entities' hierarchy of MLflow, a model corresponds to an MLflow experiment.

**Model Endpoint**: Every model has each own endpoint that contains routing rule to active model version endpoint.

**Model Version**: The model version represents an iteration within a model. A model version is associated with a run within MLflow. A Model Version can be deployed as a service, there can be multiple deployments of model version with different endpoint each.

**Model Version Endpoint**: A model version endpoint is a way to obtain model inference results in real-time, over the network (HTTP).

**Environment**: The environment’s name is a user-facing property that will be used to determine the target Kubernetes cluster where a model will be deployed to. The environment has two important properties, name and Kubernetes cluster.

repository: babywyrm/merlin

repo_name: babywyrm/merlin


text:
# Wingman
![Logo](/Wingman.png)

![NuGet Build](https://img.shields.io/nuget/v/Wingman.svg)

General-purpose C# assistance library.

Includes support for WPF with Caliburn.Micro.

## NuGet
Wingman is on [NuGet](https://www.nuget.org/packages/Wingman).

To install the latest version, open PowerShell in your project directory, and simply run:
```ps
Install-Package Wingman
```

Wingman has several sub-packages. The main package installs all of them, but you can install any of the sub-packages individually:
```ps
Install-Package Wingman.DI
Install-Package Wingman.Services
Install-Package Wingman.WPF
```

The packages have inter-dependencies. For example, Wingman.WPF will always install Wingman.DI.

 Supported .NET Framework Versions

We target a varying range of .NET Framework versions from v4.0 to v4.8, so all of your projects from April 2010 forwards should work with Wingman.

For frameworks v4.5 - v4.7, the base release and latest release are targeted, however not release v4.x.1. This means that for these frameworks, v4.x.1 projects will target the v4.x release of Wingman.

Please keep in mind that .NET 4.0 projects cannot be mocked with [Moq](https://github.com/moq/moq4), so the release target isn't tested, however it compiles.

Release Date                 |Framework Version|Supported|Targeted|Tested
:---------------------------:|:---------------:|:-------:|:------:|:----:
13th February 2002|v1.0             |❌       |❌       |❌
24th April    2003|v1.1             |❌       |❌       |❌
07th November 2005|v2.0             |❌       |❌       |❌
06th November 2006|v3.0             |❌       |❌       |❌
19th November 2007|v3.5             |❌       |❌       |❌
12th April    2010|v4.0             |✅       |✅       |❌
15th August   2012|v4.5             |✅       |✅       |✅
17th October  2013|v4.5.1           |✅       |❌       |❌
05th May      2014|v4.5.2           |✅       |✅       |✅
20th July     2015|v4.6             |✅       |✅       |✅
30th November 2015|v4.6.1           |✅       |❌       |❌
02nd August   2016|v4.6.2           |✅       |✅       |✅
05th April    2017|v4.7             |✅       |✅       |✅
17th October  2017|v4.7.1           |✅       |❌       |❌
30th April    2018|v4.7.2           |✅       |✅       |✅
18th April    2019|v4.8             |✅       |✅       |✅

The .NET Standard, and .NET Core and Mono are not currently supported.

## How to Use Wingman
Wingman currently includes basic support for Caliburn.Micro.

### BootstrapperBase
The author includes a `BootstrapperBase` base implementation which allows bootstrapping with a minimal amount of code.

The most basic bootstrapper might looks like this:
```cs
using Wingman.Bootstrapper;
using Wingman.Container;

class Bootstrapper : BootstrapperBase<IShellViewModel>
{
    protected override void RegisterViewModels(IDependencyRegistrar dependencyRegistrar)
    {
        dependencyRegistrar.Singleton<IShellViewModel, ShellViewModel>();
    }
}
```

As you may have noticed, one of the `BootstrapperBase` classes accepts a single generic parameter - the root ViewModel to use for `DisplayRootViewModel`.

`RegisterViewModels` is an abstract method because the root ViewModel (`IShellViewModel` in this case) must always be registered with the dependency registrar, otherwise the root view cannot be displayed by Caliburn. The `BootstrapperBase` will throw if the root ViewModel isn't registered!

`BootstrapperBase` will also register two additional dependencies for you automatically:
- An `IWindowManager` implementation (from Caliburn)
  - This serves to spawn windows and is always necessary.
- An `IServiceFactory` implementation
  - This is a convenience general-purpose factory, provided by Wingman, described in its own section.

Caliburn's container bootstrapping methods have been overridden and sealed by Wingman, and they delegate all calls to `IDependencyRetriever`.

The `Configure` method has also been sealed, and calls these methods in order:
```cs
RegisterViewModels(IDependencyRegistrar dependencyRegistrar);
RegisterServices(IDependencyRegistrar dependencyRegistrar);

RegisterFactoryViewModels(IServiceFactoryRegistrar dependencyRegistrar);
RegisterFactoryServices(IServiceFactoryRegistrar dependencyRegistrar);
```

The first two methods are simply used to register dependencies with the default container. `TRootViewModel` must be registered in `RegisterViewModels`, however, apart from that, there is nothing to stop you from registering services in the first method, and ViewModels in the second. The convention was created to make registration easier to read, as there are usually two separate clusters of registrations in the `Configure` method.

The Factory versions of these methods relate to registering with `IServiceFactory`, which is described in its own section.

Wingman also overrides `OnStartup` using the "template method" pattern, and displays the root view for the ViewModel templated when inheriting `BootstrapperBase`.

You can override these two method to take action before or after displaying the root view, respectively:
```cs
OnStartupBeforeDisplayRootView(object sender, StartupEventArgs e);
OnStartupAfterDisplayRootView(object sender, StartupEventArgs e);
```

All other `BootstrapperBase` methods have been left intact as per Caliburn's implementations.

Wingman's `BootstrapperBase` implementation aims to reduce hassle when setting up a new project, ensuring that the app has been bootstrapped properly by throwing descriptive exceptions early on during the startup phase.

### DependencyContainer
As you may have noted, Wingman includes two dependency interfaces - `IDependencyRegistrar` and `IDependencyRetriever`. These serve to register and retrieve dependencies from a dependency container. The interfaces have largely been based on the [`SimpleContainer`](https://github.com/Caliburn-Micro/Caliburn.Micro/blob/master/src/Caliburn.Micro.Core/SimpleContainer.cs) implementation in Caliburn.

The interfaces are split due to the fact that registrations and retrieval from the dependency container often happen separately, which means that too much information is passed to consumers that do not use both concepts.

Wingman comes with a default implementation of these two interfaces (`DependencyContainer`), which can be instantiated via `DependencyContainerFactory.Create()`. `DependencyContainer` also implements `IDependencyActivator`, a simple event that is raised when an instance is created from the container, which isn't used by Wingman specifically, but is present in Caliburn's `SimpleContainer` implementation.

Any custom implementations of these interfaces can either manually implement `IDependencyRegistrar` and/or `IDependencyRetriever`, or derive the `DependencyContainerBase` class which implements both interfaces and the convenience generic methods defined in the interfaces. `IDependencyActivator` is optional.

For custom container implementations, you must pass instances of your registrar and retriever to the base constructor of `BootstrapperBase`:
```cs
using Wingman.Bootstrapper;
using Wingman.Container;

class Bootstrapper : BootstrapperBase<IShellViewModel>
{
    public Bootstrapper() : base(MyCustomContainerRegistrar.Instance, MyCustomContainerRetriever.Instance)
    {
    }

    protected override void RegisterViewModels(IDependencyRegistrar dependencyRegistrar)
    {
        dependencyRegistrar.Singleton<IShellViewModel, ShellViewModel>();
    }
}
```

Custom implementations may be necessary when using different dependency containers, such as [Castle Windsor](https://github.com/castleproject/Windsor) and [Ninject](https://github.com/ninject/ninject).

Wingman may introduce custom implementations for these containers in the future. If you happen to implement one of these, feel free to send a pull request! (Include unit tests!)

### ServiceFactory
Wingman provides a general-purpose factory, which can generate implementations with dependencies as well as arguments. Unfortunately, to make the process simple, arguments are weakly-typed, passed as an `object[]`.

The ServiceFactory is split into two interfaces:
1. `IServiceFactoryRegistrar`
   - Registers dependency creation strategies with the factory.
2. `IServiceFactory`
   - Generates instances of registered services via the appropriate strategy.

The default implementations of these interfaces are `ServiceFactoryRegistrar` and `ServiceFactory` (respectively), and they can both be instantiated via `ServiceFactoryFactory.Create(IDependencyRegistrar, IDependencyRetriever)`. A pair of objects are returned, `IServiceFactoryRegistrar Registrar` and `IServiceFactory Factory`. The purpose of the registrar being a separate object is so that the registrar is allocated once at startup, all the dependencies are swiftly registered, and the registrar is garbage-collected, releasing all registration-related class instances.

The `BootstrapperBase` class already takes care of instantiating and registering the factory with the default dependency container.

Creating a service instance is as simple as this:
```cs
class MyService
{
    private readonly ISomeService _someService;

    public MyService(IServiceFactory serviceFactory)
    {
        _someService = serviceFactory.Create<ISomeService>(somePieceOfData);
    }
}
```

There are two strategies for registering services:
1. FromContainer
2. PerRequest

#### FromContainer
The FromContainer strategy will simply retrieve the service from the container, letting the container do any dependency resolution. This means that you cannot pass any arguments to the service being created (an exception will throw!).

FromContainer dependencies only need an interface registration with the factory, and must be registered with the dependency container beforehand:
```cs
using Wingman.Bootstrapper;
using Wingman.Container;
using Wingman.ServiceFactory;

class Bootstrapper : BootstrapperBase<IShellViewModel>
{
    protected override void RegisterViewModels(IDependencyRegistrar dependencyRegistrar)
    {
        dependencyRegistrar.Singleton<IShellViewModel, ShellViewModel>();
    }

    protected override void RegisterServices(IDependencyRegistrar dependencyRegistrar)
    {
        // Any registration strategy applies here, Singleton is just used by default
        dependencyRegistrar.Singleton<IService, ServiceImpl>();
    }

    protected override void RegisterFactoryServices(IServiceFactoryRegistrar serviceFactoryRegistrar)
    {
        serviceFactoryRegistrar.FromContainer<IService>();
    }
}
```

The default `IServiceFactoryRegistrar` will throw if the `FromContainer` service hasn't been registered with the `IDependencyRegistrar`!

The above registration means a use like this applies:
```cs
serviceFactory.Create<IService>();
```

However, this will throw:
```cs
serviceFactory.Create<IService>(argument1, argument2); // Cannot pass arguments to FromContainer registrations
```

#### PerRequest
The PerRequest strategy will resolve all dependencies, and then inject constructor parameters.

Take the following service:
```cs
class ServiceImpl : IService
{
    public ServiceImpl(IDependency dependency, IDependency2 dependency2, string myName)
    {
        // blah
    }
}
```

You can create it like this:
```cs
serviceFactory.Create<IService>("You are called ServiceImpl.");
```
The dependencies will be resolved automagically.

The above usage implies this kind of registration:
```cs
using Wingman.Bootstrapper;
using Wingman.Container;
using Wingman.ServiceFactory;

class Bootstrapper : BootstrapperBase<IShellViewModel>
{
    protected override void RegisterViewModels(IDependencyRegistrar dependencyRegistrar)
    {
        dependencyRegistrar.Singleton<IShellViewModel, ShellViewModel>();
    }

    protected override void RegisterServices(IDependencyRegistrar dependencyRegistrar)
    {
        // Any registration strategy applies here, Singleton is just used by default
        dependencyRegistrar.Singleton<IDependency, DependencyImpl>();
        dependencyRegistrar.Singleton<IDependency2, Dependency2Impl>();
    }

    protected override void RegisterFactoryServices(IServiceFactoryRegistrar serviceFactoryRegistrar)
    {
        serviceFactoryRegistrar.PerRequest<IService, ServiceImpl>();
    }
}
```

#### Alternative Use
ServiceFactory can be used outside of WPF and Caliburn.Micro projects, however the default implementation depends on `IDependencyRetriever`, which may be a slightly restrictive interface, due to its Caliburn-oriented nature.

Should you wish to use the ServiceFactory in other contexts, it will still work equally as well, however you might need custom implementations of `IDependencyRetriever` for your specific dependency container (see the **DependencyContainer** section).

Feel free to post pull requests or issues of such usages, informing the author of ways the library can be shaped to facilitate ease of such use.

repository: Aleksbgbg/Wingman

gha_language: C#

gha_license_id: MIT

repo_name: Aleksbgbg/Wingman


text:
  Make Pro 2d Games with Godot

  Open Source A-RPG Demo

This is the full source code with all the system produced for the [Make Professional 2d Games with Godot](https://gumroad.com/l/godot-tutorial-make-professional-2d-games) course.

![The game's boss, the Wild Boar](https://i.imgur.com/Bt57gQH.png)

This game demo tries to show good Godot programming practices to support a growing game project. It has multiple interlocking systems, the core gameplay loop in place, a boss encounter, an inventory and shop systems, user interface with nested menus...

![Grasslands with the two monsters available in the game, the mosquito and the porcupine](https://i.imgur.com/OPg5QEn.png)

## LICENSE ##

The entire source code is available under the MIT licence and everyone is welcome to [contribute](https://github.com/GDquest/make-pro-2d-games-with-godot/issues/)! Better art, gameplay improvements, code re-factoring, and more…

All the techniques I used to build this project are in our [intermediate-level Godot course on Gumroad](https://gumroad.com/gdquest). If you're interested in getting it, be aware it's not 100% step-by-step.

If you have requests for tutorials from elements of that game demo, please feel free to [ask on Twitter](https://twitter.com/NathanGDquest)! I will not redo what's in the course but I'll gladly make extra videos that would benefit everyone! 😄

This is our first open game on GDQuest. We are looking to build more Free games and game creation tools in the future. Be sure to [subscribe to our YouTube channel](http://youtube.com/c/gdquest) to know when that happens ☺

## Features ##

Here's a list of the gameplay features and a few of the systems you will find in the demo

### Gameplay ###

- A player that can walk, jump, and do a three hit combo with a sword
- Two monsters with steering based movement
- Boss with 3 phases, drops random stacks of coins upon dying
- Items, and inventory, and a shop that will cover your basics for an RPG game

### Core systems ###

- LevelLoader, to load maps cleanly, keep the player's data around
- Save and load system
- Game node to handle pause and initialize the game at the start
- Shader to animate the transition between levels

### User interface ###

- An inventory menu and a shop menu where you can buy and sell items between two characters
- A pause menu with sound options
- A system to create life bars that hook onto monsters and follow them in the game world, but that are still managed by the UI system
- The animated player life bar (tutorial)
- Animated boss light bar that appears when the boss spans

### Visual effects ###

- Layered particle systems like explosions, bursting fire, rock sparkles, dust
- Beautiful noise-based fog thanks to [Gonkee](https://github.com/Gonkee/Gonkee-Fog-Shader)

### A few misc extras

- Modular hit box and damage source system to create ranged and melee weapons
- Stats node to manage the player and the monsters' health
- Gaps the player can fall into


text:
---
layout: job
title: "Senior Fullstack Developer "
subtitle: ONGOING
imagejob: /images/fullstackteam_job_offer.png
image-alt-job: Fullstack Team Bright Inventions
hours: Full-time
salary: 20 000 - 24 000 PLN + VAT (B2B) or 16 600 - 19 900 PLN gross (UoP)
salary_min: 16000
salary_max: 24000
working time: 26 paid days off + Polish bank holidays
technology:
  - TypeScript
  - JavaScript
  - Node.js
  - React
title_more_about_us: if you want to know a bit more about us, take a look below 🙋🏻♀🙋🏻♂
show_new_title_more_about_us: true
links_more_about_us: >-
 [How to Start Working at Bright Inventions - A Quick Guide for Candidates
  ](https://brightinventions.pl/blog/how-to-start-working-at-bright-inventions-a-quick-guide-for-candidates/)

  [Screening - How to Get Prepared ](https://brightinventions.pl/blog/recruitment-screening-what-is-it-for/)

  [7 reasons to work at Bright Inventions](/blog/reasons-to-join-bright)

  [No Time for Bullsh\*\*. Feedback Culture](/blog/no-time-for-bullshit-feedback-culture/)

  [Bright Onboarding - What Is Waiting for You](/blog/how-to-make-your-onboarding-bright)
title_recruiter_info: Do you have any questions? Ask Agata from our Bright team!
name_recruiter: Agata
workplace_recruiter: Junior Recruiting Specialist
image_recruiter_info: /images/agata_recruiter.png
image_alt_recruiter_info: Agata Mietlińska - A Recruiter at Bright Inventions
button_linkedin: https://www.linkedin.com/in/agatamietli%C5%84ska/
button: join our bright team
published: true
hidden: false
show_recruiter_info: true
order: 5
recruting_image2_title: interview (technical part & non-technical part)
recruting_image3_title: programming task
description: We are looking now for a Full Stack Developer who has already had
  experience with web development and knows how to build Cloud Platform
  projects.
language: en
---
## bright culture 🧡

At Bright Inventions you'll be an important part of [a group of talented, ambitious and positive developers, designers, managers and marketers](https://brightinventions.pl/about-us/team/) who love to solve real problems and build software that really matters in today’s world.

We place a strong emphasis on accountability, and we value team members **who take ownership of their work and are willing to make improvements based on regular and open feedback.** Positive attitude, flexibility and teamwork are elemental parts of our success. Instead of focusing on problems we empower our team members to identify issues, propose solutions, and contribute to continuous growth.

## about the role 🧑🏻💻🧑🏻💻

We are seeking an experienced Fullstack Developer to join our bright team. The ideal candidate will have **a strong understanding of both frontend and backend development**, along with the ability to work on a variety of projects ranging from web applications to database design.

As a Fullstack Developer, you will collaborate with cross-functional teams to design, develop, and maintain software solutions that meet our clients' needs.  **You will feel great in our team if you are a team player who approach challenges and complexities with a problem-solving mindset and openess to feedback.**

## what you will do 🤝

* collaborate with the product manager/owner to understand project requirements and translate them into technical specifications
* develop responsive and user-friendly frontend applications using modern web technologies
* design and implement server-side logic, APIs, and database structures for backend applications
* participate in code reviews to maintain code quality and ensure best practices
* provide constructive feedback to team members as well as to the clients
* share knowlege with the rest of the team (outside and inside the organisation)

## what we would like to see ✅

* at least 4 years of commercial programming experience as a fullstack develoepr or ina  similar role
* solid understanding of TypeScript/JavaScript
* deep working experience with Node.js and React
* a solution-oriented mindset
* positive approach and flexibility to work on new challenges
* advanced level of English (written and spoken)

## we would also appreciate if you have 🙌

* familiarity cloud platforms and deployment processes
* experience with working on startup projects

## what you will find in our Bright Team 🚀

* culture of responsibility, flexibility, teamwork and positivity
* business value over technical perfection
* flat structure and a great impact on the key project decisions
* flexible schedule and remote work possibility
* mentoring program and regular 1:1 meetings
* continuous feedback and open communication
* MultiSport and private medical package
* company library with an extra budget for professional books
* good equipment: MacBook and additional accessories
* Bright Day once a month for non-project stuff
* weekly sport classes and in-house yoga time
* office in Gdańsk Wrzeszcz with a parking space nearby
* team retreats once a quarter and lunch roulette initiative
* board games evenings

repository: bright/new-www

branch_name: refs/heads/gatsby

gha_language: TypeScript

repo_name: bright/new-www


text:
# SQL Based Storage

The following schemas are needed when using an SQL based storage such as the default DBAL repository implementations.
The given examples are for PostgreSQL, but these could be adjusted for MySQL or others. `event_stream` should be
replaced by the lowercase name of your aggregate(s).

## EventRepository

```postgresql
CREATE TABLE event_stream (
    event_id UUID PRIMARY KEY,
    event_name VARCHAR(100) NOT NULL,
    aggregate_id UUID NOT NULL,
    payload JSON NOT NULL,
    metadata JSONB NOT NULL,
    created_at TIMESTAMP(6) NOT NULL,
    version INT,
    UNIQUE (aggregate_id, version)
);
```

## MetadataRepository

```postgresql
CREATE TABLE event_stream_metadata (
    aggregate_id UUID PRIMARY KEY,
    metadata JSONB NOT NULL
);
```

## SnapshotRepository
```postgresql
CREATE TABLE event_stream_snapshot (
    aggregate_id UUID PRIMARY KEY,
    version INT,
    state TEXT NOT NULL
);
```

repository: MyOnlineStore/event-sourcing

gha_language: PHP

repo_name: MyOnlineStore/event-sourcing


text:
## What?
This is a universal bootstrapper for Java.
It allows you to start any java main class without caring too much about configuring classpath.

## Why ?
Do not have to care about the jar files to pass to the JVM. Or having to script something to go through all libs in some folder to collect jars. Script that will not be the same on linux and Windows.

## How?
First build the bootstrapper.
Then use it like this:

`java -jar itineric-bootstrapper-x.x.x.jar -l lib com.example.MyMainClass -- param1 param2`

To get details about options use `-h` like this:

`java -jar itineric-bootstrapper-x.x.x.jar -h`

repository: itineric/itineric-bootstrapper

repo_name: itineric/itineric-bootstrapper


text:
---
title: Install Portworx on vSphere with Amazon EKS Anywhere
linkTitle: Amazon EKS Anywhere
description: This section describes lists the steps to deploy Portworx on vSphere having Amazon EKS Anywhere.
keywords: portworx, VMware, vSphere, EKS Anywhere, Amazon EKS Anywhere
aliases:
    - /portworx-install-with-kubernetes/on-premise/aws/eks-anywhere/portworx-vsphere-eks-anywhere/
---

Portworx can be installed on a Kubernetes cluster running on vSphere and managed by [Amazon EKS Anywhere](https://anywhere.eks.amazonaws.com).

### Prerequisites

Before you install Portworx on vSphere, ensure that you meet the following prerequisites:

|**Environment**|**Resources**|
|------|------|
|Install

**Note:** Default Bottlerocket base image is not supported.| Ubuntu 20.04.4 LTS
 Ubuntu 18.04.6 LTS|
|Deployment Host

**Note**: The same vSphere host where you deploy EKS-Anywhere.| VM OS: Linux
vCPU: 4
 Memory: 16 GB
 Disk storage: 200 GB|
|Control-Plane VMs| Minimum: 1
 Recommended: 3
vCPUs: 2
 RAM: 8 GB
 OS Volume: 25 GB|
|Worker Node VMs| Minimum: 3 (for storage cluster)
 vCPUs: 8
RAM: 16 GB
 OS Volume: 25 GB|

### Step 1: vCenter user for Portworx

Provide Portworx with a vCenter server user that has either the full admin role, or for increased security, a custom-created role with the following minimum [vSphere privileges](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.security.doc/GUID-FEAB5DF5-F7A2-412D-BF3D-7420A355AE8F.html):

* Datastore
    * Allocate space
    * Browse datastore
    * Low level file operations
    * Remove file
* Host
    * Local operations
    * Reconfigure virtual machine
* Virtual machine
    * Change Configuration
    * Add existing disk
    * Add new disk
    * Add or remove device
    * Advanced configuration
    * Change Settings
    * Extend virtual disk
    * Modify device settings
    * Remove disk

If you created a custom role with the permissions above, select **Propagate to children** when assigning the user to the role.

{{<info>}}
**NOTE:** All commands in the subsequent steps need to be run on a machine with `kubectl` access.
{{</info>}}

### Step 2: Create a Kubernetes secret with your vCenter user and password

{{< content "shared/cloud-references-auto-disk-provisioning-vsphere-vsphere-secret.md" >}}

### Step 3: Generate Portworx spec

1. Navigate to [PX-Central](https://central.portworx.com/) and log in, or create an account.
2. Select **Portworx Enterprise** and click **Continue**.
3. On the **Basic** page, ensure that **Use the Portworx Operator** is selected. Select the latest version of Portworx from the **Portworx Version** drop-down, the **Built-in** option for etcd, and then click **Next**.

2. On the **Storage** page, select **Cloud** as your environment, and **vSphere** as your cloud platform. Select the **Create Using a Spec** option to configure your storage devices, specify the following, and click **Next**:

    * In the **vCenter Endpoint** field, specify the hostname or IP address of your vCenter server.
    * In the **vCenter datastore prefix** field, specify the prefix name of the vCenter datastore you want to use.
    * In the **Kubernetes Secret Name** field, specify the name of the secret that you specified in [Step 2](#step-2-create-a-kubernetes-secret-with-your-vcenter-user-and-password), which is `px-vsphere-secret`.
    * In the **vCenter Port** field, enter port 443, if it is not auto  filled.

3. Choose your network and click **Next**.

4. On the **Customize** page, enable Stork, CSI, Monitoring, and Telemetry in **Advanced Settings** and click **Finish** to generate the spec.

{{< content "shared/portworx-install-with-kubernetes-4-apply-the-spec.md" >}}


text:
# Using Docker

## Pre-built images in DockerHub

There are two types of pre-built images in [DockerHub]:

* Multi-Arch images
  * mirakc/mirakc:latest
    * Alias of mirakc/mirakc:$LATEST_VERSION
  * mirakc/mirakc:$DISTRIBUTION
    * Alias of mirakc/mirakc:$LATEST_VERSION-$DISTRIBUTION
  * mirakc/mirakc:$VERSION
    * Alias of mirakc/mirakc:$VERSION-debian
  * mirakc/mirakc:$VERSION-$DISTRIBUTION

Where:

* VERSION
  * main or version tags
  * LATEST_VERSION points to the latest version tag
* DISTRIBUTION
  * alpine
    * Based on alpine:3.13
  * debian (main platform)
    * Based on debian:buster-slim

Platforms listed below are supported:

* linux/amd64
* linux/arm/v6 (only for alpine)
* linux/arm/v7
* linux/arm64/v8

Each image contains the following executables other than mirakc:

* [recdvb] configured without `--enable-b25`
* [recpt1] configured without `--enable-b25`
* [mirakc-arib]
* [curl]
* [socat]

At this point, Alpine-based images don't work properly on some 32-bit platforms
like Raspberry Pi OS due to [this issue](https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0#musl_1.2).
Use Debian-based images instead.

## Build a custom image

### Install additional software

You can easily build a custom image which contains additional software.

Specify one of pre-built images in the `FROM` directive in `Dockerfile`.  And
then install additional software like below:

```Dockerfile
FROM mirakc/mirakc:alpine

RUN apk add --no-cache ffmpeg
...
```

### Copy mirakc from a pre-built image

If you want to create a cleaner image, you can copy only necessary files from a
pre-built image like below:

```Dockerfile
FROM mirakc/mirakc:alpine AS mirakc-image

FROM alpine:3.13

COPY --from=mirakc-image /usr/local/bin/mirakc /usr/local/bin/
COPY --from=mirakc-image /etc/mirakurun.openapi.json /etc/

...

ENV MIRAKC_CONFIG=/etc/mirakc/config.yml
EXPOSE 40772
VOLUME ["/var/lib/mirakc/epg"]
ENTRYPOINT ["mirakc"]
CMD []
```

Don't copy binary files from a musl-based image (like alpine) into a glibc-based
image (like debian) and vice versa.  Some of binary files in the musl-based
image are dynamic-linked against `musl`.

Use an architecture-specific image if you like to cross-build a custom image.

## Build an image from source

This repository contains the following two Dockerfile files for `docker buildx`:

* [Dockerfile.alpine](../docker/Dockerfile.alpine) for alpine-based images
* [Dockerfile.debian](../docker/Dockerfile.debian) for debian-based images

Use the `--platform` option for specifying your target platforms like blow:

```shell
docker buildx build -t $(id -un)/mirakc:arm32v7 -f docker/Dockerfile.debian \
  --platform=linux/arm/v7 .
```

The following command transfers the created image to a remote docker daemon
which can be accessed using SSH:

```shell
docker save $(id -un)/mirakc:arm32v7 | docker -H ssh://remote load
```

### Support new architectures

`Dockerfile.*` uses scripts in [docker/build-scripts](../docker/build-scripts) for
cross-compiling tools like `recpt1`.  If you want to create Docker images which
have not been supported at this point, you need to modify those scripts.

`vars.*.sh` defines variables used in other scripts.  The target platform string
will be passed using the `TARGETPLATFORM` environment variable in the build time.
See the following page for details about `BUILDPLATFORM` and `TARGETPLATFORM`:

* https://docs.docker.com/buildx/working-with-buildx/#build-multi-platform-images

[recdvb]: http://cgi1.plala.or.jp/~sat/?x=entry:entry180805-164428
[recpt1]: https://github.com/stz2012/recpt1
[mirakc-arib]: https://github.com/mirakc/mirakc-arib
[curl]: https://curl.haxx.se/docs/manpage.html
[socat]: http://www.dest-unreach.org/socat/doc/socat.html
[DockerHub]: https://hub.docker.com/r/mirakc/mirakc

repository: shirow-github/mirakc

repo_name: shirow-github/mirakc


text:
##  Checks 1099 Update (CHECKS.E3)

<PageHeader />

##

![](./CHECKS-E3-1.jpg)

**Check#** Enter the check number which you want to update for notes or 1099
data.

**Co.Code** The company code for this check.

**Vendor#** The vendor number to which the check is being paid.

**Name** The name of the vendor or rep to which the check is being paid.

**Rep Id** The rep number to which the check is being paid.

**Check.Date** Enter the date which appears on the check.

**Check.Amt** The amount for which the check was issued.

**Disb.Acct#** The G/L account number from which this check is being paid.

**Disc.Amt** The amount of discount which was taken on this check.

**Disc.Acct#** The G/L account number which is being credited for the discount
amount.

**Status** The status of this check record. P = Posted V = Void S = Stop
Payment C =

**Notes** Enter any notes applicable to this check.

**Amount for 1099** This is the total expense amount flagged for 1099
reporting as recorded in the 1099 file. It is based on the amounts flagged
below and/or the vendor and rep 1099 settings. If the 1099 amount needs to be
manually adjusted, enter the new amount here. This amount will be recorded on
the 1099 file for the year. The 1099 file must be generated before this amount
can be adjusted.

**Expense Acct** The expense account for the associated amount.

**Acct.Desc** This field contains the description of the GL account.

**Expense Amt** Enter the expense amount for the associated account number.

**1099** Check here if this expense item will be included in 1099 reporting
for the vendor or rep. If this check number is not related to a vendor or rep
number, then this box cannot be checked.

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

<PageFooter />

repository: zumasys/docs

gha_language: JavaScript

repo_name: zumasys/docs


text:
# eMarket

A web project based on MVC model that primarily serves as an online marketplace. Users can sell items or browse items put on sale by others.

## Getting Started

Before trying to run the project create a database for the project by importing __e-market_project.sql__ file present inside __models__ folder.
1. Type in following commands on CLI of Cloud9 if using CS50 IDE
      * apache50 start ./_project_name_
      * mysql50 start
2. If using XAMPP, simply store the project in the htdocs folder. Navigate to the public folder using browser.

## Features

1. Create account and manage it.
2. Sell and Buy item.
3. Comment using _disqus API_.
4. Receive relevant notifications using _OneSignal API_.
5. Message and chat with other users using _SendBird API_.

## Built With

* [Sublime Text](https://www.sublimetext.com/) - A sophisticated text editor for code, markup and prose
* [XAMPP](https://www.apachefriends.org/index.html) - PHP development environment
* [OneSignal](https://onesignal.com/) - Multi-platform Push Notification Service
* [Disqus](https://disqus.com/) - Comments Plugin
* [SendBird](https://sendbird.com/) - Messaging SDK and Chat API for Websites

## License

This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details


text:
2.0.12 / 2015-09-22
===================

  * Release 2.0.11
  * update localytics
  * Merge pull request #436 from graingert/ISO8601
  * Use invariant locale for ISO8601 date formatter

2.0.11 / 2015-09-22
===================

  * update localytics

2.0.10 / 2015-09-16
===================

  * Merge pull request #432 from segmentio/uxcam
  * uxcam: update header
  * bump uxcam

2.0.9 / 2015-09-15
==================

  * Fix podfile for 0.38.0+

2.0.8 / 2015-09-11
==================

  * Fix mixpanel import (#417)

2.0.7 / 2015-09-11
==================

  * Add support for custom dimensions and metrics.
  * Send revenue to Localytics and not cents
  * Upgrade GoogleAnalytics to 3.13.0
  * Updating Amplitude SDK v3.0.0

2.0.6 / 2015-08-20
==================

  * Fix typo
  * Prevent crash when error occurs writing payload to disk

2.0.5 / 2015-08-11
==================

  * Update Taplytics to 2.4.0
  * Fix how Optimizely root is enabled

2.0.4 / 2015-08-11
==================

  * pod: fixes for kahuna

2.0.3 / 2015-08-11
==================

  * mixpanel: update to 2.8.2 (close #400)
  * Fix kahuna link
  * Integration file changes were removed during fetching from segment repo. Redoing it.
  * SDK 2 Segment wrapper changes.

2.0.2 / 2015-08-10
==================

  * Fix import (close #388)
  * Merge pull request #399 from segmentio/fix/circle
  * remove some links

2.0.1 / 2015-08-06
==================

  * Fix uxcam
  * add use-libraries to pod release
  * fix platform versions

2.0.0 / 2015-08-06
==================

  * bump deployment target to 7 for moengage

1.12.8 / 2015-08-06
===================

  * fix script require

1.12.7 / 2015-08-06
===================

  * update package.json for npm org

1.12.6 / 2015-08-06
===================

  * Fix links to libs

1.12.5 / 2015-07-31
===================

  * Update Kahuna integration to avoid clashing with MoEngage

1.12.4 / 2015-07-31
===================

  * Update Kahuna SDK
  * Kahuna: Added the IF condition for forwarding failedToRegisterError in case it was recorded.

1.12.3 / 2015-07-31
===================

  * Fix Kahuna push notification swizzling

1.12.2 / 2015-07-20
===================

  * Update Taplytics to 2.3.12
  * Add MoEngage integration
  * Fix mixpanel screen method to respect trackNamedPages and trackCategorizedPages
  * Update Google Analytics

1.12.1 / 2015-07-13
===================

  * Add Optimizely Root integration
  * Add Apptimize root integration
  * Update Countly SDK
  * Add UXCam Integration

1.12.0 / 2015-06-22
===================

  * Clean up auto synthesized properties in subclasses
  * Force ISO 8601 for sentAt timestamp
  * Remove deprecated header files
  * Update Tapstream SDK
  * Update Quantcast SDK
  * Update Optimizely SDK
  * Update Mixpanel SDK
  * Update Localytics SDK
  * Update Google Analytics SDK
  * Update Flurry SDK
  * Update Countly SDK
  * Update Bugsnag SDK
  * Update Apptimize SDK
  * Update Amplitude integration
  * Make Tapstream headers public

1.11.13 / 2015-06-15
====================

  * Update Crittercism pod
  * Update Taplytics to 2.1.96
  * Force ISO 8601 Dates
  * Update AppsFlyer
  * Added pushSandbox option to Taplytics.

1.11.12 / 2015-06-09
====================

  * Use infoDictionary and override with values from localizedInfoDictionary
  * Added delayLoad, and shakeMenu options for Taplytics. Removed random, old files in Tapstream's directory.
  * Call [super start] in all integrations

1.11.11 / 2015-06-01
====================

  * Write copies of queue, traits

1.11.10 / 2015-05-27
====================

  * Localytics: Dismiss In App Messages
  * Send custom dimensions to Localytics
  * Kahuna: Move push registration to start method
  * Fix: Added more checks for concurrency
  * Updated Taplytics. Added group functionality
  * Enable Monitoring web views for Crittercism
  * Update Crittercism Integration
  * Update Optimizely SDK

1.11.9 / 2015-05-18
===================

  * seg: remove use of mutable traits, use immutable live context
  * Merge pull request #313 from segmentio/send-context.traits
  * Send context.traits
  * Bump pod
  * Merge pull request #311 from jonathannorris/Taplytics-2.1.86
  * Updated Taplytics to 2.1.86

1.11.8 / 2015-05-11
===================

  * Use Localized Info Dictionary instead of default
  * Respect trackAllPages setting for Amplitude
  * Respect trackAllPages setting for Mixpanel
  * Add Kahuna Integration
  * Add Apptimize Integration.
  * Update Amplitude to version 2.4.0

1.11.7 / 2015-05-05
===================

  * Use the right context for sending custom context fields
  * Fix for iOS 6 compatibility
  * Updated Taplytics 2.1.82

1.11.6 / 2015-05-03
===================

  * Actually send custom context fields

1.11.5 / 2015-05-01
===================

  * Updated Taplytics to 2.1.78
  * Add ability to send custom context fields
  * Update Kahuna integration
  * Check CBCentralManagerOptionShowPowerAlertKey != NO
  * Swift support
  * Add flush method
  * Add alias method
  * Update Google Analytics integration and sets the segment tracker always as default

1.11.3 / 2015-03-27
===================

  * Drop flaky test
  * Update Amplitude integration to 2.3.0
  * Update Kahuna Integration
  * Send location to flurry

1.11.2 / 2015-03-10
===================

  * Merge pull request #273 from jonathannorris/Taplytics-2.1.60
  * Updated Taplytics to 2.1.60
  * Merge pull request #269 from jonathannorris/Taplytics-2.1.56
  * Merge pull request #268 from segmentio/fix-plan
  * Updating Taplytics to 2.1.56
  * All enabled events should be sent to Segment

1.11.1 / 2015-03-06
===================

  * Update bugsnag dependency
  * Update localytics
1.11.0 / 2015-02-24
===================

  * Merge pull request #266 from segmentio/tracking-plan
  * Tracking Plan
  * bugsnag: add headers from last update
  * tests: improve output for header test

1.10.5 / 2015-02-18
==================

 * Merge branch 'master' of github.com:segmentio/analytics-ios
 * Fix call to localytics (#259)
 * Merge pull request #261 from jonathannorris/Taplytics-reset-user
 * Merge pull request #260 from jonathannorris/Taplytics-2.1.46
 * Merge pull request #262 from y-ogi/fix/mixpanel_people_settings
 * bug fixed: Even if you set "People" off on Segment, the SDK always calls "trackChage" API of Mixpanel.
 * Added reset user function, requires #260
 * Updated Taplytics to 2.1.46
 * Merge branch 'master' of github.com:segmentio/analytics-ios
 * Update history.md
 * Fix release script to include history.md changes
 * Merge pull request #255 from jonathannorris/Taplytics-2-1-42
 * updated Taplytics to 2.1.42

1.10.4 / 2015-02-12
==================

 * Add headers
 * Update bugsnag to 4.0.1
 * Update history.md

1.10.3 / 2015-02-12
==================

 * Merge pull request #256 from segmentio/catch-serialization-error
 * Catch serialization errors
 * Merge pull request #210 from segmentio/fix/localytics
 * localytics customer lifetime value
 * Ignore IDE files
 * Update history.md

1.10.2 / 2015-02-09
==================

 * Fix cached traits to be included in context.traits

1.10.1 / 2015-02-05
==================

 * Update test
 * Add kahuna header
 * Add deps target to makefile
 * Add separate build phase for opening release dir in finder
 * Taplytics 2.1.36

1.10.0 / 2015-02-04
==================

 * Add kahuna

1.9.1 / 2015-02-03
==================

 * Fix dupd symbols
 * Updated Taplytics to 2.1.34

1.9.0 / 2015-02-02
==================

 * Fix localytics
 * Remove testflight
 * Add bugsnag logger header
 * updating Taplytics to 2.1.32

1.8.15 / 2015-01-21
==================

 * Update optimizely to 1.0.75

1.8.14 / 2015-01-19
==================

 * updated Taplytics to 2.1.26
 * updating Taplytics integration to support user attributes and analytics events
 * Properly cast objc_msgSend calls
 * Fix mapping of createdAt -> $created

1.8.13 / 2015-01-15
==================

 * Upload localytics to 3.0.0

1.8.12 / 2015-01-13
==================

 * Update optimizely
 * Updating Taplytics to 2.1.22
 * Update Amplitude to v2.2.4

1.8.11 / 2015-01-09
==================

 * Add app.namespace to be bundle identifier

1.8.10 / 2015-01-05
==================

 * Update Taplytics to v2.1.20
 * add support for GA remarketing

1.8.10 / 2015-01-05
==================

 * Update Taplytics to v2.1.20
 * add support for GA remarketing

1.8.8 / 2014-12-12
==================

 * Fix cli-release script to update changelog
 * Update google analytics to 3.10
 * Fix reachability

1.8.7 / 2014-12-02
==================

 * Update mixpanel to 2.6.0

1.8.2 / 2014-10-30
==================

 * tapstream: post notification that integration has started
 * mixpanel: add check that user id isn't nil before identifying (just prevents an NSLog call they were making)

1.8.1 / 2014-10-30
==================

 * tapstream: update to 2.8.3

1.8.0 / 2014-10-23
==================

 * add: api for enabling/disabling ad tracking

1.7.10 / 2014-10-21
==================

 * mixpanel: update to 2.5.4

1.7.9 / 2014-10-21
==================

 * add: timezone to context
 * taplytics: add missing headers

1.7.8 / 2014-10-20
==================

 * localytics: fix call to register notifications
 * localytics: update to 2.71.0
 * taplytics: update to 2.0.10

1.7.7 / 2014-09-18
==================

 * Update mixpanel to 2.5.3
 * appsflyer: add logs

1.7.6 / 2014-09-16
==================

  * mixpanel: fix resources being bundled

1.7.5 / 2014-09-08
==================

  * flurry: track screen calls as events (disable via a setting in the web ui)

1.7.4 / 2014-09-08
==================

  * update: mixpanel to 2.5.1

1.7.3 / 2014-08-28
==================

  * fix: remote notification invocation

1.7.2 / 2014-08-28
==================

  * updat: localytics to 2.6.0

1.7.1 / 2014-08-28
==================

  * update: mixpanel to 2.5.0

1.7.0 / 2014-08-27
==================

  * add: appsflyer
  * fix: leak warnings

1.6.2 / 2014-08-26
==================

  * add: add -reset for ga

1.6.1 / 2014-08-25
==================

  * fix: remove log

1.6.0 / 2014-08-25
==================

  * add: testflight
  * fix: queue dispatching to integrations until settings request is finished
  * fix: improve logging for disabled integrations
  * fix: namespace async utils with seg\_

1.5.11 / 2014-08-20
==================

  * fix: remote notification forwarding
  * add: ecommerce to ga

1.5.10 / 2014-08-12
==================

  * update: ga to 3.0.9
  * fix: reachability name clashing

1.5.9 / 2014-08-12
==================

  * fix: add rest of integration headers as public
  * fix: add tests for integration headers to be included as public

1.5.8 / 2014-08-08
==================

  * fix: use introspection for iad

1.5.7 / 2014-08-08
==================

  * fix: enable optimizely's mixpanel integrations
  * fix: add checks for bluetooth symbols before use
  * fix: add build module to improve building the sdk
  * udpate: ga to 3.0.7

1.5.6 / 2014-08-07
==================

  * fix: iad to be weaker

1.5.5 / 2014-08-07
==================

  * fix: include all tapstream headers
  * fix: make advertising managers use anonymous
  * fix: include locale
  * fix: fix thread-safety of SEGLocation

1.5.4 / 2014-08-04
==================

  * fix: analytics version set correctly when installed from cocoapods
  * fix: iad referrer get/set once rather than when queued
  * fix: warning to import top-level framework headers
  * fix: set iad, adsupport, bluetooth as weak frameworks

1.5.3 / 2014-07-31
==================

  * update: optimizely to 0.6.52

1.5.2 / 2014-07-25
==================

  * fix: getting case-insensitive properties with mixpanel
  * fix: weak usage of bluetooth
  * fix: quantcast sessioning
  * add: send referrer data when installed from iad referrer

1.5.1 / 2014-07-20
==================

  * fix: bad import

1.5.0 / 2014-07-20
==================

  * add: optimize
  * remove: apptimize

1.4.0 / 2014-07-17
==================

  * add: -registerForRemoteNotificationsWithDeviceToken:options:

1.3.1 / 2014-06-19
==================
* fix: enabling/disabling integrations

1.3.0 / 2014-06-16
==================
* add: apptimize integration

1.2.1 / 2014-06-19
==================
* fix: manual install issue with taplytics
* fix: build phase error

1.2.0 / 2014-06-10
==================
* add: taplytics integration
* fix: add Analytics.h to public headers
* fix: ci tests

1.1.0 / 2014-06-03
==================
* add: ability to configure the lib with the new SEGAnalyticsConfiguration api

1.0.2 / 2014-05-31
==================
* fix: logging errors
* fix: attempt to flush queue when flushAt is updated
* fix: log when CLLocationManager errors
* fix: document SEGAnalyticsConfiguration

1.0.1 / 2014-05-30
==================
* fix: localytics subspec to dependend on Localytics-iOS-Client podspec
* fix: make parameter asserts more informative
* fix: use xctest

1.0.0 / 2014-05-23
==================
* add: ability to build specific integrations
* fix: using segment's spec
* fix: compiler error not finding +[Flurry setPushToken:]
* fix: make parameter asserts more informative
* fix: use NSCParameterAssert consistently

0.11.5 / 2014-05-14
==================
* fix: using adsupport framework optionally

0.11.4 / 2014-05-14
==================
* fix: incrementing and blocked events in segment integration
* fix: using ASIdentifierManager when adsupport framework isn't linked

0.11.3 / 2014-05-12
==================
* fix: including idfa to tapstream integration

0.11.2 / 2014-06-10
==================
* fix: debug logs to only happen when debug is enabled

0.11.1 / 2014-06-01
==================
* fix: including quantcast headers

0.11.0 / 2014-06-10
==================
* add: quantcast integration
* add: wifi, bluetooth, location, address to be sent
* fix: travisci to use utf-8
* fix: prefix screen events with Viewed
* fix: minor fixes to match segment's spec
* update: localytics depdency

0.10.6 / 2014-06-10
==================
* fix: podspec to require arc

0.10.5 / 2014-4-12
==================
* Added support for Mixpanel increment

0.10.4 / 2014-4-12
==================
* Updated Mixpanel from 2.3.2 to 2.3.4
* Updated Crittercism from 4.3.1 to 4.3.3
* Updated Flurry from 4.3.2 to 4.4.0
* Updated Google Analytics from 3.0.3c to 3.0.6
* Exposed remaining Google Analytics headers
* Added support for Google Analytics userId
* Fixes traits to copy, thanks @realf!

0.10.2 / 2014-3-14
==================
* Updating Amplitude to new 2.0

0.10.1 / 2014-3-1
=================
* Fixing Localytics to arm64 build
* Fixing Mixpanel flush before reset

0.10.0 / 2014-2-23
==================
* Updating Google Analytics SDK to 3.0.3c
* Updating Localytics SDK to AMP 2.22.0
* Updating Mixpanel SDK to 2.3.2
* Removing dependency on AdSupport

0.9.9 / 2014-2-17
=================
* Bundling resources for Mixpanel
* Adding disable/enable methods for handling optout
* Adding reset method for handling user logout
* Updating Flurry, Google Analytics SDKs
* Updated settings url to be https
* Changing settings request to update on app foreground rather than timer

0.9.8 / 2014-2-5
================
* Updating Mixpanel to 2.3.1 and Flurry to 4.3.1
* Adding MPNotification.h

0.9.7 / 2014-1-30
=================
* Ensuring that no "touchdown" references are in the SDK

0.9.6 / 2014-1-27
=================
* Fixing Pods arm64 build issue to fix support for 64-bit devices

0.9.5 / 2014-1-25
=================
* Fixing Pods x86_64 build issue to fix support for 64-bit simulators

0.9.4 / 2014-1-23
=================
* Updating Localytics, Crittercism, Flurry, Google Analytics, Mixpanel and TapStream SDKs
* Removing support for Chartbeat since their lib doesn't have an arm64 slice
* Moving support for Omniture to server-side
* Adding arm64 slice to the fat lib to fully support iOS 7

0.9.3 / 2014-1-14
=================
* Fixing background event handling for Localytics

0.9.2 / 2014-1-10
=================
* Saving userId to disk for persistence between app launches

0.9.1 / 2013-12-29
==================
* Fixing issue with Countly threading
* Adding UUID for tracing events in Segment.io
* Adding timestamp for future time-correction in Segment.io
* Cleaning up docs in Analytics.h

0.9.0 / 2013-12-18
==================
* Setting up Travis-CI testing
* Adding Tapstream support
* Updating Mixpanel to 2.2.1
* Updating Bugsnag to 3.1.0
* Adding Reachability test case to prevent regressions
* Updating minimum iOS version to 6 since only 4% of devices are using older
* Adding support for alias

0.8.0 / 2013-11-27
==================
* Adding Crittercism support
* Fixing Omniture file references in build system

0.7.5 / 2013-11-10
==================
* Adds support for Omniture eVars and props
* Changes "context" to "options"

0.7.4 / 2013-11-8
=================
* Adds support for Mixpanel Surveys
* Adds support for Omniture SiteCatalyst by Adobe
* Improves internal reporting to Segment.io

0.7.3 / 2013-11-8
=================
* Fixes critical issue #60 with NSContainer array subscripting, many thanks to @lhasiuk

0.7.2 / 2013-11-6
=================
* Fixes critical issue #60 with NSContainer array subscripting, many thanks to @lhasiuk

0.7.1 / 2013-11-6
=================
* Fixing issue with Localytics not accepting booleans or integers, only strings.

0.7.0 / 2013-10-29
==================
* Changing debug to a class method
* Updating the internals so that reset method is unnecessary
* Fixing issue with cached settings
* Updating Mixpanel SDK to 2.0.4

0.6.6 / 2013-10-21
==================
* Updating Google Analytics SDK
* Fixing internal version number

0.6.5 / 2013-10-14
==================
* Updating Google Analytics, Chartbeat, Flurry and Amplitude SDKs
* Fixes common linker issue with old Google Analytics SDK

0.6.4 / 2013-10-2
=================
* Fixed identify to allow nil userId

0.6.3 / 2013-9-13
=================
* Fixing backgrounding crash issue
* Improving Countly logging
* Merging @cristianbica's pull request to fix literals syntax for iOS 5

0.6.2 / 2013-9-10
=================
* Queueing before settings cache is loaded the first time
* Flushing data to Segment.io on app close
* Using a custom store in NSUserDefaults to maintain user identity
* Prefixing internal classes to prevent compilation time conflicts
* Updating the Flurry and Mixpanel SDKs (iOS 7 support)
* Adding support for Mixpanel push notifications

0.5.3 / 2013-7-31
=================
* Adding comments, documentation and setup guide to Analytics.h
* Automatically handling app state hooks internally

0.5.2 / 2013-7-12
=================
* Adding Cocoapod podspec, with testing project
* Updating podspec to download from AWS rather than Github Raw

0.5.1 / 2013-7-11
=================
* Fixing build settings to include an armv7s slice, optimized for iPhone 5
* Moving version number to be visible externally from the library

0.5.0 / 2013-7-5
================
* Fixing compile and run-time bugs
* Adding a complete testing app, including for crash reporting tests
* Adding debug logging setting to reduce debug log output by default

0.4.0 / 2013-6-18
================
* Adding provider headers and binaries to project
* Restructuring project for Framework Builds vs CocoaPod builds

0.3.4 / 2013-6-16
================
* Removing Crittercism to avoid HockeySDK PLCrashReporter collisions
* Adding support for context.providers to ProviderManager

0.3.3 / 2013-6-5
================
* Implementing the reset method to help with debugging

0.3.2 / 2013-6-2
================
* Cleaning up NSLogs everywhere

0.3.1 / 2013-6-1
================
* Removing OS X Platform from podfile

0.3.0 / 2013-6-1
================
* Re-architecting the library to bundle providers
* Adding support for Amplitude
* Adding support for Bugsnag
* Adding support for Chartbeat
* Adding support for Countly
* Adding support for Crittercism
* Adding support for Flurry
* Library now downloads the provider settings from the Segment.io server

0.2.2 / 2013-4-24
=================
* Fixing timestamps to include millisecond precision

0.2.1 / 2013-4-16
=================
* Fixing initWithSecret method signature in header file

0.2.0 / 2013-4-16
=================
* Simplifying sessionId to behave the same on iOS 6 as on iOS 5 and OS X
* Fixing reset function to actually destroy userId and roll sessionId

0.1.1 / 2013-4-11
=================
* Added a getSessionId method

0.1.0 / 2013-4-11
=================
* Added a testing suite
* Added context variable, which includes device info and metadata for Segment.io
* Added alias method

0.0.5 / 2013-4-1
================
* Merged fix from @pkamb to fix types in logging statements.

0.0.4 / 2013-3-23
==================
* Removed UDID usage after Apple's announcement that it will no longer be accepted in the app store https://developer.apple.com/news/?id=3212013a
* Renamed repo to analytics-ios-osx

0.0.3 / 2013-3-13
==================
* Made timestamp more accurate
* Added max batch size

0.0.2 / 2013-3-12
==================
* Merged in numerous improvements from [tonyxiao](https://github.com/tonyxiao)
    * support for OSX apps
    * a shared dispatch queue and async flushing
    * removed JSON library dependency to use native JSON support
* Added enqueueAction to DRY things up
* Added an optional initialization method that reveals flushAt and flushAfter
* Added Cocoapods podspec

0.0.1 / 2013-3-9
==================
* Added working library for iOS
* Added README

repository: orta/analytics-ios

repo_name: orta/analytics-ios


text:
# dotenv-safe

Identical to [`dotenv`](https://github.com/motdotla/dotenv), but ensures that all necessary environment variables are defined after reading from `.env`.
These needed variables are read from `.env.example`, which should be commited along with your project.

[![Build Status](https://travis-ci.org/rolodato/dotenv-safe.svg)](https://travis-ci.org/rolodato/dotenv-safe)

# Installation

```
npm install --save dotenv-safe
```

```
yarn add dotenv-safe
```

# Example

```dosini
# .env.example, committed to repo
SECRET=
TOKEN=
KEY=
```

```dosini
# .env, private
SECRET=topsecret
TOKEN=
```

```js
// index.js
require('dotenv-safe').config();
```

Since the provided `.env` file does not contain all the variables defined in
`.env.example`, an exception is thrown:

```
MissingEnvVarsError: The following variables were defined in .env.example but are not present in the environment:
  TOKEN, KEY
Make sure to add them to .env or directly to the environment.

If you expect any of these variables to be empty, you can use the allowEmptyValues option:
require('dotenv-safe').config({
  allowEmptyValues: true
});
```

Not all the variables have to be defined in `.env`, they can be supplied externally.
For example, the following would work:

```
$ TOKEN=abc KEY=xyz node index.js
```

# Usage

Requiring and loading is identical:

```js
require('dotenv-safe').config();
```

This will load environment variables from `.env` as usual, but will also read any variables defined in `.env.example`.
If any variables are already defined in the environment before reading from `.env`, they will not be overwritten.
If any variables are missing from the environment, a [`MissingEnvVarsError`](MissingEnvVarsError.js) will be thrown, which lists the missing variables.
Otherwise, returns an object with the following format:

```js
{
  parsed: { SECRET: 'topsecret', TOKEN: '' },          // parsed representation of .env
  required: { SECRET: 'topsecret', TOKEN: 'external' } // key/value pairs required by .env.example
                                                       // and defined by environment
}
```

If all the required variables were successfully read but an error was thrown when trying to read the `.env` file, the error will be included in the result object under the `error` key.

`dotenv-safe` compares the actual environment after loading `.env` (if any) with the example file, so it will work correctly if environment variables are missing in `.env` but provided through other means such as a shell script.

## Continuous integration (CI)

It can be useful to depend on a different set of example variables when running in a CI environment.
This can be done by checking if the `CI` environment variable is defined, which is supported by virtually all CI solutions.
For example:

```js
require('dotenv-safe').config({
  example: process.env.CI ? '.env.ci.example' : '.env.example'
});
```

# Options

[Same options and methods supported by `dotenv`](https://github.com/motdotla/dotenv#options).

```js
require('dotenv-safe').config({
    allowEmptyValues: true,
    example: './.my-env-example-filename'
});
```

## `allowEmptyValues`

If a variable is defined in the example file and has an empty value in the environment, enabling this option will not throw an error after loading.
Defaults to `false`.

## `example`

Path to example environment file.
Defaults to `.env.example`.

# Motivation

I regularly use apps that depend on `.env` files but don't validate if all the necessary variables have been defined correctly.
Instead of having to document and validate this manually, I prefer to commit a self-documenting `.env` file (no values, key names only) which can be used as a reference.

repository: globocom/secDevLabs

extension: markdown

repo_name: globocom/secDevLabs


text:
pyof: Python bindings for openFrameworks
========================================

Currently these bindings are for Mac OS X only. They only wrap the
core openFrameworks library (don't include any of the addons).

About OpenFrameworks
--------------------

OpenFrameworks is a C++ library designed to assist the creative process by
providing a simple and intuitive framework for experimentation.

The library is designed to work as a general purpose glue, and wraps together
several commonly used libraries under a tidy interface: OpenGL for graphics,
rtAudio for audio input and output, freeType for fonts, freeImage for image
input and output, Quicktime for video playing and sequence grabbing.

For more information see [http://www.openframeworks.cc](http://www.openframeworks.cc).

Dependencies
------------

* [openFrameworks 0062](http://www.openframeworks.cc)
* [Python](http://www.python.org) - tested with 2.6.5
* [SWIG](http://http://www.swig.org/) - tested with version 2.0.1

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

Copy the pyof folder to your openFrameworks root folder. The location is important,
as the openFrameworks libraries are linked using relative path names. The directory
structure should look like this:

    openFrameworks
    |
    --- addons
    |
    --- apps
    |
    --- libs
    |
    --- other
    |
    --- pyof
    |
    --- scripts
    |
    --- xcode templates

In the pyof folder, run the following command to build the extension module:

    $ python setup.py build

Then to install the module in your Python site-packages directory:

    $ python setup.py install

Finally, if you do not have a copy of the fmodex dynamic library in your
/usr/local/lib folder (or equivalent), run the following command:

    sudo cp ../libs/fmodex/lib/osx/libfmodex.dylib /usr/local/lib

### A note for Snow Leopard Users

As the Quicktime framework is 32-bit only, you must use a version of Python
that supports 32-bit. The version is provided by Apple and that comes with
Snow Leopard is compiled for PPC, i386 and x86_64 architectures. If you
build your own version of Python, make sure that the i386 architecture
is included at least.

The following commands will build and install Python
for i386 and x86_64 (Intel processors) on Snow Leopard:

    ./configure --enable-framework
                --enable-universalsdk=/Developer/SDKs/MacOSX10.6.sdk
                --with-universal-archs=intel

    make

    sudo make frameworkinstall

Use
---

Have a look at the file sinewave.py in the examples folder.

Contributing
------------

Send any comments, queries, suggestions or bug reports to j at johnglover dot net.

repository: bttaylor/pyof

repo_name: bttaylor/pyof


text:
# Balcony Shelves for a Small City Balcony

For years we struggled to use our balcony for anything useful because it is so small and it is impossible to mount something to the walls. We the decided to add to new elements to the balcony: A shelf with a wood cladded wall to mount herb pots and a two story raised bad with a net for climbing plants such as tomatoes.

The first project was a sturdy shelf to store all the related things for gardening: compost, tools, fertilizer, pots etc. Additionally the shelf can be used to place pottet plants in the sun. The backwall has a wood cladded wall that is mounted to the balcony structure with pipe clamps where different herbs can be hung for the most efficient space use.

I used [these galvanized balcony pots](https://www.otto.de/p/astor24-pflanzkuebel-haengetoepfe-zink-blumentopf-garten-balkon-blumen-topf-kraeutertopf-gelaendertopf-6-haengetoepfe-pastell-hochwertig-verarbeitet-S0I2M0XW), shortened the hanger and bent it to fit around the wooden cladding.

![shelf](../assets/balcony/shelf.png)
_(The shelf with the cladded wall for herbs)_

The second part of the project was inspired by raised beds. To save space, I decided to make a two story raised bed. The lower level is still sunny most of the day and can be used for strawberries, chilies etc. The upper level is intended for tomatoes and other plants that have to be tied to something.

![raised bed](../assets/balcony/raised_bed.png)
_(The raised beds with strawberries and space for tomatoes)_

repository: TimGoll/TimGollDE

repo_name: TimGoll/TimGollDE


text:
# University of London: Responsive Web Design

<img src="https://i.imgur.com/t4CJvim.png">

![University of London](http://i.imgur.com/Qktqnu1.png) INSTRUCTORS
#### Instructors: Dr Matthew Yee-King, Dr Marco Gillies, Dr Kate Devlin, Dr Mick Grierson

In this course you will learn how to apply concepts from interaction design and human computer interaction in order to design and build an interactive, professional looking website. You will learn how to make your web page designs adapt to different screen sizes using responsive grid layouts. You will learn how to add navigation and other design elements, and you will learn how to separate data and display using JavaScript objects and templates.

## Course include

1. Explain why users need to know where they are, where they can go and what is on a web page
2. Create wireframe mockups of web pages
3. Identify the key functional elements of web pages
4. Use Bootstrap components to realise page designs
5. Use JavaScript data structures such as arrays and objects to define the data used in a web page
6. Use the Handlebars template library to convert data to HTML
7. Add interactivity to templates using JavaScript event listeners

url: https://raw.githubusercontent.com/Mudasirrr/Courses-/fa566235d6b9751f73c69d0d46351a14fcdeb585/University of London - Responsive Website Development and Design Specialization/University of London - Responsive Web Design/README.md

repository: Mudasirrr/Courses-

repo_name: Mudasirrr/Courses-