projector-docker
Vagrant
Our great sponsors
projector-docker | Vagrant | |
---|---|---|
12 | 115 | |
2,094 | 25,852 | |
- | 0.6% | |
5.7 | 9.0 | |
almost 2 years ago | 8 days ago | |
Shell | Ruby | |
Apache License 2.0 | MIT License |
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.
projector-docker
-
Codespaces but open-source, client-only, and unopinionated
Although they've basically closed source it since release, Jetbrains Projector was a fantastic tool I've used a lot in the past for that - Just spin up a docker container on my home server and pull out my ipad keyboard
https://github.com/JetBrains/projector-docker
Unfortunately, It's hard to tell if JetBrains Gateway will keep all of the remote dev features or not.
- Running python scripts on homeserver?
- Self-hosted development environment for Python
- Moving your favorite IDE to the cloud (VSCode vs JetBrains)
-
Cloud IDE for rust
If you have a student package from JB, you can use CLion for Rust development (as do I) and spin up a cloud instance of Clion https://github.com/JetBrains/projector-docker Then you can access it from anywhere over the web.
- I need a setup where I can work from any system on my code.
-
Recommended IDE with Python interpreter?
You can self host Jetbrains IDEs actually! https://github.com/JetBrains/projector-docker
-
Intellij failing badly on Chrome Os
Maybe try using IntelliJ Projector - just run your IntelliJ harmlessly (almost) in the browser :D You can run it simply using docker, run on your machine, or even on the cloud. I have tried to use that for my personal projects and it works.
- Run JetBrains IDEs Remotely with Docker
-
JetBrains Projector released - Access Your IDE Remotely With Projector
Worked a lot better using one of their Docker images, but feels like it has too many drawbacks compared to my current VcXsrv setup. Cool stuff though, hope it gets developed further.
Vagrant
-
Ask HN: Please recommend how to manage personal serverss
Take a look at Vagrant! https://www.vagrantup.com/ In my admittedly limited understanding I believe it offers closer to a nix like reproducable rather than repeatable deployments.
-
Software Company HashiCorp Is Weighing a Potential Sale
on the off chance one hasn't been tracking it, there were several "we don't need your stinking BuSL" projects when this drama first started:
https://github.com/opentofu#why-opentofu (Terraform)
https://github.com/openbao/openbao#readme (Vault)
and I know of several attempts at Vagrant <https://github.com/hashicorp/vagrant/forks> but I don't believe one of them has caught traction yet
There are also some who have talked about an "open Nomad" but since I don't play in that space I can't speak to it
-
Ask HN: Cleanest way to manage Windows OS?
It sounds like you're using Nix as a sort of configuration management solution. CM just isn't worth it for managing a single desktop IMO. It triples the effort for whenever you need to add or remove a package, as you must now add that also to your nix configuration. You're supposed to be able to make that back up in time saved restoring to the next machine, but inevitably the next machine will be different enough that you'll have to edit it all anyway. In the end I just got tired of trying to manage my own machine with infrastructure as code (though in fairness I was using puppet at the time not nix).
I keep a git repository with all my dot files in it[1]. This seems to work the best. It has a Windows folder as well, and I copy that out whenever I need to set up Windows.
A lot of people like using WSL but I hate how it hogs on my memory. Hyper-V is a terrible virtualization engine for consumer-grade use cases because it can't thin provision RAM. If I need to use docker, I will spin up a small Linux VM using vagrant[3] with Virtualbox[4] and put Docker on there. Vagrant is an extremely underrated tool in my opinion, particularly in a Windows context.
I use scoop for packages. Typically I will scoop install msys2 and then pin it so that it doesn't get blown away by the next upgrade.
Then I basically do all of my development inside of msys2. I can get most things running in there without virtualization. In my case that means sbcl and roswell for common lisp, senpai for irc, and tmux and nvim for sanity. Msys2 uses the pacman package manager and this is good enough.
All In all, I set up my Windows machine affresh after a while of not using it and it took me about 3 hours. Most of that time was just getting through upgrades though, I felt like it was pretty fast.
1: https://git.sr.ht/~skin/dotfiles
2: https://www.msys2.org/
3: https://www.vagrantup.com/
4: https://www.virtualbox.org/
-
A Developer's Journal: Simplifying the Twelve-Factor App
Tools like Docker and Vagrant can be used to allow local environments to mimic production environments.
- Is there any place where I can download an already configured Virtual machine? For example with Linux Ubuntu or Windows 10 preinstalled?
-
UTM – Virtual Machines for iOS and macOS
There's an open issue [1]. A scripting interface has since been added [2], and updated [3], so there's progress.
[1] https://github.com/hashicorp/vagrant/issues/12518
- Vagrant license changed to BUSL-1.1
-
HashiCorp Adopts Business Source License
Someone should fork and maintain Vagrant with an MPL open source license:
https://github.com/hashicorp/vagrant
-
Codespaces but open-source, client-only, and unopinionated
https://github.com/hashicorp/vagrant/blob/v2.3.7/CHANGELOG.m... ?
The changelog lists both improvements and bug fixes and there's even apparently some effort to port it away from ruby: https://github.com/hashicorp/vagrant/blob/v2.3.7/internal/cl...
-
Vagrant Fatal Error: Runtime BSDThread_Register Error
If you’ve ever encountered the dreaded “Vagrant fatal error: runtime BSDThread_Register error,” you’re not alone. This perplexing error message can be frustrating and confusing, especially if you’re new to Vagrant and virtualization. But fear not! In this article, we’ll unravel the mystery behind this error, explain its meaning, and provide solutions to help you overcome it.
What are some alternatives?
Code-Server - VS Code in the browser
Packer - Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
projector-server - Server-side library for running Swing applications remotely
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
QEMU - Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
ZeroTier - A Smart Ethernet Switch for Earth
Capistrano - A deployment automation tool built on Ruby, Rake, and SSH.
rust
Puppet - Server automation framework and application
projector-client - Common and client-related code for running Swing applications remotely
BOSH - Cloud Foundry BOSH is an open source tool chain for release engineering, deployment and lifecycle management of large scale distributed services.