preevy VS LocalStack

Feel free to star the Preevy repo here.

We at Livecycle, a Docker-centric company, are super excited to share some highlights from the event and discuss how we are developing our products, Livecycle Docker Extension and Preevy, to improve collaboration, feedback, etc., in the vision that Docker is moving with their recent development and announcement at DockerCon.

To learn more about how to use Preevy, just check out the docs site.

Historically, many developers have preferred to facilitate this type of collaboration with ephemeral preview environments that are triggered with every PR or commit. And indeed, we have built robust solutions like “Preevy” to facilitate the creation of these environments for dockerized applications on any cloud or Kubernetes cluster.

Preevy also integrates into your CI pipeline to convert your pull requests into easily shareable ephemeral environments

My typical day is filled with a couple of meetings, building the Lifecycle community on Slack, collaborating with projects and people, and creating strategies and content (videos, blogs, short forms for Twitter and LinkedIn) around the product to increase adoption. I heavily focus on the company’s Open Source offering called Preevy which helps create a preview environment using Docker Compose underneath.

Also, at Livecycle, we are building Preevy, which helps you create a preview environment for Docker Compose applications. Do check out https://github.com/livecycle/preevy. It's open source, and don't forget to leave a star to show your support.

Check out the docs here

A dedicated docs site with relevant technical information and how-to guides for people who want to use it

About “Preevy” - an open source tool that simplifies the creation of preview environments

Later you can use any S3 compatible storage because the code I write will still work, but for testing purposes on my local machine, I will use LocalStack:

Acesse o site da LocalStack e faça login.

To give this a slightly different spin:

--> "The best optimization is simply not spinning things up."

At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.

We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".

What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.

(For others who hadn't heard of it: localstack is

LocalStack Website

O Localstack: https://localstack.cloud/, é um recurso que possibilita simular diversos recursos AWS (dynamoDB, s3, iam, cognito, ses), dentro da sua máquina, utilizando o docker.