These replies prompted me to go looking. Firefox Android (which I'm using) does have an option in the settings under Accessibility called "Zoom on all websites". It works!
Chrome has a similar option, which also works on this site. I expect this might break a few pages, but Google Maps and OpenStreetMap work fine, with pinch zoom zooming the map when you do it on the map.
Don't have to use PowerShell either, it's been available for ages through Disk Management. Right-click on a partition -> Change Drive Letter and Path -> Add -> Mount in following empty NCTS folder.
> where I create LOC records for devices without a dynamic IP address so I can figure out where the f*k they are without having to keep a continuous mental map running at all times
Obligatory bash.org quote[1]:
<erno> hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is.
I like JSON schema, but I haven't found any good tools to designing them. Or at least not a few years ago when I was looking.
However, we already had an XMLSpy license, so decided to just stick with designing XSDs in XMLSpy and then just translate that to JSON Schema.
If you make some small decisions, like value with attributes becomes an object, you can get a fairy decent subset of XSD to map 1:1 onto JSON Schema 2020-12.
As a nice side effect of writing the XSD to JSON Schema converter, it's trivial for us to support reading XMLs and convert that to JSON. Great for the customers who have programs that doesn't speak JSON.
Yes, I've been searching for a long time for a good solution to allow non-coding people to visually design JSON Schemas. The closest thing I found is the schema editor in the amazing Stoplight service, but that is sadly not open source.
Heck, I'm a coder and I get lost when just dealing with the raw JSON Schema.
It's not a problem for a dozen properties, but we have several hundreds in our larger schemas, even accounting for them being fairly normalized w.r.t. types. And five or more levels of nesting turns into an effective ten plus levels in the schema.
One underutilised feature of JSON Schema is referencing external schemas and reusing them in multiple places, rather than copying them over and over again. The main hurdle to a better use of this feature is the lack of a good standard for schema repositories; I've been working on addressing this, but it's difficult to find the time. :/
> One underutilised feature of JSON Schema is referencing external schemas and reusing them in multiple places
Yeah, though while it does make each subschema somewhat more readable and contained, you still don't get a good overview. If you're reading the spec for a given object, do you don't easily see where it's being used in the schema.
For now I've just supplied the JSON Schema as a self-contained thing, and deferred other parties to the XSD to get an overview. The self-contained makes it trivial to load into a validator and such.
So while it helps for knowing what to fill into that exact object, it doesn't help for getting a feel for the overall schema. This is where the visual view of tools such as XMLSpy really helps.
> lack of a good standard for schema repositories
Interesting, do you have something public to show? For our large ones I feel they'd be entirely custom anyway, but perhaps I can see standard sub-schemas useful for other tasks. Would be interesting to have a look.
True, when focusing only on the schemas as code. But good tooling could provide links and similar.
> do you have something public to show
Just a very early PoC [0]. I'm slowly working my way through a very long to-do list of improvements, but I'm lacking time and resources to do it more efficiently.
> TrueNAS was very unfriendly towards even the idea of opening a shell [1] and IIRC you couldn't even install debian packages out of the box.
It's meant to be an appliance, so it makes sense in that setting. That said, it does support hosting Docker images, so you don't really need much in the way of installing packages IME.
True, but that disrupts ecosystems. Or so the argument against go building storage dams go.
That said, there's been a fair bit of talk here in Norway recently about tax incentives blocking hydro owners from upgrading old generators, improving efficency. Apparently a lot of currently unused power available if they "just" did that.
I wonder if it's possible to also increase the amount of generation on existing dams? I could imagine there being situations where there's excess peak flow capacity but it isn't utilized because the flow rate would be unsustainable. But if we're looking for storage it could make sense.
A twenty-foot container, I imagine? Retail for onesies seems to be about 4× that.
Typically panels account for about a third of the cost of a turnkey solar power system, but that's largely because of historical design features that are no longer necessary.
You can run it with much less. I don't recall the bare minimum but with a bit of tweaking 2GB should be plenty[1].
I recall reading some running it on a 512MB system, but that was a while ago so not sure if you can still go that low.
Performance can suffer though, for example low memory will limit the size of the transaction groups. So for decent performance you will want 8GB or more depending on workloads.
Which is why Norway wasn't affected by EU's trade barrier on ferro-alloys... oh wait[1].
[1]: https://www.reuters.com/world/china/eu-imposes-quotas-curb-i...
reply