Hey @thencein and @newsrobert - I’m currently running a hacked-up, dockerized Newsblur instance [at least for now]. It’s hobbling along but I haven’t gotten it “production” ready due to a number of outstanding issues I’ve yet to resolve (some of which I’ve outlined here: Self-hosting documentation; I did include some of the steps I found useful in setting up, notably you’ll want to look at the models.py modification if you want to keep your articles around for longer than 10 days or whatever the default is).
TBH, I don’t remember all of ths steps I took but I’m happy to try to help out here. Notably, you should be sure to update ./docker/local_settings.py [and docker-compose.yml to update the db password there] and ./docker/data.json, then ensure you’ve run the three docker-compose commands at NewsBlur/docker/README.md at master · samuelclay/NewsBlur · GitHub to initialize the DB.
I tried setting up a net-new local dockerized NewsBlur instance earlier today to try to replicate the errors you two are seeing and to develop a reproducible build, but I failed at despite having a somewhat functioning reference setup. I’ll keep trying to get a local instance running so I can get you guys a reproducible build.
In any case, while trying to do that, I re-discovered a couple of things:
Is there anyway to set this up without needing emails being sent out etc?
Yep; the issue is that example.com doesn’t have an MX record; you can still give NewsBlur a fake email address but the domain needs to have a valid MX record. I was able register a dummy user using dummy@google.com [with my local, broken setup this will log me in only once and leave me in a state where I’m unable to perform basic actions including adding a feed which fails with a generic error message and not much else to go on].
I suspect the reason for this is that the database dump that it’s trying to import is either outdated/incorrect, hence postgres falls over.
I think you’re spot on here; my guess is that the init.sql.gz file that you have needs to be re-initialized and the existing one may be hanging around from the last time you were playing around with NewsBlur or something to that effect. I got the same error when I tried spinning up a local instance of NewsBlur on the same dev host I had used to configure my running NewsBlur instance and after clearing out some cruft and ensuring I was starting net-new, that specific error disappeared.
@newsrobert: the issue you’re running into looks like it could be an issue with your environment or a setting, maybe in local_settings.py or data.json. Do you recall what steps you took to set up your environment or what config changes you’ve made, if any?
@samuelclay: thank you for the pointer, however it’s unclear [to me, at least] how the link you provided relates to the issues reported in this thread.
I’ll keep poking at my local instance to see what I can dig up.