| Nov | DEC | Jan |
| 15 | ||
| 2019 | 2020 | 2021 |
COLLECTED BY
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Collection: Archive Team: The Github Hitrub
jeff5
commented
|
Add to the Windows build script a clause to create and use a virtual |
Build in a virtual environment on Windows (GH-267)
Loading status checks…
0a77ef7
Add to the Windows build script a clause to create and use a virtual environment and install Sphinx there, comparable with the Unix Makefile. The user may suppress this behaviour by defining a her preferred command in the environment variable SPHINXBUILD, as before.
the-knights-who-say-ni
added
the
CLA signed
label
| > .\make html | ||
| in the checkout directory, and again this will write the files to the | ||
| ``_build\html`` directory. |
To build the devguide on an Unix-like system use:
$ make html
On Windows, use:
> .\make html
You will find the generate files in _build/html.
.\ shouldn't even be necessary unless that's a PowerShell-ism; the same command should work on both platforms.
docquality.rst
Outdated
| .. code-block:: ps1con | ||
| PS> Set-ExecutionPolicy -Scope CurrentUser RemoteSigned | ||
|
|
||
| if "%1" == "clean" ( | ||
| for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i | ||
| del /q /s %BUILDDIR%\* | ||
| goto end | ||
| ) | ||
|
|
||
| rem If we get this far, we're going to use the SPHINXBUILD command |
| @@ -183,3 +196,4 @@ cmd /C %PYTHON% tools\serve.py %BUILDDIR%\html | |||
| goto end | |||
|
|
|||
| :end | |||
| endlocal | |||
| rem If we get this far, we're going to use the SPHINXBUILD command | ||
| if not defined SPHINXBUILD ( | ||
| rem If it is not defined, we build in a virtual environment | ||
| if not exist venv ( |
if not exist %~dp0venv should do it, but make sure I remembered the correct flags.
popd is needed).
docquality.rst
Outdated
| > .\make html | ||
| in the checkout directory, and again this will write the files to the | ||
| ``_build\html`` directory. |
.\ shouldn't even be necessary unless that's a PowerShell-ism; the same command should work on both platforms.
docquality.rst
Outdated
| .. code-block:: ps1con | ||
| PS> Set-ExecutionPolicy -Scope CurrentUser RemoteSigned | ||
jeff5
commented
|
@zware So it does. The file explorer version was nice because it opened in the folder you had highlighted, so I'd generally do that 2 or 3 times to get started. Nearly there with a change set satisfying @ezio-melotti .
In this section of the devguide you also claim |
Simplify wording and add comment following review.
Loading status checks…
563a7c5
Contributor
Author
jeff5
commented
|
@zware The |
Always build relative to the directory containing make.bat
Loading status checks…
f5f5a5d
Whatever the current directory when invoked, the build takes place into _build/... in the directory that contains make.bat, and returns to the invocation directory.Contributor Author
jeff5
commented
|
Although still showing "changes requested" I believe the review comments are now answered, mostly by change. (Not sure if I've subverted the workflow somehow.) Anyhow, is this good enough to land this now? |
| @@ -39,14 +41,29 @@ if "%1" == "help" ( | |||
| echo. check | |||
| echo. serve to serve devguide on the localhost (8000) | |||
| goto end | |||
| ) | |||
| :help0 | |||
if "%1" == "something" (
...
goto end
)
.bat files either, but as briefly stated in the related issue #267, the .\make html currently builds nothing because goto end is executed unconditionally. I attributed this to known issues with parenthetical ifbodies and goto, anr the legacy-style work-around made it go away.
On closer inspection, the problem is the un-escaped (8000). I can fix that.
There is no OR operator, but I can make it a bit clearer (closer to what sphinx-quickstart generated).
Properly escape parentheses in the help text.
Loading status checks…
3297e43
Previously this disabled subsequent build targets by making "goto end" accidentally unconditional. We also describe the "check" target.zware approved these changes
ezio-melotti
merged commit 3d92a7e
into
python:master
ezio-melotti
commented
|
Merged, thanks for the PR! |
jeff5
commented
|
Thanks for the helpful reviews. You may have spotted that my contributions are a side-effect of trying to re-use your work, or follow its model, in a devguide for Jython. I'll offer further things as I spot them. |
jeff5
deleted the
jeff5:iss267cp-win-venv
branch
jeff5
mentioned this pull request
Successfully merging this pull request may close these issues.
None yet
4 participants Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. ●© 2020 GitHub, Inc. ●Terms ●Privacy ● ●Security ●Status ●Help ●Contact GitHub ●Pricing ●API ●Training ●Blog ●About You can’t perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
