starred/ArchiveBox

Fork 0

mirror of https://github.com/ArchiveBox/ArchiveBox.git synced 2026-04-25 17:16:00 +03:00

[GH-ISSUE #554] Less "open" public website #352

New issue

Closed

opened 2026-03-01 14:42:47 +03:00 by kerem · 5 comments

kerem commented

2026-03-01 14:42:47 +03:00

Owner

Originally created by @shepner on GitHub (Nov 28, 2020).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/554

Type

General question or discussion
Propose a brand new feature
Request modification of existing behavior or design

What is the problem that your feature request solves

Occasionally I would like to share links to pages I have clipped. However, the public ArchiveBox site is rather "open" (very easy for anyone to look at everything stored in there) and Id rather if that was not the case. Im not asking for iron-clad security here but Id like to keep people (and bots) from snooping.

Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes

Ideally: Implement granular access controls to the website which are tied to user accounts which can exist in an external system (ie Okta, Authelia, LDAP, etc).
Minimally: Make it so the directory structure is not publicly visible, provide an option to disable public access to the archive root, and an option to entirely disable public archive access.

What hacks or alternative solutions have you tried to solve the problem?

Since I want to make ArchiveBox Internet accessible so I can archive sites from my mobile devices, the minimal solution above should provide a modicom of privacy and is better than expecting the user to somehow figure out how to do this via Nginx or the like.

How badly do you want this new feature?

It's an urgent deal-breaker, I can't live without it
It's important to add it in the near-mid term future
It would be nice to have eventually

I'm willing to contribute dev time / money to fix this issue
I like ArchiveBox so far / would recommend it to a friend
I've had a lot of difficulty getting ArchiveBox set up

Originally created by @shepner on GitHub (Nov 28, 2020). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/554 ## Type - [ ] General question or discussion - [ ] Propose a brand new feature - [x] Request modification of existing behavior or design ## What is the problem that your feature request solves Occasionally I would like to share links to pages I have clipped. However, the public ArchiveBox site is rather "open" (very easy for anyone to look at everything stored in there) and Id rather if that was not the case. Im not asking for iron-clad security here but Id like to keep people (and bots) from snooping. ## Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes Ideally: Implement granular access controls to the website which are tied to user accounts which can exist in an external system (ie Okta, Authelia, LDAP, etc). Minimally: Make it so the directory structure is not publicly visible, provide an option to disable public access to the archive root, and an option to entirely disable public archive access. ## What hacks or alternative solutions have you tried to solve the problem? Since I want to make ArchiveBox Internet accessible so I can archive sites from my mobile devices, the minimal solution above should provide a modicom of privacy and is better than expecting the user to somehow figure out how to do this via Nginx or the like. ## How badly do you want this new feature? - [ ] It's an urgent deal-breaker, I can't live without it - [x] It's important to add it in the near-mid term future - [ ] It would be nice to have eventually --- - [ ] I'm willing to contribute dev time / money to fix this issue - [x] I like ArchiveBox so far / would recommend it to a friend - [ ] I've had a lot of difficulty getting ArchiveBox set up

kerem

2026-03-01 14:42:47 +03:00

closed this issue
added the
why: functionality

status: idea-phase
labels

kerem commented

2026-03-01 14:42:48 +03:00

Author

Owner

@pirate commented on GitHub (Nov 28, 2020):

Config options to manage which parts are public already exist:

github.com/ArchiveBox/ArchiveBox@e4d2ac432d/archivebox/config.py (L71)

archivebox config --set PUBLIC_SNAPSHOTS=True
archivebox config --set PUBLIC_INDEX=False
archivebox config --set PUBLIC_ADD_VIEW=False

You can also manage the Snapshot view/edit/add/delete permissions on a per-user basis under http://127.0.0.1:8000/admin/core/user/

@pirate commented on GitHub (Nov 28, 2020): Config options to manage which parts are public already exist: ![image](https://user-images.githubusercontent.com/511499/100522069-17323380-3176-11eb-9a06-7b3b7e3a42c0.png) https://github.com/ArchiveBox/ArchiveBox/blob/e4d2ac432db2627cec7cfa5fb02e8b83bb4269bb/archivebox/config.py#L71 ```bash archivebox config --set PUBLIC_SNAPSHOTS=True archivebox config --set PUBLIC_INDEX=False archivebox config --set PUBLIC_ADD_VIEW=False ``` You can also manage the Snapshot view/edit/add/delete permissions on a per-user basis under http://127.0.0.1:8000/admin/core/user/

kerem commented

2026-03-01 14:42:48 +03:00

Author

Owner

@shepner commented on GitHub (Nov 29, 2020):

Ok, I think I figured out what those settings do. Are they documented somewhere? Similarly, is there some documentation for the various user account permissions? I havnt found them in the wiki.

@shepner commented on GitHub (Nov 29, 2020): Ok, I think I figured out what those settings do. Are they documented somewhere? Similarly, is there some documentation for the various user account permissions? I havnt found them in the wiki.

kerem commented

2026-03-01 14:42:48 +03:00

Author

Owner

@pirate commented on GitHub (Nov 29, 2020):

They are not documented yet because it's sort of a "beta" feature. We're planning on improving the permissions system in the future and this is just the bare minimum first version we implemented. I may add them to the Wiki but I haven't decided yet if we want to advertise these config options because they might change soon.

@pirate commented on GitHub (Nov 29, 2020): They are not documented yet because it's sort of a "beta" feature. We're planning on improving the permissions system in the future and this is just the bare minimum first version we implemented. I may add them to the Wiki but I haven't decided yet if we want to advertise these config options because they might change soon.

kerem commented

2026-03-01 14:42:48 +03:00

Author

Owner

@shepner commented on GitHub (Nov 29, 2020):

k. In that case, Ill try to keep an eye out for that. Thanks!

@shepner commented on GitHub (Nov 29, 2020): k. In that case, Ill try to keep an eye out for that. Thanks!

kerem commented

2026-03-01 14:42:48 +03:00

Author

Owner

@cdvv7788 commented on GitHub (Dec 5, 2020):