SFTP Setup

To view your changes while working on a site, you will need to use SFTP to upload your changes to either a development sandbox, or the static site directories for webteam or feature articles.

Static file directories are live on our production environment. Edit these very carefully. You may not have access to static file directories: access to individual directories usually has to be granted on an as-needed basis.

If you are working remotely: You will need to connect to the BU VPN to SFTP to our servers.

Sandboxes

For work on Framework, custom themes, plugins, and other WordPress-specific work.

  • Protocol: SFTP
  • Server: ist-wp-app-dv01.bu.edu
  • Path: /var/www/sandboxes/{sandbox-name}/current/
  • Username and Password: [usually the same as your] BU Kerberos

Static File Directories

For work on static HTML sites and uploading presentation files for client work.

  • Protocol: SFTP
  • Server: webdev.bu.edu
  • Path: /web/w/e/webteam/projects/
    • The path is always the first two letters of the site you want to edit, then the name of the site.
  • Username and Password: [usually the same as your] BU Kerberos

Trouble uploading a file, or permission denied?

This is usually caused by one of two things:

For Sandboxes

Someone uploaded files with a different set of permissions than you have. 

Shoot a developer this link for assistance: Fix File Permissions Issues

For Static File Directories

You need access to the folder in AFS.

Ask the Director of Interactive Development to grant you access to the folder you need and sharing this: http://www.bu.edu/help/web/site-access/

For SSH Key Issues

SSH Keys with GitHub

Code Editors

Selecting the right local code editor or IDE is key to efficient development. This section highlights tools that streamline coding, debugging, and project management, helping you choose the environment that best suits your workflow.

Set up for VS Code
Set up for Zed
Set up for Coda
Set up for Atom
Set up for Sublime Text

Global .gitignore for Editor-specific Files

Do you get tired of adding your editor-specific config files to the .gitignore file in each and every repo you work on? Like the .vscode folder or other editor plugin configs?

 

Instead of doing that in each repo, you can set up a global .gitignore file in your Home Directory for macOS. Anything specific to your configuration, editor, workflow, tools, etc., can and should be added there. This keeps the .gitignore files in our repos clean and free from personal editor, plugin, or config clutter.

 

Even though most folks use VSCode, it’s best to add those entries — and things like .DS_Store — to your global .gitignore instead of each repo.

 

Find Out How