This terraform module allows you to deploy GraphDB instance in Google Compute Engine.

• About GraphDB
• Features
• Versioning
• Prerequisites
• Inputs
• Quick Start
• Metadata
• Resources
• Local Development
• Release History
• Contributing
• License

Ontotext GraphDB is a highly efficient, scalable and robust graph database with RDF and SPARQL support. With excellent
enterprise features,
integration with external search applications, compatibility with industry standards, and both community and commercial
support, GraphDB is the
preferred database choice of both small independent developers and big enterprises.

The module provides the building blocks of configuring, deploying and provisioning a single VM of GraphDB
using Google Compute Engine. Key features of the module include:

• Google Cloud Compute Engine Instance

The Terraform module follows the Semantic Versioning 2.0.0 rules and has a release lifecycle separate from the GraphDB
versions. The next table shows the version compatability between GraphDB, and the Terraform module.

Before you begin using this Terraform module, ensure you meet the following prerequisites:

• Google Cloud CLI:
  Google Cloud CLI

• Terraform Installed: You should have Terraform installed on your local machine. You can download Terraform from
  the [https://developer.hashicorp.com/terraform/install?product_intent=terraform](Terraform website).

• Google Cloud Credentials: Ensure that you have Google Cloud credentials configured on your machine. You can configure Google Cloud access
  keys and secret keys using the Google Cloud CLI.

• Terraform Google Cloud Provider Configuration: Configure the Google Cloud provider in your Terraform project. You can add your Google Cloud
  access and secret keys as environment variables or use other methods for provider configuration.

terraform init
terraform apply

Additionally, to specify custom values for the variables, you can use a .tfvars file, or specify individual
variables on the command line, e.g. -var project_id=<test-project>.

To update and validate the metadata.yaml and metadata.display.yaml you can use Google’s CFT
tool https://pkg.go.dev/github.com/GoogleCloudPlatform/cloud-foundation-toolkit/cli/bpmetadata

Run the following command in the project directory to regenerate the metadata:

cft blueprint metadata -d -p .

Or simply to validate:

cft blueprint metadata -v -p .

• Examples for configuring Blueprint metadata
  • https://github.com/GoogleCloudPlatform/marketplace-tools/blob/master/examples/terraform/wordpress/metadata.display.yaml
  • https://github.com/g-awmalik/terraform-google-canonical-mp/blob/main/metadata.display.yaml
• Blueprint reference https://pkg.go.dev/github.com/GoogleCloudPlatform/cloud-foundation-toolkit/cli/bpmetadata

Instead of using the module dependency, you can create a local variables file named terraform.tfvars and provide
configuration overrides there.
Here’s an example of a terraform.tfvars file:

project_id = "example-project-id"

zone = "us-central1-a"

machine_type = "n2-highmem-8"

boot_disk_size = "500"

boot_disk_type = "pd-ssd"

allowed_ingress_cidrs = ["0.0.0.0/0"]

All notable changes between version are tracked and documented at CHANGELOG.md.

Check out the contributors guide CONTRIBUTING.md.

This code is released under the Apache 2.0 License. See LICENSE for more details.

A simple one page website for professional resume.

Rexumee is using a minimalize Spring Boot stack with embedded web server, and a YAML file for the resume content. Just download (clone) the source code, build and test from local environment or build the Docker container for production deployment.

• Java 8
• Maven, as build system and dependency management.
• Spring Boot 1.5.x, as main web framework and project bootstrapping.
• Apache Freemarker, html template engine.
• Project Lombok, a library to help minimize code boilerplate.
• Undertow Web Server, lightweight and embedded web application server.
• Docker, container base deployment.
• startbootstrap-resume, Bootstrap template.

To edit resume content with your preferences, open the file: src/main/resources/application.yml , then edit under the resume sections. All the content structure are using YAML markup language convention. Check the customable fields from example or from the online demo.

mvnw clean package

mvnw spring-boot:run

Application will run on port 8080, access the URL http://localhost:8080 from web browser.

There is alternative for run the application. After build, go to target folder, make sure there is rexumee.jar file. Then, from that folder run:

java -jar rexumee.jar

Make sure you have installed Docker & Docker Compose prior to deployment, if not:

• Find out the documentation about Docker Installation at here.
• How to install Docker-Compose here.

From the project root folder, run:

docker-compose up -d

Check whether the deployment run properly:

docker ps

And you can access the webpage from port 80.

For online demo and preview, please visit here.

Copyright 2018 Maikel Chandika (mkdika@gmail.com). Code released under the Apache License, Version 2.0. See LICENSE file.

Supports commands and events (CQRS).

This package serves as a shared library for all message interfaces, commands and events in the system. It ensures consistency and correctness while implementing the event data model across Applications, Microservices, Aggregators and various programming languages.

Client’s event data model is exported as command and event enums, and message interfaces, to enable easy lookup of the available identifiers in the system.

import { Commands, Events } from "@devpie/client-events";

console.log(Commands.EnableAccounting);
// EnableAccounting

console.log(Events.MembershipAdded);
// MembershipAdded

Existing interfaces allow us to type check the message body being sent, ensuring correctness of implementation.

export interface MembershipAddedEvent {
  id: string;
  type: Events.MembershipAdded;
  metadata: Metadata;
  data: {
    MemberId: string;
    TeamId: string;
    UserId: string;
    Role: string;
    Created: string;
  };
}

Messaging systems allow Microservices to exchange messages without coupling them together. Some Microservices emit messages, while others listen to the messages they subscribe to.

A message is a generic term for data that could be either a command or an event. Commands are messages that trigger something to happen (in the future). Events are messages that notify listeners about something that has happened (in the past). Publishers send commands or events without knowing the consumers that may be listening.

This package is written in TypeScript but converted to language targets. Each supported language has its own package.

Supported languages include:

• TypeScript See package
• Golang See package

Modify src/events.ts, the source of truth, then re-build to update all packages.

npm run build

Here’s the steps to perform a manual release for Typescript and Go packages (needs to be automated). Publishing Go modules relies on git tags. https://blog.golang.org/publishing-go-modules

# 1. npm run build
# 2. update ./package.json version
# 3. commit changes to git
# 4. create a new tag for release
git tag v0.0.1
# 5. push new tag
git push origin v0.0.1
# 6. push changes to remote repository
git push origin main
# 7. publish npm module
npm publish

Yasen-Baka, a multifunctional Discord bot
with special World of Warships commands., written with the discord.py api.
You can invite the bot to your guild with this link

I no longer use discord for personal reasons. I will try to fix bugs as they come up but as of this momnet I do not plan on adding any new features.

If you are interested in continuing this project please shoot me an email at mat1g3r at gmail dot com.

To get started with the bot, simply type ?help into your guild channel.

Commands are divided into 9 categories, they are listed below.

• Bot Info Commands:

  help, info, ping, prefix reset, prefix set, prefix
  

• Fun Commands:

  choose, repeat, roll, salt
  

• Moderation Commands:

  masspm, purge
  

• Music Commands:

  play, playdefault, playing, playlist, setskip, skip, stop
  

• Nsfw Commands:

  danbooru, e621, gelbooru, konachan, rule34, yandere
  

• Osu Commands:

  osu
  

• Utility Commands:

  avatar, currency, joined, latex, stackoverflow
  

• Weeb Commands:

  LN, anime, ayaya, chensaw, joke, kanna, karen, manga, safebooru, umi
  

• World of Warships Commands:

  clan, shame, shamelist add, shamelist remove, shamelist
  

To self host yasen, you will need those packages installed on your system:

• Python3.6+: https://www.python.org/downloads/ Python3.5 and below is not supported
• FFmpeg: https://ffmpeg.org/
• SQLite3: https://www.sqlite.org/

In addition, you will need to execute the following command to install required libraries:

First cd into the directory where yasen is located, then:

pip install -Ur requirements.txt

Make a copy of YasenBaka/data/sample_db in the YasenBaka/data/ directory and rename it to yasen_db

Make a copy of YasenBaka/config/sample_config.json in the YasenBaka/config/ directory and rename it to config.json. Then you will need to fill out the required config values and api keys. I am not responsible for helping you obtaining any of the api keys.

Finally to run, do:

python3 yasen-baka.py

For non-developers, you can contribute by reporting bugs or making suggestions.
Simply open a Github issue here

For developers, if you are interested in contributing, follow the steps below:

1. Fork it ( https://github.com/MaT1g3R/YasenBaka/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am ‘Add some feature’)
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

👋 Welcome to the Keptn community! This repository is used for community management related issue tracking, including but not limited to community programs, enhancement ideas, memberships and permissions. See also the community page on keptn.sh/community.

• Keptn Community Page – Community landing on the Keptn website, with information for users and contributors
• Keptn chapter on community.cncf.io – Project and user group meetings
• Slack – Join us for realtime discussions and Q&A in the #keptn channel on CNCF Slack (if you’re not in CNCF slack already, invite yourself here
• Keptn on GitHub Discussions – Additional resource for Q&A and discussing proposals
• Community Newsletter – Subscribe to get updates on the state of Keptn every two weeks!
• Social media: @keptnProject on Twitter, KeptnProject on LinkedIn

• Community Membership Ladder – Community membership: roles, responsibilities and application guidelines.
• Keptn Advisory Board – Group of industry leaders and visionaries that provide advice to the Keptn project.
• Community Rockstars – Award for top Keptn contributors and advocates, that is given on a quarterly basis.

There are also some resources stored in this repository or elsewhere:

• Community Roadmap – Major community initiatives as a part of the Keptn roadmap.
• Mentorship and Outreach programs – programs we participate in.
• Artwork – Keptn logos and artwork.
• Keptn Project Infrastructure – Documentation and notes regarding the project infrastructure being used by the project: website, delivery infrastructure, repositories and services, etc.
• Keptn incubation in the CNCF – Materials related to Keptn application for the incubation in the Cloud Native Computing Foundation.

All meetings are listed in the CNCF Keptn Community Chapter as well as the public Keptn Google Calendar

Any contributions to the Keptn community are appreciated! See the Keptn Contributing Guidelines.

Made with contrib.rocks.

Analysis of delays of domestic flights from Us Airportsin 2008

We analyzed a data set of delayed flights from 2008 in the U.S. to determine the factors which contribute to delays. Among the factors inverstigated were individual airlines, total number of flights, time of day, month of year and airport. We were unable to perform further analysis on the reasons for delay because there were many missing values for the flight delay reason columns.

1. Count of All Flights vs. Delayed Flights: It is apparent from the graph of all flights vs delayed flights that there is a correlation between the two, as was expected. Surprisingly, the volatility in the delayed curve not present in the all-flights curve indicates that delayed flights is not a perfect function of the total number of flights. For example, the variance (or increases and decreases) in the delayed curve between weeks 10 and 20, 50 and 52 and to a lesser extent 36 and 40, is not reciprocated in the all-flights curve.

2. Average Airline Delay Time: The major airline carriers, US Airways, United Airlines, and Southwest Airlines appear to have limited carrier-caused delay times on average. Conversely, all the carrier who shoulder the blame for the longest extended wait times are smaller airlines like Hawaii, Comair, and Atlantic Southeast. Lastly, Mesa Airlines is clearly the worst airline for those fliers who lack patience or loose schedules.

3. Airline Percent Flights Delayed: Unlike the average carrier delay times, the major airlines have the highest percentag of flights delayed. Interestingly, contrary to their laid-back image, the airlines representing Hawaii boast the most punctual departures of any carrier.

4. Percentage of Flights Delayed by Hour and Day: The heat map – Days Of Week + Time of Day, indicates that afternoons and evenings are relatively more delayed compared to mornings. Friday and Sunday evenings are at the peak of delays.

5. Percentage of Flights Delayed by Month: Flight delays are maximum in around the holiday season. During Christmas and Thanksgiving, the delays could go up to 57%. We have some outliers in the middle of February and end of March, where there are no holidays or any reason that stands out.

6. Delays by Airport: The bubble map showed that the airports with most amount of delays are ATL in Atlanta and ORD in Chicago. ATL had 131,613 delays which constitutes 31.75% of all flights from ATL. ORD had 125,979 delays which constitutes 35.95% of all flights from ORD. Some airports with a lower amount of delays had a higher percentage of delayed flights. For example, AKN in King Salmon had 72 delays which constitutes 62.07% of all flights from AKN.

Delayed US flights in 2008: https://www.kaggle.com/giovamata/airlinedelaycauses All US flights in 2008: https://www.kaggle.com/vikalpdongre/us-flights-data-2008#2008.csv Airport longitude and latitude location: https://raw.githubusercontent.com/jpatokal/openflights/master/data/airports.dat

1. Jupyter Notebook
2. Seaborn, Plotly, pyplot