unspecified

awesome-public-datasets

23 May 2020Last Commit39309 (7134/yr)Github Stars101Issues

NOTICE: This repo is automatically generated by apd-core. Please DO NOT modify this file directly. We have provided a new way to contribute to Awesome Public Datasets. Join the slack community for more communication.

This list of a topic-centric public data sources in high quality. They are collected and tidied from blogs, answers, and user responses. Most of the data sets listed below are free, however, some are not. Other amazingly awesome lists can be found in sindresorhus's awesome list.

Table of Contents

awesome-sysadmin

12 May 2020Last Commit10383 (1916/yr)Github Stars4Issues

A curated list of amazingly awesome open source sysadmin resources. Please read CONTRIBUTING if you wish to add software and consider donating to the FLOSS projects you use regularly.

Automation build.

Backup software. Also see Restic's list of Linux backup software.

Build and software organization tools.

Conversation-driven development and management. See https://www.reddit.com/r/chatops for more information.

Managing software on desktop computers.

Cloning software.

Web Based collaborative code review system.

awesome-bigdata

21 May 2020Last Commit8822 (1498/yr)Github Stars12Issues

A curated list of awesome big data frameworks, resources and other awesomeness. Inspired by awesome-php, awesome-python, awesome-ruby, hadoopecosystemtable & big-data.

Your contributions are always welcome!

Note: There is some term confusion in the industry, and two different things are called "Columnar Databases". Some, listed here, are distributed, persistent databases built around the "key-map" data model: all data has a (possibly composite) key, with which a map of key-value pairs is associated. In some systems, multiple such value maps can be associated with a key, and these maps are referred to as "column families" (with value map keys being referred to as "columns").

huboard

03 Jun 2019Last Commit1696 (198/yr)Github Stars147Issues

This repository serves as the central issue tracker (HuBoard | GitHub) for the HuBoard project

![Next release](https://img.shields.io/github/issues-raw/huboard/huboard/1%20-%20Next release.svg?label=Next%20Release)

HuBoard consists of many different sub-projects. The main ones are:

![Web: Next release](https://img.shields.io/github/issues-raw/huboard/huboard-web/1%20-%20Next release.svg?label=Next%20Release)

huboard-web is our most active repository, it houses both the front-end EmberJS code as well as the ruby on rails API for the main HuBoard application

diamond

17 Mar 2017Last Commit1214 (136/yr)Github Stars0Issues

horde

16 May 2020Last Commit245 (25/yr)Github Stars6Issues

This is the old, monolith Horde repository that used to contain all Horde components, i.e. all Horde libraries and applications in one single repository. It's still completely available in read-only mode.

For any new development use the separate Git repositories at https://github.com/horde and the Horde Git Tools at https://github.com/horde/git-tools.

golangci

25 May 2018Last Commit49 (22/yr)Github Stars18Issues

GolangCI is an automated golang codereview tool.

This repository contains the central issue tracker for the GolangCI project.

GolangCI consists of sub-projects. The main ones are:

golangci-api is the Golang server with REST API for golangci-web.

golangci-web is a frontend of golangci.com. It uses React, Redux, Typescript, Webpack.

golib is a small Golang HTTP framework. It's used in golangci-api.

golangci-worker is the queue worker. When user creates or updates GitHub pull request, golangci-api gets webhook event about it. Then it send this event to distributed queue. golangci-worker handles such queue events and runs code analysis.

charjabox

10 Feb 2020Last Commit8 (12/yr)Github Stars2Issues

Ansible based Homeserver setup using Docker.

Inspired by Ansible NAS and HomelabOS

CharjaBox is an Ansible playbook that can be used to easily deploy your Homeserver setup.

All supported applications can be installed on your server using Docker by simply changing some variables and running the playbook.

Read the documentation here.

You can use the playbook charjabox/scripts/initialize.yml to skip part of steps 3 and 4. This playbook asks you about your server IP, group name and settings folder and creates the files for you automatically.