dbpedia / databus

A digital factory platform for managing files online with stable IDs, high-quality metadata, powerful API and tools for building on data: find, access, make interoperable, re-use
Apache License 2.0
36 stars 16 forks source link

documentation update: needs fix at setting up local environment #146

Closed Tethet-18 closed 7 months ago

Tethet-18 commented 7 months ago

The documentation says to be in root folder to setup the local environment but we need to be in the devenv folder. Also in the devenv folder when you run '''make env-build'' it does not work with error that ''./lookup-application.war'' file is missing.

manonthegithub commented 7 months ago

true, the Dockerfile for lookup servlet is broken @holycrab13 could you fix the Dockerfile or maybe the algorithm for running devenv changed?

Tethet-18 commented 7 months ago

does anyone have any idea how to get around it for now ? I am trying to set up the project locally and work on the issue 129 .

manonthegithub commented 7 months ago

@Ayush-Kumar91221 seems like you can just ignore the step make env-build and just run make env-start

Tethet-18 commented 7 months ago

I tried running it but it returns another error: docker compose up [+] Running 1/6 ⠦ virtuoso 4 layers [⠀⠀⠀⠀] 0B/0B Pulling 3.6s ⠏ edaedc954fb5 Pulling fs layer 0.9s ⠏ 8bc9c228e3da Pulling fs layer 0.9s ⠏ 4fe13735df1b Pulling fs layer 0.9s ⠏ 4f4fb700ef54 Waiting 0.9s ✘ gstore Error 3.6s Error response from daemon: pull access denied for gstore-dev, repository does not exist or may require 'docker login': denied: requested access to the resource is denied make: *** [Makefile:21: env-start] Error 18

after looking up for it in docker hub i found gstore:dev is something you can install but i could not find gstore-dev. Is it a typo in the docker-compose file? How to get around it

manonthegithub commented 7 months ago

Hey @Tethet-18 , yes you should set dbpedia/gstore:dev image, we have done changes to our envs recently and this broke integrity with documentation

Tethet-18 commented 7 months ago

updates were made to the docs. However there were some fixes which have been addressed in issue #147. Made PR of its fix