otj-pg-embedded
phoenix_container_example
otj-pg-embedded | phoenix_container_example | |
---|---|---|
6 | 9 | |
666 | 19 | |
0.2% | - | |
6.4 | 9.1 | |
14 days ago | 2 days ago | |
Java | HCL | |
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.
otj-pg-embedded
-
Testcontainers
Anyone have an opinion of embedded-postgres vs https://github.com/opentable/otj-pg-embedded (of which its a fork) for Clojure use?
-
What's the best approach for creating an embedded Postgresql to be used in production?
Can you elaborate a bit on this part? I'm still unsure why it's unadvised to do this, as I understood from other commenters it's because there is no official support for it correct? Why can't I use opentable for instance? https://github.com/opentable/otj-pg-embedded
-
SQLite Is Dynamically Typed (2020)
It's pretty easy to run embedded postgres on the JVM: https://github.com/opentable/otj-pg-embedded
The defaults create a temporary DB which is useful for dev & tests, but a pair of calls to .setCleanDataDirectory(false) and .setDataDirectory("...") will change that.
If you don't like the default postgres version, you may select one from https://search.maven.org/search?q=io.zonky.test.postgres or include your own postgres binary.
- Experiment: using PostgreSQL as a user process
-
Pg_tmp – Run tests on an isolated, temporary PostgreSQL database
I've been using this embedded PostgreSQL thing for tests:
https://github.com/opentable/otj-pg-embedded
It's very simple to use and works perfectly. The one problem, and it's a significant one, is that it only ships one version of PostgreSQL, and adding another was difficult enough that I didn't.
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
What are some alternatives?
testcontainers-go - Testcontainers for Go is a Go package that makes it simple to create and clean up container-based dependencies for automated integration/smoke tests. The clean, easy-to-use API enables developers to programmatically define containers that should be run as part of a test and clean up those resources when the test is done.
elixir-boilerplate - ⚗ The stable base upon which we build our Elixir projects at Mirego.
Testcontainers - Testcontainers is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
amazon-ecs-agent - Amazon Elastic Container Service Agent
postgresql-embedded - Embedded PostgreSQL Server
ecs-deploy - Simple shell script for initiating blue-green deployments on Amazon EC2 Container Service (ECS)
integresql - IntegreSQL manages isolated PostgreSQL databases for your integration tests.
multi-env-deploy - Complete example of deploying complex web apps to AWS using Terraform, Ansible, and Packer
localstripe - A fake but stateful Stripe server that you can run locally, for testing purposes.
Veil - Simple passwordless authentication for your Phoenix apps
embedded-postgres - Run a real Postgres database locally on Linux, OSX or Windows as part of another Go application or test
NuGet - NuGet Gallery is a package repository that powers https://www.nuget.org. Use this repo for reporting NuGet.org issues.