mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #402] Bare metal Install #267
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#267
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 @john-clark on GitHub (Jul 30, 2020).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/402
Bare metal and Publishing wiki articles did not provide results desired. https://github.com/pirate/ArchiveBox/wiki/Publishing-Your-Archive only provides read-only access. My install was on headless Debian 10, running "archive server" only provides local access, and do not have access to GUI. This is not for world-readable sites just internal testing usage. Would be better to provide a non-proxy solution but I just wanted to be able to see the program operation.
@pirate commented on GitHub (Jul 30, 2020):
Unfortunately to add sites from the UI you need to create a user to log in as, even if the archived files themselves are public. This is a fundamental limitation of the Django admin requiring user authentication, and it's not something I want to change as it's a lot of effort for relatively little gain.
The recommended solution if you want both archive read and write access to be public is to do the following:
If I misunderstood your question or if this doesn't answer your question, feel free to comment back and I'll reopen the ticket (a screenshot of what you're seeing would help too).
@john-clark commented on GitHub (Jul 30, 2020):
Yes, misunderstanding, no work requested, above solution is working fine. Systemd runs as the user I ran archivebox init with. This was an attempt to document the steps I took to be able to remotely get to archivebox login and web interface from remote computer. https://github.com/pirate/ArchiveBox/wiki/Publishing-Your-Archive is a read only non-interactive page. I wanted to be able to see the django server hosted at 127.0.01:8000 on my management pc.