I think having a single-page website is very valuable since it will allow people to use this as a homepage in any browser, without requiring an extension to be installed.

Done.

Another suggestion, now that I have this set as homepage, is to reduce the load time as much as possible. I expect it to load instantaneously, with no javascript or custom fonts - those are luxuries :) Ideally generate a static page for each book and serve one randomly.

I don't think a painted buffer is any good. A real solution would be physically separated bike lanes.

Preferably on the right hand side, that removes the drivers from the equation (most cars only have a single occupant), and it stops cars from having to cross the bike lane.

https://argu-logos.s3.amazonaws.com/photos/4357/Overtoom_Ams...

The bike lane is behind the parked cars next to the pedestrian area (and a little bit lower), you can see a cyclist on the left hand side of the picture.

Hey! Here's something very similar I've built with Angular too https://github.com/vahek/InvoicingJs

I recommend making use of localstorage, so the company info doesn't have to be entered every time.

Nicely done! The idea of using localstorage has been mentioned a couple times, For a couple fields localstorage does make sense. We were aiming more of a Firebase like backend support so that one is able to send out just links to invoices.

HN community has definitely given us a few ideas and we look forward to implement a couple of those.

localStorage on its way..will be pushed shortly.. +1

Thanks for the suggestions

There's this: http://ihackernews.com/ However, I'd really like an official responsive version.

I also recommend changing the default SSH port.

I hate it when people do that, myself. Especially when you have a lot of other tools, many of which don't take port arguments easily.

IMO best practice is to firewall off everything except some bastion hosts or VPN gateway.

Totally agree. If you stick to good security practices, working around a non-standard port is an unnecessary annoyance imho.

I actually do this on my personal server because more than one public wifi (and one of my previous jobs, at a public high school) disallowed outbound 22 connections.

Don't do this. It adds almost no extra security and makes it hard for routers that prioritizes port 22 traffic as interactive.

Sure, it'll not stop dedicated manual intrusion attempts, but it will actually prevent a ton of automated bots from even just trying to connect with common passwords through SSH.

Which is irrelevant if you have any one of: strong passwords, no passwords, fail2ban

Which is relevant if you're one to actually look at your login attempt logs.

Worth looking at:

http://bsdly.blogspot.com/2013/02/theres-no-protection-in-hi...

2222 is a dumb choice as an alternative port, it's both obvious and quite commonly used. I'm using a port on 4XXXX-range that's normally not used for anything and therefore not scanned by the bots unless all the 65536 ports are. The automated login attempts disappeared almost immediately, except for a few that were quickly blocked.

Now the logs are clean from automated login bots, the only thing left are real dedicated hacking attempts that is worth pursuing further.

It's what I do, you can't break in a door that doesn't exist, only those you know exist.

>Sure, it'll not stop dedicated manual intrusion attempts, but it will actually prevent a ton of automated bots

Doesn't take long to port scan a server.

Going back to the classics, is port knocking still a thing? (I've been out of this discussion for a while, serious question)

One of my freelance projects uses port knocking, but they're the only one I've worked with that have used it in recent years.

guess i'm going back to port 22...

I'm convinced too. Back to 22 we go.

Here's something I wrote very quickly (bash script): https://github.com/vahek/vSetup It does most of the stuff mentioned in the post, however doesn't setup automatic updates or Logwatch.

(to both corin and vahe): That kind of shell scripting is the horrorshow that motivated configuration management tools* in the first place. Shell scripts require a lot of added complexity to manage multiple heterogeneous servers, or to be idempotent.

* Puppet, Chef, Ansible, Salt, CFEngine, etc.

I agree. However, there is no learning curve to get started using this script and was put together in a few minutes.

Currently, mostly students, since course websites are kind of hard to find.