(DouglasMeyer) Hello. I'm quite intrigued with the Dat concept, but I've only seen it working in the beaker browser. Does it work in other modern browsers? I've tried `dat-js` and `dat` (through webpack), but I think they ran into issues around signaling. Any examples I should try working off of?
(DouglasMeyer) Ok. I'll keep digging around. Thanks!
son0p has quit
justicefries joined the channel
justicefries has quit
ogd
we dont really support dat on the client side right now, just in node, which is why youre prob having a hard time finding a client side version :D
justicefries joined the channel
its a bit DIY. we spent a lot of time trying to make a nice webrtc transport but we shifted focus away from it because it was too hard to make fast enough for our use case
that being said, if you are willing to roll up your sleeves you can definitely get it to work
justicefries has quit
justicefries joined the channel
dat-gitter1
(DouglasMeyer) Great to know! I'm definitely excited around the tech stack associated with dat. Maybe I'll buckle down and try to sort it out when I get into some related projects. Thanks!
justicefries has quit
justicefries joined the channel
justicefries has quit
justicefries joined the channel
ZerataX has quit
ZerataX joined the channel
(fasiha) VPS writing to a Dat archive. I'd like to retire the VPS and "move" the Dat archive to a new computer, which will write to it, while preserving the archive's history. In this situation, is it safe to `tar` the original archive directory (including `.dat` and secret keys and all), move it to the new computer, and decommission the old VPS?
(fasiha) Sorry, I meant to say, “I have a VPS writing to a Dat archive…”
jimpick
I’ve done that and it worked ... you might want to use the -S flag on tar for sparse files
jimpick: is the idea to make the containerfile install mininet?
jimpick
no, it's the other way around
i run mininet, and it creates 'vms' ... and then i run systemd-nspawn in each vm
the vms aren't really normal vms ... they are sort of like a chroot, but instead of having a different root directory, they have different networking configuration
they all share the same root filesystem
it's weird, and fun, and lightweight
there's a special 'controller' vm it spins up that controls all the software defined switches
the tutorial is probably better at explaining it than me
larpanet has quit
mafintosh
ah ok
jimpick
i think it will be really fun trying to simulate different topologies
it has certain topologies built into it for free ... for fancy topologies, you can use python to define them
but i think we can write our tests without having to use python
mafintosh
nice
jimpick: is it too much to ask, to try and run mininet in an unbuntu container and then inside that container run the topology? :D
justicefries has quit
justicefries joined the channel
jimpick
with `mnexec`, i can run commands inside a vm from outside. it might get a bit hairy though since i'm going to run systemd-nspawn inside each one, so the tape tests will want to go one level deeper inside the nested vm to spawn stuff
we can do more lightweight testing by not using systemd-nspawn and just install the things we want to test in the root image ... but i think it would be nice to use mkcontainer and model actual machines