<p>From what I see in your screenshot, it looks like you stumbled upon a <a href="https://github.com/craftcms/docs" rel="nofollow noreferrer">Craft 3 installation</a>, in which case neither a <code>Craft</code> nor <code>Public</code> folder exist.</p>

<h3>Craft 3 specific</h3>

<p>The <code>public</code> folder is now called <code>web</code>, so that's where you should point your MAMP documentroot (or whatever that's called in MAMP). The Craft code is now located in composer's <code>vendor</code> folder, that should magically appear after running <code>composer install</code>. Craft's source would then be in <code>vendor/craftcms/cms</code>.</p>

<p>You can read more about the overall structure of a Craft CMS 3 project in the <a href="https://nystudio107.com/blog/setting-up-a-craft-cms-3-project" rel="nofollow noreferrer">Setting up a New Craft CMS 3 Project</a> article.</p>

<h3>Frontend build tools and JS dependencies (package.json, webpack.mix.js)</h3>

<p>Further more, I see that <a href="https://laravel.com/docs/5.6/mix" rel="nofollow noreferrer">Laravel Mix</a> is used for frontend (js, css) automization, meaning that you have to install JS dependencies by running <code>npm install</code> or <code>yarn install</code>, after which you can use the command defined in <code>package.json</code> to run Mix. I guess this is something like <code>npm run watch</code> (when developing) or <code>npm run prod</code> before you push anything to production.</p>

<h3>Modules</h3>

<p>And: I see a <code>modules</code> folder, that would most likely mean that a custom module was used for this specific site. Modules are a (poorly documented ;)) Craft 3 way of extending your site without building a plugin and trying to get that to work through composer. They are essentially a wrapper for Yii2's modules.</p>

<p>It's very possible that the Module is just vestigial, however, since that folder is created by default if you do <code>composer create-project -s RC craftcms/craft PATH</code>. You can read more about Modules in the <a href="https://nystudio107.com/blog/enhancing-a-craft-cms-3-website-with-a-custom-module" rel="nofollow noreferrer">Enhancing a Craft CMS 3 Website with a Custom Module</a> article.</p>

<h3>Environment settings</h3>

<p>Last but not least: copy <code>.env.example</code> to <code>.env</code> and use that to set credentials for your environment (db settings and stuff).</p>

CC BY-SA 3.0
2018-03-28T13:28:33.177Z
Heh I was just typing up something along the same lines, but you beat me to it :P lol
Jalen Davenport
CC BY-SA 3.0
2018-03-28T13:52:48.303Z
It's very possible that the `modules` folder is just there in a vestigial way; it's created by default if you do a `composer create-project -s RC craftcms/craft`. I wrote up some documentation on modules here: [Enhancing a Craft CMS 3 Website with a Custom Module](https://nystudio107.com/blog/enhancing-a-craft-cms-3-website-with-a-custom-module)
andrew.welch
CC BY-SA 3.0
2018-03-28T14:17:51.130Z
At the first sight it looks like this is a screenshot from a git repository so it's usual that it does not contain the vendor folder -> all the needed plugins. We don't know if the former developer already worked with certain plugins or not. Maybe they are all on the development server and not inside the repo. I would just like to know why you know it is not installed? When you take a look into all our projects they are looking quite similar -> you would suggest a new developer to start from scratch
Robin Schambach
CC BY-SA 3.0
2018-03-29T09:57:38.180Z
Looks a lot like this site was set up by someone who knew what they were doing. Have you read the README? It's clearly been modified by the dev so it may well contain detailed setup instructions, my readmes do.
Seth Warburton
CC BY-SA 3.0
2018-03-29T17:39:30.280Z
@andrew.welch I had to look up vestigial but yes, that’s very possible ;)
Paul
CC BY-SA 3.0
2018-03-28T13:26:57.330Z
2018-03-28T13:56:36.483Z
2018-03-28T13:56:36.483Z
Paul
<p>I have a client who started a Craft CMS site with another developer. I guess the other developer quit, and now the client wants me to make some changes to the site.</p>

<p>The site was created with Composer (which I haven't used before), and I'm stumped on how to get it installed on my local machine using MAMP. I ran Composer to install the dependencies, but there isn't a "Craft" folder and a "Public" folder like I'm used to seeing.</p>

<p>Here's a screenshot of the file structure.
<a href="https://i.sstatic.net/Rk1GG.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Rk1GG.jpg" alt="file-structure"></a></p>

<p>Anyone have any advice on how to get this site installed locally so I can make the changes requested?</p>

<p>Thank you in advance!!</p>

<composer>
Copy a Craft 3 site to my local machine (MAMP)
# Copy a Craft 3 site to my local machine (MAMP)

(Asked by: username_0 on 2018-03-28)

I have a client who started a Craft CMS site with another developer. I guess the other developer quit, and now the client wants me to make some changes to the site.

The site was created with Composer (which I haven't used before), and I'm stumped on how to get it installed on my local machine using MAMP. I ran Composer to install the dependencies, but there isn't a "Craft" folder and a "Public" folder like I'm used to seeing.

Here's a screenshot of the file structure.
[![file-structure](https://i.sstatic.net/Rk1GG.jpg)](https://i.sstatic.net/Rk1GG.jpg)

Anyone have any advice on how to get this site installed locally so I can make the changes requested?

Thank you in advance!!

**Tags:** composer


---

## 1 answers

### Answer by username_1 on 2018-03-28. Score: 4 | Accepted answer

From what I see in your screenshot, it looks like you stumbled upon a [Craft 3 installation](https://github.com/craftcms/docs), in which case neither a `Craft` nor `Public` folder exist.

### Craft 3 specific

The `public` folder is now called `web`, so that's where you should point your MAMP documentroot (or whatever that's called in MAMP). The Craft code is now located in composer's `vendor` folder, that should magically appear after running `composer install`. Craft's source would then be in `vendor/craftcms/cms`.

You can read more about the overall structure of a Craft CMS 3 project in the [Setting up a New Craft CMS 3 Project](https://nystudio107.com/blog/setting-up-a-craft-cms-3-project) article.

### Frontend build tools and JS dependencies (package.json, webpack.mix.js)

Further more, I see that [Laravel Mix](https://laravel.com/docs/5.6/mix) is used for frontend (js, css) automization, meaning that you have to install JS dependencies by running `npm install` or `yarn install`, after which you can use the command defined in `package.json` to run Mix. I guess this is something like `npm run watch` (when developing) or `npm run prod` before you push anything to production.

### Modules

And: I see a `modules` folder, that would most likely mean that a custom module was used for this specific site. Modules are a (poorly documented ;)) Craft 3 way of extending your site without building a plugin and trying to get that to work through composer. They are essentially a wrapper for Yii2's modules.

It's very possible that the Module is just vestigial, however, since that folder is created by default if you do `composer create-project -s RC craftcms/craft PATH`. You can read more about Modules in the [Enhancing a Craft CMS 3 Website with a Custom Module](https://nystudio107.com/blog/enhancing-a-craft-cms-3-website-with-a-custom-module) article.

### Environment settings

Last but not least: copy `.env.example` to `.env` and use that to set credentials for your environment (db settings and stuff).

> **Comments:**
> **username_2**: Heh I was just typing up something along the same lines, but you beat me to it :P lol  
> **username_3**: It's very possible that the `modules` folder is just there in a vestigial way; it's created by default if you do a `composer create-project -s RC craftcms/craft`. I wrote up some documentation on modules here: [Enhancing a Craft CMS 3 Website with a Custom Module](https://nystudio107.com/blog/enhancing-a-craft-cms-3-website-with-a-custom-module)  
> **username_4**: At the first sight it looks like this is a screenshot from a git repository so it's usual that it does not contain the vendor folder -> all the needed plugins. We don't know if the former developer already worked with certain plugins or not. Maybe they are all on the development server and not inside the repo. I would just like to know why you know it is not installed? When you take a look into all our projects they are looking quite similar -> you would suggest a new developer to start from scratch  
> **username_5**: Looks a lot like this site was set up by someone who knew what they were doing. Have you read the README? It's clearly been modified by the dev so it may well contain detailed setup instructions, my readmes do.  
> **username_1**: @username_3 I had to look up vestigial but yes, that’s very possible ;)  

---

