nullroute

joined 2 weeks ago
[–] nullroute@programming.dev 2 points 1 week ago

Thank you VitoRobles

[–] nullroute@programming.dev -3 points 1 week ago

Feyd, another temple guardian.

Where is the harm in sharing a tool with people? What is the problem exactly? Is it written somewhere on this site, or in this community, that we are not allowed to share (or promote, if you prefer) a tool? Is it forbidden?

Did you actually test LocalEmu? Install it? Read what it does? Or did you join the dance for something else entirely?

What a clown.

[–] nullroute@programming.dev -1 points 1 week ago (2 children)

aquafunk, the planet is in shit just for me, apparently. Not for the rest of humanity. Maybe I am the only one breathing pollution every day in most of the places I go, and the only one who has felt the climate change of the last twenty years that everyone else around me has been feeling too. Or maybe that one is also a scam invented by LLMs.

On "you are the one person presenting this app": yes, I am the one presenting it, and I am proud of what I shipped. I am also humble about it. A side question, since you took the time to lecture me about personal responsibility: did you install it? Did you actually try it? Do you work with AWS on a daily basis? Are you boycotting AWS too, since AWS is built on top of a mountain of open-source software they make profit from, and since AWS also uses LLMs to ship its features?

[–] nullroute@programming.dev 0 points 1 week ago (1 children)

I said it in my first reply, paragraph one. Not embarrassed. Calling someone defensive because they respond to attacks instead of capitulating is a rhetorical trick, not an argument. Attacking a stranger over a free open source project, for fun or out of some hidden envy, says more about you than about the project :).

[–] nullroute@programming.dev 4 points 1 week ago

Why what, exactly? Could you be more specific?

[–] nullroute@programming.dev 9 points 1 week ago (15 children)

Hey, thanks for the comments, let me answer all three at once.

Yes, parts of the LocalEmu code are generated with an LLM (Claude, mostly). It is very controlled and architected by me. I have written enough code over the years to understand what I am doing and what the LLM is doing, and what ships under my name is my call and my responsibility.

Let me ask back: what does the fact that parts of the code are LLM-generated change about the final result? The repo is Apache-2.0 and public. The behaviour is testable. If something is wrong, I would like to know so I can fix it. If it works, why does the way it was typed matter?

I genuinely do not understand the hostility against people who use AI tools and know what they are doing. I am not ashamed of using the tools this era gives me to improve my productivity and ship something useful. The opposite: I would be ashamed if I could not design and code these things myself when I need to. I can. It would just take much longer, and I accept that.

I am not competing with LLMs. Claude, GPT, Cursor, whatever you use, they win the war of producing a lot of code quickly, sometimes better than I would. They also help me with the tasks I do not have time for on a side project: documentation, unit tests, E2E tests. And honestly, designing a website or a landing page with the right CSS. I love the result. I never had the time in my career to learn the frontend side properly, and for a backend / CLI guy like me, LLMs are something amazing here. That is the part of the project that is the most LLM-shaped, and I am not going to pretend otherwise.

We are in an accelerated AI era and every developer gets to decide if they want to ride the wave or not. I have my own opinion about it, but that debate is not what this post is about and I do not want to hijack the thread with it.

The post is about sharing a project I maintain with my own time and energy, looking for a community that shares the goal of making it grow. Maybe other projects after that with the same community, or parts of it. If you have a use case, a bug, a missing service or a workflow LocalEmu does not handle yet, that is what I would love to hear about.

PRs and issues are welcome: https://github.com/localemu/localemu

[–] nullroute@programming.dev 2 points 1 week ago

Thanks for trying LocalEmu :). Yes, you can map a directory without scripting per-file uploads.

aws s3 sync ./mydir s3://mybucket/ works against LocalEmu out of the box (or awsemu s3 sync with the bundled zero-config CLI). For "always populated on start", drop a one-line script in /etc/localemu/init/ready.d/ and it runs on every boot:

docker run --rm -d -p 4566:4566 \
  -v $PWD/fixtures:/fixtures:ro \
  -v $PWD/init:/etc/localemu/init/ready.d:ro \
  -e DASHBOARD_API_OPEN=1 localemu/localemu

Where init/ready.d/seed.sh does awsemu s3 sync /fixtures s3://mybucket/. Or PERSISTENCE=1 if you'd rather load once and have it stick.

LocalStack inspired a lot of this, we're the free open-source continuation.

[–] nullroute@programming.dev 4 points 1 week ago

Appreciate it :). Ping me on GitHub if you hit any snags, feedback very welcome.

 

I maintain LocalEmu, a free and open-source (Apache 2.0) AWS emulator. It started as a fork of the archived LocalStack Community edition. The goal is to keep a genuinely free, open local AWS emulator alive and maintained.

What it does:

  • Emulates 132 AWS services on a single endpoint (localhost:4566)
  • Pure-Python core, with real Docker engines for Lambda, EC2, RDS, ECS, EKS, and OpenSearch
  • Point your existing AWS CLI, boto3, Terraform, CDK, or Pulumi at it, zero config
  • No account, no auth token, no telemetry. Persistent state across restarts
  • Optional fidelity knobs: IAM policy enforcement, throttling, latency injection, Lambda cold starts

Why I built it: kill the multi-minute deploy loop, drop the dev/test AWS bill to zero, and stop keeping real credentials on dev machines.

It's for fast local dev, testing, and learning, not production, and not bit-for-bit parity with the real cloud.

Repo: https://github.com/localemu/localemu Site: https://localemu.cloud/

Happy to answer questions, and feedback is very welcome.

view more: next ›