Tenzer

There is already pretty decent documentation on the Mastodon website for how to install and configure a server: https://docs.joinmastodon.org/admin/prerequisites/.

If you'd like to see the NixOS way I used, I could probably make a separate blog post about that.

When I got started with Mastodon, I myself was trying to find resources on when or when not to run your own Mastodon server, but had a hard time of finding that, so I hoped the post at least could help answer that for other people, although my experience with running Mastodon obviously is limited for now.

I've previously profiled pipenv and found it to be slowed down massively due to launching pip for each package it was working on. Unfortunately the maintainers think the progress bar is more important than performance: https://github.com/pypa/pipenv/issues/2207

I think most browsers don't include referrer information when clicking a link on a HTTPS site which leads to a HTTP site, but other than that I believe the information is kept by default.

Site owners can however tell browsers how much information they should include in the "referer" header via the "Referrer-Policy" response header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re....

Perhaps you can use my command line image printer for something like that: https://github.com/Tenzer/explosion.

I can definitely relate to that, my biggest pet peeve is probably people writing ElasticSearch instead of Elasticsearch - even though it isn't written like that anywhere on the official website.

On the topic of the Schuko plug, I never really understood why there had to be that many variations of it. Being from Denmark, I have more often than not had problems with the ground pin obstructing me from using a Danish plug in other countries. It has often times lead me to either saw off the ground pin, or replace the plug with a two-pin connector without the ground pin - in both cases decreasing the security of the plug for accessibility.

Python 3.4? Really? Why not 3.5!

The post ends with "We look forward to your feedback as you try out nginScript [...]" but it doesn't mention where we can test it out. Does anybody know more about that?

It might be worth noting that if you pickle data in Python 3 then it actually has protocol versions which aren't compatible with Python 2: https://docs.python.org/3/library/pickle.html#data-stream-fo....

Sure, that's also what I cover in the post. The latter part about rewriting is only relevant when you want to have the service behind an ELB to be located at something else than "/".

No, you can't. You can instead create your own EC2 server, give it a static IP (well, "Elastic IP") and then hope your own server doesn't go down. This is the reason why I prefer to use an ELB since I never seen stability issues with it.

Neat! I want to get started on some Lua scripting as well, probably first to just get a bunch of metrics out of Nginx via StatsD. There's access to a whole bunch of numbers via Lua that you otherwise can't get out from the stub_status page.

I would expect that to be the way the Nginx Plus implementation works, but I have never had a chance to try it out.

Dynamic modules are on the road map, according to this article: http://www.infoworld.com/article/2951849/web-services/nginx-....

Sure, that's not really related to the protocol used. It's instead handled by the upstream module and the "ip_hash" flag: http://nginx.org/en/docs/http/ngx_http_upstream_module.html#....

You can also use Nginx for the PROXY protocol, that was added in version 1.5.12. You should just add "proxy_protocol" to your "listen" directive: http://nginx.org/en/docs/http/ngx_http_core_module.html#list....

Regarding how the ELB works, then I think the AWS engineers have a different idea on how to implement stuff. AWS is very much a dynamic platform and the engineers seem to have embraced this when they came up with this solution.

It doesn't necessarily mean you can't use websockets through an ELB, it just means that you would need to be able to handle reconnects, but that shouldn't be a new challenge for any system relying on connections being open for long. Also, the load balancer servers doesn't switch every 60 seconds, you can have connections running for a lot longer than that. I would also assume the load balancers keep handling connections for a while after they were taken out of the DNS rotation, in order to make sure DNS caches are updated before the IP addresses stops working.

I think the reasoning for it is for performance. If you can make all the DNS queries you need before you start serving any requests, then you don't have to wait for DNS servers while clients hammer your server.

Ideally I would have like it to be an option though, instead of it basically having become a feature in Nginx Plus - if it wasn't for the way I described in the post.

It's good to hear it was of use to somebody :)

I know you can use a map in Nginx to do what you ask for, as long as you have a list of domains already: http://nginx.org/en/docs/http/ngx_http_map_module.html#map. I can only imagine it also being possible to make fully dynamic, I just don't have a clear way of doing it in mind right now.