Internaly Hosted Revo Installation

Hi All,

I have a question regarding the usage of Revolution (rc1) on an internally hosted server. Now this particular server is in an environment where it does not have access to the internet (only office traffic to/from this machine) so I’m wondering what kind of issues would arise in this scenario. I’ve already noticed that the security notice rss feed doesn’t update and the Web Transport Facility isn’t available. I haven’t seen much info available on the internals/mirroring of WTF, or how to implement your own WTF. I would consider grabbing and installing individual packages, but I also haven’t noticed a way to browse WTF packages outside of modx. I’d welcome any additional thoughts or ideas regarding this. Thanks in advance.

There no issues what-so-ever to run it disconnected from the public world, security will for sure be better

About the transport packages, just grab the zip files you need from http://modxcms.com/extras/?versionFilter=revolution (or any other source) and put them in /core/packages folder. then install manually via "Search Locally for Packages".

There are system settings to turn off the RSS feeds on the welcome page.

As for package management, if you’re running behind a firewall, you’ll have to confirm with your sysadmin if cURL requests are allowed through. If not, then you wont be able to use the remote downloading. You’ll have to install packages via the method that oori suggests.

Hey guys thanks for the help. I had suspected I might have to resort to local uploads, but I’d love to be able to use the repository distribution mechanism. As for cURL... Remote requests would work fine, just to other internal servers. I would like to be able to setup a repository on another dev server and if we happen to have other modx deployments I can use a common repository.

Quote from: feamsr00 at Apr 06, 2010, 02:32 PM

Hey guys thanks for the help. I had suspected I might have to resort to local uploads, but I’d love to be able to use the repository distribution mechanism. As for cURL... Remote requests would work fine, just to other internal servers. I would like to be able to setup a repository on another dev server and if we happen to have other modx deployments I can use a common repository.

We will, post-GA, be releasing code packages that will allow you to setup your own custom "Providers" to MODx Partners (more on that at a later time). Or in the meantime, you can reverse-engineer the current provider at http://rest.modxcms.com/extras/

Well! I’d like to say I’m far too lazy to do that, but... It seems like an interesting challenge, as I’ve done rpc work before. Is it a "RESTful" interface (as the url implies), some form of XML-RPC, or SOAP?

It is a REST interface, although the POST parts of the rest interface are still being ironed out. It uses the modRestClient and modRestServer classes provided in MODx Revolution.

Huh. The server class is right there. Is this as complete as I think it is? Does it just need the proverbial "water"? Tho I’d still like see the environment this runs in.