ftp_paradise 1.4.5 → 1.5.3
Sign up to get free protection for your applications and to get access to all the features.
Potentially problematic release.
This version of ftp_paradise might be problematic. Click here for more details.
- checksums.yaml +4 -4
- data/README.md +152 -28
- data/bin/{iftp → ftp_paradise_shell} +1 -1
- data/doc/README.gen +97 -15
- data/doc/todo/{TODO_FOR_FTP_PARADISE_PROJECT.md → todo_for_the_ftp_paradise_project.md} +0 -0
- data/ftp_paradise.gemspec +30 -39
- data/lib/ftp_paradise/base/base.rb +375 -0
- data/lib/ftp_paradise/colours/colours.rb +27 -27
- data/lib/ftp_paradise/colours/use_colours.rb +6 -1
- data/lib/ftp_paradise/configuration/configuration.rb +7 -4
- data/lib/ftp_paradise/connection/README.md +0 -0
- data/lib/ftp_paradise/connection/connection.rb +2782 -15
- data/lib/ftp_paradise/constants/constants.rb +91 -5
- data/lib/ftp_paradise/entry/entry.rb +42 -5
- data/lib/ftp_paradise/{connection → gui/gtk3/ftp_client}/constants.rb +33 -21
- data/lib/ftp_paradise/gui/{shared_code/ftp_paradise/ftp_paradise_module.rb → gtk3/ftp_client/ftp_client.rb} +658 -170
- data/lib/ftp_paradise/gui/gtk3/ftp_client/misc.rb +27 -0
- data/lib/ftp_paradise/project/project.rb +11 -15
- data/lib/ftp_paradise/requires/require_class_connection.rb +7 -0
- data/lib/ftp_paradise/requires/require_net_ftp.rb +7 -0
- data/lib/ftp_paradise/requires/require_the_ftp_paradise_project.rb +4 -3
- data/lib/ftp_paradise/requires/require_the_ftp_paradise_project_with_the_GUI_bindings.rb +1 -1
- data/lib/ftp_paradise/requires/require_the_toplevel_methods.rb +1 -0
- data/lib/ftp_paradise/{interactive_ftp → shell}/menu.rb +554 -448
- data/lib/ftp_paradise/shell/shell.rb +2321 -0
- data/lib/ftp_paradise/toplevel_methods/connect.rb +3 -0
- data/lib/ftp_paradise/toplevel_methods/dataset.rb +111 -0
- data/lib/ftp_paradise/toplevel_methods/file_related_actions.rb +4 -3
- data/lib/ftp_paradise/toplevel_methods/ftp_object.rb +6 -5
- data/lib/ftp_paradise/toplevel_methods/login_name.rb +6 -4
- data/lib/ftp_paradise/toplevel_methods/misc.rb +19 -0
- data/lib/ftp_paradise/toplevel_methods/opn.rb +1 -1
- data/lib/ftp_paradise/toplevel_methods/password.rb +4 -2
- data/lib/ftp_paradise/toplevel_methods/port.rb +4 -1
- data/lib/ftp_paradise/toplevel_methods/remote_url.rb +11 -5
- data/lib/ftp_paradise/toplevel_methods/upload_and_download.rb +1 -0
- data/lib/ftp_paradise/version/version.rb +6 -1
- data/lib/ftp_paradise/www/web_interface.cgi +1 -1
- data/lib/ftp_paradise/yaml/automatically_connect_on_startup_of_the_interactive_ftp_shell.yml +0 -0
- data/lib/ftp_paradise/yaml/debug.yml +0 -0
- data/lib/ftp_paradise/yaml/open_in_default_editor.yml +0 -0
- data/lib/ftp_paradise/yaml/show_full_names.yml +0 -0
- data/lib/ftp_paradise/yaml/use_colours.yml +0 -0
- data/test/testing_minimal_pure_net_ftp_example_to_connect.rb +13 -3
- metadata +52 -126
- data/lib/ftp_paradise/base/cliner.rb +0 -23
- data/lib/ftp_paradise/base/colours.rb +0 -83
- data/lib/ftp_paradise/base/prototype.rb +0 -171
- data/lib/ftp_paradise/base/reset.rb +0 -29
- data/lib/ftp_paradise/connection/data.rb +0 -164
- data/lib/ftp_paradise/connection/debug.rb +0 -78
- data/lib/ftp_paradise/connection/directory_handling.rb +0 -271
- data/lib/ftp_paradise/connection/do_login.rb +0 -108
- data/lib/ftp_paradise/connection/download.rb +0 -86
- data/lib/ftp_paradise/connection/file_handling.rb +0 -174
- data/lib/ftp_paradise/connection/ftp_object.rb +0 -21
- data/lib/ftp_paradise/connection/initialize.rb +0 -88
- data/lib/ftp_paradise/connection/initialize_a_new_net_ftp_object_with_this_url.rb +0 -20
- data/lib/ftp_paradise/connection/is_connected.rb +0 -46
- data/lib/ftp_paradise/connection/misc.rb +0 -474
- data/lib/ftp_paradise/connection/notify.rb +0 -71
- data/lib/ftp_paradise/connection/password.rb +0 -47
- data/lib/ftp_paradise/connection/port.rb +0 -33
- data/lib/ftp_paradise/connection/remote_pwd.rb +0 -72
- data/lib/ftp_paradise/connection/remote_url.rb +0 -164
- data/lib/ftp_paradise/connection/remove.rb +0 -143
- data/lib/ftp_paradise/connection/reset.rb +0 -78
- data/lib/ftp_paradise/connection/run.rb +0 -18
- data/lib/ftp_paradise/connection/set_array_available_hosts.rb +0 -27
- data/lib/ftp_paradise/connection/set_input.rb +0 -18
- data/lib/ftp_paradise/connection/show.rb +0 -153
- data/lib/ftp_paradise/connection/sync_ftp_object_onto_the_main_namespace.rb +0 -24
- data/lib/ftp_paradise/connection/transfer_mode.rb +0 -163
- data/lib/ftp_paradise/connection/upload.rb +0 -253
- data/lib/ftp_paradise/connection/use_default_dataset.rb +0 -40
- data/lib/ftp_paradise/connection/username.rb +0 -42
- data/lib/ftp_paradise/constants/misc.rb +0 -57
- data/lib/ftp_paradise/constants/namespace.rb +0 -14
- data/lib/ftp_paradise/constants/newline.rb +0 -14
- data/lib/ftp_paradise/constants/roebe.rb +0 -31
- data/lib/ftp_paradise/constants/roebe_ftp_constants.rb +0 -233
- data/lib/ftp_paradise/gui/gtk2/ftp_paradise.rb +0 -34
- data/lib/ftp_paradise/gui/gtk3/ftp_paradise.rb +0 -34
- data/lib/ftp_paradise/interactive_ftp/constants.rb +0 -103
- data/lib/ftp_paradise/interactive_ftp/directory_handling.rb +0 -216
- data/lib/ftp_paradise/interactive_ftp/help.rb +0 -50
- data/lib/ftp_paradise/interactive_ftp/initialize.rb +0 -27
- data/lib/ftp_paradise/interactive_ftp/interactive_ftp.rb +0 -998
- data/lib/ftp_paradise/interactive_ftp/main_loop.rb +0 -51
- data/lib/ftp_paradise/interactive_ftp/misc.rb +0 -208
- data/lib/ftp_paradise/interactive_ftp/mode.rb +0 -124
- data/lib/ftp_paradise/interactive_ftp/readline.rb +0 -113
- data/lib/ftp_paradise/interactive_ftp/remove.rb +0 -97
- data/lib/ftp_paradise/interactive_ftp/reset.rb +0 -90
- data/lib/ftp_paradise/interactive_ftp/run.rb +0 -22
- data/lib/ftp_paradise/interactive_ftp/show.rb +0 -184
- data/lib/ftp_paradise/interactive_ftp/upload.rb +0 -90
- data/lib/ftp_paradise/interactive_ftp/user_input.rb +0 -53
- data/lib/ftp_paradise/toplevel_methods/can_connect_to_remote_site.rb +0 -28
- data/lib/ftp_paradise/toplevel_methods/clear_user_dataset.rb +0 -28
- data/lib/ftp_paradise/toplevel_methods/data.rb +0 -31
- data/lib/ftp_paradise/toplevel_methods/determine_user_dataset_from_this_hash.rb +0 -37
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: c26a08971e887fa0ecdb6ea40624c14fcdcee8e62fbdaf4dc3303fa4efe8e116
|
4
|
+
data.tar.gz: d103baf29e4453269e7cec1ce1da7e94c8f4d579fb7a594dcb87809892bc2733
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 02edbe9791818a5870735afdf78285ba89eefe3dd706d00c64fb2f0404fac731ece897d497bafc593bf437a380cf05c79fa4327f0abbd8c938eb7796561f748e
|
7
|
+
data.tar.gz: 46610d361fb597a295dfcef48d583cb045c9ab3be1135d2d33d23aa2a5b6182f45bb79ec1bcea1954808b4a89b13c5f595b1e26a5a1421452d8603a610de6203
|
data/README.md
CHANGED
@@ -1,5 +1,5 @@
|
|
1
|
-
[![forthebadge](
|
2
|
-
[![forthebadge](
|
1
|
+
[![forthebadge](https://forthebadge.com/images/badges/built-with-love.svg)](https://www.gobolinux.org/)
|
2
|
+
[![forthebadge](https://forthebadge.com/images/badges/made-with-ruby.svg)](https://www.ruby-lang.org/en/)
|
3
3
|
[![Gem Version](https://badge.fury.io/rb/ftp_paradise.svg)](https://badge.fury.io/rb/ftp_paradise)
|
4
4
|
|
5
5
|
## FtpParadise - Introduction
|
@@ -32,7 +32,7 @@ FTP. (Evidently you have to first connect to the remote
|
|
32
32
|
website via your FTP login credentials, so make sure to do
|
33
33
|
that first before inputting commands.)
|
34
34
|
|
35
|
-
## Requiring the FtpParadise library
|
35
|
+
## Requiring the FtpParadise library
|
36
36
|
|
37
37
|
Simply do the following in order to require this project:
|
38
38
|
|
@@ -53,17 +53,6 @@ This is mostly for convenience. Use in your code whatever you
|
|
53
53
|
prefer. Most may prefer foo=, I like to read a leading set_
|
54
54
|
though, visually.
|
55
55
|
|
56
|
-
## The interactive component of the FTP Paradise:
|
57
|
-
|
58
|
-
The **interactive** component will properly tell the user whether
|
59
|
-
he/she is connected to a remote host or whether the user is not
|
60
|
-
connected, since as of the version **1.0.35**.
|
61
|
-
|
62
|
-
If you need to determine manually whether you are connected, do
|
63
|
-
input this command in the interactive shell:
|
64
|
-
|
65
|
-
connected?
|
66
|
-
|
67
56
|
## Autoconnecting (Added as of December 2017)
|
68
57
|
|
69
58
|
This presently works only on my home system, by checking whether
|
@@ -291,29 +280,164 @@ toplevel method:
|
|
291
280
|
This will return nil if no connection has been made as of
|
292
281
|
yet.
|
293
282
|
|
283
|
+
## FtpParadise::Entry
|
284
|
+
|
285
|
+
This small class will represent a remote entry, that is,
|
286
|
+
the entries that you get via .list() from a FTP-object.
|
287
|
+
|
288
|
+
It contains useful methods such as .is_a_directory?
|
289
|
+
or .is_a_file?.
|
290
|
+
|
294
291
|
## The graphical user interface (ruby-gtk3)
|
295
292
|
|
296
|
-
There exists a small ruby-gtk3 client for the ftp_paradise
|
297
|
-
|
298
|
-
|
293
|
+
There exists a small ruby-gtk3 client for the ftp_paradise gem.
|
294
|
+
|
295
|
+
In <b>July 2022</b> the project was rewritten from scratch,
|
296
|
+
with the ruby-gtk3 client as the new primary focus for this
|
297
|
+
gem.
|
298
|
+
|
299
|
+
In order to use this client, you first have to install
|
300
|
+
the gtk3 gem, and then do:
|
301
|
+
|
302
|
+
gem install gtk_paradise
|
299
303
|
|
300
304
|
For selecting a local file, you currently have to
|
301
305
|
double-click. At some later point I will extend this
|
302
306
|
to one-click only.
|
303
307
|
|
308
|
+
A screenshot follows next, showcasing this GUI:
|
309
|
+
|
310
|
+
## The difference between .putbinaryfile() and .puttextfile()
|
311
|
+
|
312
|
+
.putbinaryfile() is used for a file transfer to the remote
|
313
|
+
server in binary mode.
|
314
|
+
|
315
|
+
.puttextfile() is used to transfer a local file
|
316
|
+
to the remote server in ASCII (aka text) mode.
|
317
|
+
|
318
|
+
So what is the difference?
|
319
|
+
|
320
|
+
Well, first we have to determine whether there is a
|
321
|
+
difference. Yes, there is - meaning you may end
|
322
|
+
up receiving corrupt files during FTP transfer
|
323
|
+
if the upload was handled incorrectly, aka
|
324
|
+
the wrong mode was used.
|
325
|
+
|
326
|
+
Ok, so we now know that we have to use the correct
|
327
|
+
mode if possible.
|
328
|
+
|
329
|
+
An example for a binary file is an image file
|
330
|
+
such as <b>foobar.jpg</b>. Note that TYPE I
|
331
|
+
means I for Image, which is the same thing
|
332
|
+
as binary, as far as the FTP protocol is concerned.
|
333
|
+
|
334
|
+
The TYPE A command, on the other hand, where A stands
|
335
|
+
for ASCII, is to be used if the transfer mode
|
336
|
+
should be in ASCII.
|
337
|
+
|
338
|
+
So which files should be transferred in binary
|
339
|
+
mode?
|
340
|
+
|
341
|
+
The following "table" gives a few examples here:
|
342
|
+
|
343
|
+
Image files: .jpg, .bmp, .png
|
344
|
+
Sound files: .mp3, .avi, .wma
|
345
|
+
Video files: .flv, .mkv, .mov, .mp4
|
346
|
+
Archive files: .zip, .rar, .tar
|
347
|
+
Other files: .exe, .doc, .xls, .pdf
|
348
|
+
|
349
|
+
Note that typically <b>binary</b> mode is the default.
|
350
|
+
|
351
|
+
So when to use the ASCII transfer mode?
|
352
|
+
|
353
|
+
Well - it is is recommended to use it only if you
|
354
|
+
want to transfer text files, such as a .md file or
|
355
|
+
a .txt file.
|
356
|
+
|
357
|
+
Text files that use UTF-8 character encoding should
|
358
|
+
not be transferred via ASCII mode. Examples for
|
359
|
+
these are Japanese or Chinese text files.
|
360
|
+
|
361
|
+
But why is it necessary to use the ASCII transfer mode?
|
362
|
+
|
363
|
+
This is due to the way end-of-lines (EOLs) are handled.
|
364
|
+
In FTP, EOLs in ASCII files (such as text files) are
|
365
|
+
denoted by carriage return+line feed (CRLF) pairs
|
366
|
+
(see RFC959).
|
367
|
+
|
368
|
+
## The FtpParadise::Shell - the interactive component of the FTP Paradise
|
369
|
+
|
370
|
+
The **interactive** component of the FtpParadise project will properly
|
371
|
+
tell the user whether he/she is connected to a remote host or whether
|
372
|
+
the user is not connected, since as of the version **1.0.35**.
|
373
|
+
|
374
|
+
You can start the interactive shell via:
|
375
|
+
|
376
|
+
bin/ftp_paradise_shell
|
377
|
+
ftp_paradise_shell # <- This works if you have that file added to your $PATH
|
378
|
+
|
379
|
+
If you need to determine manually whether you are connected,
|
380
|
+
do input this command in the <b>interactive shell</b>:
|
381
|
+
|
382
|
+
connected?
|
383
|
+
|
384
|
+
|
385
|
+
## Licence
|
386
|
+
|
387
|
+
The licence for this gem is the MIT licence.
|
388
|
+
|
389
|
+
Basically the most important part of the MIT licence is that, aside
|
390
|
+
from you being able to use the project as you see fit, is the no
|
391
|
+
warranty disclaimer to avoid any potential misuse from the use
|
392
|
+
of the software at hand.
|
393
|
+
|
394
|
+
You can read up on this licence here:
|
395
|
+
|
396
|
+
https://opensource.org/licenses/MIT
|
397
|
+
|
398
|
+
The usual copyright assignment is:
|
399
|
+
|
400
|
+
Copyright 2022 Robert Heiler
|
401
|
+
|
402
|
+
|
403
|
+
|
404
|
+
## Contact information and mandatory 2FA coming up in 2022
|
405
|
+
|
406
|
+
If your creative mind has ideas and specific suggestions to make this gem
|
407
|
+
more useful in general, feel free to drop me an email at any time, via:
|
408
|
+
|
409
|
+
shevy@inbox.lt
|
410
|
+
|
411
|
+
Before that email I used an email account at Google gmail, but in **2021** I
|
412
|
+
decided to slowly abandon gmail for various reasons. In order to limit this
|
413
|
+
explanation here, allow me to just briefly state that I do not feel as if I
|
414
|
+
want to promote any Google service anymore, for various reasons.
|
415
|
+
|
416
|
+
Do keep in mind that responding to emails may take some time, depending on
|
417
|
+
the amount of work I may have at that moment.
|
418
|
+
|
419
|
+
In 2022 rubygems.org decided to make 2FA mandatory for every gem owner:
|
420
|
+
see https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html
|
304
421
|
|
305
|
-
|
422
|
+
As I can not use 2FA, for reasons I will skip explaining here (see
|
423
|
+
various github issue discussions in the past), this effectively means that
|
424
|
+
Betty Li and others who run the show at rubygems.org will perma-ban me
|
425
|
+
from using rubygems as a developer.
|
306
426
|
|
307
|
-
|
308
|
-
|
309
|
-
|
427
|
+
As I disagree with that decision completely, this will mean that all my
|
428
|
+
gems will be removed from rubygems.org prior to that sunset date, e. g.
|
429
|
+
before they permanently lock me out from the code that I used
|
430
|
+
to maintain. It is pointless to want to discuss this with them anymore -
|
431
|
+
they have made up their minds and decided that you can only use
|
432
|
+
the code if 2FA is in place, even though the code itself works just
|
433
|
+
fine. If you don't use 2FA you are effectively locked out from your
|
434
|
+
own code; I consider this a malicious attack. See also how they limited
|
435
|
+
discussions to people with mandatory 2FA on the ruby-bugtracker, thus
|
436
|
+
banning everyone permanently without 2FA:
|
310
437
|
|
311
|
-
|
438
|
+
https://bugs.ruby-lang.org/issues/18800
|
312
439
|
|
313
|
-
|
314
|
-
|
315
|
-
|
316
|
-
of course, as long as they are in the spirit of the project at
|
317
|
-
hand, e. g. fitting to the general theme.)
|
440
|
+
Guess it may indeed be time to finally abandon ruby - not because
|
441
|
+
ruby is a bad language, but there are people now in charge who
|
442
|
+
really should not be part of ruby in the first place.
|
318
443
|
|
319
|
-
Thank you.
|
data/doc/README.gen
CHANGED
@@ -30,7 +30,7 @@ FTP. (Evidently you have to first connect to the remote
|
|
30
30
|
website via your FTP login credentials, so make sure to do
|
31
31
|
that first before inputting commands.)
|
32
32
|
|
33
|
-
## Requiring the FtpParadise library
|
33
|
+
## Requiring the FtpParadise library
|
34
34
|
|
35
35
|
Simply do the following in order to require this project:
|
36
36
|
|
@@ -51,17 +51,6 @@ This is mostly for convenience. Use in your code whatever you
|
|
51
51
|
prefer. Most may prefer foo=, I like to read a leading set_
|
52
52
|
though, visually.
|
53
53
|
|
54
|
-
## The interactive component of the FTP Paradise:
|
55
|
-
|
56
|
-
The **interactive** component will properly tell the user whether
|
57
|
-
he/she is connected to a remote host or whether the user is not
|
58
|
-
connected, since as of the version **1.0.35**.
|
59
|
-
|
60
|
-
If you need to determine manually whether you are connected, do
|
61
|
-
input this command in the interactive shell:
|
62
|
-
|
63
|
-
connected?
|
64
|
-
|
65
54
|
## Autoconnecting (Added as of December 2017)
|
66
55
|
|
67
56
|
This presently works only on my home system, by checking whether
|
@@ -289,14 +278,107 @@ toplevel method:
|
|
289
278
|
This will return nil if no connection has been made as of
|
290
279
|
yet.
|
291
280
|
|
281
|
+
## FtpParadise::Entry
|
282
|
+
|
283
|
+
This small class will represent a remote entry, that is,
|
284
|
+
the entries that you get via .list() from a FTP-object.
|
285
|
+
|
286
|
+
It contains useful methods such as .is_a_directory?
|
287
|
+
or .is_a_file?.
|
288
|
+
|
292
289
|
## The graphical user interface (ruby-gtk3)
|
293
290
|
|
294
|
-
There exists a small ruby-gtk3 client for the ftp_paradise
|
295
|
-
|
296
|
-
|
291
|
+
There exists a small ruby-gtk3 client for the ftp_paradise gem.
|
292
|
+
|
293
|
+
In <b>July 2022</b> the project was rewritten from scratch,
|
294
|
+
with the ruby-gtk3 client as the new primary focus for this
|
295
|
+
gem.
|
296
|
+
|
297
|
+
In order to use this client, you first have to install
|
298
|
+
the gtk3 gem, and then do:
|
299
|
+
|
300
|
+
gem install gtk_paradise
|
297
301
|
|
298
302
|
For selecting a local file, you currently have to
|
299
303
|
double-click. At some later point I will extend this
|
300
304
|
to one-click only.
|
301
305
|
|
306
|
+
A screenshot follows next, showcasing this GUI:
|
307
|
+
|
308
|
+
## The difference between .putbinaryfile() and .puttextfile()
|
309
|
+
|
310
|
+
.putbinaryfile() is used for a file transfer to the remote
|
311
|
+
server in binary mode.
|
312
|
+
|
313
|
+
.puttextfile() is used to transfer a local file
|
314
|
+
to the remote server in ASCII (aka text) mode.
|
315
|
+
|
316
|
+
So what is the difference?
|
317
|
+
|
318
|
+
Well, first we have to determine whether there is a
|
319
|
+
difference. Yes, there is - meaning you may end
|
320
|
+
up receiving corrupt files during FTP transfer
|
321
|
+
if the upload was handled incorrectly, aka
|
322
|
+
the wrong mode was used.
|
323
|
+
|
324
|
+
Ok, so we now know that we have to use the correct
|
325
|
+
mode if possible.
|
326
|
+
|
327
|
+
An example for a binary file is an image file
|
328
|
+
such as <b>foobar.jpg</b>. Note that TYPE I
|
329
|
+
means I for Image, which is the same thing
|
330
|
+
as binary, as far as the FTP protocol is concerned.
|
331
|
+
|
332
|
+
The TYPE A command, on the other hand, where A stands
|
333
|
+
for ASCII, is to be used if the transfer mode
|
334
|
+
should be in ASCII.
|
335
|
+
|
336
|
+
So which files should be transferred in binary
|
337
|
+
mode?
|
338
|
+
|
339
|
+
The following "table" gives a few examples here:
|
340
|
+
|
341
|
+
Image files: .jpg, .bmp, .png
|
342
|
+
Sound files: .mp3, .avi, .wma
|
343
|
+
Video files: .flv, .mkv, .mov, .mp4
|
344
|
+
Archive files: .zip, .rar, .tar
|
345
|
+
Other files: .exe, .doc, .xls, .pdf
|
346
|
+
|
347
|
+
Note that typically <b>binary</b> mode is the default.
|
348
|
+
|
349
|
+
So when to use the ASCII transfer mode?
|
350
|
+
|
351
|
+
Well - it is is recommended to use it only if you
|
352
|
+
want to transfer text files, such as a .md file or
|
353
|
+
a .txt file.
|
354
|
+
|
355
|
+
Text files that use UTF-8 character encoding should
|
356
|
+
not be transferred via ASCII mode. Examples for
|
357
|
+
these are Japanese or Chinese text files.
|
358
|
+
|
359
|
+
But why is it necessary to use the ASCII transfer mode?
|
360
|
+
|
361
|
+
This is due to the way end-of-lines (EOLs) are handled.
|
362
|
+
In FTP, EOLs in ASCII files (such as text files) are
|
363
|
+
denoted by carriage return+line feed (CRLF) pairs
|
364
|
+
(see RFC959).
|
365
|
+
|
366
|
+
## The FtpParadise::Shell - the interactive component of the FTP Paradise
|
367
|
+
|
368
|
+
The **interactive** component of the FtpParadise project will properly
|
369
|
+
tell the user whether he/she is connected to a remote host or whether
|
370
|
+
the user is not connected, since as of the version **1.0.35**.
|
371
|
+
|
372
|
+
You can start the interactive shell via:
|
373
|
+
|
374
|
+
bin/ftp_paradise_shell
|
375
|
+
ftp_paradise_shell # <- This works if you have that file added to your $PATH
|
376
|
+
|
377
|
+
If you need to determine manually whether you are connected,
|
378
|
+
do input this command in the <b>interactive shell</b>:
|
379
|
+
|
380
|
+
connected?
|
381
|
+
|
382
|
+
LICENCE_IS_MIT
|
383
|
+
|
302
384
|
ADD_CONTACT_DETAILS
|
File without changes
|
data/ftp_paradise.gemspec
CHANGED
@@ -2,6 +2,7 @@
|
|
2
2
|
# Gemspec for Project FtpParadise.
|
3
3
|
# =========================================================================== #
|
4
4
|
require 'ftp_paradise/version/version.rb'
|
5
|
+
require 'roebe'
|
5
6
|
|
6
7
|
Gem::Specification.new { |s|
|
7
8
|
|
@@ -42,67 +43,57 @@ EOF
|
|
42
43
|
# =============================================================== #
|
43
44
|
s.post_install_message = <<-EOF
|
44
45
|
|
45
|
-
|
46
|
-
|
46
|
+
The interactive file, which can be started by typing "iftp",
|
47
|
+
requires a library called configuration. This is part of the
|
48
|
+
gem called "Roebe", so you may have to install this gem
|
49
|
+
first:
|
47
50
|
|
48
|
-
|
49
|
-
be downloaded here:
|
51
|
+
gem install roebe
|
50
52
|
|
51
|
-
|
53
|
+
If you wish to start the interactive FTP, the file can be
|
54
|
+
found at:
|
52
55
|
|
53
|
-
|
54
|
-
other gem called "configuration". (You can extract the gem and
|
55
|
-
look at it before you install it of course. Its sole purpose
|
56
|
-
is to read in a bunch of .yml yaml files to provide a proper
|
57
|
-
base configuration for a project.)
|
56
|
+
bin/iftp
|
58
57
|
|
59
|
-
|
60
|
-
found at:
|
58
|
+
And should on most Linux systems end up on:
|
61
59
|
|
62
|
-
|
60
|
+
/usr/bin/iftp
|
63
61
|
|
64
|
-
|
62
|
+
if the --prefix is at /usr (obviously, if you install into
|
63
|
+
your home directory, then it will be at another location;
|
64
|
+
rubygems should take care of this).
|
65
65
|
|
66
|
-
|
66
|
+
So just typing "iftp" should suffice to start the interactive FTP
|
67
|
+
component, but keep in mind that you need to download the
|
68
|
+
configuration gem listed above first.
|
67
69
|
|
68
|
-
|
69
|
-
|
70
|
-
rubygems should take care of this).
|
70
|
+
You can disable the colour-section of the interactive FTP
|
71
|
+
by issuing:
|
71
72
|
|
72
|
-
|
73
|
-
component, but keep in mind that you need to download the
|
74
|
-
configuration gem listed above first.
|
73
|
+
iftp --disable-colours
|
75
74
|
|
76
|
-
|
77
|
-
|
75
|
+
You can also batch-upload some scripts through the command
|
76
|
+
called:
|
78
77
|
|
79
|
-
|
78
|
+
ftp_upload
|
80
79
|
|
81
|
-
|
82
|
-
|
80
|
+
ftp_upload --help should give you some information on how
|
81
|
+
to use it.
|
83
82
|
|
84
|
-
|
85
|
-
|
86
|
-
ftp_upload --help should give you some information on how
|
87
|
-
to use it.
|
88
|
-
|
89
|
-
Consider installing the "roebe" gem for making "Configuration"
|
90
|
-
available.
|
91
|
-
|
92
|
-
Thank you and have fun!
|
83
|
+
Thank you and have fun.
|
93
84
|
|
94
85
|
EOF
|
95
86
|
|
96
87
|
s.authors = ['Robert A. Heiler']
|
97
|
-
s.email =
|
98
|
-
s.license = '
|
88
|
+
s.email = Roebe.email?
|
89
|
+
s.license = 'MIT'
|
99
90
|
s.files = Dir['**/*']
|
100
91
|
s.files << ['README.md']
|
101
92
|
s.files = s.files.flatten
|
102
93
|
s.executables = Dir['bin/*'].map { |entry| File.basename(entry) }
|
103
94
|
s.require_paths = ["lib"]
|
104
95
|
|
105
|
-
s.homepage = '
|
96
|
+
s.homepage = 'https://rubygems.org/gems/ftp_paradise'
|
106
97
|
|
107
98
|
s.required_ruby_version = '>= '+RUBY_VERSION
|
108
99
|
s.required_rubygems_version = '>= '+Gem::VERSION
|
@@ -117,6 +108,6 @@ EOF
|
|
117
108
|
s.add_dependency 'rcfiles'
|
118
109
|
s.add_dependency 'opn'
|
119
110
|
s.add_dependency 'verbose_truth'
|
120
|
-
s.add_dependency 'gtk_paradise'
|
111
|
+
# s.add_dependency 'gtk_paradise'
|
121
112
|
|
122
113
|
}
|