Login to download the latest version of Mint and your favorite Pepper, purchase additional licenses, or post in the Forum. Don't have an account? Create one!

In Partnership with Media Temple

Mint Forum

Mint, Media Temple, and Rails Containers

I’m installing Mint at Media Temple with SimpleLog in a Rails container.

I added…

RewriteCond %{REQUEST_URI} ^/mint.*
RewriteRule .* - [L]

…to my .htaccess, and uploaded the mint folder to my /public directory, and I know it’s not helpful, but I’m getting this error…

[500]: Application error (Apache)
Sorry, there was an error processing your request. Please try again or contact the site administrator.

…I’ve submitted a ticket to Media Temple to see if this is on their end because of the way the Rails containers are setup. Has anybody else worked with Mint in a Rails Container?

Looks like I might have sorted this out. I was hitting /mint and it wasn’t recognizing the index.php automatically. Once I explicitly went to /mint/index.php it worked.

I’ve updated the .htaccess to include index.php as the DirectoryIndex, but it’s still not working. I can access it explicitly using index.php, but the script isn’t picking up any data since the mint script tag doesn’t reference the index.php file.

I suppose theoretically, I could change the Mint script, but I think getting the htaccess working would be a better solution.

Shaun Inman
Mint/Pepper Developer
Posted on Feb 05, '07 at 09:53 am

John Topley seems to have figured this out.

Shaun - I’m no htaccess/rewriterule whiz, but Media Temple runs its containers on a proxy. It’s a bit over my head, but it seems that as a result, the “simple” problem is that the .htaccess file that sets index.php as a directoryindex is being ignored.

I’ve sent several support requests to Media Temple, but haven’t had a response in 3 days. I’m hoping it’s just because of the weekend. I’ll post any updates here if I hear from them.

garretdimon - You should give MediaTemple a call, they are always backlogged with emails, but everytime I’ve called them I’ve gotten right through, and solved the problem in one exchange. It’s a lot better than going back and forth over 20 plus emails.

Which I bet Shaun is loving right now ;-)

dummied
Minted
Posted on Feb 26, '07 at 08:51 pm

The answer, as it turns out, is to install Mint on a subdomain (ie. mint.yourdomain.com) and then point your rails stuff there.

Media temple has instructions for subdomain creation and it’s really that simple (two folders, one in /domains with your proposed subdomain name and another html folder inside of that).

Then just stick the mint folder in that html folder, make sure everything’s pointing to the right spot, and you should be good to go.

(for the record, Garrett had this answer already …)

Bruno
Minted
Posted on Mar 29, '07 at 04:14 pm

I have the same problem getting mint 1.2 to work for a rails app on a Media temple GS container. I moved mint to it’s on sub domain. And modified the script tags in my htm files to look at the new mint location but mint is still not recording the visits.

The tag looks like this:

script src=”http://mint.mydomain.com/?js” type=”text/javascript”>script

where mydomain is my actual domain name.

If I browse to mint.mydomain.com I am able to login to mint and see all the stats except for new stats which are not being recorded.

Thank you!

Shaun Inman
Mint/Pepper Developer
Posted on Mar 29, '07 at 05:36 pm

Could be a Site Domain(s) preference/config problem. Which of your sites are we talking about? bo…com be…com or bi…com?

Bruno
Minted
Posted on Mar 29, '07 at 06:20 pm

bitemyphoto.com.

I have mint running under mint.bitemyphoto.com

Thank you!

Shaun Inman
Mint/Pepper Developer
Posted on Mar 30, '07 at 09:56 am

You appear to have two calls the the Mint JavaScript include on your homepage (once in the <head> tag and again before closing the <body> tag). Other than that (which is potentially causing the problem you describe) everything appears to be working as expected.

Bruno
Minted
Posted on Mar 31, '07 at 07:08 pm

Removed the extra tag and still no go. Could it be something on the db, maybe because I exported the db from the old host into the new one, something might be locked.

I tried double checking everything.

Does it make a differece that mint is on the root of mint.bitemyphoto.com and not inside the /mint folder?

Do I have to have anything special inside my .htaccess file? These are the contents of my .htaccess file now

MTSTART — Automatically generated, don’t modify —

RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.)$ http://1.2.1**.16:2010/$1 [P]

MTEND

Bruno
Minted
Posted on Mar 31, '07 at 07:14 pm

I have noticed that under Mint: Preferences: configuration, Mint location is set to the old location: bitemyphoto.com/mint and when I try to change it tries to forward here: http://mint.bitemyphoto.com/mint where I get a 404 file not found, because mint is here http://mint.bitemyphoto.com

Shaun Inman
Mint/Pepper Developer
Posted on Apr 02, '07 at 10:11 am

Add ?moved to your current Mint installation url. That should update it’s internal pointers. Everything else about your installation checks out. I wonder if there’s a conflict with the other JavaScript you have on the page (I know prototype changes the array and object prototype properties— which could interfere with Mint).

Have you tried tracking a static HTML page with just the Mint JavaScript?

Bruno
Minted
Posted on Apr 03, '07 at 09:46 am

It works now, it was a discrepancy between where mint was to where mint preference page thought mint was. My dumb mistake.

Thank you!

You must be logged in to reply. Login above or create an account