Downloading Revolution via SVN

☆ A M B ☆
1,056 Posts

pixelchutes Reply #71, 18 years, 9 months ago

Quote from: marazmus at Dec 27, 2007, 12:41 AM

1) rename build.config.sample.php to build.config.sample

I think it should be:

1) rename build.config.sample.php to build.config.php

Thanks for the quick steps!

Quote from: My

Execution time: 56.8098 s

:) This newest revision is slick!

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.

623 Posts

cbaone Reply #72, 18 years, 9 months ago

404 not found! Hmm. I’m running MAMP. Everything went smoothly until I put in the URL: http://localhost:8888/MAMP/htdocs/modx097/setup/ - Not Found
The requested URL /MAMP/htdocs/modx097/setup/ was not found on this server.>

Apache/2.0.59 (Unix) PHP/5.2.1 DAV/2 mod_ssl/2.0.59 OpenSSL/0.9.7l Server at localhost Port 8888]

Anything anyone can think of off-hand?

Thanks. I’m really looking forward to this release!

The MODx has you...
Utah Web Design

7,075 Posts

davidm Reply #73, 18 years, 9 months ago

Did you follow the instructions and rename build.config.sample.php to build.config.php, edit it with proper info and then execute the command "php transport.core.php" from the command line before trying to go to the setup ?

I have installed 0.9.7 with MAMP 1.7.1 /OS X 10.5.1, with no such issues...
Nothing comes to mind, except check the changeset maybe you downloaded a broken rev ?

.: COO - Commerce Guys - Community Driven Innovation :.

MODx est l'outil id

4,205 Posts

dev_cw Reply #74, 18 years, 9 months ago

http://localhost:8888/MAMP/htdocs/modx097/setup/

Shouldn’t the URL be:

http://localhost:8888/modx097/setup/

I don’t think that you need the MAMP/htdocs part.

I create virtual hosts for each project so that I can isolate them like: www.mylocalprojectname.tld:8888 (or for a real world example www.modx961.loc:8888/ ) this just makes it easier to work for me. It is a very easy process to do this manually or you can use MAMP Pro which has the needed features to do this for you.

[font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

Something is happening here, but you don't know what it is.
Do you, Mr. Jones? - [bob dylan]

☆ A M B ☆
24,524 Posts

sottwell Reply #75, 18 years, 9 months ago

No, the MAMP/htdocs is part of the file path (/Applications/MAMP/htdocs), not the URL. The web root starts in the htdocs directory. If you’re using the pro version you can have your web root wherever you want it.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

4,205 Posts

dev_cw Reply #76, 18 years, 9 months ago

If you’re using the pro version you can have your web root wherever you want it.

I think you can change the root location in the standard version as well, but you need to manually edit the etc/hosts and the httpd.conf (the one in MAMP) file to add new virtual hosts. The only advantage I see is that you get to run all your local projects at root level on their own virtual host, which I find cool, and have them in any folder on your computer (sites do not need to be in the MAMP/htdocs folder, which is also way cool. You can transform any local directory into a virtual server.

I have attached my notes on how to do this with MAMP Standard in case anyone is interested.

[font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

Something is happening here, but you don't know what it is.
Do you, Mr. Jones? - [bob dylan]

213 Posts

rav3n Reply #77, 18 years, 9 months ago

ok i exported from SVN, then built it, then tried to install. nb: script is using much memory so you should set your php.ini like this:
max_execution_time = 360 ; Maximum execution time of each script, in seconds
max_input_time = 120 ; Maximum amount of time each script may spend parsing request data
memory_limit = 32M

or you’ll get white screen on install step

MODX Staff
10,725 Posts

opengeek Reply #78, 18 years, 9 months ago

Quote from: rav3n at Jan 20, 2008, 07:08 PM

ok i exported from SVN, then built it, then tried to install. nb: script is using much memory so you should set your php.ini like this:
max_execution_time = 360 ; Maximum execution time of each script, in seconds
max_input_time = 120 ; Maximum amount of time each script may spend parsing request data
memory_limit = 32M

or you’ll get white screen on install step

Agreed the install step likely needs some optimization and refactoring to free memory properly, but I do not recommend changing the max_execution_time and max_input_time in php.ini -- the script itself uses ini_set() to alter the max_execution_time just for the request involving the installation step. The memory_limit change likely is needed for now.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

332 Posts

chinesedream Reply #79, 18 years, 8 months ago

Quote from: davidm at Jan 12, 2008, 04:03 AM

Did you follow the instructions and rename build.config.sample.php to build.config.php, edit it with proper info and then execute the command "php transport.core.php" from the command line before trying to go to the setup ?

I have installed 0.9.7 with MAMP 1.7.1 /OS X 10.5.1, with no such issues...
Nothing comes to mind, except check the changeset maybe you downloaded a broken rev ?

I rename the build.config.sample.php and entered my database info, but I don’t know how to execute the command "php transport.core.php" from the command line embarrassed

24,544 Posts

BobRay Reply #80, 18 years, 8 months ago

Quote from: chinesedream at Jan 21, 2008, 09:15 PM

I rename the build.config.sample.php and entered my database info, but I don’t know how to execute the command "php transport.core.php" from the command line

You can just type localhost/_build/transport.core.php in your browser’s address window (unless the site is in a subdirectory, then you’ll have to add the subdirectory name after localhost).

Or, you can shell out to the OS, navigate to the _build directory and type php transport.core.php (this will only work if the php client is in the include path or if you give the full path to the php client on the command line).

Bob

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting