testcontainers-rs VS docker

Testing with added infrastructure can be quite tricky. testcontainers aims to solve this by providing an open-source framework for providing local, lightweight containers for your application that can be immediately thrown away after use. It also has a Rust SDK!

Add tests! You can use testcontainers to spin up Docker containers for Postgres and other infrastructure which makes testing your database extremely easy. You can find more about this here.

You didn't mention how do you start Postgres for the tests. Is it assumed it runs in the background? A cool crate I use lately for this kind of thing is test_containers that can start docker containers from code, for example - Postgres

Do you manually spin up the containers or do you use testcontainers?

For the repo testing, that’s simple. https://github.com/testcontainers/testcontainers-rs will start a Docker image and you just use that when instantiating the repo.

Thanks for sharing! I'm still a beginner with Rust and still pretty new to testing in general - is there any benefit to using something like this over bringing up the service as a separate container using something like testcontainers? I suppose the biggest one is this is in-memory and doesn't require the party running tests to have Docker available locally. The tradeoff is the extra work to create all the mocks (i.e. my library has several dozen endpoints).

Deploying AI models into production requires tools that can package applications and manage them at scale. Docker simplifies the deployment of AI applications by containerizing them, ensuring that the application runs smoothly in any environment. Kubernetes, an orchestration system for Docker containers, allows for the automated deployment, scaling, and management of containerized applications, essential for AI applications that need to scale across multiple servers or cloud environments.

Linux Mint with Cinnamon: https://www.linuxmint.com/ as far as desktop OSes go it's familiar (Ubuntu without snaps by default), whereas the UI feels both snappy, doesn't use too much resources and is actually pretty to look at.

MobaXTerm: https://mobaxterm.mobatek.net/ this one is a bit more Windows centric but I ended up paying for it and replaced mRemoteNg and PuTTY with it, it's even better than Remmina or whatever Linux has to offer - you can manage SSH/RDP/VNC/... sessions, input across multiple sessions side by side and it just simplifies things a lot (jump host support, a port forwarding too and so much more).

GitKraken: https://www.gitkraken.com/ also a piece of software that I paid for, this one actually makes using Git pleasant, feels better to use than SourceTree and Git Cola (even though that latter is wonderfully lightweight, too) and honestly I prefer that to the CLI nowadays.

Kanboard: https://kanboard.org/ is a lightweight Kanban project management tool, it might not have every feature under the sun but it's the most snappy project management tool I've ever used, looks simple and runs well. I honestly love it, what a nice thing to have.

Most modern text editors and IDEs: I personally pay for JetBrains IDEs but also like Visual Studio Code as a text editor and both have helped me immensely, they're reasonably performant when you have the RAM, look nice, often give you suggestions about how to improve your code and also have a plethora of plugins in their ecosystems. Nowadays I unapologetically use LLMs as well and overall it feels like I have these great tools and cool autocomplete (that is sometimes a bit silly and wrong) at my disposal, that makes me happy.

Kdenlive: https://kdenlive.org/ imagine if there was a successor to Windows Movie Maker, though something that gets most of the important stuff out of Sony Vegas, except is also completely free and works on most platforms. Kdenlive is all of that and also somehow quite pleasant to use, I actually prefer it to DaVinci resolve. There is a bit of a learning curve to any piece of software like this, but everything mostly makes sense in this one.

Gitea: https://about.gitea.com/ I still use this for my personal Git repositories and integrating with CI systems and it's lightweight, looks good and just feels pleasant to use. Previously I self-hosted GitLab and constantly ran into resource exhaustion as well as doubts about the next update is going to corrupt all of my data and break (it did), so now I use Gitea instead.

Drone CI: https://www.drone.io/ a container native CI solution that I can also self host. It's container oriented, integrates with Gitea nicely, is similarly nice to GitLab CI and doesn't cause me headaches like Jenkins would.

Docker: https://www.docker.com/ yes, even Docker desktop. It just makes working with containers really pleasant and predictable, even when something like Podman also exists (and also is great). I don't know, I feel like Docker really saved me from having brittle legacy environments, even self-contained containers with health checks and resource limits with still the same brittle code inside of those make me feel way more safe.

Note: Before running your application in the next step, make sure you have Docker installed and running. It's required to locally run Encore applications with databases.

Developing WordPress plugins and themes often requires a reliable development environment. Current we have good solutions as wp-env from Autommatic, Local WP from WP Engine, Docker, XAMPP (for old ones) and so on. All this can be good suits for a development environment, specially Local WP that is probably the easiest one to get up and running and wp-env that leverages Docker as a development environment in a very easy way to use.

Docker, an open-source development platform, provides containerization technology for building and packaging applications along with their dependencies into portable images.

With each app containerized with Docker, this allows it to be run on any other developer's machine also running Docker. Although I had automated deployments to Heroku without this, I decided to upload each service to a container registry.

Docker

Today we are going to see all the power that a CLI (Command line interface) can bring to development, a CLI can help us perform tasks more effectively and lightly through commands via terminal, without needing an interface. For example, git and Docker, we practically use their CLI all the time, when we execute a git commit -m "commit message" or docker ps -a we are using a CLI. I'm going to leave an article that details what a CLI is.

Docker (required): Understanding Docker is crucial for deploying software in containers, making your project portable and scalable. I use it for start Folo server.