On Jul 18, 2012, at 1:19 PM, jp.malr...@free.fr wrote:
It is logging now. Don't know if it's because it took time to start logging
output or if it is because I made the directory writable by apache...
It's not apache writing to the log folder It's the user running wotaskd...
Unless they
Hi guys,
This is something I'm thinking about for months, and since I see a lot of
people having issues with deployment, I have a couple of ideas to improve it.
1) To have REST actions inside wotaskd. By having that, we won't ever need
JavaMonitor to manage wotaskd. You could use curl or any
I think about this each day as I update apps on our servers. Jenkins makes it
easier, but the final install steps should be automated. However, each build
on Jenkins shouldn't necessarily go live. The final deployment step should
take a forced action or trigger to signify a deployable build.
So I successfully pushed my project to a git repo. so the obvious test is to
clone it back to my computer and see that everything is okay.
I cloned my repo and imported it into eclipse. it compiles and runs just fine,
thank you.
however, when I open the project (turn down the disclosure
Le 2012-07-24 à 09:05, Theodore Petrosky a écrit :
So I successfully pushed my project to a git repo. so the obvious test is to
clone it back to my computer and see that everything is okay.
So you enabled Git (git init) on your computer and pushed it to a remote
repository? You didn't need
Yup, most of the time you want to push a build automatically is for staging
servers. For prod, good chance that you want to do it at a specific time.
I think about this each day as I update apps on our servers. Jenkins makes
it easier, but the final install steps should be automated.
I understand that I didn't NEED to clone it back, I was being thorough and
checking to see if I cloned it to a second machine (at home) what would that
person see. This is my first time.
I just checked the bitbucket repo and the .settings directory is included.
but from an email from maik, I
Am 24.07.2012 um 14:22 schrieb Pascal Robert:
Hi guys,
This is something I'm thinking about for months, and since I see a lot of
people having issues with deployment, I have a couple of ideas to improve it.
1) To have REST actions inside wotaskd. By having that, we won't ever need
Le 2012-07-24 à 09:56, Johann Werner a écrit :
Am 24.07.2012 um 14:22 schrieb Pascal Robert:
Hi guys,
This is something I'm thinking about for months, and since I see a lot of
people having issues with deployment, I have a couple of ideas to improve it.
1) To have REST actions
Hi Paul et al.,
Am 20.07.2012 um 01:09 schrieb Paul Hoadley:
I've found that git-svn-clone does a pretty reasonable job of converting the
Subversion conventions for branches/tags into their Git counterparts.
Combined with git-filter-branch, you should be able to extract individual
Check the JavaScript console in your browser to see if any errors are there.
Hi,
I downloaded JavaMonitor from
http://jenkins.wocommunity.org/job/Wonder/lastSuccessfulBuild/artifact/Root/Roots/JavaMonitor.tar.gz
I installed it. It looks great! thanks guys. I just have a problem, it seems
You are right,
I found this error.
NetworkError: 404 Not Found -
http://mysite.com/WebObjects/Frameworks/Ajax.framework/WebServerResources/prototype.js;
The JavaMonitor application does not have the frameworks embedded?
Should I copy the Framework's WebServerResources to the Web Server folder?
Maybe I did something wrong during the WebObjects deployment environment
installation.
I followed this tutorial
http://wiki.wocommunity.org/display/documentation/Deploying+on+Linux
I copied the WebObjects folder to my webserver:
cp -rp /opt/Local/Library/WebServer/Documents/WebObjects
Copy the frameworks from JavaMonitor.woa/Contents/Frameworks into
/var/www/htdocs/WebObjects/Frameworks
Then remove /var/www/htdocs/WebObjects/Frameworks/*.framework/Resources
which will just leave the static resources *.framework/WebServerResources
On Tue, Jul 24, 2012 at 3:08 PM, WebObjects
On a similar subject, I'm trying to setup a new Lion server machine for
deployment. I'm trying to use these instructions:
http://wiki.wocommunity.org/display/documentation/Deploying+on+Mac+OS+X+Server
But I'm not getting very far because (I think) of changes made to Lion.
The first thing
On Jul 24, 2012, at 5:22 AM, Pascal Robert wrote:
Hi guys,
This is something I'm thinking about for months, and since I see a lot of
people having issues with deployment, I have a couple of ideas to improve it.
1) To have REST actions inside wotaskd. By having that, we won't ever need
Hi Jess,
I've always used the WOInstaller.jar option.
You create the directory:
/System/Library/WebObjects/Adaptors/Apache2.2
Seeing that this is a fresh install, you shouldn't have anything installed —
but if you did:
rm -f /System/Library/WebObjects/Adaptors/Apache2.2/mod_WebObjects.la
rm -f
Just as a follow up, I did run the Apple installer. If I now run the
WOInstaller will there be problems? Also, I think you need to specify a
destination when using the WOInstaller, but I don't see any directions saying
where that should be. Finally, since I ran the apple installer, shouldn't
I've never used the other installer. But, I don't think you'll have any
problems.
We install to:
/opt/webobjects
-G
On Jul 24, 2012, at 8:46 PM, Jeffrey Schmitz wrote:
Just as a follow up, I did run the Apple installer. If I now run the
WOInstaller will there be problems? Also, I think
That path should not be mysite.com/WebObjects/Frameworks/... but
mysite.com/WebObjects/JavaMonitor.woa/Frameworks/...
You could try to set -WOFrameworksBaseURL
/WebObjects/JavaMonitor.woa/Frameworks explicitly at startup though it is
strange that it is not set automatically to the correct
20 matches
Mail list logo
