Magento2 – Setup Magento Project After Cloning Git Repository

The repo is up to date.
Here is how the resources in pub/static should work.
The meaning of "module" changed in magento 2. Now the files are not separated between code, template and skin. Everything goes in the same module Vendor_Module.

When requesting a resource from pub/static, if the file does not exist the request is rewritten to ../static.php?resource={resource name here}.
Take a look at the .htaccess file in the pub/static folder to understand better.

You get 404 responses probably because you don't have mod_rewrite enabled.
You should enable it.
But it can work without it.
There is a 'cache' system for these static resources.
navigate to the folder dev/tools/Magento/Tools/View and run this in the command line

php deploy.php

[EDIT]
In the later versions there is no more dev/tools/Magento/Tools/View folder.
You can get the same effect by running this command:

php bin/magento setup:static-content:deploy

[/EDIT]

This will copy the static resources from each module to the pub/static folder.
Be patient, it will take a while.
Remember this for the future. It is recommended to do this on the live server. It will speed up the access to static resources.

But there is a catch.

If you modify one of the static resources inside a module, the changes will not be available until you run php deploy.php again.
And you should never modify any file from pub/static directly. The changes will be overwritten the next time your execute deploy.php.

For some reason I'm able to do this on my own so here is the steps Note I'm using Ubuntu 16.04 for my local env :

1. Make sure all the file permission is your user : sudo chown -R you-user:your-user .
2. Create your database schema. You can do this via cli or mysqlbranch.

3. Edit your app/etc/env.php and find these file :

   array (
   'host' => 'localhost',
   'dbname' => 'yourdatabase',
   'username' => 'root',
   'password' => 'root',
   'model' => 'mysql4',
   'engine' => 'innodb',
   'initStatements' => 'SET NAMES utf8;',
   'active' => '1',
   )
   

4. Now make bin/magento executable sudo chmod +x bin/magento

5. This is IMPORTANT STEP : disable your additional module first, and there will only magento original module only to feed and setup the database. You can first move all your module first out of the app/code and app/design.

6. run bin/magento setup:install --admin-user="gujarat" --admin-password="wkwkwkw" --admin-email="gujarat@balala.com" --admin-firstname="gujarat" --admin-lastname="santana". This will take forever to install.

7. bin/magento setup:upgrade. If you have trouble in this step, this is more likely because of your custom module move all your custom module first to another directory and run this command again.

8. bin/magento setup:di:compile

9. Set appropriate permission files and folder.

You should see your sites now, but don't forget to move all your custum module to its respected directory. And run the upgrade and compile command from 7 & 8 step.