embedded-postgres-binaries
rules_rust
Our great sponsors
embedded-postgres-binaries | rules_rust | |
---|---|---|
5 | 9 | |
123 | 608 | |
2.4% | 3.8% | |
5.9 | 9.5 | |
2 months ago | 4 days ago | |
Shell | Starlark | |
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.
embedded-postgres-binaries
- Testcontainers
-
Show HN: pgxman for Postgres Extensions
A core part of npm is that the dependencies are installed in the folder/project you are working in (unless you use the --global flag which is discouraged for most use-cases).
Can I use this in any way without a global system state? Like with https://github.com/zonkyio/embedded-postgres-binaries or similar that don't have a global install? Or with a distro that supports multiple versions/instances of postgresql?
-
Two Tier Architectures Are Anachronistic
You may be interested in this
https://github.com/zonkyio/embedded-postgres-binaries
I've been using this for test runners in Node and Go for a while now and it's been quite painless. Would be nice to have wider language support though
-
When to Use Bazel?
Nice, this seems a lot simpler than I thought. Nice tip on embedded-postgres-binaries (https://github.com/zonkyio/embedded-postgres-binaries).
- Ephemeral Postgres Databases
rules_rust
-
NixOS: Declarative Builds and Deployments
The same reason Bazel builds avoid using Cargo when building Rust software, so I'll describe why Bazel would do this:
- Bazel wants to cache remote resources, like each respective crate's source files.
- Bazel then wants to build each crate in a sandbox, and cache the build artifacts
This is an established practice, and Nix wants to drive the build for the same reasons.
See:
- https://github.com/bazelbuild/rules_rust
- https://github.com/google/cargo-raze
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
To answer your question, I don't know if Soong or Bazel can reuse the files produced by an incremental Rust compilation. I tried searching the rules_rust repository and found some discussions, but nothing that clearly told me "Yes, this is supported".
-
When to Use Bazel?
Bazel doesn't allow targeting a lot of platforms (especially embedded) from Rust, even when the Rust ecosystem supports these targets. Something is off with its design if new work needs to be done for every platform that's already available behind an interface that's as consistent as what rustc gives.
What is supported needs to be inferred from this file, as far as I can tell: https://github.com/bazelbuild/rules_rust/blob/main/rust/plat...
-
Cpp-like build tools for Rust?
You might be overjoyed to learn that you can use a build tool that forces you to manually write out the dependencies between each file.
-
How to enable suggestions/autocomplete in VS Code?
I am using rules_rust and have the VS Code Bazel plugin installed, but I am still not getting autocomplete.
-
Blog Post: Fast Rust Builds
Other than that, the performance of both for builds should be determined exactly by the organization of code into separate crates and the rustc invocations. Bazel generally encourages smaller crates, but that's very subtle. There is at least 1 case I can think of where rustc is overfit to cargo, in a way that is not easily replicable by bazel, which is the metadata/rlib pipelining https://github.com/bazelbuild/rules_rust/issues/228
-
Modern C++ Won't Save Us (2019)
Rust integrates pretty seamlessly into Bazel projects via rules_rust (https://github.com/bazelbuild/rules_rust). The existing rules even allow for c calling rust and rust calling c. Example: https://github.com/bazelbuild/rules_rust/blob/main/examples/...
-
Why Zig When There Is Already C++ and Rust?
With any compiled language you can use the compiler and vendor your dependencies instead of using the language's conventional package manager. For example, nothing prevents skipping Cargo and building Rust directly with rustc the way Bazel does.
https://github.com/bazelbuild/rules_rust
What are some alternatives?
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
postgres-gcs-backup - Simple Docker image to backup a Postgres db, to a GCS bucket
cargo-chef - A cargo-subcommand to speed up Rust Docker builds using Docker layer caching.
dockertest - Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work.
cargo-sweep - A cargo subcommand for cleaning up unused build files generated by Cargo
embedded-database-spring-test - A library for creating isolated embedded databases for Spring-powered integration tests.
www.ziglang.org
zapatos - Zero-abstraction Postgres for TypeScript: a non-ORM database library
bazel-coverage-report-renderer - Haskell rules for Bazel.
tempgres-server - REST service for creating temporary PostgreSQL databases
wg-allocators - Home of the Allocators working group: Paving a path for a standard set of allocator traits to be used in collections!