#MapDB 2.0 | Map Browser

1043 messages Ā· Page 2 of 2 (latest)

noble knot
#

The answer to my question was yes, bootstrap icons

noble knot
#

If anyone want to review. I'll resolve my todos and merge soon, then we can deprecate the old map database. We'd want to leave it up as like legacy-mapdb.cncnet.org, with uploads disable, until we migrate maps themselves, but this should be ready as a drop in replacement for the client, and the basic search / upload.

https://github.com/CnCNet/cncnet-map-api/pull/22/files

#

I need to fix Chinese character support too

shrewd forge
#

cool nice job ill give a look at the pr soon !

noble knot
#

The update here is I’m talking to UI devs.

smoky pendant
#

so is all legacy features restored?

#

if yes we could try testing them by temporarily switching
also no way to easily migrate maps to the new DB?

noble knot
#

Yeah all legacy should be functional

#

I can migrate the old maps but I’d need programmatic access to the database so that I can script it

#

Personally I think we should migrate the old maps after we have thoroughly tested, because the migration will be quite slow

smoky pendant
smoky pendant
noble knot
#

It will interrupt anyone who is in the lobby, has uploaded their map, the database switch happens, then the guest tries to download it.

noble knot
#

Do we know our peak hours?

We could just flip the domains off hours. The only way someone will be interrupted is if they click ā€œplayā€ and a transfer starts right as we flip the domains

trail fjord
noble knot
# trail fjord What kind of access? I'll see if I can sort something out for you?

I need to be able to temporarily view the database and map file system. Like a database connection to my machine. This access can be removed after the migration.

I need the new map database to be able to programmatically access the database and file system for the old map database so that I can ingest the data to the new one.

We can discuss the details in private to not expose too much info.

#

I think we should do this after the new map database has been running in prod for a few days and we know it doesn’t have issues.

smoky pendant
#

@topaz berry @austere marsh @trail fjord what do you think? do we need to port older map database? seems like a minor issue to not warrant porting

#

users will just reupload

#

@scenic salmon do you know how often it is that users use map database as actual db and not just to upload maps

noble knot
#

I think we should port it purely for historical reasons. We’re the largest source of lost maps

#

I personally have used it to find a lot

#

Or we can just keep the old one running in read only mode

scenic salmon
#

only if they ask here and get linked it

noble knot
#

I will say for me personally the legacy maps are extremely important. There have been many maps on there that I thought were lost to time.

The new map db has a search interface and a way to search legacy maps. I am happy to put in the work to make sure we don’t lose that history.

If I’m out voted, then I’ll at least want to save a copy locally, and I’ll find some way to host it.

#

I am happy to push the migration back just so that it’s not a blocker to finishing the project. But please do not delete the legacy database. I would probably cry lol

smoky pendant
#

I meant that we could probably conduct tests without porting

noble knot
#

Oh my bad

sick gyro
#

Been a while since I’ve chimed in here. How we looking @noble knot and @smoky pendant?

smoky pendant
#

not much from my side, should probs ask @trail fjord

trail fjord
#

ah yes thanks for the prompt reminder, I've sent a DM to @noble knot so i can get the spec required will then setup and communicate here accordingly once I know further

trail fjord
#

box built and info handed to @noble knot

noble knot
#

Working on getting the prod copy running. Hopefully we’ll have the client switched over in the next week.

noble knot
#

I don't know why I have been making test maps by hand when the random map generator has been fixed facepalm

noble knot
#

Got it deployed but having some route issues. Pinged the relevant parties.

shrewd forge
#

@noble knot
sup, found an issue with the CD workflow i've set up.

It is using the "latest" tag to download the most recent image (The APP_TAG env var set in the .env on the server). But sometimes due to caching, it won't pull the latest image on the server and you will end up using the same image as before šŸ˜„ What a silly issue...

I've drafted a fix on the ladder-api repo : https://github.com/CnCNet/cncnet-ladder-api/pull/361

I did not had time to test it yet but once i did we should apply similar changes to the map-api.

I'll make the PR once i know it's working. I'll keep you informed.

noble knot
#

I’ll check it tonight after work

scenic salmon
#

re: banned maps

can I check if the MapDB 2.0 will have a simplified map banning function? i.e. there's been one guy that's adamant on making cheat maps disguised as original maps

(I think I've asked this before)

smoky pendant
#

what is the old way and what is the supposed simplified way?

thorn hemlock
#

i haven't seen the map db 2.0 UI but i'm assuming all of the maps will be searchable and there would be a feature to ban maps