New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
more remote destinations choices #1308
Comments
From a technical point of view, it's impossible to use FTP in a Web Extension. It seems Dropbox could be supported, see https://www.dropbox.com/developers/documentation/http/documentation. I need to do some tests to check if it's supported in a Web Extension. FYI, you could maybe use SingleFile Companion Lite to save pages in a synchronized folder on your disk as a workaround. See https://github.com/gildas-lormeau/single-file-companion-lite. |
I added the support of Dropbox as a new destination. The feature will be available in the next version. |
@paponius Out of curiosity, did you try the new destination for Dropbox? |
Applying for production status If you don't request the production status from the Dropbox, the app will have a limit of 500 users. You can now request for additional "test users" to solve the limit immediately but temporarily. Enable additional users on the link above. For the Google Drive,It works for me now, but Also, a custom-named directory would be nice, now it's saving to the root dir of GDrive. Anyway, I don't use GDrive for this, as it will not show you the html as an html, but as a plain text source. |
Thank you for the feedback, I've requested the production status to Dropbox. You can add a path into the filename template, e.g. The companion could indeed implement a FTP client. |
I would like the option to have a separate download directory, rather than the browser default download directory. |
I noticed https://github.com/gildas-lormeau/single-file-companion-lite, i will try that |
That's a browser limitation. WebExtension does not have an access to the OS filesystem. If you have full access to the server where you want SingleFile to put saved files to, explore also the WebDAV option. QNAP: |
Would Samba be easily supported? Similar to how WebDAV is already supported. Not sure if it would also be impossible like FTP. |
FTP is not "impossible" per se. Samba with JS is even less debated and explored. There are Node.JS libraries for both Samba and FTP, but nothing to be readily used in browser's JS. I would say, even if it may be theoretically possible, it would be a big project by itself. And not something I would expect to be developed just for the purpose of adding such function to SingleFile plugin. The companion app could add Samba, but I am not sure how big demand would be for such feature and how big a priority it would be. An option to run a command after a page is saved. With possibility to use placeholders like in output file name. |
@paponius Thanks for the reply. That is fine, adding Samba isn't essential especially since we already have WebDAV which likely can accomplish a similar purpose most of the time. More variety is nice but not needed in this particular case. If it becomes as simple as WebDAV was to add in the future, maybe then it can be reconsidered. |
@gildas-lormeau , great product you made. I would like to POST the captured content and its originating URL to an API endpoint. The authentication for sending to the endpoint would be an Authorization Bearer token. If I were to code this up and provide a PR would you except it into SingleFile? Thank you |
@yooper I guess the implementation would be very similar to the one used for github, see https://github.com/gildas-lormeau/SingleFile/blob/e57af7306a2002ffea21e8036269bc543d3b94ec/src/lib/github/github.js. What name would be given to this kind of API in SingleFile? Is it standardized or very easy to describe in a specification document? |
Hello @gildas-lormeau , The name for the destination would be
Configuration values that are hard-set
|
Thank you for the info. Could you give me more details about 4 and 5? What are field names? |
Sure. The Content-Type header in an HTTP POST/PUT request indicates the type of data in the request body. HTTP status codes are three-digit numbers that a server sends to a browser's request to indicate if a request can be fulfilled. This is useful for displaying an error if the REST API endpoint is not working. Hope that helps. |
Thank you but I would like to know what "File Field Name" (4) and "Url Field Name" (5) are for. |
Sorry about that.. To provide versality so that the field names can get mapped to the whatever the field names are in the end point. For example, I have an API endpoint that expects the name of the file attribute as Thank you, |
Thank you, so they woule the field names of the form. Your proposal serms OK to me. Maybe the word "form" should be in the name, e.g. 'REST Form API Endpoint' |
Hey @gildas-lormeau , I submitted a PR for pushing saves to a REST API endpoint. Please let me know if you have any questions. Really looking forward to having that feature enabled in SingleFile. |
Is your feature request related to a problem? Please describe.
sort of. google drive feature not working, box.net dropping DAV support
Describe the solution you'd like
Another protocol/cloud. like FTP/dropbox.
I do save a web page, attach the file to email, use plugin in Thunderbird to convert the attachment to dropbox and send.
I expect clickable link to show the page on the other end.
I wanted to simplify this process.
maybe even an option to save to cloud and open email to send the link. (mailto protocol)
I usually use dropbox for this, but I guess gdrive is fine too, if it worked.
cheers
The text was updated successfully, but these errors were encountered: