No devenv videos yet. You could help us improve this page by suggesting one.
Based on our record, devenv should be more popular than Artifactory. It has been mentiond 37 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
It works on MacOS/Windows, unlike systemd. Therefore it's well suited for development environment setups for polyglot teams. https://devenv.sh/ is one example that uses it to do just that. - Source: Hacker News / 29 days ago
Sounds like nix using devenv[1] also would solve this problem. https://devenv.sh/. - Source: Hacker News / 29 days ago
Software developers often want to customize: 1. Their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow). 2. Their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here. 3. Or even their operating systems: for... - Source: Hacker News / about 2 months ago
Https://devenv.sh/ and nix in general are great for setting up dev environments. - Source: Hacker News / 2 months ago
2) A way to run services apps depend on (databases, job runners, cache etc). I am going to suggest one of the Nix based tools that do those things:- Source: Hacker News / 4 months ago- https://devenv.sh/ (I use this at work).
I kind of hate it, but Artifactory seems popular at companies: https://jfrog.com/artifactory/. Source: 11 months ago
When not providing all dependencies yourself, you might suffer from people deleting the packages you depend on (IMHO a very rare scenario). If it is really that critical (hint: usually it isn't), create a local mirror of Pypi (full or only the packages you need). Devpi, Artifactory, etc. Can do that or you just dump the necessary files into Cloud storage, so you have a backup. Source: about 1 year ago
Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago
Like suppose for a second that . . . Idk . . . a product team wants our ci workflows to start using Artifactory. Okay great, I don't know Artifactory integration but I'm going to tell them "Sure, I'll get right on that.". Source: over 1 year ago
If these "assets" have an independent release schedule I would treat them separately (especially if they are externally provided). If they are not built from source then treat them as artefacts, they don't belong in git. You can store the in an artefact repository (like Artifactory of Nexus) or (as u/nekokattt points out) in something like S3. Source: over 1 year ago
Flox - Manage and share development environments with all the frameworks and libraries you need, then publish artifacts anywhere. Harness the power of Nix.
Sonatype Nexus Repository - The world's only repository manager with FREE support for popular formats.
Podman - Simple debugging tool for pods and images
Cloudsmith - Cloudsmith is the preferred software platform for securely storing and sharing packages and containers. We have distributed millions of packages for innovative companies around the world.
DevBox - Everyday utilities for the everyday developer
Git - Git is a free and open source version control system designed to handle everything from small to very large projects with speed and efficiency. It is easy to learn and lightweight with lighting fast performance that outclasses competitors.