alnoda-workspaces
spec
Our great sponsors
alnoda-workspaces | spec | |
---|---|---|
171 | 48 | |
1,294 | 2,783 | |
- | 8.0% | |
5.9 | 7.3 | |
9 months ago | 25 days ago | |
Dockerfile | ||
GNU Affero General Public License v3.0 | Creative Commons Attribution 4.0 |
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.
alnoda-workspaces
- Emacs code editor in browser. Link to the Dockerfile - https://github.com/bluxmit/alnoda-workspaces/tree/main/workspaces/emacs-workspace
- Truly portable environments for various engineering projects
-
Personalized and highly extendable Docker-based self-hosted cloud development environment that does not require much of Docker knowledge
Get all the details at our [GitHub repo](https://github.com/bluxmit/alnoda-workspaces) or documentation https://docs.alnoda.org/.
- This docker image contains RStudo, JupyterLab, Radian and VScode.
-
Super easy complex self-hosted development environments without knowledge of Docker.
Docs: https://docs.alnoda.org/
-
Remote Desktop from anywhere
Please check out my project https://github.com/bluxmit/alnoda-workspaces It is very easy to launch, self-host, and you can install lots of applications, including various Linux desktops and hundreeds other applications. In the docs you will find how to self-host on server or kubernetes, including https and auth
- How we made containerized development environments without knowledge of Docker
- Personal workspaces in Docker without deep knowledge of Docker
- Alnoda worksapce. portable containerized browser-based development environments in Docker containers. You can create your own custom workspace or customize any workspace with your preferred stack of applications without knowing Docker.
-
Best uses for a second home server
One more place: https://github.com/bluxmit/alnoda-workspaces/tree/main/workspaces
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"] }
What are some alternatives?
infracost - Cloud cost estimates for Terraform in pull requestsπ°π Shift FinOps Left!
features - A collection of Dev Container Features managed by Dev Container spec maintainers. See https://github.com/devcontainers/feature-starter to publish your own
Code-Server - VS Code in the browser
features - A collection of development container 'features' for machine learning and data science
zsh-in-docker - Install Zsh, Oh-My-Zsh and plugins inside a Docker container with one line!
conda-devcontainer-demo - Mini Conda + Mamba dev container setup to make working with environments easy.
migra - Like diff but for PostgreSQL schemas
tweek - Tweek - an open source feature manager
docker-experiment - Encapsulating (almost) every single software on my computer in a Docker container
lapdev - Self-Hosted Remote Dev Environment
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
microservice-rust-mysql - A template project for building a database-driven microservice in Rust and run it in the WasmEdge sandbox.