Nice visualization of the new infections by state: rt.live.
I wanted to enable a file upload. Whenever I was uploading I received the error code “413 Request Entity Too Large” from the nginx ingress controller in kubernetes.
I found the solution here.
Use the following annotation to allow unlimited upload size:
In my case, the ingress file definition now looks like this:
--- apiVersion: networking.k8s.io/v1beta1 # for versions before 1.14 use extensions/v1beta1 kind: Ingress metadata: name: my-name namespace: my-namespace annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 nginx.ingress.kubernetes.io/proxy-body-size: "0" spec: # The specs, omitted for readability
Today, I am launching writic.app. I was always looking for a solution to keep a journal which is online but private - something which is very hard to find across all the available social networks. The following features are essential to me:
These kinds of data is obviously very sensitive and I believe some things should stay private. For this reason I created Writic. I wanted to create the ability to access this data from anywhere where there is internet and also at the same time offer access from the smartphone as well as the browser. Many of the apps I have tested do either one thing only or are full of features I don’t really require. With Writic, I am trying to keep it simple and avoid any clutter, especially ads and selling of any personal data.
I am planning to keep it initially free of charge and later introduce either a pay-what-you-want or a minimal fee like $1/month, depending on the user base. Another option I am considering is a “pro” version with more advanced features.
Things I am currently considering for the roadmap are:
Interesting list of things that the author learned the hard way
Sometimes, you’ll have to say no: No, I can’t do it; no, it can’t be made in this time; no, I don’t feel capable of doing this; no, I don’t feel comfortable writing this.