vmware-archive / webcommander

Powerful, flexible, intuitive and most importantly simple. That is what a real automation solution should be. No matter how complicated the task is, we'd like to turn it into a single click. Is that possible? Not without webcommander :)
MIT License
165 stars 47 forks source link

Install issues..... #119

Closed mikemast01 closed 8 years ago

mikemast01 commented 8 years ago

I follow the install and config page, but when i go to the webcommander page on my server I get "This XML file does not appear to have any style information associated with it. The document tree is shown below.".... and then it shows me the index.xsl text on the screen. I fell like I missed something, and went thru the document a few times and cant figure out what.. Thanks for any help in pointing me in the right direction.

Mike

9whirls commented 8 years ago

Please open http://your_server_address/webcmd.php in your browser and post a screenshot and source code (right click on the page and select "view source") here.

mikemast01 commented 8 years ago

image

mikemast01 commented 8 years ago

<?xml version="1.0"?>

<?xml-stylesheet type="text/xsl" href="index.xsl" ?>

This command generates _def.xml. It parses all powershell scripts to get information from comment based help and parameter attributes. This is an example python command Python This is an example ruby command Ruby This is an example perl command Perl
mikemast01 commented 8 years ago

It does not look like I can copy and paste the source... So I attached it....

source.txt

9whirls commented 8 years ago

It works well. webcmd.php is the entry point. If you download from walnut branch, entry point is index.html

mikemast01 commented 8 years ago

OK.. the site defaults to index.xsl when it is installed.. does that need to change to webcmd.php ?

mikemast01 commented 8 years ago

so i Hve the webcommander-master.. should I use the walnut branch? what is the difference?

9whirls commented 8 years ago

Yes, it's better to change webcmd.php to be the default. If setup.ps1 works for you, this is configured automatically. https://github.com/vmware/webcommander/blob/master/powershell/Install/setup.ps1#L167

mikemast01 commented 8 years ago

it worked, but index.xsl was set as default.

PS C:\Users\admmmasters> C:\WebCommander\powershell\Install\setup.ps1 Downloading WPI ... WPI downloaded successfully. Downloading WebCommander package... WebCommander package downloaded successfully IIS is already installed. Web Platform Installer is already installed. PHP is already installed. Extracting WebCommander package... WebCommander package extracted successfully. Stopped all existing websites. Creating WebCommander website... WebCommander website created successfully. Configuring website authentication... Windows authentication is enabled. Changing x86 Powershell profile... Powershell profile changed successfully. Changing WSMAN settings... WSMAN settings changed successfully. PS WSMan:\localhost\Client> C:\WebCommander\powershell\Install\setup.ps1

9whirls commented 8 years ago

If you never used webcommander before, I recommend walnut because it contains all latest features.

mikemast01 commented 8 years ago

Ok I will look into installing walnut and see... Thanks for the quick responses .

9whirls commented 8 years ago

You are welcome. Please note that master and walnut could co-exist on the same server. Considering you already have master setup, you could just download walnut zip and extract it in the folder where you install master.

https://github.com/vmware/webcommander/archive/walnut.zip

mikemast01 commented 8 years ago

I got walnut working on another port another site, so I can look at both, while I get used to working with webcommander.

9whirls commented 8 years ago

That's smart.

9whirls commented 8 years ago

I forgot to mention yesterday. If you run walnut at any other port than 80, you need to modify sources.json to make local scripts show in the command list https://github.com/vmware/webcommander/blob/walnut/sources.json#L2

mikemast01 commented 8 years ago

in what file? That is where I am a little confused, on this and I am trying to figure out. is how the scripts show up in the list, and how to make it so only certain ones show up in the list.?

9whirls commented 8 years ago

In webcommander\sources.json, you could add multiple URLs to command definition files. A command definition file, also in JSON format, includes mulitple script definitions. The definition file could be generated automatially from powershell scripts by running genDefJson.ps1

mikemast01 commented 8 years ago

Thanks, I am figuring this out as I go. Is there a way to get rid of the "example perl/Pyton/ruby command" from showing up? I modified the def file to get only the scripts I want to show, but those are still listed.

Thanks

9whirls commented 8 years ago

Sorry, I was ralking about walnut. For master, just remove perl, python and ruby folders.

mikemast01 commented 8 years ago

Thanks so much, you are awesome. I have been writing scripts for customers to use, and they run them thru citrix after I compile to a exe... I have been looking for a web interface that would be better for users to use to create snaps, delete snaps and console access, and this looks great.

9whirls commented 8 years ago

Cool. Once you feel comfortable to use webcommander, please think about contributing your scripts. Your valuable work could also benefit others! BTW, do you mind let me know which company you work for?

mikemast01 commented 8 years ago

Thanks , will do.. I work for Emerson.

http://www.emerson.com/en-us

9whirls commented 8 years ago

Nice. Got 1 more fortune 500 user :)

mikemast01 commented 8 years ago

LOL…

Web Commander will be a good starting point for me to develop something internally for us to use.

Mike Masters | VMware Administrator | Emerson | 8000 W. Florissant Ave. | St. Louis | MO | 63136 | USA T +1 314.553.2542 | F + 1 314.553.1491 | M +1 314.502.8914 CompTIA | A+ , Net + , Sec. + VMWare | VCP 3,4,5 VCAP5-DCA MCITP | 2008 SA/VA

From: Jerry Liu [mailto:notifications@github.com] Sent: Tuesday, February 02, 2016 3:25 PM To: vmware/webcommander Cc: Masters, Mike [CORP/US] Subject: Re: [webcommander] Install issues..... (#119)

Nice. Got 1 more fortune 500 user :)

— Reply to this email directly or view it on GitHubhttps://github.com/vmware/webcommander/issues/119#issuecomment-178829010.

9whirls commented 8 years ago

That sounds a great plan! Looking forward to getting your pull requests.

virtmann commented 8 years ago

Any plans for updating the installation wiki page to cover walnut?

9whirls commented 8 years ago

It is the same. Once you setup by following the wiki, copy walnut code to c:\webcommander.