Actually, wether you run the browser and server on the same computer or the browser on one computer and the server on another makes no difference. Communication between client and server is handled in the exact same way.
Uploaded files land in the directory specified by upload_tmp_dir in php.ini. Usually, you can expect this directory to be emptied every now and again since stuff is not supposed to be stored there permanently. Hence, you will need to move the file from this place to a place of your choice. It's your server, so that's not a problem. Moreover, unless you keep one folder per user, or randomly create folders on the fly, you won't need to store the path in the db anyway. That can be done in the php script if you always use the same folder.
But, before we get to that part, there are other things to deal with. Your form needs the enctype attribute with something like
<form enctype="multipart/form-data" ...>
Then, you don't use $POST for file uploads, but $FILES
// see if there is a file and make sure no error occured
if (isset($_FILES['path']) && $_FILES['path']['error'] == 0) {
// possibly you want to check if the upload actually was an image and otherwise reject it
// do this here
/* the tmp_name element holds the filename used by the server
make sure the file has actually been uploaded and also move it.
This example uses the original filename (used on the client's side), but there is
a risk of this filename allready being in use on the server side.
If overwriting of existing files is not acceptable, additional checking is needed */
move_uploaded_file($_FILES['path']['tmp_name'],
'/some/place/of/your/choice/'.$_FILES['path']['name']);
// Now you can choose to insert the whole path and file, which is:
'/some/place/of/your/choice/'.$_FILES['path']['name']
}