mirror of
https://github.com/PowerDNS-Admin/PowerDNS-Admin.git
synced 2026-04-25 08:45:55 +03:00
[GH-ISSUE #22] postgresql? #17
Labels
No labels
bug / broken-feature
bug / broken-feature
docs / request
feature / request
help / other
mod / help-wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PowerDNS-Admin-PowerDNS-Admin#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @piwats on GitHub (Apr 13, 2016).
Original GitHub issue: https://github.com/PowerDNS-Admin/PowerDNS-Admin/issues/22
Hello,
could you please provide install instructions for use with postgresql?
I got the app running (via uwsgi/nginx), also I got it to run under postgresql, unfortunately it does not show any dns records at all. I have to assume that the db setup I did is somehow wrong.
pdns logs say it transmits the json data.
Many thanks
@ngoduykhanh commented on GitHub (Apr 14, 2016):
hi @piwats ,
It looks like that you completed the setup for running PowerDNS-Admin with Posgresql. Your issue is a bug actually. I've fixed it at commit
a9cd4911b9. Please checkout the new code and let me know if it fixes your issue.@piwats commented on GitHub (Apr 14, 2016):
Hello there,
unfortunately I still cannot see any records.
@piwats commented on GitHub (Apr 14, 2016):
Could it be because I run in a subdirectory? e.g. server.com/pdns?
@ngoduykhanh commented on GitHub (Apr 14, 2016):
hi @piwats
It works for me on Ubuntu 14.04 and Postgresql 9.4. What are you environment? I don't think the subdirectory can cause this issue, but have you tried removing it?
Can you show me your
config.pyfile also ?@piwats commented on GitHub (Apr 14, 2016):
I'm on gentoo wit pgsql-9.5.2, to be precisely.
@piwats commented on GitHub (Apr 14, 2016):
Ah, I forgot to mention, that I also tried to run it in /. Same behavior, no changes.
@piwats commented on GitHub (Apr 19, 2016):
Could you please change the create_db.py script so I can try it with postgresql?
Last time I had to create the db structure by hand, maybe I did something wrong?
@ngoduykhanh commented on GitHub (Apr 19, 2016):
@piwats : didn't
create_db.pywork for you? I works fine for me with Postgresql. Can you create new bank database and rerun the script?@piwats commented on GitHub (Apr 19, 2016):
I've got it now:
Somehow the app won't work if the venv (aka 'flask' directory) is not inside of PowerDNS-Admin...
@ivanfilippov commented on GitHub (Apr 19, 2016):
Hi @piwats
The flask directory contains all the dependencies (Flask, SQLAlchemy, etc), but you can install the dependencies into your system Python packages without the
virtualenvand avoid needing it there. 😄@ivanfilippov commented on GitHub (Apr 19, 2016):
I should mention that
virtualenvis the recommended way of doing it, unless you're building a docker image or something that will only ever run PowerDNS-Admin.@piwats commented on GitHub (Apr 19, 2016):
My initial setup as described in #23 was:
../PowerDNS-Admin
../venv
Now it is
../PowerDNS-Admin
../PowerDNS-Admin/flask
where venv = flask, meaning
virtualenv flask@ngoduykhanh commented on GitHub (Apr 20, 2016):
For you description #23, they are:
Yes. you need the
env(flask) directory in insidePowerDNS-Adminto make it work.@piwats commented on GitHub (Apr 20, 2016):
That I have already changed. I think it is safe to close this issue.