28 ms·
We're open sourcing parts of our code as soon as we consider it modular and well documented enough. We started with our build system but the plan is to open sou
by cadeuh 10y ago
We're open sourcing parts of our code as soon as we consider it modular and well documented enough. We started with our build system but the plan is to open source everything over the coming weeks!
And yes, that's exactly why it was made for. Have a look at our examples of deployments: https://infinit.sh/documentation/deployments https://infinit.sh/documentation/deployments
- mtrn 10y agoExcellent, thanks!
- virtualritz 10y agoThat sounds like I will be able to deploy infinit.sh on my NAS (QNAP 469), running some ARM Linux flavor?
- ccrone 10y agoWe don't build the FS for ARM just yet but since we use a lot of the same code we did for our file transfer application that runs on Android and iOS, it shouldn't be too difficult to do. Feel free to add and upvote what you'd like to see: http://infinit-sh.uservoice.com http://infinit-sh.uservoice.com
- urza 10y agoHi, that is great. I've never heard of you before, so I am still trying to wrap my head around it, could you please help me understand it, I have some questions. If I have two servers, each with ZFS filesystem, could I use infinit.sh to connect them, create shared "disk" and expose it to clients on Mac/Win/Mobile so they can access the files? Will the ZFS advantages be maintained? E.g. if I set the Z2 raid on one server and mirror on another? Could I do snapshots on the server and later browse them? Will the ZFS data integrity prevent data corruption? Thanks.