python






but how would i write the file to an ftp server, rather than local?
would i just replace to /home/sp00f with .... ftp/ etc?

Different ways of doing it. You could use an scp library, you could call a command line scp function, or if possible you could mount the ftp file system locally using nfs and treat it as any other directory.

what method do yall use?

the last way "mount ftp to file system locally" sounds the easiest. id like to learn that next

None of the above. Using FTP inherently insecure especially since you have to store you credentials in your script. This allows anyone to grab the username and password and vandalize your FTP.

A much better result is using a REST API with valid authentication so that you simply POST your data to your server. This also allows the use of SQL databases for further ease of storage and use.

okay thank you, ill look up how how all of that works ^\_^

You could mount the remote ftp to local dir and treat it as local in your script. eg. curlftpfs

You should use sftp too. Then you can still mount it like that, or use sshfs, or using ssh key authentication you wouldn't have to save login/password in your script

If the end user has the auth key you didn't protect anything. Might as well give them the username and password.

If this project is for anything other than personal use all these suggestions in this thread are useless.

ty men,

personal use.. i've been grabbing a little bit to learn at a time.

i understanding writing local or usb/media

so now im trying to grasp the next building block before doing it A) online, or B\) securely

This post was edited by spoofdaboss on Jan 24 2017 09:58am

Its not an or but an and. If you want to do anything online or remotely you want to design it securely from the start.

I would look into flask since you are using python and how to use its rest api. This may be a good start: http://blog.luisrei.com/articles/flaskrest.html

The ideal situation is to assign an authenticated token to your client and then let the client use a post/get api to fetch the data.

This way only clients with an authenticated token can use the api and if a token is leaked you can revoke it. This also separates the user from the storage mechanism so they can't vandalize any data except their own (depending on design).

This also allows for use of a SQL database like mysql or sqlite where you can store data and fetch it in a logical way.

Say you only want to fetch a users shoe:



Or you want to sort all users by first name:



Makes manipulating data much easier.

Wonderful, thank you. I will probably end up reading this a few times.