51–59 of 59 posts
Earlier quoted context omitted.
Does it need to be relational? Perhaps boltdb could do it https://github.com/boltdb/bolt
I’ve been looking for something precisely like Bolt, thank you for the link!
Earlier quoted context omitted.
If you just want to share files and not giving the option to upload files, you could try graft... https://github.com/sandreas/graft graft serve ./*.txt will serve every txt file in the current dir...
If you don't mind, I have a question about graft. > graft will prompt for a password, run an sftp server and promote it via zeroconf. Is that a one time password that will be used by the "receiver" to download the file?
I wrote graft to have a simple portable tool for transfering files in a network without shares - the main idea behind it was to run:
graft serve myfiles/*.txt
on the server side and then
graft receive
on the client side without having to remember the ip or hostname - because zeroconf / mdns is used, it will find the server automatically, if the network is not too big. If there is more than one server, it will prompt you to choose the right one.
I only used SFTP, because it is a secure way to transfer files over the network.
Earlier quoted context omitted.
If you just want to share files and not giving the option to upload files, you could try graft... https://github.com/sandreas/graft graft serve ./*.txt will serve every txt file in the current dir...
For that use case, I just use `python3 -m http.server` (or the Python 2 equivalent), especially since Python is almost always already installed.
I've been avoiding starting a project myself which will require SFTP. Passing text files around via SFTP is how a lot of the world works. It's still painful to implement this, and makes the transfer of data slow (polling for new files to process etc). This introduces a big delay in any data feedback cycles. Managing users with system accounts is painful too. This project looks to alleviate a lot of these problems. It…
For me, in a previous system I uploaded as a .tmp file, then the uploaded renames to .zip at the end of the upload. The rename is atomic so no chance of the consumer reading a partial file.
I was dealing in CSV, TSV and XML files. I chose to upload them all in a zip wrapper not only because they compress well, but also because each file has a CRC and the file won’t be extracted if the file is damaged or truncated. It’s hard to tell if a raw CSV file has been truncated.
Using JSON for configuration: Fail
Earlier quoted context omitted.
If you were planing on using this on a PaaS host where the file system is ephemeral this would be a non-starter.
What would the RL use case be for running this server, whose purpose is to facilitate transferring files from one computer's filesystem to another, on an ephemeral filesystem?
Earlier quoted context omitted.
What would your preferred config file formats be, and why?
Any format which enables inline comments, so INI, YAML
The configuration format it's a your choice
I've been avoiding starting a project myself which will require SFTP. Passing text files around via SFTP is how a lot of the world works. It's still painful to implement this, and makes the transfer of data slow (polling for new files to process etc). This introduces a big delay in any data feedback cycles. Managing users with system accounts is painful too. This project looks to alleviate a lot of these problems. It…