ports #9911
Comments
|
It's difficult to say without knowing more specific details, usually our docker-compose container is all the virtualization someone will need to run the OSF locally for standard OSs. If you want to set up up a docker container inside a virtual environment, you're going to have to make sure both are networked correctly to access them. So, for example, you don't need to expose the 5432 (the postgres port number) in your environment because that already exposed within docker. Virtual machines vary widely so this may be different for you, but hopefully that points in the right direction. |
|
Thanks for the swift answer! Sorry for the bad phrased question. There will no container within the virtual machine involved. Just the virtual machine. Does that make it easier? |
|
To set up our entire environment without using Docker is pretty difficult, I wouldn't recommend it. But if you just want to see what the site looks like locally using your virtual machine, just open the ports you need for whatever it is you are doing. So if you need to access the actual site, that port is 5000, the REST server is 8000, file server (waterbutler) is 7777 etc. These services really depend on each other to work, that's why I recommend using docker-compose, it's very difficult to have everything setup under one virtual machine. But it really depends on what your virtualization strategy is. |
|
Thanks again. Maybe it is then easier for me to try with docker-compose on a real machine. What ports need to be accessible on the real machine? If I test it locally only, are there still ports that need to be accessible? |
|
The docker-compose and Dockerfile define the accessible ports. They should be accessible from the browser via your localhost for example url |
|
Thanks again for the swift reply. I am now using docker-compose and follow the instructions here. Unfortunately, when running the migrations, there is a problem with the communication to the database: But the postgresql container is started without errors: The loopback is created and the port seems open and reachable: I've closely followed the instructions. Only change I had to make was to reduce the What could be wrong here? |
|
Based on these it seems as though postgres, (port 5432) is unaccessible, but it does look based on the postgres log you provide that postgres is actually running fine, so it's difficult to say what the problem is. If you had to change the |
|
Thanks again for your comment! Highly appreciated. I've now run the steps on a different (virtual) machine and indeed I can now run all the steps from the (the port is open ) Any hint how to proceed here? |
|
It looks like your Slowest Nodes (totalTime => 5% ) | Total (avg)
----------------------------------------------+--------------------
Babel: ember-osf-web (2) | 98653ms (49326 ms)
Babel: registries (2) | 67215ms (33607 ms)
Babel: analytics-page (2) | 60147ms (30073 ms)
Babel: osf-components (1) | 39314ms
Babel: ember-source (5) | 32158ms (6431 ms)in the ember_osf_web logs when it's finished building. |
|
Thanks again. I got this resolved! The local instance is now (kind of) running. The initial page loads a long time, but does not show anything else besides the header. After switching to 'Support' and the back to 'OSFHome' there is some content below some large white space. Is that a known thing? |
|
The header with no page is actually a unintended result of how the routing is configured locally, admittedly it's a bit confusing, but if you go to |
|
Thanks so much for the again swift reply. This is really great! I am still struggling to set this up properly, however. The improper loading I can circumvent if I follow the instructions more closely and browse to 'localhost:5000' on the machine with OSF itself. But that is a remote server and I would rather access it from a browser at my desktop. If I go to <ip.of.remote>:5000 this does not work properly (as described in my previous post). So, my first question would be the steps to make the OSF installation properly accessible from other computers rather than localhost only. My second issue is, that registering a new user does not work, as no confirmation email is sent out. Any hint, what might cause this? |
|
Second question first:
This is because the email service is not set up, you still have many elements to configure, (email, authentication .etc) to run OSF exactly as you would in a finished state, like the virtualization, how you set up the email is up to you. When I am developing for the OSF and want to create a user account locally I will check the the docker-compose logs. The web container's logs are configured to print the info any email it would have sent had the email service been set up, so they are valuable info for testing and development. Now the first question:
This is a broad question and there's many answers, it really depends on how you want to configure your network. We at COS have a very complex and frequently changing network environment that we are constantly improving so there's not a simple "do this" answer. However if I wanted to set up a small clone of the OSF I would use a cloud service, we are use Google Cloud Service now, but any other implementation is necessarily going to differ from ours because the scale of our operations. It really depends on what your resources are, and what your desired use case is. If you just want to explore the code or test features, I recommend tunneling via ngrok, that can make ports publicly available for testing with limitations. Ultimately there's no single answer to give here. |
I am trying to setup a local dev instance following the readme. I'd like to do that in virtual machine. When setting up the virtual machine, I need to specify the ports that need to be opened.
Hence, my question: Which ports need to be accessible? Are all ports in the docker-compse.yml needed to be open?
Thanks in advance!
The text was updated successfully, but these errors were encountered: