SFTP Drive in Windows Explorer

An SFTP drive in Windows Explorer is a remote server directory mounted as a drive letter. Theme edits, script archive upload, and copying files/ backups can be done without a separate FTP client. MicroDrive mounts SSH/SFTP so copying feels like normal drag and drop.

For broker and quotes integrators, this is a fast path to upload white-label assets, replace a logo, deploy Charting Library chunks, or download logs. Remember that it still works over the network: large copies and antivirus scans on the drive letter can be slower than one scp or rsync.

Why use it during script launch

• Upload the archive into document root.
• Replace config, logos, and brand favicon.
• Copy files/ and templates before an update.
• Upload static TradingView Library.
• Download nginx or PHP logs during a feed incident.

After mounting, test write access in document root and directory reading. If writing works but the web still serves old files, check cache or opcache rather than assuming the drive lied.

Security practice

Mount with a limited user key, not root, if the user has enough rights for the target paths. Do not keep the drive connected 24/7 on a shared PC with stored password in an open config. Disconnect it after sessions on someone else's machine.

1. Create a separate Linux deploy user with access to /var/www/....
2. Connect MicroDrive and create a test file.
3. Open the file over HTTP and delete the test.
4. Check permissions: the web server must read, but does not need write access everywhere.

Connection to trading products

Typical paths are cabinet templates, terminal assets, and symbol config near the feed. Products: white label, BO, Forex, quotes, TradingView. Do not edit live config without a copy; one extra character in JSON can break the chart.

For SQL, use a database editor or console. MicroDrive is for files. Small code edits in a browser: MicroEditor. Server power: MicroPanel.

Copy performance

Thousands of small PHP template files over SFTP are slower than one archive. Practical path: upload tar.gz or zip through the drive or scp, then unpack over SSH or panel console. For backups, pack first and copy the archive back.

Windows antivirus scans the drive letter on the fly. Do not disable protection entirely, but exclusions for the working deploy folder may save hours.

Typical failures

SSH disconnect makes the drive drop and leaves an incomplete copy. NAT timeouts, wrong user shell, or server key-exchange policy can block connection. Keep a backup channel: MicroPanel console.

Do not mount production document root on a laptop with OneDrive or desktop cleanup sync. Two-way "cleanup" can erase files.

Acceptance

Read and write a test file, deploy an archive, check the site, disconnect the drive, and reconnect by key. Record document root and deploy user in the runbook.

An SFTP drive speeds routine deployment if you remember permissions, archives instead of countless small files, and a separate deploy account. Make a copy before updates and rollback stops being a quest.

White-label script update scenario

Pause ads or enable a maintenance banner. Archive files/, templates, and config locally. Upload the new version as an archive. Unpack over SSH. Run migrations. Check cabinet, terminal, and one demo deal. Only then remove the banner. MicroDrive is a delivery channel, not a place to manually edit a thousand files one by one.

Do not copy secret configs to a personal Desktop without encryption. Delete local payment-key copies after work.

Collaboration

Two people working in the same document root over SFTP without Git will overwrite each other. Agree on work windows or move to Git plus deploy. For micro-edits, MicroEditor also needs one operator per file at a time.

File names with non-Latin characters and spaces can be troublesome over SFTP; brand assets should use Latin names.

Quotes and chart files

TradingView Library chunks are convenient to upload once through the drive. After deployment, check MIME type and browser or CDN cache. Symbol dictionaries are better changed through admin or controlled deploy, not live edits from a marketer's PC drive letter.

Access and error logs can be downloaded through the drive, but large live tails are better read with tail in MicroPanel console.

Checksums and integrity

After uploading an archive, compare checksum. A damaged zip over unstable Wi-Fi is a common cause of a white screen after update. Keep checksums in the release changelog. Store critical config copies outside document root.

Do not mount several servers as drive letters without clear labels; you will upload to the wrong stand. Name shortcuts by environment such as broker-prod and quotes-stage.

Deploy policy

Define work window, responsible person, rollback point, and who checks the demo deal after deployment. The drive is a tool; the procedure protects production. For trading scripts, post-deploy check always includes feed and one deal, not only the landing page.

File-deploy operating rhythm

Every deployment gets a record: what was uploaded, checksum, and who checked the demo deal. Keep the last N release archives. Review deploy-user access. If someone uploaded through personal admin SSH, close the debt with a separate key.

Train a new person on staging once per quarter. A single person who knows the deployment ritual is a risk.

MicroDrive is for people, not CI/CD. Automated deploy keys and humans-through-drive can fight over file ownership if used in parallel. Choose the deployment owner for the release window.

When several projects live on one machine, mount different roots with clearly named letters and shortcuts. Before copying, read the path in the address bar, not only the icon.

If Explorer hangs on the drive, disconnect it through the utility rather than cutting VPN. After a broken copy, compare archive size with the source.