COLLECTED BY

Organization: Archive Team

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: ArchiveBot: The Archive Team Crowdsourced Crawler

ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).

To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.

There is a dashboard running for the archivebot process at http://www.archivebot.com.

ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20201019115846/https://docs.github.com/pt/enterprise-server@2.22/admin/packages/enabling-github-packages-for-your-enterprise

Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para obter as informações mais recentes, acesse a documentação em inglês. Se houver problemas com a tradução desta página, entre em contato conosco.

GitHub Docs

Habilitar o GitHub Packages para a sua empresa

Você pode começar a usar o GitHub Package Registry na sua instância habilitando o recurso, configurando armazenamento de terceiros, configurando os ecossistemas que você deseja apoiar e atualizando seu certificado de TLS.

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Ou, learn how to contribute.

Observação: GitHub Package Registry está atualmente em beta para GitHub Enterprise Server 2.22. Para participar da versão beta da sua instância, use o formulário de inscrição.

Após ter sido convidado para participar do beta, para habilitar GitHub Package Registry para a sua instância, siga as instruções do representante da sua conta.
Configurar armazenamento de terceiros para pacotes da sua empresa. Para obter mais informações, consulte "Configurar armazenamento de terceiros para pacotes".
Habilitar ou desabilitar cada pacote de ecossistema para sua empresa. Para obter mais informações, consulte "Configurar pacotes de suporte para a sua empresa".
Se o isolamento de subdomínio estiver habilitado para a sua instância, o que é necessário para usar o GitHub Package Registry com o Docker, crie e faça o upload de um certificado TLS que permite a URL de host de pacote para cada ecossistema que você deseja usar, como, por exemplo, npm.HOSTNAME. Certifique-se de que o host de cada pacote contém https://.

Você pode criar o certificado manualmente ou usando o Let's Encrypt. Se você já usa o Let's Encrypt, você deverá solicitar um novo certificado TLS depois de habilitar GitHub Package Registry. Para obter mais informações sobre as URLs de host do pacote, consulte "Habilitar o isolamento de subdomínio". Para obter mais informações sobre o upload de certificados TLS para GitHub Enterprise, consulte "Configurar TLS".

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Ou, learn how to contribute.