Updates domain references

kkolstad · Aug 30, 2017 · 15256b1 · 15256b1
1 parent 98b022c
commit 15256b1
Show file tree

Hide file tree

Showing 30 changed files with 198 additions and 210 deletions.
diff --git a/_config.yml b/_config.yml
@@ -1,6 +1,6 @@
 name: "Event Store"
 description: "The open-source, functional database with Complex Event Processing in JavaScript."
-url: "https://geteventstore.com"
+url: "https://eventstore.org"
 permalink: /blog/:year:month:day/:title/index.html
 sass:
     sass_dir: _sass

diff --git a/_data/downloads.json b/_data/downloads.json
diff --git a/_data/events.json b/_data/events.json
@@ -178,7 +178,7 @@
         },
         {
             "name": "Ouro’s 2nd Birthday",
-            "url": "https://geteventstore.com/two-years-on/",
+            "url": "https://eventstore.org",
             "info": "17 Sept 2014, London, UK",
             "countrycode": "gb"
         }

diff --git a/_data/resources.json b/_data/resources.json
@@ -2,7 +2,7 @@
     "blogs":[
         {
             "name": "Event Store Blog",
-            "url": "https://geteventstore.com/blog"
+            "url": "https://eventstore.org/blog"
         }
     ],
     "videos": [
@@ -37,7 +37,7 @@
         },
         {
             "name": "Papercraft Ouro Template",
-            "url": "https://geteventstore.com/downloads/papercraft-ouro.pdf"
+            "url": "https://eventstore.org/downloads/papercraft-ouro.pdf"
         }
     ]
 }
diff --git a/_includes/header.html b/_includes/header.html
@@ -10,7 +10,7 @@
     <title>{% if page.title != "Homepage" %}{{ page.title }} – {% endif %}{{ site.name }}</title>
     <link rel="stylesheet" href="/css/main12.css">
     <link rel="stylesheet" href="//fonts.googleapis.com/css?family=Roboto:400,400italic,700,700italic|Source+Code+Pro:400,700">
-    <link rel="alternate" type="application/rss+xml" title="Event Store" href="https://geteventstore.com/blog/feed/index.xml">
+    <link rel="alternate" type="application/rss+xml" title="Event Store" href="https://eventstore.org/blog/feed/index.xml">
 </head>
 
 <body>
@@ -22,11 +22,11 @@ <h1 class="site-logo">
                 </a>
             </h1>
             <ul class="site-navigation">
-                <li class="site-navigation__item"><a href="/community/">Community</a></li>
-                <li class="site-navigation__item"><a href="/support/">Commercial Support</a></li>
-                <li class="site-navigation__item"><a href="/blog/">Blog</a></li>
-                <li class="site-navigation__item"><a href="http://docs.geteventstore.com">Documentation</a></li>
-                <li class="site-navigation__item"><a href="/downloads/">Downloads</a></li>
+                <li class="site-navigation__item"><a href="/community">Community</a></li>
+                <li class="site-navigation__item"><a href="/support">Commercial Support</a></li>
+                <li class="site-navigation__item"><a href="/blog">Blog</a></li>
+                <li class="site-navigation__item"><a href="/docs">Documentation</a></li>
+                <li class="site-navigation__item"><a href="/downloads">Downloads</a></li>
             </ul>
             <a href="javascript:void(0)" class="site-navigation-toggle">Menu</a>
         </div>

diff --git a/_posts/2012-10-05-special-offer.md b/_posts/2012-10-05-special-offer.md
@@ -16,4 +16,4 @@ The specific terms of the offer are as follows:
 
 Invoices will be issued upon receipt of order and must be paid within 30 days. Appliances will be shipped upon payment of invoices. We’ll even pop a t-shirt and some Ouro stickers in too.
 
-Contact [sales@geteventstore.com](mailto:sales@geteventstore.com).
+Contact [sales@eventstore.org](mailto:sales@eventstore.org).
diff --git a/_posts/2012-11-19-oredev-developer-conference-a-deep-look-into-the-event-store.md b/_posts/2012-11-19-oredev-developer-conference-a-deep-look-into-the-event-store.md
@@ -5,6 +5,6 @@ author: "Dan Leech"
 layout: blog-post
 ---
 
-> What if I told you that the new Event Store (OSS [geteventstore.com](/)) is an ACID compliant database with only 24 bytes of mutable data? This session will look deep inside the Event Store and architectural decisions and trade offs made in the development of it.
+> What if I told you that the new Event Store (OSS [eventstore.org](/)) is an ACID compliant database with only 24 bytes of mutable data? This session will look deep inside the Event Store and architectural decisions and trade offs made in the development of it.
 
 See the full presentation (52 minutes) on [Øredev’s website](http://oredev.org/2012/sessions/a-deep-look-into-the-event-store) or on [Vimeo](https://vimeo.com/53153270). The video was recorded on Thursday 8th November 2012 at the Øredev Developer Conference in Malmö, Sweden.
diff --git a/_posts/2013-02-12-projections-1-theory.md b/_posts/2013-02-12-projections-1-theory.md
@@ -5,7 +5,7 @@ author: "Greg Young"
 layout: blog-post
 ---
 
-Over at [geteventstore.com](https://geteventstore.com) we have 1.0’d the Event Store as an Event Store (i.e. storing/retrieving events/multinode version/etc) but in the process we did not release projections. They are still marked as experimental. Projections are however getting close to ready so its time to write a bit about them as the official documentation takes shape.
+Over at [eventstore.org](https://eventstore.org) we have 1.0’d the Event Store as an Event Store (i.e. storing/retrieving events/multinode version/etc) but in the process we did not release projections. They are still marked as experimental. Projections are however getting close to ready so its time to write a bit about them as the official documentation takes shape.
 
 Through the series we will get fairly deep into their usage but for many the best way to understand them to understand the underlying theory so let’s start there.
 

diff --git a/...20-getting-started-part-2-implementing-the-commondomain-repository-interface.md b/...20-getting-started-part-2-implementing-the-commondomain-repository-interface.md
@@ -13,7 +13,7 @@ layout: blog-post
 
 <strike>Jon Oliver’s</strike>* <strike>excellent</strike>** [CommonDomain](https://github.com/joliver/CommonDomain) project has been around for some time, and many developers have built systems either using it directly or using it as inspiration for their own Aggregate + Event Sourcing base classes and repository interfaces. In this post, we’ll look at implementing the `IRepository` interface using the Event Store for storage.
 
-The purpose of this is to provide a sample implementation that you can customise according to the specific needs of your system rather than to provide framework code - for this reason we don't intend to provide a NuGet package of it! The code, along with some integration tests and the necessary supporting files, are available in the [GitHub repository for this blog series](http://github.com/EventStore/getting-started-with-event-store).
+The purpose of this is to provide a sample implementation that you can customise according to the specific needs of your system rather than to provide framework code - for this reason we don't intend to provide a NuGet package of it! The code, along with some integration tests and the necessary supporting files, are available in the [GitHub repository for this blog series](https://github.com/eventstore/getting-started-with-event-store).
 
 ## The Interface
 
@@ -35,7 +35,7 @@ It’s contained in the CommonDomain.Persistence assembly which is available eit
 Before we jump into reading or writing, let’s take a look at our dependencies. The constructor in our implementation looks like this:
 
 ```csharp
-public GetEventStoreRepository(EventStoreConnection eventStoreConnection, Func<Type, Guid, string> aggregateIdToStreamName)
+public geteventstoreRepository(EventStoreConnection eventStoreConnection, Func<Type, Guid, string> aggregateIdToStreamName)
 {
     _eventStoreConnection = eventStoreConnection;
     _aggregateIdToStreamName = aggregateIdToStreamName;
@@ -148,10 +148,10 @@ public TAggregate GetById<TAggregate>(Guid id, int version) where TAggregate : c
 
         if (currentSlice.Status == SliceReadStatus.StreamNotFound)
             throw new AggregateNotFoundException(id, typeof (TAggregate));
-                
+
         if (currentSlice.Status == SliceReadStatus.StreamDeleted)
             throw new AggregateDeletedException(id, typeof (TAggregate));
-                
+
         sliceStart = currentSlice.NextEventNumber;
 
         foreach (var evnt in currentSlice.Events)
@@ -163,7 +163,7 @@ public TAggregate GetById<TAggregate>(Guid id, int version) where TAggregate : c
 
     return aggregate;
 }
-        
+
 private static TAggregate ConstructAggregate<TAggregate>()
 {
     return (TAggregate)Activator.CreateInstance(typeof(TAggregate), true);

diff --git a/_posts/2013-07-08-testing-event-store-ha.md b/_posts/2013-07-08-testing-event-store-ha.md
@@ -7,13 +7,13 @@ layout: blog-post
 
 As we prepare to release Event Store 2.0.0 binaries (the source code was just merged to the master branch over on [GitHub](http://github.com/EventStore/EventStore)), we also will be opening up access to one of the test environments that we’ve been using for our commercial high availability clustered product, Event Store HA.
 
-We get many questions asking how the clustered version behaves during network partitions and server failures – [now you can see for yourself](http://ha.geteventstore.com)!
+We get many questions asking how the clustered version behaves during network partitions and server failures – [now you can see for yourself](https://eventstore.org)!
 
 <figure>
 	<img src="/images/blog-ha-setup.jpg">
 </figure>
 
-The cluster in the picture above is now [connected to the web](http://ha.geteventstore.com) to allow people to see a cluster in action, as well as some of the testing we perform on them. This particular cluster is running a power outage test (and has been for some time). We can also test network partitions both of which the cluster can easily handle.
+The cluster in the picture above is now [connected to the web](https://eventstore.org) to allow people to see a cluster in action, as well as some of the testing we perform on them. This particular cluster is running a power outage test (and has been for some time). We can also test network partitions both of which the cluster can easily handle.
 
 We pull the power on a node programmatically using the device seen here:
 

diff --git a/_posts/2013-07-09-murphy.md b/_posts/2013-07-09-murphy.md
@@ -7,7 +7,7 @@ layout: blog-post
 
 As all of us who have released production software before know, if something totally rare and unseen will happen it almost always happens the day of release. In our shared career histories, we’ve personally seen many such examples: routers going bad, disks failing, servers with bad memory, admins blocking the ports you use on the firewalls, admins switching from two-phase to three-phase commit on the DTC (why did we increase in latency by 40%?!), and of course we all love dealing with multiple levels of managed providers. Literally, we have seen all sorts of fun stuff *(and we’d love to hear your stories on Twitter – [@geteventstore](http://twitter.com/geteventstore))!*.
 
-Yesterday we pushed the source for Event Store 2.0.0 so some early adopters can start looking through/testing with/using. We are currently working on making sure the binaries are stable before releasing them along with the NuGet packages. We also released [ha.geteventstore.com](http://ha.geteventstore.com). As we [discussed yesterday](/blog/20130708/testing-event-store-ha) this is one of our clusters that we have automated for power failures/network partitions. It does about 1,000 power failures per day to help make sure you don't have a problem when/if you happen to lose power.
+Yesterday we pushed the source for Event Store 2.0.0 so some early adopters can start looking through/testing with/using. We are currently working on making sure the binaries are stable before releasing them along with the NuGet packages. We also released [eventstore.org](https://eventstore.org). As we [discussed yesterday](/blog/20130708/testing-event-store-ha) this is one of our clusters that we have automated for power failures/network partitions. It does about 1,000 power failures per day to help make sure you don't have a problem when/if you happen to lose power.
 
 At about 0300 local time last night we ended up losing a node. The data hard drive actually went bad – who would have thought such a thing would happen on the day you release?! Windows was not so happy either - the box entered a zombie state. Once we were able to get it to boot up about all we could get it to do was...
 

diff --git a/_posts/2013-07-19-v2-0-binaries-released.md b/_posts/2013-07-19-v2-0-binaries-released.md
@@ -5,7 +5,7 @@ author: "Greg Young"
 layout: blog-post
 ---
 
-Version 2.0 binaries are now available for download at [geteventstore.com/downloads](/downloads)</a>.
+Version 2.0 binaries are now available for download at [eventstore.org/downloads](/downloads)</a>.
 
 The new version is fully compatible with all database files from old versions no data upgrade is required. With the addition of security you will likely get asked for a username/password, the default is admin:changeit.
 

diff --git a/_posts/2014-09-01-event-store-3.0.0-features-in-memory-db.md b/_posts/2014-09-01-event-store-3.0.0-features-in-memory-db.md
@@ -5,7 +5,7 @@ author: "James Nugent"
 layout: blog-post
 ---
 
-*As we gear up to launch version 3.0.0 of Event Store [at our annual birthday party (which you should totally come to!)](/two-years-on), we decided it would be a good idea to run a short series of articles describing some of the new features for those who haven't seen them. If there are things you want to know about in particular, please get in touch on Twitter, [@GetEventStore](https://twitter.com/GetEventStore)!*
+*As we gear up to launch version 3.0.0 of Event Store [at our annual birthday party (which you should totally come to!)](/two-years-on), we decided it would be a good idea to run a short series of articles describing some of the new features for those who haven't seen them. If there are things you want to know about in particular, please get in touch on Twitter, [@geteventstore](https://twitter.com/geteventstore)!*
 
 ##In-Memory Mode
 

diff --git a/_posts/2014-09-02-event-store-3.0.0-features-media-types.md b/_posts/2014-09-02-event-store-3.0.0-features-media-types.md
@@ -5,13 +5,7 @@ author: "James Nugent"
 layout: blog-post
 ---
 
-*As we gear up to launch version 3.0.0 of Event Store [at our annual birthday
-party (which you should totally come
-to!)](https://geteventstore.com/two-years-on), we decided it would be a good
-idea to run a short series of articles describing some of the new features and
-changes for those who haven't seen them. If there are things you want to know
-about in particular, please get in touch on Twitter,
-[@GetEventStore](https://twitter.com/GetEventStore)!*
+*As we gear up to launch version 3.0.0 of Event Store, we decided it would be a good idea to run a short series of articles describing some of the new features and changes for those who haven't seen them. If there are things you want to know about in particular, please get in touch on Twitter, [@geteventstore](https://twitter.com/geteventstore)!*
 
 ##New Media Types and Headers
 

diff --git a/_posts/2014-09-02-ouros-birthday.md b/_posts/2014-09-02-ouros-birthday.md
@@ -20,7 +20,3 @@ There will be plenty of people from the community there, as well as much of the
 Event Store team, and we are sure there will be lots of good discussions.
 Afterwards there will be a bit of a celebration with free food/beer and, of
 course, some ouro-themed goodies!
-
-If you'd like to come along, please register (for free!) via EventBrite so we
-know how much food and beer to buy - you can find more information and the sign
-up page [here](https://geteventstore.com/two-years-on/)!
diff --git a/_posts/2014-09-03-event-store-3.0.0-static-linking-where-did-singlenode-go.md b/_posts/2014-09-03-event-store-3.0.0-static-linking-where-did-singlenode-go.md
@@ -11,7 +11,7 @@ to!)</a>, we decided it would be a good
 idea to run a short series of articles describing some of the new features and
 changes for those who haven't seen them. If there are things you want to know
 about in particular, please get in touch on Twitter,
-<a href="https://twitter.com/GetEventStore">@GetEventStore</a></p>
+<a href="https://twitter.com/geteventstore">@geteventstore</a></p>
 
 ##Where did SingleNode go?
 
@@ -25,4 +25,4 @@ We originally developed Event Store to run on Windows or Linux, via .NET or Mono
 
 Consequently we recently put some effort into statically linking Mono, not only on Linux but also on macOS (which previously required building from source in order to run 64 bit Mono). Fortunately Mono has a relatively nice way of making a bundle and then statically linking the framework so that the only external system dependency is `glibc`. Hopefully there'll be something this nice for making Windows binaries one day!
 
-You can check out the statically linked packages by [downloading Event Store v3.0.0-rc9](https://geteventstore.com/downloads/) for Linux or macOS. For those interested in how to bundle and statically link Mono, the [scripts are part of our open-source repository](https://github.com/EventStore/EventStore/blob/dev/scripts/package-mono/package-mono.sh#L115-121)!
+You can check out the statically linked packages by [downloading Event Store v3.0.0-rc9](https://eventstore.org/downloads) for Linux or macOS. For those interested in how to bundle and statically link Mono, the [scripts are part of our open-source repository](https://github.com/EventStore/EventStore/blob/dev/scripts/package-mono/package-mono.sh#L115-121)!
diff --git a/_posts/2014-09-04-event-store-3.0.0-client-api-for-jvm-clients.md b/_posts/2014-09-04-event-store-3.0.0-client-api-for-jvm-clients.md
@@ -11,7 +11,7 @@ to!)</a>, we decided it would be a good
 idea to run a short series of articles describing some of the new features and
 changes for those who haven't seen them. If there are things you want to know
 about in particular, please get in touch on Twitter,
-<a href="https://twitter.com/GetEventStore">@GetEventStore</a></p>
+<a href="https://twitter.com/geteventstore">@geteventstore</a></p>
 
 ##Using Event Store From JVM Languages
 
@@ -141,6 +141,4 @@ es.appendToStream(STREAM_NAME, new ResponseReceiver() {
 },EVENT);
 ...
 es.close();
-```
-
-Stanislavas will be one of the speakers at our [birthday party event](https://geteventstore.com/two-years-on) in London on the 17th September!
+```
diff --git a/_posts/2014-09-05-event-store-3.0.0-new-configuration-options.md b/_posts/2014-09-05-event-store-3.0.0-new-configuration-options.md
@@ -11,7 +11,7 @@ to!)</a>, we decided it would be a good
 idea to run a short series of articles describing some of the new features and
 changes for those who haven't seen them. If there are things you want to know
 about in particular, please get in touch on Twitter,
-<a href="https://twitter.com/GetEventStore">@GetEventStore</a></p>
+<a href="https://twitter.com/geteventstore">@geteventstore</a></p>
 
 ##Configuration Changes
 

diff --git a/_posts/2015-12-17-event-store-3.4.0-released.md b/_posts/2015-12-17-event-store-3.4.0-released.md
@@ -4,7 +4,7 @@ author: "Pieter Germishuys"
 layout: blog-post
 ---
 
-Event Store 3.4.0 is now released! The headline feature is the addition of the [HTTP API for “competing consumers”](http://docs.geteventstore.com/http-api/3.4.0/competing-consumers/), but there have been numerous other improvements and bug fixes. We have also moved from [self hosting](https://apt-oss.geteventstore.com/index.html) our Event Store packages to hosting the packages on [packagecloud](https://packagecloud.io/EventStore/EventStore-OSS).
+Event Store 3.4.0 is now released! The headline feature is the addition of the [HTTP API for “competing consumers”](/docs/http-api/3.4.0/competing-consumers), but there have been numerous other improvements and bug fixes. We have also moved from [self hosting](https://apt-oss.eventstore.org/index.html) our Event Store packages to hosting the packages on [packagecloud](https://packagecloud.io/EventStore/EventStore-OSS).
 
 There is also an accompanying update to the .NET Client API and the Embedded Client. These are now in the NuGet gallery.
 
@@ -22,7 +22,7 @@ The release notes for 3.4.0 are listed below, along with the release notes for 3
 - [#762](https://github.com/EventStore/EventStore/pull/762) **(All Platforms)** Move usages of dates to Utc Now from Now.
 - [#759](https://github.com/EventStore/EventStore/pull/759) **(All Platforms)** Introduce a new role (ops) which has permissions to perform scavenge, monitor through the web UI as well as shutting down event store nodes. With this a new default user will be introduced called `ops`.
 - [#749](https://github.com/EventStore/EventStore/pull/749) **(All Platforms)** Set a sane default for message timeouts (10 seconds) (Competing Consumers).
-- [#737](https://github.com/EventStore/EventStore/pull/737) **(All Platforms)** Add HTTP Competing Consumers. Documentation can be found [here](http://docs.geteventstore.com/http-api/3.4.0/competing-consumers/)
+- [#737](https://github.com/EventStore/EventStore/pull/737) **(All Platforms)** Add HTTP Competing Consumers. Documentation can be found [here](https://eventstore.org/docs/http-api/3.4.0/competing-consumers/)
 
 ## Event Store UI 3.4.0 release notes
Original file line number	Diff line number	Diff line change
Expand Up		@@ -16,4 +16,4 @@ The specific terms of the offer are as follows:

		Invoices will be issued upon receipt of order and must be paid within 30 days. Appliances will be shipped upon payment of invoices. We’ll even pop a t-shirt and some Ouro stickers in too.

		Contact [sales@geteventstore.com](mailto:sales@geteventstore.com).
		Contact [sales@eventstore.org](mailto:sales@eventstore.org).