bazel_compose
entr
bazel_compose | entr | |
---|---|---|
1 | 47 | |
12 | 4,028 | |
- | - | |
0.0 | 6.8 | |
over 3 years ago | about 1 month ago | |
Python | C | |
MIT License | GNU General Public License v3.0 or later |
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.
bazel_compose
-
You Don't Need to Rebuild Your Development Docker Image on Every Code Change
While this is great for people with a fundamental understanding of containers and your prod environment this will usually lead to some issues with developers that don't need to, or want to, have context in these areas.
In the past, to make a very similar workflow possible, I've built tools that automatically watch your source files and rebuild & restart only what is needed [0]. This was built for bazel + docker-compose but there isn't a reason one couldn't watch the "build:" contexts for what files are important.
At a previous company one of our engineers was a huge fan of this volume mount approach and every single time something broke (which was very frequent due to some prod/dev env magic we had) I had to assist quite a few more junior devs figure out what was wrong with their machine. For those with scripting languages, was it their system's newline endings? For compiled languages, was their system SDK different then what was in the container? For prod bugs, did they forget to rebuild & test the container before opening their PR (we had no automated integration testing)?
In my opinion, if you can make your build system in charge of building/packaging things you'll have a much happier time.
[0] - https://github.com/CaperAi/bazel_compose
entr
- Entr – tool for watching files and running commands
-
Meet entr, the standalone file watcher
entr ("Event Notify Test Runner"; GitHub), is a command-line tool written by Eric Radman that allows running arbitrary commands whenever files change.
-
How to build a website without frameworks and tons of libraries
I use something very similar on https://lunar.fyi and https://lowtechguys.com but I wouldn’t call this “simple” anymore.
They use Jinja templating, I prefer Slim (https://github.com/slim-template/slim#syntax-example) which has a more Pythonic syntax (there is plim [0] in Python for that)
I use Tailwind as well for terse styling and fast experimentation (allows me to write a darkMode-aware and responsive 100 line CSS in a single line with about 10 classes)
For interaction I can write CoffeeScript directly in the page [1] and have it compiled by plim.
I run a Caddy static server [2] and use Syncthing [3] to have every file save deployed instantly to my Hetzner server.
I use entr [4] and livereloadx [5] to rebuild the pages and do hot reload on file save. All the commands are managed in a simple Makefile [6]
———
You can already see how the footnotes take up a large chunk of this comment, this is not my idea of simple. Sure, the end result is readable static HTML and I never have to fight obscure React errors, but it’s a high effort setup for starters.
Simple for me would be: write markdown files for pages, a simple CSS for general styling (should be optional), click to deploy on my domain. Images should automatically be resized to multiple sizes and optimized, videos re-encoded for smaller filesize etc.
I have mostly implemented that for myself (https://notes.alinpanaitiu.com/How%20I%20write%20this%20blog...) but it feels fragile. I’d rather pay for a professional solution.
[0] https://plim.readthedocs.io/en/latest/
[1] https://github.com/FuzzyIdeas/lowtechguys/blob/main/src/rcmd...
[2] https://caddyserver.com/docs/command-line#caddy-file-server
[3] https://syncthing.net
[4] https://github.com/eradman/entr
[5] https://nitoyon.github.io/livereloadx/
[6] https://github.com/FuzzyIdeas/lowtechguys/blob/main/Makefile
- How to start a Go project in 2023
-
[Guide] A Tour Through the Python Framework Galaxy: Discovering the Stars
Try entr for fast reloading. Another one is hupper.
- Use entr when working on you rice for auto config refreshing
- The Unix process API is unreliable and unsafe
- How do you develop cloud-native applications locally on Kubernetes?
-
What are the not-so-obvious tools that you don't want to miss?
entr
- Test driven development is adhd dream
What are some alternatives?
Docker Compose - Define and run multi-container applications with Docker
watchexec - Executes commands in response to file modifications
skaffold - Easy and Repeatable Kubernetes Development
nextjs-tailwind-ionic-capacitor-starter - A starting point for building an iOS, Android, and Progressive Web App with Tailwind CSS, React w/ Next.js, Ionic Framework, and Capacitor
telepresence - Local development against a remote Kubernetes or OpenShift cluster
modd - A flexible developer tool that runs processes and responds to filesystem changes
volta - Volta: JS Toolchains as Code. ⚡
swc-node - Faster ts-node without typecheck
air - ☁️ Live reload for Go apps
vim-test - Run your tests at the speed of thought
integresql - IntegreSQL manages isolated PostgreSQL databases for your integration tests.
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.