Files

54 lines
2.7 KiB
Markdown
Raw Permalink Normal View History

2012-12-18 08:28:03 +01:00
Our Umbraco
2012-12-17 23:26:00 -08:00
==========
2012-12-18 14:57:05 +01:00
Complete source of the umbraco community site, our.umbraco.org.
2017-03-31 14:47:44 +02:00
## Build in visual studio
2015-07-07 09:31:57 +02:00
Make sure to allow NuGet Package Restore in VS (Tools > Options > Package Manager). The first buid of the project will take quite a while, be patient, it will finish at some point.
Upon build a web.config file will be copied into the `OurUmbraco.Site` project which you can use in the following step.
2012-12-18 14:57:05 +01:00
2016-04-18 13:04:41 +02:00
If you're working on the frontend (the js/css/etc parts in `~/OurUmbraco.Client`) then you can either run `~/build/BuildClientFiles.bat` to build them and have them copied into the site or `~/build/RunGulp.bat` if you're actively working (gulp will monitor changes, build and copy). Or if you have npm/gulp installed on your machine you can run the usual commands in the `~/OurUmbraco.Client` folder:
```
npm install
npm install -g install gulp -g
gulp
```
2017-03-31 14:47:44 +02:00
## Database restore
2015-07-06 18:35:22 +02:00
Download the SQL Server Database from: http://umbracoreleases.blob.core.windows.net/ourumbraco/OurDev.zip
2012-12-18 08:27:14 +01:00
2016-01-05 15:25:28 +01:00
Restore the database to SQL Server 2012 SP2 (won't work on earlier version) and update the connection strings (`umbracoDbDSN`) in `OurUmbraco.Site/web.config`.
2012-12-18 10:37:26 +01:00
2017-03-31 14:47:44 +02:00
## Logging in
2012-12-18 15:28:50 +01:00
All users and members use the same password: Not_A_Real_Password
2012-12-18 14:57:05 +01:00
2015-07-07 09:31:57 +02:00
To log in, try `root` / `Not_A_Real_Password` for the backoffice and `member423@non-existing-mail-provider.none` / `Not_A_Real_Password` for the frontend.
2017-03-31 14:47:44 +02:00
## Projects Area
2015-07-07 09:32:20 +02:00
If the projects area seems empty then that's because you need to rebuild the Examine indexes for it through the Developer section of Umbraco
2015-07-07 09:31:57 +02:00
2017-03-31 14:47:44 +02:00
## Documentation area
2017-01-25 22:58:12 +01:00
If the documentation area seems empty then that's because you need to download the documentation, look for the `documentationIndexer` in the Examine dashboard in the Developer section of Umbraco and Rebuild the index. This will automatically download the latest documentation from github.
2012-12-18 15:28:50 +01:00
2017-03-31 14:47:44 +02:00
## Syncing your fork with the original repository
2012-12-18 10:37:26 +01:00
To sync your fork with this original one, you'll have to add the upstream url once:
2012-12-18 10:37:51 +01:00
2012-12-18 14:57:05 +01:00
git remote add upstream git://github.com/umbraco/OurUmbraco.git
2012-12-18 10:37:26 +01:00
And then each time you want to get the changes:
2012-12-18 10:37:51 +01:00
2012-12-18 14:57:05 +01:00
git fetch upstream
2012-12-19 16:00:16 +01:00
git rebase upstream/master
2012-12-18 14:57:05 +01:00
Yes, this is a scary command line operation, don't you love it?! :-D
2012-12-19 16:00:16 +01:00
(More info on how this works: http://robots.thoughtbot.com/post/5133345960/keeping-a-git-fork-updated)
2017-03-31 14:47:44 +02:00
## Issues
2015-06-16 10:35:06 +02:00
If you're creating a pull request, make sure that it's backed by an issue on the tracker: http://issues.umbraco.org/issues?q=project%3A+our.umbraco.org
Mention the issue number in your pull request so we can merge it in more easily.
Even if you're not planning on sending a pull request, you can always create an issue on the tracker if it doesn't exist yet, it helps other find ways to contribute.