NotionCommotion Posted November 8, 2016 Share Posted November 8, 2016 How would you recommend structuring your project directory. For instance, where should vendor go? What about public folder, and what do you call it (html, public, etc). Should "src" be used, and what for? What should be ignored in Git (i.e. vendor and logs)? Should public js/css files be directly in the public directory, or should they be located in the code directory and a symbolic link used? Is there some sort of psr standard? My hopes are to be consistent with the industry. Thanks Quote Link to comment https://forums.phpfreaks.com/topic/302482-recommended-directory-structure-when-composer-is-used/ Share on other sites More sharing options...
requinix Posted November 8, 2016 Share Posted November 8, 2016 - Put vendor/ at the same level as your own directory for classes and such - probably at the top - "public" can be called whatever the hell you want it to be - IMO "src" doesn't make sense for PHP so call it something else - Ignore files that you don't want in source control - Putting public files in a "public" directory is reasonable; symbolic links are a hassle to deploy - If you want to know whether there's a PSR then you should check if there's a PSR - The industry is not consistent Quote Link to comment https://forums.phpfreaks.com/topic/302482-recommended-directory-structure-when-composer-is-used/#findComment-1539062 Share on other sites More sharing options...
NotionCommotion Posted November 8, 2016 Author Share Posted November 8, 2016 I had looked for a PSR, but didn't find one at http://www.php-fig.org/. I really need to standardize on one approach, and guess if I am not doing so, not much hope for the industry. Quote Link to comment https://forums.phpfreaks.com/topic/302482-recommended-directory-structure-when-composer-is-used/#findComment-1539080 Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.