Hi, recently i opened an issue on github, as i have problems accessing my omeka s istance through a reverse proxy. Perhaps it is a trivial question. Here is the link to the issue: https://github.com/omeka/omeka-s/issues/1763
Would you have an idea on how to proceed?
Giacomo
Indeed, any setting you set in local.config.php overides the omeka ones, so you can add the needed params :
'file_store' => [
'local' => [
'base_path' => 'xxx',
'base_uri' => 'yyy',
],
],
Thank for the reply.
This would only apply to the files, how could i then change the internal address everywhere else in the website?
e.g.
{
"@context": "http:\/\/193.175.29.222\/refa\/api-context",
"@id": "http:\/\/193.175.29.222\/refa\/api\/items\/1",
"@type": [
"o:Item",
"ecrm:E22_Human-Made_Object"
],
"o:id": 1,
"o:is_public": true,
"o:owner": {
"@id": "http:\/\/193.175.29.222\/refa\/api\/users\/1",
"o:id": 1
},
"o:resource_class": {
"@id": "http:\/\/193.175.29.222\/refa\/api\/resource_classes\/194",
"o:id": 194
},
"o:resource_template": {
"@id": "http:\/\/193.175.29.222\/refa\/api\/resource_templates\/2",
"o:id": 2
},
"o:thumbnail": null,
"o:title": "Title of the item",
...
I have no good idea for that, except fake your proxy.
solved in the github issue
system
Closed
September 17, 2022, 2:16pm
6
This topic was automatically closed 250 days after the last reply. New replies are no longer allowed.