Problem with cache busting - asset_path not printing asset versions

[Zachary_Brewer]

Hey all,
Long time Roots user, I have deployed several Sage 9 sites successfully.
Having an annoying time this morning trying to stage a site in progress.
Vagrant is working fine.

Server is DO droplet, 16.04.
On provision, Ansible complained that I needed to:

`sudo pip install passlib`

which I did, no problem. I figure this was because I recently upgraded Ansible.

Then Provision worked without error.
Deploy worked, also without error. I imported the DB, copied plugins and uploads.
The admin is fine, and the front of the site loads the content, but is missing styles and scripts. I get 404s for the scripts and styles because I am now missing the hashes. Is this an issue with passlib, or have I not configured the asset hashing correctly?
Maybe my brain is just not working correctly.

Apologies in advance if I’ve left out some crucial info for an assist.
What was I even doing before I found the Roots stack?
Zach

[strarsis]

You have to transfer the built artifacts of your sage theme, too, you can use a hook for this:

(r)sync of theme dist

Is syncing the theme dist folder on deploy enabled by default? It seemed to work but suddenly it stopped working and there is no dist/ folder at all copied when running the deploy script/playbook. There is a rsync command mentioned in ‘deploy-hooks/build-before.yml’ but it is commented out. - Is this intended for being used when building the theme during deploy? When running deploy, there are no errors but dist is also not synced.

[Zachary_Brewer]

Hmm, I have the build-before.yml file un-commented and my theme folder replacing ‘sage’.
So, not sure that’s the issue. Is that what you meant?
Thank you
zach

[strarsis]

Yes.

Are the theme files versioned? Are the theme files really on the target server?

[Zachary_Brewer]

Yes, I have confirmed Versioned assets are in the dist directory on the server, as expected.

[Zachary_Brewer]

I should also mention, I am using Sage 9 beta2