mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #288] Bugfix: django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty. #207
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#207
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 @mpeteuil on GitHub (Oct 20, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/288
Describe the bug
After installing in editable mode on branch
v0.4.3, runningarchivebox initresults in an exceptionThe directions I followed were basically these: https://github.com/pirate/ArchiveBox/wiki/Roadmap#-pip-install-archivebox
Steps to reproduce
git clone https://github.com/pirate/ArchiveBox.git && cd ArchiveBox && git checkout v0.4.3pyenv local 3.7.4pipenv install && pipenv shellpip install -e .mkdir data && chmod 777 data && cd dataarchivebox initAfter running the last step, I get the above error. At that point the
ArchiveBox.conffile has already been created with something like:Screenshots or log output
Software versions
MacOS 10.14.6374dd393.7.4@pirate commented on GitHub (Oct 21, 2019):
Odd, does it work on the
v0.4.0branch? Thanks for reporting, it's probably a simple mistake I made somewhere like accidentally initializing django withsetup_djangobefore the config file is read.@mpeteuil commented on GitHub (Oct 22, 2019):
Sure thing. Yes, it looks like the
v0.4.0branch works fine.@pirate commented on GitHub (Jul 24, 2020):
This should be fixed on the latest
djangobranch. If you still see any problems comment back here and I'll reopen the ticket.