yuvipanda
yuvipanda on Hacker News
Thanks! This is a good start.
Do you have ideas on how you will make the governance of the registry open? Who will make important decisions around policies, and how will they be made? I personally find this to be the core reason I find it hard to use startup-run package registries.
JupyterHub isn't really setup to do a 'dashboard' style web application - is purely intended for interactive use. The design choices made reflect this.
There's ongoing work on formalizing the proxy better (https://github.com/jupyterhub/jupyterhub/issues/848) - someone will probably write a pure python proxy when that gets merged :)
Disclaimer: I work on the hub.
Sorry to hear you found the hub too complex. We're working on making easier-to-use hub setups that fit different use cases. Can you tell us a little more about what your use case was and (optionally) which parts of the hub setup you found too complex?
Thanks!
You can use systemd or docker with JupyterHub, and make it as protected (or not) as you want. We could also write a spawner that spawns full fledged VMs, which would give you 'real' untrusted isolation - would that be something interesting to you?
Don't see anything else around that fits that bill. They also have amazing IRC bridging - I have been using Matrix bridged into Freenode as my primary 'IRC Client' for almost a year now.
Have you considered adding kubernetes support?
<3
My only question is if it is required that they mention 'I have cramps' explicitly publicly. Not sure if their menstrual cycle is anyone's business. There's also no reason for it to be taboo, but not sure where the balance of 'it is nbd, deal with it!' vs 'I do not really want to broadcast this information to my teammates' is.
We run it at Wikimedia for our Tool Labs setup, and are migrating more things to it over time.
There used to be a team dedicated to making MW Core better / cleaner, but that was lost in a re-org earlier in 2015.
> The Taco Bell answer? xargs and wget. In the rare case that you saturate the network connection, add some split and rsync. A "distributed crawler" is really only like 10 lines of shell script.
As someone who has had to cleanup the messes of people who started with this and built many hundred line dense bash scripts... please do not do this.
> I made most of a SOAP server using static files and Apache's mod_rewrite. I could have done the whole thing Taco Bell style if I had only manned up and broken out sed, but I pussied out and wrote some Python.
I feel sad for whoever inherited this person's systems.
"Write code as if whoever inherits it is a psychopath with an axe who knows where you live" is something I heard pretty early on in life and it's been pretty useful.
I think :terminal has changed the way I develop at least a little bit. I haven't checked out the async linters yet.
I've switched 100% to neovim. Is pretty nice! No real GUI though.
Can't all those three things be done with simple AJAX too, instead of having to make your entire application Javascript based?
Does anyone know what license this would be under?
They aren't making it generally available to the public yet, only to certain beta folks who know what they are getting. It isn't broken out of the box since it isn't 'out of the box' yet.
https://defuse.ca/audits/encfs.htm is an EncFS security audit, that didn't come out too clean. If you install encfs on debian it pops up a warning screen telling you to not use it for anything too sensitive atm.
I wish it offered using symmetric crypto - so I won't have to find ways to secure a GPG key...
I presume one wouldn't strip copyright in those cases.
Just donated (paypal to jason at textfiles.com). I wonder if Patreon can be a good way to do fundraising for things like this.
Awesome! I've used
https://www.gnu.org/software/libmicrohttpd/ in the past (for fun stuff I was building to learn C), will try this out instead. But..
> Only HTTPS connections allowed
Seems a bit painful. HTTPS on the webserver itself is a fair bit more painful to setup and administer than HTTPS in your reverse proxy / loadbalancer (I prefer nginx). Web servers should support plain HTTP.
Can't the services just listen on different ports?