Replies: 3 comments
-
|
Hi @nikhiltri, I'm a bit confused because Twill doesn't control your Laravel application We definitely don't intend for Twill developers to git ignore the public folder in their own apps, for the reasons you mentioned. I do know that the updates to the frontend build pipeline in 3.x resulted in the generation of static html files that we don't actually need, and we're planning to address that. I may be missing something in your message, let me know! |
Beta Was this translation helpful? Give feedback.
-
|
I misunderstood the purpose of Twill's So to ignore temporary files within the public folder that Twill generates, perhaps adding the following lines to Laravel's base |
Beta Was this translation helpful? Give feedback.
-
|
Correct. We'll make sure to drop those html files from the build in the next release so that you can ignore a single path. |
Beta Was this translation helpful? Give feedback.
-
Description
I'm confused about the configuration Twill provides in the site-wide
.gitignorefile and could use some clarification. In Twill 3.0, thepublic/folder and its contents are included in the.gitigorefile. But for Laravel projects,public/index.phpis the main point of entry for the entire site. Out of the box, Laravel includes a few critical files in thepublic/folder that do make sense to maintain in source control for a project: https://github.com/laravel/laravel/tree/10.x/publicOn the other hand, Twill compiles some of its files into the
public/that don't make sense to keep in source control, like compiled CSS and JS on thepublic/assets/folder and compiled HTML in the root of thepublic/folder. Could this folder be organized in a way so all temporary files are in distinct places that can be in the.gitignorefile, so that the wholepublic/folder doesn't need to be?Versions
Twill version: 3.0.1
Laravel version: 10.8.0
PHP version: 8.1
Database engine: PostgreSQL
Beta Was this translation helpful? Give feedback.
All reactions