Installation LivestreetCMS on MODX Revolution package 10 clicks

I have often written about your module modLivestreet for a bunch MODX Revolution + LivestreetCMS (In this Topeka in detail the idea and implementation of schemes, etc.).
After almost two weeks since the beginning of the module development, I came to the following conclusion: it is too hard work. The idea itself is simple: MODX Revolution (which historically do not have enough modules for creating blogs) to tie LivestreetCMS in order to get the kind of sociolosko with good functionality.

The first package I have thrown fast, and ensures the redirection of queries to Livestreet and output content in MODX. But then I tried to implement the synchronous operation with users of MODX - and LS-., and then something else... In General, the functionality grew, the code is also. The problems manifested in the difficulties settings of this Union. If MODX is possible to say in General, no serious problems have arisen (or at least did not have to touch a single byte code engine), then Livestreet everything was difficult... anyway had to go into code. I certainly understand that some things can and overload classes in your plugin to do, but this is only a partial solution to the problem. And some moments not to overload, as for example was the case of the class Jevix. But that's not the important part. The main thing — setting up all this requires a lot of manual work. When I wrote manual for installing and configuring all this, I'm puzzled... it Seems not much, but still more than nothing.

So anyway, yesterday I decided to change the policy. I decided to put together a package for MODX, which already bears fully configured for Livestreet, and setting we have already created the extension for social programs.
However, the module itself can be used independently (for example, changing Livestreet settings in system preferences for different contexts, it is possible to work with several Livestreet-sites). In General, the module is quite suitable for the bonding of the existing Livestreet-sites (law in this case would have to resort to manual setup according to the manual).

So, how is the installation?
1. Download a package for MODX Revolution (for synchronous operation with users requires at least version 2.2.0, if the only content to give you and earlier to use).
2. Fill it in /core/packages/ and installed locally (sorry, still in the MODX repository is not empty).

interesting pictures of the installation process, they're here

3. After the package is installed, simply insert the snippet [[!modLivestreet.run]] in the required start-up document (with a blank template. Or create a template with this snippet), and all.

For those who have never done

After all :-)
Go to the page and see Livestreet :-)


In the future, the project will develop in this direction (the package with the finished Livestreet-ohms). I think it's right. Who need to quickly and simply already have. Want tuning? The module itself is completely independent, without any problems, dopilivat to his Livestreet. Useful infa is on offsayte.

Finally, a little FAQ.

what if I don't want Livestreet live at home hanging out? If I want to have it somewhere under /forum/ ?
All this section will be for Livestreet base. Just remember to make the main page with the snippet modLivestreet.run for this section.

what if I want on a separate domain, like forum.moysite.com?
In MODX, create a new context, in this master page from the snippet modLivestreet.run cables in MODX url to this context and all. If you want links to Livestreet-and led on domain forum., and Wayfinder, etc has formed links to the main site, the context set site_url — the primary domain and setting modLivestreet.site_url specify the domain of the forum. However you still need to change settings in Wayfinder to full URL-s was formed, but this is minor and directly to the module are not relevant.

And will work for MODX tags if I put them in Livestreet templates?
Yes, there are. All content Livestreet is processed before output the MODX parser.

what about security? But if someone writes in a topic MODX tags (snippet, system configuration, etc.)?
Still do not worry. All security measures taken. All requests to the server are cleaned and the brackets MODX tags are replaced by codes, so there is something to write, you'll see exactly what I wrote.
But there is one big BUT: if you have linked Livestreet with MODX, you don't get it in its pure form without being bound to MODX, as cleaning does the MODX tags, and if someone will write the tags in LS, they are then processed in MODX.
Later will be written cleaner and on the side of Livestreet.

And optimizing some give advice?
The most important tip — set up Rewrite rules on your server. In the basic configuration MODX completely banishes all statics Livestreet through.

I Have nginx and rules written here are

location /templates/{
root /www/site.ru/public_html;
access_log off;
expires 30d;
}

location /uploads/{
root /www/site.ru/public_html;
access_log off;
expires 30d;
}

location ~/engine/.*\.js{
root /www/site.ru/public_html;
access_log off;
expires 30d;
}

That is physically Livestreet can be completely outside of the DOCUMENT_ROOT.
In General, will know for sure.

what is A "Synchronous operation with users"?
In your MODX users, Livestreet — the. In the normal mode in Livestreet occurs independent work (the user is logged in — it is only in Livestreet, logged — it is itself).
In synchronous mode synchronous: checked — is in Livestreet, is in MODX (even if you created a user through the admin panel MODX), logged in — logged and Livestreet-and MODX, the error is somewhere there? — process completed there (that is, if the password is incorrect for at least one user, can't login either).
By default, synchronous mode is disabled. You can enable it by changing the setting modLivestreet.sync_users
By the way, in the installed Livestreet admin:
login: admin
pass:admin

But if....?
All the rest of the questions in the comments.

Article based on information from habrahabr.ru