Odd site deployment behavior

[Watts Martin]

So, I want to do a sanity check here -- is anyone using the "Deploy Site" command successfully?

I've been trying to replicate a simple workflow using this command that I normally do with a shell script (or lately with another editor that has site publishing functionality): in the project folder, there's a "source/" folder and a "build/" folder. Another program, CodeKit, handles the build process, so deploying is just a simple matter of syncing build/ with the remote server.

When I choose "Deploy Site" or "Re-Deploy Entire Site", what happens is: nothing. It instantly returns, and no files are uploaded to the server.

I think I've confirmed I have the correct site settings here: the local site root is the build folder, and I have server settings that work with "Open/Save to SFTP" commands.

So as a test, I started a new project file to make sure mine didn't have anything weird in it, and instead of deploying to the remote server, I checked "Deploy to folder" and set that folder to /Users/watts/Sites/ctracks. (Like the local site root, you select this folder with a dialog box, so there's no chance of mistyping the path in BBEdit's settings.)

And...the same thing happens.

When I do "Deploy Site" or "Re-Deploy Entire Site", that should just copy the build/ folder in my project directory to ~/Sites/ctracks, right? (And process includes and placeholders along the way, but I don't have any of those.)

I've also noticed that nothing happens when I have it set to "Check syntax" and "Stop if errors occur" for deployment, even if the "Check Syntax" command finds errors.

So: is there something else I should be looking at on my end? While this feels like a bug, I'd think it'd be a bug other people would have run into by now unless it's something unique to my system. But I can't figure out what that might be.

-- Watts

[Greg Raven]

Yeah, I use Deploy Site sporadically, trading off between it and Transmit, depending on my mood. I also use CodeKit, although not for building my site(s) … I use it for the preview function and for checking / processing JavaScript and SCSS. The only "issue" I have with Deploy Site is that I always think of something else I want to edit on the site while BBEdit is already busy doing the upload. With Transmit I can edit pages while the upload is occurring, which is a terrible idea and a bad habit, but sometimes I can't help myself.

[Rich Siegel]

On 17 Jun 2021, at 20:15, Watts Martin wrote:

> When I choose "Deploy Site" or "Re-Deploy Entire Site", what happens
> is:
> nothing. It instantly returns, and no files are uploaded to the
> server.

Deploy Site will only process and upload files that are HTML (or
HTML-like such as files that map to "PHP in HTML" and some others) *or*
which can have HTML generated for them, such as Markdown; and of course
images. Anything else is skipped.

There are a lot of moving parts, so your best bet is probably to write
to support and include a Zip of the project and assets as well as a
"defaults export" of your BBEdit preferences.

R.

--
Rich Siegel Bare Bones Software, Inc.
<sie...@barebones.com> <https://www.barebones.com/>

Someday I'll look back on all this and laugh... until they sedate me.

[@lbutlr]

On 17 Jun 2021, at 18:15, Watts Martin <lay...@gmail.com> wrote:
> So, I want to do a sanity check here -- is anyone using the "Deploy Site" command successfully?

I have used it in the past without issue, but since my web server is accessed only via ssh with keys and no passwords, I was unable to get the BBEdit site settings to do what I needed and so I use rsync from the command line instead, via an alias for each sites. Something like this:

alias wacme="rsync -haP /path/to/local/wacme www.example.com:/path/to/live/wacem --stats"
alias wapex="rsync -haP /path/to/local/wapex www.example.com:/path/to/live/wapex --stats"
&c

It is not quite as clean as BBEdit's deploy was, but as long as I remember to check the syntax and links myself, it's basically fine.

I COULD mount the remote server and then deploy to folder, but this worked for me.

Despote 20+ years on BBEdit, I am not really a power user and my first move when I encounter friction is usually a terminal session and a bash script. I've done many very silly things in bash scripts.

--
We are born naked, wet and hungry; then it's all downhill.