Files
OurUmbraco/README.md
T

62 lines
3.0 KiB
Markdown
Raw 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.
2015-07-07 09:31:57 +02:00
##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.
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
##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
2015-08-01 14:10:05 +02:00
Restore the database to SQL Server 2012 (won't work on earlier version) and update the connection strings (`umbracoDbDSN`) in `OurUmbraco.Site/web.config`.
Currently, we have some invalid data in the database that prevents the upgrade installer to run when you start the site. This is fixable by running the following queries first:
```
alter table umbracoLanguage drop constraint PK_language;
alter table umbracoLanguage alter column id int not null;
alter table umbracoLanguage add CONSTRAINT PK_language PRIMARY KEY CLUSTERED (id);
CREATE UNIQUE NONCLUSTERED INDEX [IX_cmsDictionary_id] ON [dbo].[cmsDictionary]
([id] ASC) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY];
delete from umbracoNode where id = 147605
delete from umbracoNode where id = 147606
delete from umbracoNode where id = 148645
```
After doing that you should be able to start the site and run the upgrade with no problems.
2012-12-18 10:37:26 +01:00
2012-12-18 15:28:50 +01:00
##Logging in
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.
2015-07-07 09:32:20 +02:00
##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
2015-07-07 09:31:57 +02:00
2015-07-07 09:32:20 +02:00
##Documentation area
If the documentation area seems empty then that's because you need to download the documentation, look for the the `Github Documentation` tab in the dashboards in the Developer section of Umbraco and use the `Get Docs!!` button.
2012-12-18 15:28:50 +01: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)
2015-06-16 10:35:06 +02:00
##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
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.