spec
miniforge
Our great sponsors
spec | miniforge | |
---|---|---|
48 | 56 | |
2,666 | 5,078 | |
8.7% | 6.2% | |
7.3 | 7.7 | |
11 days ago | 4 days ago | |
Shell | ||
Creative Commons Attribution 4.0 | 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.
spec
-
Show HN: Lapdev, a new open-source remote dev environment management software
Hi, Lapdev dev here. Let me try to answer your question.
It's installed on a remote server so it provides remote environments. If you use VSCode remote, then you can "open" it through VSCode remote ssh.
The environment that Lapdev provides essentially is a container (other format is on the roadmap) with things pre-installed as defined in Devcontainer(https://containers.dev/) format.
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
Happy to take this one, as I am one of the cofounder of Daytona.
Daytona solves all the automation and provisioning of the dev environment, actually wrote an article here laying out exactly what we do: https://www.daytona.io/dotfiles/diy-guide-to-transform-any-m...
Daytona currently supports only the dev container (https://containers.dev/) "dev env infrastructure as code" standard, but are looking to support others such as devfile, nix and flox.
Hope this helps
-
A Journey to Find an Ultimate Development Environment
The full usage of the container means that you'll do the development inside the container. All the tools for development need to be installed inside the container. One of the technologies that leverage this approach is Devcontainers.
- Use Docker to create a local development Python environment
-
Launching dev containers from code - is impossible?
... is how I introduced the concept of dev containers in my last article.
-
Dev Containers: Open, Develop, Repeat...
How it works? Dev Containers is a specification based on Docker. This specification describes a metadata file (devcontainer.json), which defines how the project (Docker container, IDE settings, plugins, etc) is set up.
-
Try MongoDB and Laravel in 1-click via GitHub Codespaces
Codespaces is built to run Dev Containers, an open standard for Development Containers. The Dev Container will reference a Docker build file, which describes the software and services our app is running on. It also defines things related to our development environment, including IDE plugins, network ports, and more.
-
Dev Container for React Native with Expo
// For format details, see https://aka.ms/devcontainer.json. For config options, see the // README at: https://github.com/devcontainers/templates/tree/main/src/typescript-node { "name": "Node.js & TypeScript", // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile "image": "mcr.microsoft.com/devcontainers/typescript-node:1-20-bullseye", // Features to add to the dev container. More info: https://containers.dev/features. // "features": {}, // Use 'forwardPorts' to make a list of ports inside the container available locally. "forwardPorts": [8081], "initializeCommand": "bash .devcontainer/initializeCommand.sh", // Use 'postCreateCommand' to run commands after the container is created. "postCreateCommand": "bash .devcontainer/postCreateCommand.sh", // Configure tool-specific properties. // "customizations": {}, // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root. // "remoteUser": "root", // "containerEnv": { // }, // "remoteEnv": { // "DEV_USER_HOST": "${localEnv:USERNAME}" // }, "runArgs": ["-p=8081:8081", "--env-file", ".devcontainer/.env"] }
-
Microsoft Docker Development Container Templates
I do not know why someone shared this repo, there is nothing special about it other than containing some start templates. I would start here for understanding Dev Containers: https://containers.dev
If you have a scenario where using a container as your development environment makes sense, this is some tooling that can improve the developer experience vs just using plain Docker and Docker Compose.
I see it as being similar to the relationship between Vagrant and Virtual Machines.
You can use plain Dockerfiles if you prefer, dev containers provides some tooling to smooth out the rough edges of using Docker to host your dev environment including mounting your source code into the container etc. Details are at: https://containers.dev
miniforge
- Python 3.12
- Installing Anaconda on ChromeOS using Linux
-
PSA: conda-libmamba-solver can cut two hours off of your Anaconda install, but has only 47 GitHub stars. It deserves more praise.
Mambaforge!
See the section on the miniforge github repo. It's just like miniconda/miniforge in that its quite a small download vs full-fat Anaconda.
-
A quick guide to using mamba-forge for python virtual environment management
Just to further clarify: you don't need mamba to avoid the Anaconda distribution. The place you get mambaforge also supplies (and originally supplied) miniforge, which is miniconda with conda-forge set as the default channel. All the *forge installers do in this regard is automatically set conda-forge as the default (and only) channel, which is something one can do manually with miniconda.
-
How to get the best Conda environment experience in Codespaces
Tip 1: To use less of your Codespaces resources start with a smaller image like Miniconda or Miniforge and install only what you need.
-
Ask HN: Programs that saved you 100 hours? (2022 edition)
miniforge, no need to deal with conda environments anymore. https://github.com/conda-forge/miniforge
-
Using my Steam Deck as my main personal Desktop PC.
gcc yes but IIRC it's missing a lot of build-essential, and the collection of available headers and development libraries is fairly small. I used conda / mambaforge to build my own toolchain, and I know others have had succeess with Homebrew or pacman - r.
Since you mentioned Homebrew, I'll shout out conda / mamba as well. While it was developed for data science and numerical python, conda-forge has a surprising breadth of packages, and I managed to get the entire gcc toolchain plus development libraries installed, all not only in the userspace, but isolated to a single virtual environment.
Talk about easy mode. conda mamba or poetry, and you're done. I think SteamOS even ships with vim and not just vi, but if you need a different version, it's available via conda.
What are some alternatives?
mamba - The Fast Cross-Platform Package Manager
pyenv - Simple Python version management
conda - A system-level, binary package and environment manager running on all major operating systems and platforms.
Poetry - Python packaging and dependency management made easy
tensorflow_macos - TensorFlow for macOS 11.0+ accelerated using Apple's ML Compute framework.
pip-tools - A set of tools to keep your pinned Python dependencies fresh.
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
pyright - Static Type Checker for Python
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS
Amethyst - Automatic tiling window manager for macOS à la xmonad.
Zappa - Serverless Python
Pipenv - Python Development Workflow for Humans.