Databases
StackOverflow2013
Postsdbo
POMagento - using "mage" command line tool locally
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMagento - using "mage" command line tool locally
    primarykey
    data
    text
    <p>I currently have Magento set up on a development server (remote, SSH access) and production server (Cloud instance, SSH access). The current set up is a subversion export to update the development/production servers. This works swell.</p> <p>If I SSH into the dev server, I can navigate to the Mage root directory and run the following command:</p> <pre><code>./mage install community Namespace_Module </code></pre> <p>This works well on the dev server. However, when I navigate to my local path (on my machine, where I've <code>svn co</code>'d Magento), running the <code>mage</code> tool always chokes when a <code>channel</code> is involved. As an example, I tried:</p> <pre><code>./mage download community Namespace_Module </code></pre> <p>And received the following response:</p> <pre><code>Error: download: Uri doesn't contain host part </code></pre> <p>I don't understand why this error occurs. I have looked into the mage tool's code and found that the error occurs when the <code>channel</code> URL is malformed. (The mage tool is basically a PHP script, and it uses <code>parse_url</code> to separate the <code>channel</code> URL into the appropriate parts for processing.) However, I am absolutely certain that the setup is identical locally, as it's all in <code>svn</code>, and I have tried many iterations of channels in an attempt to make it work locally.</p> <p>The ultimate goal of all of this is to be able to run the <code>./mage</code> tool to install modules on the local system, and commit them to <code>svn</code> from there. Ideally, running an <code>svn status</code> command should show me all the files that would be added/modified during the installation of the module.</p> <p>Anyone have any ideas as to why this might be happening and how to make it run locally? Thanks!</p> <p><strong>UPDATE</strong></p> <p>For anyone wondering, the way I handled this was using the old <code>pear</code> command line tool, then running <code>svn status</code> to extract the downloaded package pieces into the way our systems are organized. It's definitely not ideal and I am still eagerly hoping to get an answer to my original question, but it's the ugly and painful workaround I'm using in the interim.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJona
    1. USJona
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI'm not too familiar with the `mage` command line tool, but [this article](http://www.yireo.com/blog/1294-magento-15-mage-command-line) shows some of the channels being supplied as a full URL. Maybe give that a try.
      singulars
      1. POMagento - using "mage" command line tool locally
      1. USjprofitt
    2. COI'm afraid I've tried that as well, with no luck. (Just tried again to be double sure.) I still get the same error as above, though - "uri doesn't contain host part."
      singulars
      1. POMagento - using "mage" command line tool locally
      1. USJona
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload