search

vaimee / SEPA

Get notifications about changes in your SPARQL endpoint.
26 stars 10 forks source link

jpar files #23

Closed fr4ncidir closed 6 years ago

fr4ncidir commented 6 years ago

We should put them in .gitignore? In any case, I think they should be downloaded when cloning the repo, but modifications should be not checked.

relu91 commented 6 years ago

Yes I think they should be ignored. This way the jpar files that are already in the repository will be still downloaded, but we wouldn't be able to create new one or change the default one.

Maybe we could put them in a folder as an example or as reference documentation and ignore all the .jpar outside that location. What do you think?

lroffia commented 6 years ago

From version 0.9.1 the broker creates the defaults engine.jpar and endpoint.jpar (the latter uses the online instance of Virtuoso at mml.arces.unibo.it). Configurations for other endpoints can be provided in other ways (folders, readme, ...),