spec
miniforge
Our great sponsors
spec | miniforge | |
---|---|---|
48 | 56 | |
2,814 | 5,243 | |
9.0% | 7.0% | |
7.0 | 7.7 | |
3 days ago | 12 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.
-
How CDEs work - no bs blog post
Two standards for CDE configuration exist: devfile.yml and devcontainer.json. Both assume that the CDE is a single container and allow specification of which tools should be deployed to this container, as well as a reference to scripts that should run after the container has been created.
- 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.
-
Is there some catch to cause DNS issues on Linux, that is not common with Windows or Mac?
I was using Devcontainer with VS Code. In a part of the container build process, DNS lookup seemed to be failing in Debian 12. BTW, the container image was based on Debian 11. I probably tried it about 10 times in total, so I'm pretty sure it persisted, not an one time error. I noticed the build process was failing because the process failed to find some domains, with an error message like could not resolve host github.com. Some domains I noticed was github.com and ghcr.io, so it failed sometimes for one domain, and sometimes for the other.
-
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"] }
miniforge
- Python 3.12
- Installing Anaconda on ChromeOS using Linux
-
What is the difference between chat, cai-chat, and instruct, and how to use them?
Nope they don't use venv for any of the oobabooga# variants nor is it recommended for the git version. I'm using https://github.com/conda-forge/miniforge#mambaforge-pypy3 (better version of the recommended conda) for the git variant. The oobabooga* variant uses micro/miniconda (I suck with names) which you can easily drop into with cmd_?something? and does it all internally. Like whoever built that whole environment setup for the _windows/linux/mac did a great job.
-
Build llama.cpp on Jetson Nano 2GB
wget https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-aarch64.sh .
-
PSA: conda-libmamba-solver can cut two hours off of your Anaconda install, but has only 47 GitHub stars. It deserves more praise.
Mambaforge!
-
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.
- Recommendations for Data Science Workflow
-
path issue - cannot import modules in jupyter installed via pip3 (m1 mac)
I'd recommend using miniforge if you're comfortable with CLIs, otherwise https://www.anaconda.com/.
-
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
What are some alternatives?
features - A collection of Dev Container Features managed by Dev Container spec maintainers. See https://github.com/devcontainers/feature-starter to publish your own
mamba - The Fast Cross-Platform Package Manager
features - A collection of development container 'features' for machine learning and data science
pyenv - Simple Python version management
conda-devcontainer-demo - Mini Conda + Mamba dev container setup to make working with environments easy.
conda - A system-level, binary package and environment manager running on all major operating systems and platforms.
tweek - Tweek - an open source feature manager
Poetry - Python packaging and dependency management made easy
lapdev - Self-Hosted Remote Dev Environment
tensorflow_macos - TensorFlow for macOS 11.0+ accelerated using Apple's ML Compute framework.
microservice-rust-mysql - A template project for building a database-driven microservice in Rust and run it in the WasmEdge sandbox.
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more