Edward Amsden

For reference, this is the edit implementation in New Mars: https://github.com/urbit/new-mars/blob/892a490fca1aa19499355ef30115bdf714b6f50e/rust/iron-planet/src/interpreter.rs#L530-L572

I think that is the correct stopgap. I'll try to cross-validate on a Pi soon. (Sorry to take so long to get back on this. I got pulled away to...

I've opened #411 which brings over a bunch of stuff from iohk-nix that we originally did for aarch32 cross-compilation. It also changes the build to quick-cross to avoid breaking qemu....

(This appears to be a duplicate of #81, and the `Accept` header may be irrelevant)

Update: it turns out that newer versions of ofxclient (>2.0.2 I think) send a user-agent header, and a comma-separated "accept" header, both of which appear to confuse Schwab's OFX servers....

It appears that this is addressed in #81

I'm working on the above but I've given up on the cloud-init route. My current approach is to try to generate a NixOS module from the digital ocean metadata (sort...

One other thing to note is that the Digital Ocean API (as opposed to the web GUI) only supports getting a custom image from an HTTP server. It does not...

NixOS has digital ocean image builds in master, so I think it is a matter of a PR to get NixOps using them for DO. Unfortunately that's not a PR...

if @xiphiness has jets for this I'd like to propose that it be merged once those are ready.