Make automatic transfer of terms.rdf to website

[stschiff]

We will host the file terms.rdf on our website, but we'd like to keep it in this repo, since it's a core part of the schema definition and therefore needs to be in the core development repo.

Is there some way to automatically copy it over to the github.io repo every time it's changed?

[maxibor]

Or just link the raw file url in the website ?
Also.rdf files are also natively rendered by Firefox: for example https://cldf.clld.org/v1.0/terms.rdf will be rendered with Firefox, but downloaded with other browers (as of now)

[stschiff]

Well, it needs to be accessible from a simple and persistent URL. Technically that's possible via raw link to GitHub, but it's ugly and I want a safer thing. As I wrote in another issue, in the end we want to host this via a persistent URL like http://w3id.org/poseidon/terms.rdf.json. In the end we might even use that to dynamically host URIs like http://w3id.org/poseidon/individidual_SUT001 or so (but that's a different story). So we definitely want that GitHub.io page to host static files that is accessible via the w3id.org persistent URL. Happy to discuss more about this. For now, we should just take care that whatever web-framework we use to host poseidon-framework.github.io needs to be able to host static files.

[maxibor]

So, doing a bit of digging around, a Git submodule would be probably the way to go by having the poseidon-schema repository as a submodule of the poseidon-framework.github.io repository

[stschiff]

Hmm, I dislike that. I'd like to keep the repos separate. My few explorations in the world of submodules have always left me with severe headaches. I was more thinking about some dynamic way of hosting this. So if a HTTP request comes in for terms.rdf.json, we somehow serve it dynamically from within this repo?

[nevrome]

To answer the initial question:

Is there some way to automatically copy it over to the github.io repo every time it's changed?

Ja. This can be done e.g. via travis. Push certain files to repo B whenever there is a change in repo A. I used systems like this in the past.

[stschiff]

Ah, perfect! OK, we need to set this up then. Sounds good!

[nevrome]

For my master thesis I used travis to clone several repos, render a document with content from all of them and then push the document to a new branch.

https://github.com/nevrome/neomod_textdev/blob/master/.travis.yml
https://github.com/nevrome/neomod_textdev/blob/master/_deploy.sh

A setup like this requires some trial and error. I can offer to create it, but only if I get full admin rights on both repos (of course only for this task). I don't want to poke around with PRs and forks to make this work.

[stschiff]

OK, I agree. So, you all have now write permissions on all repos, but the master branch is still protected. Can you handle working with a non-master branch, or do you need to be able to temporarily push to master directly?

[nevrome]

I think 7317387 provides a general, working setup. Now: What exactly is this supposed to do? I'm just copying one file right now to the root of poseidon-framework.github.io.

@stschiff You can edit the .travis.yml and the deploy script according to your needs. You can also change which user should apply the changes by replacing the encrypted GITHUB_PAT variable following this guide. Unfortunately this always has to be user-based imho.

[stschiff]

OK, perfect. I'll have a look (also wanted to learn a bit about Travis anyway). Now we just need to host that file on the GitHub page. I'll start an issue there to get this done. I'll leave this issue open for now until I understand your change. Thanks.