how to pull from a separate Fedora instance #86
Comments
|
@jmcgranahan If you are wanting to connect Avalon to a separate Fedora 6 instance, you should be able to do this by editing the It should also work setting these in These environment variables are used in this initializer to setup the Fedora connection. |
|
@cjcolvar unfortunately there's been no change - either when adding the FEDORA_URL to the .env or updating the docker-compose.yml. Should the Fedora container even be running if we are trying to connect to an external Fedora 6 instance? When I look at the logs for the Fedora container, I see no indication it is even pointing to our external Fedora instance - it all appears to be local. Ideas? Current .env |
|
Setting The Fedora container doesn't need to be running but that shouldn't impact things. To avoid running the fedora container, you can comment out |
|
Unfortunately, no @cjcolvar - nothing unusual at least. I did log into avalon-docker-avalon-1 and confirmed we can access the external Fedora system using wget (after installing it) so at least I know it's not a firewall issue. It just appears to be ignoring the .env file and I'm not sure why : Avalon logs: Fedora logs: |
|
Without anything in Avalon's log, I think it is possible that Avalon is connecting to the external Fedora but that it isn't apparent. You can see the config that Avalon is using by running: The output should look like: |
|
@cjcolvar Running that command I get the following output:
Should there be something for "base_path"? Also, if it was connecting to our Fedora instance, shouldn't it be pulling in our collections? We did setup the FEDORA_NAMESPACE to a single namespace that we know is in our Fedora instance, yet we're not seeing any of its content in Avalon. |
|
|
|
@cjcolvar - here's our docker-compose.yml file. Maybe you can spot something that is out of whack: |
|
Try changing this line in your docker-compose.yml and restart. |
|
Before we continue beating this to a pulp here, is there anyway I can confirm Fedora connection within the Avalon app? Just launching the app (which I can access) I just have a blank slate so I would assume it is not finding our Fedora collections but I just am not sure. |
|
Is there Avalon content in your Fedora? If you know of a particular item by id then you could test if avalon is able to load it as a generic object from the rails console as a first step. For instance for a test system I have with this fedora config: and an item with avalon url of |
|
Looks like I'm getting a 500 error when running that rails command. |
|
I think there may be a misconception here. We were under the impression that Avalon could serve as the Front End for Fedora - so this statement, "Is there Avalon content in your Fedora?", wouldn't apply - it's all Fedora data @cjcolvar
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like Fedora is part of the package here, but we are needing to link Avalon to a separate Fedora instance (that is running Fedora 6). Before I start mucking around in the code, thought I would ask here if there was any guidance or anyway to do this easily.
<style> </style>The text was updated successfully, but these errors were encountered: