Regarding production deployment....

[Antoliny0919]

There haven’t been many changes yet, but recently we added a few libraries and made some stylistic changes.

I expect there have probably been some changes to the deployment process as well.
Also, when we see the automatic deployment through the CD, it definitely looks different from what we expected.

I think it might be because the build process of Tailwind has changed.
Even if I want to fix this issue, it’s difficult for me to help because I don’t know how it is being deployed in the production environment.

Could you possibly help resolve this issue?
or could you let me know how the deployment is being done?

[Antoliny0919]

@chriswedgwood 🙏

[chriswedgwood]

Yip I’ll give the system a full health check tonight

…

On Tue, 5 Aug 2025 at 09:51, Antoliny Lee ***@***.***> wrote: *Antoliny0919* left a comment (django/djangosnippets.org#601) <#601 (comment)> @chriswedgwood <https://github.com/chriswedgwood> 🙏 — Reply to this email directly, view it on GitHub <#601 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJW5M7EVD7DVIREPAIDE6D3MBWALAVCNFSM6AAAAACDEIZPF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNJUGE3DANZRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[chriswedgwood]

Ive had a look and it looks like I need to figure out the best way to put django-tailwind into the heroku pipeline. I'm gettig there just need to brush up on docs , should have it sorted within a couple days

[chriswedgwood]

@Antoliny0919 this is fixed now

I ended up following these instructions

https://medium.com/@phuitsing/heroku-buildpack-for-django-tailwind-de96be543f9

in short we were missing the node build pack and heroku was expecting a package.json in the root of the project