Two New Repositories Published

<!-- wp:paragraph --> <p>We have published two new repositories named <code><a href="https://github.com/cfwheels/cfwheels-www" data-type="URL" data-id="https://github.com/cfwheels/cfwheels-www">cfwheels/cfwheels-www</a></code> and <code><a href="https://github.com/cfwheels/cfwheels-api" data-type="URL" data-id="https://github.com/cfwheels/cfwheels-api">cfwheels/cfwheels-api</a></code> which handle the <strong><em>CFWheels.org</em></strong> landing page site and the <strong><em>api.cfwheels.org</em></strong> API documentation site respectively. </p> <!-- /wp:paragraph --> <!-- wp:paragraph --> <p>The <code>cfwheels-api</code> repository is a good example of how you can structure your own projects and keep sensitive information and the core framework files out of your project's source control repository. The project used a <code>.gitignore</code> file that keeps these files out of the repo. It also uses a <code>box.json</code> file to specify some dependencies to pull the required files back in. </p> <!-- /wp:paragraph --> <!-- wp:paragraph --> <p>Using dependencies in a <code>box.json</code> file is nothing new but what's interesting is that <code>cfwheels/cfwheels-api</code> has three dependencies defined. One is the core framework itself and pulls in the latest framework folder. The second is the newly published <code>CFWheels DotEnvSettings Plugin</code> which allows keeping sensitive information out of the repository by using a locally defined <code>.env</code> file. The last dependency is probably the most interesting, cause that one pulls in the <code>Semantic Version</code> module from ForgeBox which is a module that wasn't specifically written for CFWheels but can be pulled in and used none the less. This opens up the potential of using many more modules from ForgeBox instead of being confined to just CFWheels Plugins.</p> <!-- /wp:paragraph -->