f9176387ac
update to django-2, python3, and based on an alpine container
2019-02-13 20:17:05 -05:00
dac54a5ad7
bump pybindxml to 0.7 to handle bind 9.12
2019-01-17 13:34:37 -05:00
7c781981eb
bump to pybindxml 0.6.3
2018-04-28 12:53:33 -04:00
a27fa5c3a9
bump pybindxml to 0.6.2 to handle bind xml 3.8
2018-04-27 21:29:00 -04:00
1af8f1e31b
encrypt TSIG keys using Fernet cryptography library
2017-05-02 20:21:11 -04:00
fba94af629
update initial_data.json to be django 1.11 compliant
2017-04-18 06:21:41 -04:00
415f20b71e
NODB environment variable is not used anymore
2017-04-17 20:38:43 -04:00
ef70379a2a
add setupmethod to create key and bindserver objects. add key_name required expected failure
...
break up each test into its own function to make debugging the test failures easier.
2017-04-17 20:35:22 -04:00
90e38d2aef
enable the edit_record link, URL, and view
2017-04-17 20:29:55 -04:00
ddae5be662
Move edit/add/cname key_name and ttl form items to just use choice item instead of trying to define each element
2017-04-17 20:26:01 -04:00
235f0fe174
Simplify ttl and key_name form fields. keys are now required.
...
fix forms where the widget was being specified but overriden in the view. remove the specification of the widget
2017-04-17 20:18:14 -04:00
07b0df4b7d
correct documentation to correctly specify docker run environment variables
...
also mention which django db args are required vs optional
2017-04-01 15:24:43 -04:00
49feb07d67
fix documentation to remove incorrect usage of NODB=1 and friends
2017-03-31 23:07:32 -04:00
4c7ed9beb6
fix logic on using remote mysql db. make sqlite the fall back, logic clears up if not all variables are set
2017-03-31 23:05:47 -04:00
5aef0ad5c9
dont use sqlite database by default
2017-03-31 21:10:10 -04:00
f2c36ea863
use sqlite DB by default in dockerfile
2017-03-29 21:41:43 -04:00
6704469b9d
add support for specifying DB parameters via environment variables. sqlite or mysql.
...
updated README to focus on developing/running via docker
2017-03-29 21:05:39 -04:00
6ecae8b772
in django 1.8, django.core.context_processors moved into django.template.context_processors.
...
Note to self: always test in a container running a recent version of django. i was still testing on 1.7 :/
2017-03-25 16:20:02 -04:00
ff8088defa
add request context_processor and printing serving hostname to footer
...
eventually this will make lead to making it a bit more docker/kubernetes friendly
2017-03-25 15:53:09 -04:00
5e1b23ee67
move app container dir into /code, reference pybindxml from git repo
2016-12-19 20:15:59 -05:00
89fb79517e
add initial systemd service file for binder.
...
tested running by submitting to 3-machine coreos etcd cluster
2016-12-15 21:14:53 -05:00
4df47c24fa
comment out a few tests while i rethink form entry
2016-12-05 22:02:47 -05:00
0252c3df62
make Binder docker-friendly again. built on python image with django 1.10
2016-12-05 21:56:49 -05:00
7fdcfab8a0
add support to add CNAME in zone, loosen restrictions on record data input
2016-11-12 07:44:03 -05:00
54c3bc18cc
Merge pull request #47 from Dunedan/django-1.9
...
Adds support for Django 1.9 while dropping support for unsupported versions.
2016-02-12 20:34:54 -05:00
1331d02e1d
Merge pull request #45 from goetzk/documentation-update
...
Attempted to clarify install documentation
2016-02-12 06:24:38 -05:00
74cc4efca4
Adds support for Django 1.9 while dropping support for unsupported versions.
...
This commit adds support for Django 1.9. As the template configuration options
changed with Django 1.8 and versions earlier than 1.8 aren't supported anymore
anyway by upstream, support for them is removed.
To have the Dockerfile still working, this commit also changes its logic so the
dependencies get directly installed via the requirements.txt from PyPI, which
will ensure that always matching versions of all dependencies are present (e.g.
the Django version).
2016-02-06 19:21:52 +01:00
49b7559e86
Attempted to clarify install documentation
...
I've just worked my way through the install process and tried to
clarify/explain anything that wasn't obvious or that I thought might not be
obvious to someone new trying to use this software.
Having encountered all the same problems as @vchoi in issue #5 I've attempted
to update the documentation to clarify the requirements.
Other than that its 'misc' really: some confusion with things like
local_settings.py being missing, changed the headings and shuffled things
around for clarity, expanded on the required django commands etc.
2016-01-02 10:58:28 +11:00
8b34e7e4ae
Merge branch 'Dunedan-refactored-views'
2015-12-26 15:15:56 -05:00
2bb8f5d9cb
resurrect the ability to add a PTR record on its own, not as part of a pair of forward records
2015-12-26 15:14:29 -05:00
e9d65179ab
on the cname add result, we need the cname name, not the originating record name
2015-12-26 14:32:07 -05:00
ab9b28d525
Merge branch 'refactored-views' of https://github.com/Dunedan/binder into Dunedan-refactored-views
2015-12-26 14:10:11 -05:00
1e126e7874
Add initial dockerfile for binder. runs/exposes port 8000
2015-11-20 10:08:16 -05:00
f5b557384a
Merge branch 'master' of github.com:jforman/binder
2015-11-20 09:44:42 -05:00
6210dd3854
add initial data fixture to make automated deploys possible
2015-11-20 09:43:06 -05:00
a3c5eab978
fix missing div tags
2015-11-20 09:42:56 -05:00
534863aebe
Merge pull request #41 from Dunedan/404-template
...
Provide a template for not existing resources.
2015-09-06 01:54:36 -04:00
99f1284d43
Simplies the test code a bit.
2015-09-05 19:20:44 +02:00
3ca4cac89a
Fix the tests, after the recent changes.
2015-09-05 19:18:59 +02:00
e13b42cd13
Refactors the views used to add and delete records.
...
Notable changes are:
* Refactored views, utilizing more of Djangos features, resulting in simpler
code.
* URLs are now the same when initially filling out a form and when editing a
submitted form which contained errors.
* Instead of a result page showing the response from the DNS server (which is
now logged using Djangos "logging" functionality) the user is now redirected
back to the record listing of the current zone when the action was successful
or stays on the form page when an error occured. Proper success/error
messages are shown in both cases by utilizing Djangos "messages"
functionality.
2015-09-05 19:03:21 +02:00
7492febf08
Provide a template for not existing resources.
...
Will be of course only used if debugging is disabled.
2015-08-23 20:35:30 +02:00
7b3a24364c
Merge branch 'Dunedan-improved-form-errors'
2015-08-12 22:06:05 -04:00
ecea7964a1
Improves the rendering of forms and refactors some of their logic.
...
Changes are:
* Display invalid input in editable input fields instead of adding it to the
end of the error message. This should improve user experience in case of
typos etc. where they now can simply edit there previously entered value.
* Use a single variable for form data and form errors, instead of using two.
Makes the code a bit cleaner.
2015-08-04 20:27:02 +02:00
17ecba686e
Merge branch 'Dunedan-responsive-layout'
2015-07-28 06:17:09 -04:00
9e5991df2c
Merge branch 'responsive-layout' of https://github.com/Dunedan/binder into Dunedan-responsive-layout
...
Conflicts:
binder/templates/base.html
2015-07-28 06:16:56 -04:00
acb558b61c
Merge pull request #33 from Dunedan/add-global-authentication
...
Add global authentication
2015-07-27 06:25:03 -04:00
52ebb1e1b1
Merge branch 'master' into add-global-authentication
2015-07-24 12:14:21 +02:00
c6484e1412
Merge pull request #39 from Dunedan/style-fixes
...
Fixes some python style issues.
2015-06-18 21:46:47 -04:00
20d785840b
Fixes some python style issues.
...
No changes in binders functionality are included in this commit, just improved
python style
2015-06-13 12:05:42 +02:00
ec85c465d8
Merge pull request #38 from Dunedan/landscape.io-support
...
Adds a configuration file for static code analysis using Landscape.io.
2015-06-12 20:23:01 -04:00
jeffrey forman
Jeffrey Forman
Jeffrey Forman
Daniel Roschka
Karl Goetz