Cloudron Forum

@girish

Why do you think this is a CORS issue?

Because the HTML itself delievered by Omeka loads scripts, images, css etc. from the domain of origin. This causes the CORS issues.

@jeau Thanks for the suggestions, and sorry for replying this late. However: Happy New Year!

I don't think that using iFrames to embed an omeka exhibition is very convenient for the user, because he loses the ability to refer to or set a bookmark for a specific page.

Sorry, now I get it.

I just have to register the external domain example.org in the Domain Panel and then create an alias in my surfer app with no entry.
(That's why it says "Leave empty to use bare domain").

Thanks for pointing me in the right direction.

Aliases and Redirects do not provide the behaviour I would like to achieve.

For example, I have a surfer app at surfer.example.com with in index.html that prints out "Hello Surfer World". Additionally I have a external Domain like example.org . I want to set up this domain in a way that when I enter https:://www.example.org in a browser window it would serve my index.html with "Hello Surfer World".

I my understanding this would require the ability to alter the primary cloudron nginx.

I hope this hasn't been asked many time but i couldn't find any relating entry, so ...

On my cloudron server the surfer app just runs fine. But I wonder if i could point seperate domain to a single surfer app. So let's say my surfer is up and running at https:://surfer.<cloudron>.<tld>. Now i have a separate domain like https://<my-private-site>.<tld> which should serve the content from the surfer app.

In a standard enviroment i would simply adjust the nginx-settings to redirect the domain to the surfer-domain. But how would you do that the cloudron way?

We are using Omeka S on Cloudron as an host for several online exhibitions.

Because something like https://omeka.<cloudron>.<tld>/s/<my-exhibit> is not a very nice and memorable URL, we would like to embed these exhibits in our primary website to get URLs like https://www.<museum>.<tld>/virtual-exhibits/<my-exhibit>.

We configured our nginx to handle these URLs and to get the content from Omeka, but we ran into a Cross-Origin Resource Sharing (CORS) issue. Searching the forum i found several entries regarding to CORS (e.g. Bug: CORS error), but there doesn't seem to be a consistent solution. In https://forum.cloudron.io/post/64706 @girish gives a quick workaround, but this is not consistent.

As this issue wasn't addressed in the specific forum and time goes by, i wonder if someone knows a solution for the scenario above. I'm pretty sure I am not the only one with this requirement.