-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
comments on using ww_install in vagrant (ubuntu 14) #78
Comments
Thanks Mike - what os are you using for the vagrant install? The apreq and soap stuff has worked in the past on ubuntu and works on On Wed, Jul 30, 2014 at 6:06 AM, Michael Gage [email protected]
|
Ubuntu 14.04. I might be wrong about the soap stuff the mk directory glitch might have been a side affect. But I notice that Davis gage also needed that in his original script Main thing is to think throug options for installing WW pg and library files Mike Sent from my iPhone On Jul 30, 2014, at 12:36 PM, "Jason Aubrey" <[email protected]mailto:[email protected]> wrote: Thanks Mike - what os are you using for the vagrant install? The apreq and soap stuff has worked in the past on ubuntu and works on On Wed, Jul 30, 2014 at 6:06 AM, Michael Gage <[email protected]mailto:[email protected]>
Reply to this email directly or view it on GitHubhttps://github.com//issues/78#issuecomment-50642262. |
Michael, I also got the same errors when using the shared folders. Using There doesn't seem to be a way to change ownership after mounting which is why I chose to set the ownerships to www-data and wwdata so that the server has permissions to do what it needs to do. All other files can be changed locally on the host machine without ownership problems. With these changes, to set up a dev site will essentially involve the following steps:
|
in order to create Apache2::SOAP you need to manually create:
/usr/include/apache2 ??
Where should I install webwork? [/opt/webwork/]: /opt/webwork/
Error! You gave me a path which already exists on the filesystem.
1> Enter new location
2> Delete existing /opt/webwork and use that location
3> Quit
How would you like to proceed? [1]: Enter new location
------ in the Vagrant use case the webwork2, pg, and libraries are likely to be installed already
--- I can copy that line onto the command line and it fails because of permissions. If I use sudo it works. If I change all the permissions to 777 it works from the command line but still doesn't work seem to work from the admin page. Haven't been able to track it further yet.
-- Can you duplicate this behavior? It might be a fluke of some kind.
$externalPrograms{checkurl} = "lwp-request -d -mHEAD";
$externalPrograms{curlCommand} = "";
should be set by
these can be very handy for debugging. (paths are only approximate)
not sure why it's searching for log there in users home directory
worked pretty well. if we can allow for existing repos of webwork2, pg and libraries
it will probably be pretty fast as well.
The text was updated successfully, but these errors were encountered: