-
Notifications
You must be signed in to change notification settings - Fork 23
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
Dokumentation for oxalis deployment #692
Comments
@kevinbbb87 which particular issues did you face when trying it? |
Hi, Best, On 28 September 2015 at 20:25, Tom Bocklisch notifications@github.com
|
So you did follow the steps in the readme? It is normal that it takes quite some time during the first compilation since all the dependencies need to be downloaded. Please try You don't need any further dependencies except mongo, node and sbt. |
So here is what I know so far (Ubuntu 15.10 beta2 in VirtualBox)
creates many problems, better not to use at all
is good :-) I think it only creates a symlink so that nodejs can be found but whatever |
Startup
|
Then after opening localhost:9000 in the browser
|
Mhm the error seems to be pointing at a network connection problem while trying to download the dependencies. Could you please double check that the VM has a proper internet connection? |
Seems to be an issue with my local setup
|
so it seems like the git native protocol isn't working in the institute
to make myself happy |
didn't work again (see last line)
|
How much memory does your VM have? This is an "external" issue, the process gets killed (if it isn't you then it is most probably the system). The system might kill the process because it is running out of memory/swap space. |
ahh darn.. VM only had 768MB |
How much memory did you allocate for the VM in the end? |
5GB |
Reopen
|
I think the problem is
the wK interface opens but in a text only mode |
I can confirm that the installation instructions are not working. To reproduce the problem one has to delete
and then build. I am getting a lot of errors from npm then. |
Not sure what 'lot of errors from npm' is supposed to mean, but I changed the bower config. Can you please try again? |
@normanrz How can I test? Just try to rebuild without pulling again? |
Please try to rebuild after pulling (see 858f2fa on review). |
Just worked for me in an isolated environment. |
I will try tonight.. On 7 October 2015 at 15:10, Norman Rzepka notifications@github.com wrote:
|
@kevinbbb87, are there any remaining issues that need clarification? |
@tmbo I couldn't test yet, computer had to stay in the institute |
will try tonight |
So I tried it again, there were a lot of
messages (all bitbucket), but it works nicely nonetheless |
Bitbucket did network maintenance today. Maybe that was the issue. |
perhaps.. but I did just minutes ago and bb seems to be live again (but the link I posted is still dead) |
improve explanation for self-deploy. I tried to set up wK in a VM and failed. Perhaps you can help me get it done (this VM will probably be made available for the public to allow rapid deployment of their own wk Server). On the way we can improve the explanation
Log Time
The text was updated successfully, but these errors were encountered: