search

osm-fr / osmose-frontend

Part of osmose that shows results on the website http://osmose.openstreetmap.fr
GNU General Public License v3.0
41 stars 38 forks source link

docker ran version doesn't display the changes category (and gettext issue) #349

Open marius851000 opened 3 years ago

marius851000 commented 3 years ago

I tried running (on latest master, 83d44d28a91eb770285aa2bf39aa67bef7c5208c ), and it happened that the frontend tried to load http://localhost:20009/en/map.json . This didn't worked, as the ressource, according to route, is on http://localhost:20009/en/map/.json (that's actually a bit strange, and I wonder if this isn't a api-side bug, or a frontend bug that required change in the backend).

I use the docker version. To reproduce, you should hopefully just run, in the docker folder,

curl http://osmose.openstreetmap.fr/export/osmose-menu.sql.bz2 | bzcat > osmose-menu.sql
docker-compose build && docker-compose up

and connect to localhost:80

I worked around this on my side by changing the api-side route to correspond with client-side.

Additionally, I had an issue related to gettext. I just commented out the code, but that's another, seemingly independent problem. (that's strange... isn't docker supposed to be reproducible ?)

marius851000 commented 3 years ago

I appear that this is due to not adding a / at the end of http://localhost:8080/en/map . If a / is present, it query the map/.json url (like on osmose.openstreetmap.fr )

frodrigo commented 3 years ago

I tried running (on latest master, 83d44d2 ), and it happened that the frontend tried to load http://localhost:20009/en/map.json . This didn't worked, as the ressource, according to route, is on http://localhost:20009/en/map/.json (that's actually a bit strange, and I wonder if this isn't a api-side bug, or a frontend bug that required change in the backend).

I think the right location is /en/map/.json. Even if it is strange. (should be index.json)

The map page url is on /en/map/, and so done the right json call. There is rewrite URL on osmose.openstreetmap.fr

I worked around this on my side by changing the api-side route to correspond with client-side.

Additionally, I had an issue related to gettext. I just commented out the code, but that's another, seemingly independent problem. (that's strange... isn't docker supposed to be reproducible ?)

But all of this is an ongoing refactoring, and for now docker may not be up to date (but taking fix).

If you only want to thing with the vue js part, you does not need docker. But yes, it you want to change the API or have data locally.

marius851000 commented 3 years ago

I want to try an analyzer I'm making. The jupyter docker ran fine (except it didn't said where I could find the password, so I set one myself), but the map view for an element display too much data. It should more visible once uploaded to the frontend (I've decided to just try to host this on my computer. I already have a configured postgres server, so it should be simple)

frodrigo commented 3 years ago

You can also just look at the xml output. You can also output other format with jupyter (csv, geojson...)

marius851000 commented 3 years ago

Will try to load the geojson in JOSM. It should present it better