phoenix_container_example
pglite
phoenix_container_example | pglite | |
---|---|---|
9 | 6 | |
19 | 4,424 | |
- | 11.5% | |
9.1 | 8.4 | |
5 days ago | 16 days ago | |
HCL | TypeScript | |
Apache License 2.0 | 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.
phoenix_container_example
-
Testcontainers
It's particularly useful for testing a set of microservices.
See https://github.com/cogini/phoenix_container_example for a full example.
-
Musl 1.2.4 adds TCP DNS fallback
I use distroless images based on Debian or Ubuntu, e.g., https://github.com/cogini/phoenix_container_example
The result is images the same size as Alpine, or smaller, without the incompatibilities. I think Alpine is a dead end.
-
Where do you build your image in your pipeline?
Here is a full-featured example of building images in GitHub Actions that includes optimized caching: https://github.com/cogini/phoenix_container_example/blob/master/.github/workflows/ci-ghcr.yml
-
AWS Devops tools vs Bitbucket
Here are some examples of using GitHub actions to build, or call hosted runners in AWS to build Arm images, and using OIDC to manage AWS credentials: https://github.com/cogini/phoenix_container_example/blob/master/.github/workflows/
-
Running python when building a Docker image on AWS
Parameter Store is a good place to store things. ECS can read from it and set variables. This is a complete example of using Terraform to manage infrastructure with EC2 or ECS: https://github.com/cogini/multi-env-deploy Here is an app that runs in ECS: https://github.com/cogini/phoenix_container_example This task file sets env vars based on parameter store: https://github.com/cogini/phoenix_container_example/blob/master/ecs/taskdef.json
- Advice on CI/CD at scale from GitHub Enterprise to CodePipeline (TF & CFN) ?
-
When would you introduce Docker to your project?
Here is a complete example project which shows how to use Earthly and Visual Studio Code .devcontainer: https://github.com/cogini/phoenix_container_example
- I wrote A blog post about my experience trying to use buildkit caching to speed up CI
-
We are the AWS Containers Team - Ask the Experts - Feb 10th @ 11AM PT / 2PM ET / 7PM GMT!
I am heavily using multi-stage builds, e.g.: https://github.com/cogini/phoenix_container_example/blob/master/deploy/Dockerfile.alpine
pglite
-
Show HN: I open-sourced the in-memory PostgreSQL I built at work for E2E tests
Hey HN! For a few months, I've been building pgmock at work for our E2E and unit test suite. It emulates Postgres in WebAssembly and has full feature parity with production databases.
The cool thing about it is that you don't need any external processes or proxies. If your platform can run WASM (Node.js, browser, etc.), it can probably run pgmock. Creating a new database with mock data is as simple as creating a JavaScript object.
It's a bit different from the amazing pglite [1] (which inspired me to open-source pgmock in the first place). While pgmock runs an x86 emulator, pglite compiles a Postgres fork to native WASM directly and is hence much faster and more lightweight. However, it only supports single-user mode and a select few extensions, so you can't connect to it with normal Postgres clients (which is quite crucial for E2E testing).
Theoretically, it could be modified to run any Docker image on WebAssembly platforms. Anything specific you'd like to see?
Happy hacking!
[1] https://github.com/electric-sql/pglite
- Pgmock: In-memory Postgres for unit/E2E tests
-
Soul: A SQLite REST and Realtime Server
I've found postgres via docker to be fine for dev and testing, but there are various epheremal postgres scripts, plus this could be promising for node stuff https://github.com/electric-sql/pglite if it works out. I'd imagine if this does work out we'll see the same kind of builds for other runtimes as well (like python)
-
The Cell Programming Language
> Use SQLite for everything, or Postgres if you outgrow it.
Or both! ElectricSQL syncs front end SQLlite back to server side postgres. And they just rebuilt postgres on pure WASM (https://github.com/electric-sql/pglite). All ties together with a CRDT.
I'm not affiliated, but just think it's just cool to imagine calls to front end sqllite as the be-all-end-all.
- Testcontainers
- PGlite – Postgres in WASM
What are some alternatives?
elixir-boilerplate - ⚗ The stable base upon which we build our Elixir projects at Mirego.
dockertest - Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work.
amazon-ecs-agent - Amazon Elastic Container Service Agent
otj-pg-embedded - Java embedded PostgreSQL component for testing
ecs-deploy - Simple shell script for initiating blue-green deployments on Amazon EC2 Container Service (ECS)
services-flake - NixOS-like services for Nix flakes
multi-env-deploy - Complete example of deploying complex web apps to AWS using Terraform, Ansible, and Packer
gradle-docker-compose-plugin - Simplifies usage of Docker Compose for integration testing in Gradle environment.
Veil - Simple passwordless authentication for your Phoenix apps
NuGet - NuGet Gallery is a package repository that powers https://www.nuget.org. Use this repo for reporting NuGet.org issues.
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
rocker-versioned2 - Run current & prior versions of R using docker. rocker/r-ver, rocker/rstudio, rocker/shiny, rocker/tidyverse, and so on.