(Visual) CMS for Jekyll

Published 2017-06-22, 12:20

Jekyll is „a blog-aware, static site generator in Ruby“. It also is used by Github Pages, which means you can host simple static sites, managed via Git, for free with it. That’s great.

Not that great (for me) is that you have to manage the content in the file system and manually handle Markdown files. That’s why there are multiple visual, hosted CMS for Jekyll.

I looked at some of them:

(A more complete list is at headlessCMS.org.)

So because of the shortcomings of Siteleaf (unusable because of messing with my data), Forestry (buggy editors) and Cloudcanon (doesn’t support advanced stuff) I am actually using Prose right now.

(Of course there also several options you can self host, but as that kind of defeats the purpose to go to a Github Pages hosted static site – now I have o host the CMS myself – I skipped those. Still, some links: MeetHyde, jekyll-admin)

Topic(s): Kram, Link No comments - :(

YouTube RSS Feeds

Published 2017-04-23, 22:47

Source: http://stackoverflow.com/a/31535120

Topic(s): Link No comments - :(

Mac OS X: Unabhängige Scroll-Richtung für Maus und Touchpad

Published 2017-04-04, 12:28

Natural Scrolling ist toll auf Mac OS X. Allerdings nur mit dem Touchpad, nicht mit der angeschlossenen USB-Maus. Dummerweise sind die „Scroll Direction“-Einstellungen von Maus und Touchpad aneinander gekoppelt, so dass wenn die eine (de)aktiviert wird, die andere dies auch tut.

Heute aber eine Lösung gefunden: https://pilotmoon.com/scrollreverser/
Installiert, konfiguriert, Problem behoben.

Topic(s): Link No comments - :(

Windows 10: WLAN/Netzwerk von „Öffentliches Netzwerk“ auf „Privates Netzwerk“ umstellen

Published 2017-03-30, 13:20

Mit Windows 10 hat sich (mal wieder) geändert, wie man sein WLAN/Netzwerk von „öffentlich“ auf „privat“ umstellen kann. Das ist relevant weil die Windows Firewall zwischen diesen beiden Klassen von Verbindungen unterscheidet und manche Verbindung aus Versehen falsch kategorisiert werden kann. Also muss man es ändern. Nur wo?

Die Einstellung findet sich nun in den „Einstellungen“ (bzw. „Eigenschaften“, je nach dem wo man es findet) des jeweiligen WLANs/Netzwerkes und wird dort als „Dieser PC soll gefunden werden“ bezeichnet. Ist dieser Schalter auf „Ein“, wird die Verbindung als „privat“ gehandhabt, bei „Aus“ eben als „öffentlich“.

Logisch, oder? *augenroll

Viele weitere Möglichkeiten finden sich hier: https://www.deskmodder.de/wiki/index.php?title=Netzwerk_%C3%B6ffentlich_privat_%C3%A4ndern_Windows_10

Topic(s): Notiz, Technik No comments - :(

Remove security from a secured PDF file

Published 2017-03-07, 21:41

One of my banks stopped offering downloadable CSV files of the statements af account. Bastards.

Luckily they still offer the monthly statement as a PDF. Parse that (parsing PDFs always is a pain, but possible), you have a CSV.

Unfortunately the PDFs offered for download are Secured PDF files. And most PDF parsing libraries can’t or don’t want to handle secured files.

„Well, bank statements are sensitive information!“ you might say. Yes they are. So I would understand if they used a security setting that requires a password to open a file. But they don’t do that. The file is just secured so… I don’t know exactly. I can do everything but open them by my trusted library.

I could just open all the files and then print them again as PDF to have an unsecured PDF file. But as I have lots of statements, this doesn’t sound too fun.

Of course there are also many paid softwares to remove PDF passwords and security features. Most cost once to register, some even monthly. Meh.

But if you spend some more time googling, there are also FREE tools:

Weeny’s tool is really nice and super usable. Happy ‚customer‘ here :)

Topic(s): Kram, Link No comments - :(

git: How to rewrite history on commits that you already pushed to the remote/origin

Published 2017-02-14, 18:42

(Written October 2013)

Let’s phrase this another way:
How to rewrite commits that are already on Github?
Ho to clean up commits that I already synced?
How to rewrite public history on git?

As you probably know git is much more flexible with branches, commits and all that stuff than other CVSs like SVN were. Commits are done locally and more like local snapshots that still can be changed, where commits in SVN are directly on the server/repository and can’t be changed. So there are lot’s of tutorials that explain how all this works:

But the one thing all these instructions don’t tell you, is what to do when you already synced (pushed) these commits to the remote origin. We only get quotes like these:

Once you have published/pushed your work to shared repositories, we very much recommend against going through post-production with it. That is known as rewriting public history and in general requires telling everyone of your failings as a developer so that they can do the necessary work to recover on their side.

A word of caution: Only do this on commits that haven’t been pushed an external repository. If others have based work off of the commits that you’re going to delete, plenty of conflicts can occur. Just don’t rewrite your history if it’s been shared with others.

Don’t include any commit you’ve already pushed to a central server — doing so will confuse other developers by providing an alternate version of the same change.

or my favorite one from the GitHub documentation:

Warning: It is considered bad practice to rebase commits which you have already pushed to a remote repository. Doing so may invoke the wrath of the git gods.

There are good reasons for this if you work with other people.

Obviously this doesn’t help, when you want to rewrite public history. There are lots of cases where you want to do that, especially if you are the only committer to a project and there is noone else to consider.

Before you start playing around with rebase, it’s probably a good idea to make a backup of your current state to a branch:
$ git branch backup-branch
Then if something goes horribly wrong with you workign copy you can just get the old state back:
$ git reset --hard backup-branch

Then you can continue doing the rebase like it is described in one of these tutorials:

And after all that, the magic thing to do is this:
git push --force origin master

By the way, the sources I finally found for this, after fighting for several days, were these:

Topic(s): Technik No comments - :(

Free MS Project Viewer

Published 2017-02-14, 18:39

(Finally posted this old draft)

Topic(s): Research No comments - :(

API Load Testing

Published 2017-02-14, 13:27

Last year I not only needed to log JavaScript errors but also find a way to load test a REST(ish) API. Again some bookmarks that resulted out of my research on how to load test an API:

Software as a Service

Articles / Blog Posts

JavaScript Error Tracking and Logging

Published 2017-02-14, 13:19

Last year I needed a solution for logging and tracking errors in a JavaScript application and spent some time researching services and tools to resolve this need. This is a cleaned up dump of my bookmarks that resulted out of this research:

SaaS

Google Analytics

self-hosted

hacky

Cordova/Ionic support

As I needed it for a Ioinic app and didn’t really have a budget I went with jslog.me which worked totally fine for my needs.

Topic(s): Technik 1 single comment - :/

Keychain: How to delete one certificate whose private key is also connected to other certificates without deleting this private key

Published 2015-11-25, 14:57

When you try to delete a certain certificate, Keychain by default also deletes the private key that certificate is connected to. As you don’t want to make all your other certificates that use the same private key useless, this can be a problem.

This is how you solve this problem:

  1. Create a backup of your original keychain. You may break something, and then want to go back to where you where before
  2. Create a new keychain ‚foo‘
  3. Move the certificate you want to get rid of to this new keychain
    (This will also copy the private key of this cert and remove it from all your other certificates – which are not useless)
  4. Move only the private key back to your original keychain
    (This will of course remove it from the cert you want to delete anyway and move it back to all the certs you want to keep – that are now whole again)
  5. Check if all the certificates in your original keychain are valid again and have their private key back
  6. Delete the ‚foo‘ keychain with only the cert inside
  7. Tadaaa!

But Apple software is sooo convenient…

Topic(s): Kram No comments - :(

15 queries. 0,200 seconds.