We need to be more explicit about when to rebuild the database. Currently, the default action is to rebuild the object database every time someone issues docker compose up. This leads to longer start up times and all avatars, objects and their turves being lost each time too.
It would be preferred if it’d only happen on a first time setup and then be disabled automatically after that unless you explicitly rebuild the database yourself.
Perhaps a check could be in place to see if the database is empty at startup, and if so then fill it up.
randy: Now the rebuild flag is default off, and docker-compose up will only rebuild the database if it doesn't exist.
randy: build will trigger a db reset.
We need to be more explicit about when to rebuild the database. Currently, the default action is to rebuild the object database every time someone issues
docker compose up
. This leads to longer start up times and all avatars, objects and their turves being lost each time too.It would be preferred if it’d only happen on a first time setup and then be disabled automatically after that unless you explicitly rebuild the database yourself.
Perhaps a check could be in place to see if the database is empty at startup, and if so then fill it up.