clarete

I'm excited to share a project that I've been working on. It is a tool that aims to be a friendly and powerful static HTML site generator backed by Org-Mode files. It should be very familiar for those who have used tools like hugo or jekyll. It's far away from being as comprehensive and stable as such tools, though I do aim to get there :)

Weblorg is a declarative API that defines routes similar to how lean HTTP application frameworks are structured. With a file at the root of the website conventionally called publish.el. It contains the routes with information to find Org-Mode files and templates to render them. It's backed by a powerful templating language and we're working on a more thorough and thorough documentation. You can check out some examples and learn more about it on our website:

   website: https://emacs.love/weblorg/
   release post: https://emacs.love/weblorg/posts/v0-1-1-we-re-live.html
   github: https://github.com/emacs-love/weblorg
   templatel: https://github.com/clarete/templatel

I saw this on Reddit, lwn and now here and I didn't see anyone comment on license upgrades. when FSF released GPLv3 they migrated a ton of software from one version to another.

although GPL is usually forward compatible with its newer versions I still wonder if that's the concern behind Stallman's opinion.

I'm not sure I'd count that source as valid after reading what they wrote in /brazil. The text has the same opinion as the media they rate as "partially free". They're defending the side that won without really understanding what happened there. I wonder how better the analysis on Cuba could be.

Hmm, bad news. I'll work on polishing the new proxy support that is almost done in another branch, so we'll be able to use more reliable services for now.

And then, when I have some time, I'll write the full thing on lisp! Thanks for the heads up!

Yeah! Thank you for the contribution, I'll apply your patch and release another version as soon as I get the chance to open my computer!

So, hackernews.el is actually a very simple front-end for the guy that really has to deal with hackernews. I'm using a library that I built on top of `ruby-hackernews`, you can see what I did here: https://github.com/clarete/rhn

Thank you man!

First things that come to my mind:

s3cmd: * might be considered more robust and battle tested as people already commented here; * is written in python, so if you have a python environment running, you might be more comfortable with it;

s3sync * Smaller codebase, might be easier to keep things simpler and well tested, achieving the same stability with less time/effort; * Error reporting. One of my main reasons to keep working on s3sync was its better error reporting. I just go crazy when something wrong happens and I don't know why. * It's in ruby, if you have a ruby environment and you don't want to add any python dependencies, you might choose it

Hi, thanks for asking! I definitely tried this guy before putting more effort on s3sync. Unfortunately their cli experience is really poor and its error report didn't help me understand why synchronizing my stuff with s3 was not working.

In the end of the day, I had an unreadable file inside of the directory that I was trying to back up. I found that out using `--debug` option of the official client, but I couldn't actually continue copying the files cause of that error.

When I tried with s3sync, as I expected, it just yielded a warning about the single file I had with problems and kept working until my backup was done!

Sorry for the wall of text, I just think it's funny cause this exact question came to my mind a couple days ago and that's how I answered my self! :)

Not currently! Please feel free to open a ticket about that! Thank you! :)

So, basically, the main difference is the language they're implemented in. I started working on s3sync cause I found its code easier to read and I really needed to practice my ruby skills.

Although s3cmd is older and has more features, s3sync was designed to grow stable and well tested. I'm definitely planning to write benchmarks to s3sync and improve its performance as much as I can.

I don't think that there's any implications for that, but I'll probably relicense this library as MIT or at least LGPL pretty soon.

I just used my default licence template, which defaults to GPL.

I might be wrong, but I don't think that it's actually possible to mock built-in objects (written in C, not in python) using pytest.

A very quick test would be trying to do something like this:

>>> monkeypatch(str, "blah", "bleh") >>> assert str.blah == "bleh"

I tried it here with no success though.

I have two main use cases in my mind right now.

1) Making it easier to write tools for testing python code, like sure[0] and freezegun[1]

2) Prototyping new features for python without touching the C code.

[0] http://github.com/gabrielfalcao/sure -- where forbiddenfruit started) [1] http://github.com/spulec/freezegun

That's the idea. Everything to make testing easier! :)