PHPackages bcdo/project - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. bcdo/project AbandonedArchivedProject bcdo/project ============ A scaffolding for projects 2.5.4(5y ago)015MITTwig Since Jul 8Pushed 5y ago1 watchersCompare [ Source](https://github.com/Bcdo/project)[ Packagist](https://packagist.org/packages/bcdo/project)[ RSS](/packages/bcdo-project/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (10)Dependencies (14)Versions (13)Used By (0) DEPRECATED ========== [](#deprecated) This is no longer maintained, and is adviced to not be used. The new nitro and nitro versions coming will all be docker based. This repo was a workaround to get up and running on the nitro multipass solution. Now, there will be no need if nitro is the preferred dev enviroment. NOEN Reklamebyrå scaffolding ============================ [](#noen-reklamebyrå-scaffolding) What is this? ------------- [](#what-is-this) This is a Craft CMS scaffolding project based on the nystudio107´s docker scaffolding. I needed it to work with vm instead of docker, so I have adjusted it to be used with Craft Nitro. Before trying to use this, make sure you install Nitro first. I will keep updating this project based on my own preferences, as well as follow ups on nystudio107´s updates. Required Technology Stack ------------------------- [](#required-technology-stack) - Craft Nitro - PHP 7.4 Build instructions ------------------ [](#build-instructions) 1. From developer folder, run *"composer create-project bcdo/project project\_name"* 2. Add the site to Nitro, with *"nitro add"*. If needed, start a new nitro machine with *"nitro init -m machineName"* first. If new machine was created all of the following nitro commands has to end with "-m nameOfMachine". For new machines, ssh into machine and run *"sudo apt install composer -y && sudo apt install npm -y"* then *"sudo apt-get update -y && sudo apt-get install -y"*. 3. Exit the vm and duplicate the .env.example into .env file, and replace all the REPLACE\_ME parts. To get the IP run nitro info. Remember the name of the database for the next step. 4. Cd into the scripts folder. Run *"nitro db import seed\_db.sql"*, and name it the same as in the .env file. This will seed the db properly. 5. Nitro ssh and Cd into the root folder, and run *"composer install --no-scripts --optimize-autoloader --no-interaction"*, and *"npm install"*. When finished run *"npm run debug"* in a new terminal - Check if everything compiles properly and keep it running in the background. 6. Exit the vm again and run *"nitro db restart"*. 7. Nitro ssh into the machine and run *"./craft setup"* from root folder, and follow the instructions. To finish off, you can also run *"composer update"*. Thats it! Further down you will find optional installs as well, but not required. To log in to craft, use the following admin details: User: Password: letmein The database uses the Nitro default details. In the future, will have to work on making it even less complicated. Optional -------- [](#optional) ### Asset handling [](#asset-handling) 10. Set up aws and cloudfront as explained at , and populate the .env file accordingly. Remember the correct region, I use Stockholm which gives me the region of eu-north-1. 11. Set up a image transform service for serverless image handling as explained at 12. Populate the .env file. ### Pagetesting [](#pagetesting) 13. The webperf plugin gives you an optional to input a webpagetest api. Head over to webpagetest.org, get the free api key and populate the .env file. ### DB and Asset sync, and other scripts. [](#db-and-asset-sync-and-other-scripts) 14. In the scripts directory, duplicate the example.env.sh file, and rename it to .env.sh. 15. Edit the .env.sh files and replace REPLAC\_ME with appropriate information. 16. Create the .env.sh files for each environment, as this is ignored by git. Visit to understand the content of the scripts folder. Pre-commit checklist -------------------- [](#pre-commit-checklist) 17. Follow to set up a custom pre-commit checklist for safe git commit, project based. ### Health Score 27 — LowBetter than 49% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity6 Limited adoption so far Community9 Small or concentrated contributor base Maturity62 Established project with proven stability Bus Factor1 Top contributor holds 98.8% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~9 days Recently: every ~15 days Total 11 Last Release 2045d ago Major Versions 1.0.2 → 2.3.22020-07-28 ### Community Maintainers ![](https://www.gravatar.com/avatar/cf004954587a5638a33ea956678ab47fb9cc26a3067ffc25cbce8aa86b70bd81?d=identicon)[Bcdo](/maintainers/Bcdo) --- Top Contributors [![Bcdo](https://avatars.githubusercontent.com/u/22382795?v=4)](https://github.com/Bcdo "Bcdo (80 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (1 commits)") ### Embed Badge ![Health badge](/badges/bcdo-project/health.svg) ``` [![Health](https://phpackages.com/badges/bcdo-project/health.svg)](https://phpackages.com/packages/bcdo-project) ``` PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)