[DOCU-562] Relationship between Public and Author instances Created: 16/May/15 Updated: 19/May/15 Resolved: 19/May/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | content |
| Affects Version/s: | short term |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Gediminas Zalys | Assignee: | Antti Hietala |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
I have a quick question related to the Public and Author. So my confusion is what kind of instance have i created, is it Author or is it Public? localhost:8080/myProject-webapp/pageName.html this tells me its a public instance ... However i can access my adminCentral module by following the below URL: http://localhost:8080/myProject-webapp/.magnolia/admincentral Now this means its an author instance ..... Nevertheless, how do subscribers fit into this picture? I have read this article but it just made me more confused of what a subscriber is and what it does and why i need it. Sorry for these very basic questions, im sure there is relevant content out there explaining all this but i am struggling to fid it. Many Thanks, |
| Comments |
| Comment by Antti Hietala [ 18/May/15 ] |
You created an author instance. The video uses a Maven archetype to create a Magnolia project. As a result, you get one author instance. This is a very typical development setup. You really only need one instance during development. The only case when you might want to have a second instance (public) is when you develop or test publishing (activation). For all other development tasks one instance is usually enough.
These things have nothing to do with the instance type. You can reach pages with direct URLs on author and public. You can log into AdminCentral on author and public. The software is identical. Differences are in configuration. See What kind of instance do I have? to find out.
Subscribers come into play when you deploy your project into production. In production you should have at least two public instances so that if one goes down or traffic increases your site remains available to visitors. Download the Performance and High Availability paper to understand production considerations. The public instances "subscribe" to the content that your author instance publishes. They are called subscribers because the architecture is very similar to the pub-sub pattern you may have read about. The name also suggests that public instances have a choice regarding what content they wish to receive. A public instance can subscribe to a particular site branch, for example. Good questions! Keep them coming. You can also ask on the forum to get help from other developers. |
| Comment by Gediminas Zalys [ 19/May/15 ] |
|
Thanks Antti! Once again a great and clear response! Thanks, |