Hello Marti. Thank you for your explanation. I tried yesterday converting Author to Public and now it is much clear to me. I agree with you that having Author instance should be enough for developing. I've a few more questions, but I first try to find an answer by myself.

Olivier Marti пишет:

Hey leroy


Thank you, I'll try this configuration with two instances on Tomcat right now.

If I understand you correctly, it is possible to use one instance as a Public and as a Author in the same time ("... then you can try it on GlassFish and with one instance (public and author)")? Can you explain in more detail (or point where to read about this) for my further exploring?

Actually there is not much of a difference between an author and a public instance (as far as you don't start some fancy custom configurations). The difference is mostly the admin flag set to false, and change ACL setting for anonymous user together with another start page (not /.magnolia). So mostly the only real benefit if you have Public and Author in your Dev-Environment is that you can activate sites, which could be of interest if you do some custom workflow implementations or something similar, but normally an author should be fine.

And yeah, if you click on preview on the website you will have pretty the same result as on a public instance :)

Also as you said you plan to make a module deploying should not be much of problem once your done developing.

Hope that helps,
Olivier


Vasko Gjurovski пишет:
My best advice to you is to try the "recommended" configuration: two instances on Tomcat. You just can't miss it! If you manage to do that, then you can try it on GlassFish and with one instance (public and author). Regarding your second question (if I understood you well), what you describe as a problem for you (or at least what you want to achieve) is a basic behavior for Magnolia. So, again, install Magnolia (just the author fro starts) on Tomcat and try it. You can even download a bundle.
Regards,
Vasko
On Sun, Feb 8, 2009 at 3:55 PM, leroy <[email protected] <mailto:[email protected]>> wrote:
   It looks that I'm misunderstanding something...
   For example, I want to create module which shows some content to a
   user, this content available for everyone, so it should be accessed
   via Public instance. To add this content I use "administration"
   function of the module, for example, I log in Author instance, go to
   my module, and click "Add new page", it shows me a page, where I
   enter neccessary data to input fields, set checkboxes and etc. Is
   this possible to do with Magnolia? I have not read all a developing
   documentation yet, and the developing does't look very clear for me.
   If this is possible, how can I develop and test module for Author
   and Public instances? Or can I use Author instance like Public to
   test such things?
   Sorry if I ask stupid questions, but this is so new for me.
   Thank you for reply.
   Will Scheidegger пишет:
       Why do you need a public instance in your development
       environment? I do all the developing on an author instance, and
       every once in a while I install the results also on a public
       instance.
       -will
       On 08.02.2009, at 08:31, leroy wrote:
           Hello. I'm starting to explore Magnolia. I want to learn,
           how to develop site with this CMS. I've read some docs in
           Wiki and officional documentation, and it seems to me that
           some of them are not complete and outdated. Can you help me
           with some beginner's questions?
           I read article in wiki about developing with Netbeans +
           Glassfish
(http://wiki.magnolia-cms.com/pages/viewpage.action?pageId=12255438),
           I created new Magnolia project and it runs from Netbeans and
           function as Author instance. I can log into Admin interface,
           and looks that everything work as expected. Also I setup
           repository to use MySQL.
           Now I need to setup Public instance. I've read few articles
           about this
(http://wiki.magnolia-cms.com/display/WIKI/Newbie+perspective),
           espiciaaly how to use single war
(http://wiki.magnolia-cms.com/display/WIKI/One+war%2C+multiple+configs),
           and, if I understand correctly, I have to have two instances
           of Magnolia, which can be installed from single war which is
           configured for both Author and Public. But how can I achieve
           this with Netbeans? I need two projects ? On for Author, one
for Public? But this looks hard to develop and synchronize them.
           I can ask this question in more newbies manner: what I need
           to do after doing things described in
           Magnolia+Netbeans+Glassfish article to setup Public instance?
           Maybe I something miss in documentation? You also can give
           me links for further reading.
           Thank you in advance.

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to