Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aaron B's POC and Vagrant, Docker work #1

Closed
wants to merge 21 commits into from

Conversation

Projects
None yet
6 participants
@birkland
Copy link
Contributor

commented Apr 27, 2016

No description provided.

birkland and others added some commits Mar 31, 2016

Fix Vagrant + Virtualbox disk mounting weirdness
Virtualbox shared folders have lots of caveats and limitations.  Vagrant
automatically mounts Dockerfile build directories when building.  This
can lead to a situation where the shared directories from Vagrantfile and
DockerHostVagrantfile overlap, causing unsightly locking error messages
from Virtualbox.  This workaround switches DockerHostVagrantfile mounting
to rsync (once at startup), allowing Docker build mounts using vbox shared
folders to work without conflict
Add go proxy and wrk tools
wrk can be used to measure latency & throughput of API-X, while
the go proxy is a simple reverse proxy for demonstration, benchmarking,
or comparison purposes.  Both compile to native code, so docker-compose.yml
compiles them in containers before building images from them.  The resulting
binaries are static, and should work on any Linux x86-64 system.
Bump Camel, fcrepo-camel versions
Currently, Camel is at 2.17.0.  An attempt to use the latest
snapshot (containing fix for CAMEL-9462) didn't seem to work due to
validation of the blueprint schema contained within camel-blueprint.
Upgrading to 2.17.0 caused an exception due to read on a closed stream.
Using the jetty producer endpoint (as oposed to http4) seems to be
a workable solution.

https://issues.apache.org/jira/browse/CAMEL-9462
README.md Outdated
* You should see Fedora, with an empty root container
* Create an object through Fedora's UI
* point your browser to Fuseki at `http://${ADDR}:3030/fcrepo`

This comment has been minimized.

Copy link
@awoods

awoods Apr 27, 2016

Member

Should this instead be:
http://${ADDR}:3030/fuseki ?

This comment has been minimized.

Copy link
@acoburn

acoburn Apr 28, 2016

Contributor

No, the DEFAULT_FUSEKI_DATASET is "fcrepo". This is correct, as I understand it.

This comment has been minimized.

Copy link
@ajs6f

ajs6f Apr 28, 2016

Contributor

That might be better changed to "fedora_triple_index" or something like that. Or maybe the confusion is just inevitable.

This comment has been minimized.

Copy link
@awoods

awoods Apr 28, 2016

Member

👍 @ajs6f, avoiding confusion seems like a good goal.

This comment has been minimized.

Copy link
@birkland

birkland Apr 29, 2016

Author Contributor

Good point, will change the name

Vagrantfile Outdated
d.env = {
FCREPO_BASEURL: "fcrepo:8080/rest",
JMS_BROKERURL: "tcp://fcrepo:61616",
TRIPLESTORE_BASEURL: "fuseki:3030/fcrepo/update",

This comment has been minimized.

Copy link
@whikloj

whikloj Apr 28, 2016

Contributor

Following on from @awoods comment should this be fuseki:3030/fuseki/update??

This comment has been minimized.

Copy link
@acoburn

acoburn Apr 28, 2016

Contributor

Nope, see above. This is correct.

@@ -0,0 +1,420 @@
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T12:29:23-05:00)

This comment has been minimized.

Copy link
@whikloj

whikloj Apr 28, 2016

Contributor

Did you want to checkin this log?

This comment has been minimized.

Copy link
@birkland

birkland Apr 29, 2016

Author Contributor

It looks like this was included by error, it shouldn't be there. Thanks!

@acoburn

This comment has been minimized.

Copy link
Contributor

commented May 13, 2016

The commits in this PR were merged by @emetsger

@acoburn acoburn closed this May 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.