New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get rid of node-gyp dependency #58
Comments
Here now I get -bash-3.2# npm install nodebb-plugin-import npm WARN package.json reds@0.2.4 No repository field.
gyp ERR! configure error npm ERR! System Linux 2.6.32-6-pve |
you should get the same error if you try:
|
Yes. Exactly. -bash-3.2# npm install jsdom
gyp ERR! configure error npm ERR! System Linux 2.6.32-6-pve |
@andreapernici that's fixed in master, however, the "resume after crash" feature is till fragile. I wouldnt use it, you can just delete everything at each try |
Now I installed it. Clicked "Delete everything, then re-import to NodeBB", but honestly I don't understand why an importer should delete the MySql db content :D I'm waiting for the import to finish...I have a big DB: more than 10GB I get: But nothing is imported. |
I see a red notice not finding the exporter. Started after installing the vbulletin importer but and then stopped State: idle, by event: | Phase: Progress: 0% |
Oh no no I'm not deleting the mysql db. It just flushes the NodeBB db
|
You need to select the right exporter type or type it in.
|
Wait for the next release. Master is not stable
|
Yes I used the vbulletin importer. It starts, but after some seconds stop. Thanks for all your feedback and let me know when a stable version will be out. I'd really like to test how nodebb scale on a very large forum with high traffic. |
track it here, #60 how hard would it be for you to give me an altered version of your DB, maybe obfuscate any private data. |
If you want I can create a shell access on my test server so we can experiment there without obfuscating anything. Obviously the test server is not with a lot of power but it should be fine. |
that's been bothering me for a while
The text was updated successfully, but these errors were encountered: