docker-http-https-echo
waybackpack
Our great sponsors
docker-http-https-echo | waybackpack | |
---|---|---|
2 | 6 | |
579 | 2,771 | |
- | - | |
6.2 | 7.0 | |
22 days ago | 3 months ago | |
Shell | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-http-https-echo
- HTTP debug container
-
Upgrading from Debian Jessie to Bullseye after nearly 30 years
I do not have a documentation, but I do disaster recovery tests from time to time. This is how you can try it out:
- download the ISO of a linux distribution, Arch is good because you have continuous updates (there is no "version")
- start it on a VM engine (VirtualBox, Hybersomething in Windows, VMWare, ...)
- from that point on - start documenting
- try to on docker install a program you know that is not too complex network-wise or just start with "hello-world" (https://hub.docker.com/_/hello-world)
- you will find that when running "docker pull hello-world", docker is not installed
- install docker on Arch according to Arch docs. DOCUMENT that step
- retry, hello-world works
- now try something like https://github.com/mendhak/docker-http-https-echo
- you will learn the basics of docker networking, read some docs or just try until you have a curl call working
- at that point you can try a program you know (nextcloud, syncting, ...), pulling it from docker hub and make it work. pay attention to two things: the network and the persistent volumes (I recommend, at least for the start, the file-based ones, not the docker ones)
- grab a beer, you are 90% done, good work
- have a close look at Caddy - this is a web server similar to apache, nginx but MUCH much better. So much better that I have no words.
- you will use it as a proxy server for your containers, so that you can get to them via https://nextcloud.yourdomain.com. It os worthwhile to get your domain even if you do not expose anything because things are much easier that way (caddy will manage the TLS part)
- now learn docker-compose and add all your dockers to it (it is a YAML description of your containers).
- add backup, this will be easier if you add this program on the OS itself (it can sure be in a container but I preferred having that part independent). I recommend Borg despite its few poor choices in the design (that are not likely to bite you at that point)
TADAM! you are done.
You are independent of th eOS, if you want to install fedora or whatever it just doe snot matter because i) all your programs are maintained by someone else (than you to the maintainers, it is nice to donate sometimes) and ii) your backup is data that is easily pluggable back to a ne instance of the software
Testing new programs is super easy (you just add them to the doclker compose YAML).
I truly recommend you try with a VM and you will quickly realize it is time to reformat your server and put everything under docker :) AMA if you have questions.
waybackpack
-
People who've received a black bar on Hacker News
Thank you! But the script but the only thing that really deserves credit is Jeremy Singer-Vine's https://github.com/jsvine/waybackpack library. Pretty much made this a very straightforward task
- Upgrading from Debian Jessie to Bullseye after nearly 30 years
- Setting up a Deadsy Wiki site! (HELP WANTED)
-
Need help copying a website from the "wayback machine" iternet archive
https://github.com/hartator/wayback-machine-downloader https://github.com/jsvine/waybackpack or google "wayback machine downloader" for other options
-
Wayback Machine Downloader – Download an Entire Website from the Wayback Machine
Which paid services are you referring to? It is likely that these services aren't distributing the projects they are based on, if so, then they are in compliance with the licenses of the open source projects, which don't require attribution unless you distribute them.
This project started in 2015 btw. Another similar project called waybackpack started in 2016. There are probably more projects. IMO wayback-machine-downloader is the better project though.
https://github.com/jsvine/waybackpack
The Wayback CDX Server API these projects are based on is quite simple to use btw, just some JSON responses to decode.
https://archive.org/help/wayback_api.php
- Is there a way to scrape video links off a youtube channel and see if any of the links are archived on web.archive.org? without pasting links one by one
What are some alternatives?
letsencrypt-docker-compose - Set up Nginx and Let’s Encrypt in less than 3 minutes with a Docker Compose project that automatically obtains and renews free Let's Encrypt SSL/TLS certificates and sets up HTTPS in Nginx for multiple domain names. Configuration is done using a simple CLI tool.
wayback-machine-spn-scripts - Bash scripts which interact with Internet Archive Wayback Machine's Save Page Now
bitnami-docker-apache - Bitnami Docker Image for Apache
wayback-machine-downloader - Download an entire website from the Wayback Machine.
ladybird - Ladybird web browser [Moved to: https://github.com/SerenityOS/ladybird]
wayback - IA's public Wayback Machine (moved from SourceForge)