Retrying an SFTP upload can send teh same order twice. Give each delivery a stable ID and make the importer reject duplicates. "Try again" needs rules.
A file can exist before its upload finishes. Agree on a hand-off: temporary filename, then rename when complete. Make the importer ignore temporary files, and verify rename behavior on your storage backend.
Your supplier wants SFTP and you need somewhere to test. Sync Motion has a free 5 GB plan, with no credit card required. Bring your client and a sample file.
https://t.co/f1WI6RzmS4
"Upload successful" means the transfer completed. The ERP might still reject every row. Ask the receiving application for an acknowledgement. Preferably before accounting asks you.
Your SFTP server can be online while yesterday's file is still missing. Alert when an expected delivery misses its deadline. A green uptime graph won't tell you that.
SFTP works in your terminal but fails in cron? Check the job's user, paths, environment and access to the SSH key. Your terminal has conveniences cron may never have met.
Before building an SFTP integration, ask for the host, port, username, authentication method, host-key fingerprint and target path. "We'll send you the login" tends to leave a few gaps.
One SFTP login for every supplier makes offboarding unnecessarily exciting. Give each supplier its own account and folder permissions. Revoke access without breaking everyone else's integration.
Your SSH key identifies you to the server. The server's host key identifies it to you. Verify its fingerprint through a trusted channel before accepting it.
Yesterday someone from HackerOne paid us a visit.
Apparently testing if they can break our tenant isolation through Faraday.
Next level unlocked I guess.
Haven’t heard anything from them yet.
Logs are clean.
So maybe we succeeded.