I'm going with authorized keys in house and shell (scp/rSync) and Web API's for apps used by volunteers outside. You are right there… it's probably a more secure method… I only have a handful of people who have the FTP passwords to the server(s) and that's probably as it should remain.
It would be just so much easier to have a UI that allows for the user to enter a user name and password. On 5/12/16, 12:00 PM, "use-livecode on behalf of Richard Gaskin" <use-livecode-boun...@lists.runrev.com on behalf of ambassa...@fourthworld.com> wrote: >There are no doubt edge cases beyond these, but these three cover about >90% of upload use cases, and all the use cases you've described thus far >for your organization. > >If you have a need that falls outside of these common solutions, let's >look at it. Perhaps there's a way to resolve even highly-specialized >needs at minimal cost. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
