Searching We.Love.Privacy.Club

Twts matching #1:
Sort by: Newest, Oldest, Most Relevant
In-reply-to » (#axkd3eq) @prologic I don't understand what you're saying. podman works with TLS. It does not have the "--docker" siwtch so you have to remove that and use the exact replacement commands that were in that github comment.

@prologic@twtxt.net Change your script to this:

#!/bin/sh

set -e

alias docker=podman

if [ ! command -v docker > /dev/null 2>&1 ]; then
  echo "docker not found"
  exit 1
fi

mkdir -p $HOME/.docker/certs.d/cas

## key stuff omitted

# DO NOT DO THIS docker context create cas --docker "host=tcp://cas.run:2376,ca=$HOME/.docker/certs.d/cas/ca.pem,key=$HOME/.docker/certs.d/cas/key.pem,cert=$HOME/.docker/certs.d/cas/cert.pem"
# DO THIS:
podman system connection add "host=tcp://cas.run:2376,ca=$HOME/.docker/certs.d/cas/ca.pem,key=$HOME/.docker/certs.d/cas/key.pem,cert=$HOME/.docker/certs.d/cas/cert.pem"
# DO NOT DO THIS docker context use cas
# DO THIS: 
podman system connection default cas

⤋ Read More
In-reply-to » (#axkd3eq) @prologic I don't understand what you're saying. podman works with TLS. It does not have the "--docker" siwtch so you have to remove that and use the exact replacement commands that were in that github comment.

@prologic@twtxt.net what do you mean when you say “Docker API”? There are multiple possible meanings for that. podman conforms to some of Docker’s APIs and it’s unclear to me which one you say it’s not conforming to.

You just have to Google “podman Docker API” and you find stuff like this: https://www.redhat.com/sysadmin/podman-rest-api

What is Podman’s REST API?

Podman’s REST API consists of two components:

  • A Docker-compatible portion called Compat API
  • A native portion called Libpod API that provides access to additional features not available in Docker, including pods

Or this: https://docs.podman.io/en/latest/markdown/podman-system-service.1.html

The REST API provided by podman system service is split into two parts: a compatibility layer offering support for the Docker v1.40 API, and a Podman-native Libpod layer.

⤋ Read More

Spinach industry rebuilds reputation for producing ‘very safe food’ after contamination event
Dino Borrato lost close to $1 million and continues to plough some of his crop into the ground as the spinach industry recovers from last year’s contamination event. ⌘ Read more

⤋ Read More

@New_scientist@feeds.twtxt.net hello @prologic@twtxt.net here’s another feed that’s spewing multiple copies of the same post. This one above is repeated 8 times. @awesome-scala-weekly@feeds.twtxt.net now has 13 copies of each post every week. This definitely looks like a bug in whatever code is generating these feeds, because the source feeds don’t have multiple copies of the original posts:

I forget whether I filed an issue on this before, but can you tell me where I should do that?

⤋ Read More

Ignite Realtime Blog: Jabber Browsing Openfire Plugin 1.0.1 released
The Ignite Realtime community is happy to announce a new release of the Jabber Browsing plugin for Openfire.

This is a plugin for the Openfire Real-time Communications server. It provides an implementation for service discovery using the jabber:iq:browse namespace, as specified in XEP-0011: Jabber Browsing. Note that this feature is considered obsolete! The plug … ⌘ Read more

⤋ Read More

Ignite Realtime Blog: Agent Information plugin for Openfire release 1.0.1
The Ignite Realtime community is happy to announce a new release of the Agent Information plugin for Openfire.

This plugin implements the XEP-0094 ‘Agent Information’ specification for service discovery using the jabber:iq:agents namespace. Note that this feature is considered obsolete! The plugin should only be used by people that seek backwards compatibility with very old and very specific IM … ⌘ Read more

⤋ Read More

Ignite Realtime Blog: Certificate Manager plugin for Openfire release 1.1.1
The Ignite Realtime community is happy to announce a new release of the Certificate Manager plugin for Openfire.

This plugin allows you to automate TLS certificate management tasks. This is particularly helpful when your certificates are short-lived, like the ones issued by Let’s Encrypt.

This release is a maintenance release. It adds translations. More details are available in the [changelog] … ⌘ Read more

⤋ Read More

Ignite Realtime Blog: JmxWeb plugin for Openfire 0.9.1 release
The Ignite Realtime community is happy to announce a new release of the JmxWeb plugin for Openfire.

This plugin provides a web based platform for managing and monitoring Openfire via JMX

This release is a maintenance release. It adds translations and fixes one bug. More details are available in the changelog.

Your instance of Openf … ⌘ Read more

⤋ Read More

Ignite Realtime Blog: Search Openfire plugin 0.7.4 release!
The Ignite Realtime community is happy to announce a new release of the Search plugin for Openfire.

This plugin adds features to Openfire that makes it easier for users to find each-other.

This release is a maintenance release. It adds translations. More details are available in the changelog

Your instance of Openfire should automatically … ⌘ Read more

⤋ Read More

Isode: Cobalt 1.4 – New Capabilities
Cobalt proides a web interface for provisioning users and roles in an LDAP directory. It enables the easy deployment of XMPP, Email and Military Messaging systems.

Image

Listed below are the changes brought in with 1.4.

HSM Support

Cobalt is Isode’s tool for managing PKCS#11 Hardware Security Modules (HSM) which may be used to provide improved server security by protecti … ⌘ Read more

⤋ Read More

Isode: M-Guard 1.5 – New Capabilities
M-Guard is an XML guard that is used at a network boundary to control traffic. An M-Guard instance is an application level data diode, with traffic flowing in one direction only. Commonly, M-Guard instances will be deployed in pairs, one controlling flow in each direction. The following is a list of the new capabilties introduced in version 1.5.

Image

**M-Guard C … ⌘ Read more

⤋ Read More

Erlang Solutions: Effortlessly Extract Data from Websites with Crawly YML

The workflow

So in our ideal world scenario, it should work in the following way:

  1. Pull Crawly Docker image from DockerHub.
  2. Create a simple configuration file.
  3. Start it!
  4. Create a spider via the YML interface.

The detailed documentation and the example can be found on HexDocs here: [https://hexdocs.pm/crawly/spiders_in_yml.html#content](https://hexdocs.pm/crawly/spiders_in_yml.html#c … ⌘ Read more

⤋ Read More