swcs/OurUmbraco
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Sebastiaan Janssen
2017-03-31 14:47:44 +02:00
committed by GitHub
parent 68979fb8d3
commit d673877e4e
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -7
View File
@@ -3,7 +3,7 @@ Our Umbraco
Complete source of the umbraco community site, our.umbraco.org. Complete source of the umbraco community site, our.umbraco.org.
##Build in visual studio ## Build in visual studio
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. 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. Upon build a web.config file will be copied into the `OurUmbraco.Site` project which you can use in the following step.
@@ -15,23 +15,23 @@ npm install -g install gulp -g
gulp gulp
``` ```
##Database restore ## Database restore
Download the SQL Server Database from: http://umbracoreleases.blob.core.windows.net/ourumbraco/OurDev.zip Download the SQL Server Database from: http://umbracoreleases.blob.core.windows.net/ourumbraco/OurDev.zip
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`. 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`.
##Logging in ## Logging in
All users and members use the same password: Not_A_Real_Password All users and members use the same password: Not_A_Real_Password
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. 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.
##Projects Area ## Projects Area
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 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
##Documentation area ## Documentation area
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. 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.
##Syncing your fork with the original repository ## Syncing your fork with the original repository
To sync your fork with this original one, you'll have to add the upstream url once: To sync your fork with this original one, you'll have to add the upstream url once:
git remote add upstream git://github.com/umbraco/OurUmbraco.git git remote add upstream git://github.com/umbraco/OurUmbraco.git
@@ -45,7 +45,7 @@ Yes, this is a scary command line operation, don't you love it?! :-D
(More info on how this works: http://robots.thoughtbot.com/post/5133345960/keeping-a-git-fork-updated) (More info on how this works: http://robots.thoughtbot.com/post/5133345960/keeping-a-git-fork-updated)
##Issues ## Issues
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 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. Mention the issue number in your pull request so we can merge it in more easily.