gh-action-pypi-publish
postgres
gh-action-pypi-publish | postgres | |
---|---|---|
5 | 29 | |
844 | 2,093 | |
2.0% | 1.2% | |
8.1 | 7.5 | |
about 23 hours ago | 6 days ago | |
Python | Shell | |
BSD 3-clause "New" or "Revised" License | MIT License |
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.
gh-action-pypi-publish
-
PyPI new user and new project registrations temporarily suspended
> Recently I've seen someone on Reddit trying to automate the creation of PyPI projects through GitHub Actions. The person was complaining that the first deployment couldn't use an API key for that project since it didn't exist. So I'm not surprised some people are trying to do the same for malicious purposes.
Sorry for the tangent, but: you can do this now! If you use trusted publishing, you can register a "pending publisher" for a project that doesn't exist yet. When the trusted publisher (like GitHub Actions) is used, it'll create the project[1].
All of this is supported transparently by the official publishing action for GitHub Actions[2].
[1]: https://docs.pypi.org/trusted-publishers/creating-a-project-...
[2]: https://github.com/pypa/gh-action-pypi-publish
-
Publishing to PyPI via GitHub Action
In the documentation example, I see that the action yaml file contains the line uses: pypa/gh-action-pypi-publish@release/v1. I have never done this before and almost went with that, but I am not sure why the example shows v1 hardcoded, so I don't think I actually want this to happen. It doesn't seem to be well explained though, and the pypi-publish action repo was also quiet on this. Is this saying that it will create a release branch in my repo and call the release v1? Or how will this appear after I've done it? Will I have to manually change this v1 to v0.1.1 in the actions file AND the pyproject.toml?
-
"Even with --dry-run pip will execute arbitrary code found in the package's setup.py. In fact, merely asking pip to download a package can execute arbitrary code"
Yeah, you're uploading to PyPi in your pipeline, great. The custom github action still uses twine because the stdlib falls short on BASIC security. https://github.com/pypa/gh-action-pypi-publish/blob/unstable/v1/twine-upload.sh
-
Do you publish pypi source code to Github as well in the same form?
I never bothered with pypi myself but I hope the nudge into github actions helps you. I've found the following promising github action: https://github.com/pypa/gh-action-pypi-publish
- The Python Package Index is now a GitHub secret scanning integrator
postgres
- How to Escape a Container
-
Problem with Postgres container configuration?
EDIT: Somehow i managed to fix it right now (I struggled with this problem yesterday for hours). This github issue have helped: https://github.com/docker-library/postgres/issues/537 If anyone runs into this problem, those are crucial instructions that helped me: docker system prune docker-compose up --force-recreate --build --remove-orphans --always-recreate-deps --renew-anon-volumes
- PostgreSQL 16 Beta 1 Released!
-
PyPI new user and new project registrations temporarily suspended
Tragedy of the commons - only need a few actors to ruin it all for us. Almost all distributors face this problem, from Docker Hub to PyPI. This also reminded me of official Postgres Docker image running a cryptominer in the background [1]
[1] - https://github.com/docker-library/postgres/issues/770
- [Docker] Point d’entrée Docker-initdb.d Postgres
-
Nix Turns 20. What the Hell Is It?
If you open the dockerfile of the desired container, you can determine exactly how and what was built. If not satisfied, you can always build your own container with the right postgresql build flags.
-
archive_command not being executed?
Ok according to The Dockerfile, postgres is running in /var/lib/postgresql/data so you will need enter the container and look at the log files in /var/lib/postgresql/data/pg_log/
-
How do I create a docker image for postgres with nix?
I got started on trying to make a basic postgres image but I can't seem to figure out how to include a shell script in the same folder as my nix file (fetched from https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh and to be modified once I get it working) into the docker image as an entrypoint
- Postgres on docker works without a shell perfectly but fails when run via shell
-
What exactly is VOLUME used for inside the dockerfile?
See example here : https://github.com/docker-library/postgres/issues/601
What are some alternatives?
build - A simple, correct Python build frontend
pgBackRest - Reliable PostgreSQL Backup & Restore
git-filter-repo - Quickly rewrite git repository history (filter-branch replacement)
spilo - Highly available elephant herd: HA PostgreSQL cluster using Docker
amplify-preview-actions - This action deploys your AWS Amplify pull request preview for your public repository
checkmk - Checkmk - Best-in-class infrastructure & application monitoring
git-repo-sync - Git Repo Sync enables you to synchronize code to other code management platforms, such as GitLab, Gitee, etc.
MeshCentral - A complete web-based remote monitoring and management web site. Once setup you can install agents and perform remote desktop session to devices on the local network or over the Internet.
trufflehog - Find and verify secrets
kanban-board - Single-click full-stack application (Postgres, Spring Boot & Angular) using Docker Compose
release - Contains every things needed to release jenkins core from the jenkins infra project
deck-chores - A job scheduler for Docker containers, configured via labels.