You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working in GoblinSocket, I found that GoblinDB has no default file in configuration. Due to that, i got an epic crash when triying to initialize the databse on the first time.
But, when I went to node_modules/goblindb there was a file called goblin_db.json. So, what the hell was happening?
I opened the config.js, and I added the file param, so the file ended as this:
And it started working. But I realized that there was a new file in my GoblinSocket directory, called goblin_bd.json. What was happening? Relative routes.
/GoblinSocket
- /node_modules
- - /goblindb
- - - goblin_db.json <--- THIS IS NOT THE DB
- goblin_db.json <--- THIS IS THE DB
- index.js
So, maybe next steps could be make a consistent documentation of where the db will be stored, and try to prevent that errors, to avoid unexpected crashes that may damage the data storage.
The text was updated successfully, but these errors were encountered:
Working in GoblinSocket, I found that GoblinDB has no default file in configuration. Due to that, i got an epic crash when triying to initialize the databse on the first time.
But, when I went to node_modules/goblindb there was a file called goblin_db.json. So, what the hell was happening?
I opened the config.js, and I added the file param, so the file ended as this:
And it started working. But I realized that there was a new file in my GoblinSocket directory, called goblin_bd.json. What was happening? Relative routes.
So, maybe next steps could be make a consistent documentation of where the db will be stored, and try to prevent that errors, to avoid unexpected crashes that may damage the data storage.
The text was updated successfully, but these errors were encountered: