Go to file
Alan Pope 14cf2ce8a6
Update snapcraft configuration
This changes the build slightly. If snapcraft is triggered when there is a new tagged release in the project github release page, and it's newer than the version in the Snap Store beta channel, we build that stable release. If however, the latest stable release in github releases is already the same as the Snap Store beta channel, then we build the tip of master.

This gives a couple of advantages. 

  * One yaml can be used to build tip-of-git snaps, and stable releases alike
  * Closing the beta channel in the Snap Store will mean the next triggered build will re-build whatever the last stable release is. This is useful to force a rebuild of the stable version in case a dependency (not that there are many) has a security issue.

We also now set the version dynamically based on the git tags.
2020-01-13 11:14:08 +00:00
snap Update snapcraft configuration 2020-01-13 11:14:08 +00:00
src upgrade reqwest to v0.10.0 2020-01-07 14:22:32 +09:00
.appveyor.yml ignore beta channel again on AppVeyor 2020-01-07 17:31:36 +09:00
.gitignore Add Cargo.lock file 2019-12-03 00:30:57 -05:00
.travis.yml check beta channel on CI not to break this crate with next Rust version 2020-01-07 15:28:29 +09:00
Cargo.lock upgrade reqwest to v0.10.0 2020-01-07 14:22:32 +09:00
Cargo.toml upgrade reqwest to v0.10.0 2020-01-07 14:22:32 +09:00
LICENSE Rewrite program in Rust 2019-08-22 23:17:15 -04:00
Makefile Add --locked flag to the cargo build/test 2019-12-03 23:12:52 -05:00
README.md add option for saving output to file 2019-12-26 00:45:20 -05:00

Travis CI Build Status AppVeyor Build status

 ___     ___________    __________      ___________________    ___
|   \   /           \  |          |    |                   |  |   |
|    \_/     __      \_|    __    |    |    ___     ___    |__|   |
|           |  |           |  |   |    |   |   |   |   |          |
|           |__|    _      |__|   |____|   |   |   |   |    __    |
|   |\_/|          | \                     |   |   |   |   |  |   |
|___|   |__________|  \____________________|   |___|   |___|  |___|

A data hoarder's dream come true: bundle any web page into a single HTML file.
You can finally replace that gazillion of open tabs with a gazillion of .html files stored somewhere on your precious little drive.

Unlike the conventional "Save page as", monolith not only saves the target document, it embeds CSS, image, and JavaScript assets all at once, producing a single HTML5 document that is a joy to store and share.

If compared to saving websites with wget -mpk, this tool embeds all assets as data URLs and therefore lets browsers render the saved page exactly the way it was on the Internet, even when no network connection is available.

Installation

From source

$ git clone https://github.com/Y2Z/monolith.git
$ cd monolith
$ cargo install --path .

On macOS (via Homebrew)

$ brew install monolith

Usage

$ monolith https://lyrics.github.io/db/p/portishead/dummy/roads/ -o portishead-roads-lyrics.html

Options

  • -c: Ignore styles
  • -f: Exclude iframes
  • -i: Remove images
  • -I: Isolate document
  • -j: Exclude JavaScript
  • -k: Accept invalid X.509 (TLS) certificates
  • -o: Write output to file
  • -s: Silent mode
  • -u: Specify custom User-Agent

License

The Unlicense

Keep in mind that monolith is not aware of your browser's session