specs
compose-spec
specs | compose-spec | |
---|---|---|
3 | 24 | |
370 | 2,064 | |
0.5% | 2.2% | |
5.8 | 8.3 | |
7 months ago | 1 day ago | |
SCSS | Dockerfile | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
specs
-
Creating a pinning service that interacts with EVMs
Unfortunately, filecoin is not (or no longer?) the incentive mechanism for pinning in IPFS. FYI: https://github.com/filecoin-project/specs/issues/1191
-
Romanian anti-communist poster in 1980s.
#1: There's a partial IPFS link in Elon's S&L Appearance | 17 comments #2: IPFS emerges in Myanmar to combat censorship | 1 comment #3: Filecoin Isn't An Incentivization Network For IPFS, It's A Completely Different IPFS Network | 30 comments
-
Sci-Hub Archive
IPFS is what you're looking for, and there's already a IPFS site for LibGen so SciHub is probably not far behind.
Note: Filecoin despite advertising itself for years as an incentivisation layer for IPFS is not - it's two separate networks [1], so it lacks all the features of the mature IPFS protocol.
[1] https://github.com/filecoin-project/specs/issues/1191
compose-spec
-
One Minute: Compose
Specification: https://compose-spec.io
-
Podman Desktop v1.5 with Compose onboarding and enhanced Kubernetes pod data
https://github.com/compose-spec/compose-spec/blob/master/spe...
-
How “It works in my machine” turns to “It works in my container”
There are a number of incorrect statements in this post.
1) One should neither be using the "latest" nor just the "version" tag as the version can still vary depending on when it is pulled.
Instead, one should use a combination of version + hash, say alpine:3.18.2@sha256:82d1e9d7ed48a7523bdebc18cf6290bdb97b82302a8a9c27d4fe885949ea94d1 for reproducibility reasons. This provides for human readable versions as well as the specific hash.
2) Next, afaik, Compose has removed the need for version tags. All of the compose.yml files that I now use do not specify versions.
See https://github.com/compose-spec/compose-spec/blob/master/04-...
-
Telegraf Deployment Strategies with Docker Compose
Docker Compose v2 specifications provide a useful Secrets feature which may also be used for standalone Compose Application Stacks and not just in Docker Swarm mode. With Docker Secrets the environment variables that contain credentials for other subsystems are mounted into the Telegraf Container as files. These secret files are read through the Docker Secret Store plugin and passed to the respective plugins in a relatively safe manner. By using the Docker Secret Store Plugin, one can also avoid credentials that were previously visible via environment variables, to be now hidden behind runtime secret files within the container. Standard Method with Environment Variables As an example, it is possible to pass the credentials to a plugin via the environment variable placeholder in a telegraf configuration file where the credentials for a plugin exist in a .env file (e.g. MQTT input Plugin)
-
Some options missing for me.
also the docker-compose.yml file is very picky about what you have in it and where. Please read this so you know how to format it https://github.com/compose-spec/compose-spec/blob/master/spec.md
-
Persistent Volume Claim Volume Specific Options?
As part my quadlet helper tool, podlet, I'm adding functionality to convert compose files into k8s yaml to use with quadlet as an alternative to creating a bunch of separate quadlet files, which I've also added functionality for. So I would like to be able to transform the options on compose volumes into k8s yaml. For example, using the volume.podman.io/driver annotation to change the volume driver for a specific volume if possible.
-
New Docker Goodies: Init and Watch
If you find this helpful feature, please leave your feedback and suggestions here.
-
When I create a docker-compose file to deploy multiple containers, do the different versions of each compose file matter?
The compose spec will give what you need. https://github.com/compose-spec/compose-spec/blob/master/spec.md
-
Why Does Everything Say Docker Compose is Deprecated / Dead?
Indeed, as per the compose-spec a lot of what was version specific is going away
-
A compose file visualization tool that follows compose-spec and allows you to gernerate graph in several formats.
Hello everyone, I just made a tool to visualize compose files, and all the parsing rules follow the [compose-spec](https://github.com/compose-spec/compose-spec/blob/master/spec.md). I hope this tool will help you :D
What are some alternatives?
conventionalcommits.org - The conventional commits specification
docker-pi-hole - Pi-hole in a docker container
ntast - Notion Abstract Syntax Tree specification.
psutil - Cross-platform lib for process and system monitoring in Python
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
pexpect - A Python module for controlling interactive programs in a pseudo-terminal
Kahlan - :heavy_check_mark: PHP Test Framework for Freedom, Truth, and Justice
SaltStack - Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
inspec - InSpec: Auditing and Testing Framework
Fabtools - Tools for writing awesome Fabric files
proposals - Tracking ECMAScript Proposals
Docker Compose - Define and run multi-container applications with Docker