What's a low-effort option for a Codidact development machine? Question
I would like to be able to work with qpixel in a development environment so I could (try to) fix small bugs and build and test locally. I don't have a developer setup now and my OS is apparently too old for some of our tools. Changing the OS on the personal machine on which I depend is not an option.
However, I'd be perfectly happy to get another machine (presumably Linux) for this purpose, ideally one I could connect to remotely instead of needing to clear more table space for another monitor/keyboard/mouse. I'm assuming that this needn't be an expensive proposition; somebody told me it could be done on a Raspberry Pi, for example.
I'm not a hardware or OS tinkerer by inclination. I'm very goal-oriented when it comes to stuff like this, and I'm willing to trade money for time and aggravation. What is the minimum reasonable "off-the-shelf" (or nearly so) hardware and Linux environment that would let me accomplish my goal of a Codidact dev environment?
To clarify "nearly off-the-shelf": I'm fine with "download this thing from here and install it" level of work, but not with "figure out how to get X working at all" and "make these decisions that would require research to do". I don't need the best environment, IDE, etc; I just need something that works, and I don't want to start from bare metal with setting up an OS. Depending on the specifics, I'm probably willing to pay somebody for something that's already mostly set up.
A Raspberry Pi will run QPixel, and would be almost ideal for development as a small tinkering box. It's small, it'll fit on a desk with everything else already there, it can be remoted into. The only catch is that (unless you buy a pre-set-up Pi) you do have to set up the OS, but that's not a difficult task - as long as you can follow instructions, it should be relatively easy.
0 comment threads
While I haven't gotten to doing it myself yet, my recommendation, except for those who have to work totally offline (which would cause problems for any content coming from a CDN or other sources such as Sefaria), my recommendation is to use Amazon Web Services (AWS). This happens to be the same system used for the production environment.
While you do need to have a credit card or other payment method set up to get started, much of the basic level is either totally free or free for 12 months - what Amazon calls Free Tier. This includes:
- 750 hours of t2.micro or t3.micro (effectively one tiny server on 24/7, but could be more if you turn them on/off as needed) (Need to check specs to see if t2.micro or t3.micro is big enough.)
- 5 GB S3 storage - enough for a basic system with a bunch of test image uploads, etc.
- 750 hours of RDS, which means if you want to use a small RDS database instead of running MySQL within EC2, that is an option at no extra charge.
- 30 GB Elastic Block Storage, which works with EC2.
The alternatives are either a small-but-dedicated Linux system or a virtual machine (e.g., VirtualBox) within a Mac or Windows system.
1 comment thread
If you want something that is marginally cheaper in some regards and doesn't have too much custom stuff to wrangle with (AWS has a lot of stuff like IAM, security groups etc. that can be annoying to manage/confusing), I'd personally recommend Digital Ocean (https://digitalocean.com). You may know them from the tech tutorials that they write online (topics such as 'how do I install a certain tool or stack?').
They offer a free trial (https://try.digitalocean.com/freetrialoffer), which lets you use better resources for a while (the only issue is that downgrading is challenging, same as AWS).
1 comment thread