Discussion about public and build folders #29252
Unanswered
toviszsolt
asked this question in
Ideas / Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Guys and Girls!
I want to talk about
public
andbuild
folders.I'm a web developer for over 15 years, and I have made many commercial web based projects. Good frameworks are ready to use in the commercial segment.
In the commercial segment, there are many servers which NOT supporting Node applications. Developers shipping sites over FTP (YES! It's funny but, truth.) to these servers. If I get a job, usually the hosting and domain already exists, so I can't tell the customer: "Hey, there are no Node and Git support on your server!". In most cases, I need to work with provided hosting technologies.
My opinion is that, need a final static build directory for FTP cases. In most cases, this name is
build
,dist
or_site
. But we are all developers, so I guess to let developers configuring this parameter would be perfect.CRA (create-react-app) out of the box with the
public
folder, which is handled by developers (similar to src). They used it to pass through the build process static files, likefavicons
,robots.txt
,site verification
, or just a downloadablepdf
file. They copy these files to the build folder without and processing.Now I tried this folder structure across some projects. It's comfortable for me because I can separate real sources (needs to be compiled) from static resources.
I hope my view can help in growing.
Beta Was this translation helpful? Give feedback.
All reactions