From: kartikynwa <kartikynwa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-dotenv: update to 0.17.1.
Date: Wed, 16 Jun 2021 06:19:02 +0200 [thread overview]
Message-ID: <20210616041902.-EL4jdwqeUk9OF5OhpraBlIzDZhXgUH0o7FtXvks_jw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31470@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2186 bytes --]
New comment by kartikynwa on void-packages repository
https://github.com/void-linux/void-packages/pull/31470#issuecomment-862026550
Comment:
@ericonr
I didn't use ci-skip anywhere. Will force push a commit and see if it triggers the builds.
I have tested it. I use it on my machine for development. Here is a short example:
```
~/docker-compose-test
❯ xbps-query python3-dotenv | grep ver
pkgver: python3-dotenv-0.17.1_1
~/docker-compose-test
❯ cat docker-compose.yml
version: "3.9"
services:
hello:
container_name: ${NAME}
image: hello-world:latest
~/docker-compose-test
❯ cat .env
NAME=hello-world-container
~/docker-compose-test
❯ sudo docker-compose up
Starting hello-world-container ... done
Attaching to hello-world-container
hello-world-container |
hello-world-container | Hello from Docker!
hello-world-container | This message shows that your installation appears to be working correctly.
hello-world-container |
hello-world-container | To generate this message, Docker took the following steps:
hello-world-container | 1. The Docker client contacted the Docker daemon.
hello-world-container | 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
hello-world-container | (amd64)
hello-world-container | 3. The Docker daemon created a new container from that image which runs the
hello-world-container | executable that produces the output you are currently reading.
hello-world-container | 4. The Docker daemon streamed that output to the Docker client, which sent it
hello-world-container | to your terminal.
hello-world-container |
hello-world-container | To try something more ambitious, you can run an Ubuntu container with:
hello-world-container | $ docker run -it ubuntu bash
hello-world-container |
hello-world-container | Share images, automate workflows, and more with a free Docker ID:
hello-world-container | https://hub.docker.com/
hello-world-container |
hello-world-container | For more examples and ideas, visit:
hello-world-container | https://docs.docker.com/get-started/
hello-world-container |
hello-world-container exited with code 0
```
next prev parent reply other threads:[~2021-06-16 4:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31470@inbox.vuxu.org>
2021-06-15 20:01 ` ericonr
2021-06-15 20:01 ` ericonr
2021-06-16 4:19 ` kartikynwa [this message]
2021-06-16 4:24 ` [PR PATCH] [Updated] " kartikynwa
2021-06-16 4:29 ` kartikynwa
2021-06-16 4:35 ` kartikynwa
2021-06-16 4:38 ` kartikynwa
2021-06-16 4:43 ` kartikynwa
2021-06-16 4:46 ` kartikynwa
2021-06-17 2:55 ` ericonr
2021-06-21 12:03 ` ericonr
2021-06-23 6:29 ` kartikynwa
2021-06-23 6:45 ` [PR PATCH] [Updated] " kartikynwa
2021-06-23 6:49 ` kartikynwa
2021-06-23 6:51 ` python3-dotenv: update to 0.18.0 kartikynwa
2021-06-23 12:03 ` [PR PATCH] [Merged]: " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210616041902.-EL4jdwqeUk9OF5OhpraBlIzDZhXgUH0o7FtXvks_jw@z \
--to=kartikynwa@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).