How to structure library?

This page summarizes the projects mentioned and recommended in the original post on /r/bash

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • ipytv

    A python library to handle IPTV playlists in m3u_plus format

  • bash-commons

    A collection of reusable Bash functions for handling common tasks such as logging, assertions, string manipulation, and more

  • I think I phrased what I said poorly and unintentially communicated that I want to have all my code in one file. that' the opposite of what I'm wanting. To clarify, and I know this is splitting hairs but it illustrates my point. I think this log shell file is a good example of what I want to NOT do with my library. instead of having one file with 5 functions, I think it should be 5 files with no functions. that's to say the new file "log_info" would contain this text:

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts