This is a list of stuff that the average software developer does from week to week
- Code design
- Refactoring
- Algorithms
- Profiling
- Code reviews
- Building frameworks
| #!/bin/bash | |
| SERVER=/go/bin/api | |
| # create directory for Delve logs, we use it to know that Delve | |
| # debugger is running | |
| mkdir -p /tmp/dlv_log | |
| runServer() { | |
| echo Running server |
HackerNews discussed this with many alternative solutions: https://news.ycombinator.com/item?id=24893615
I already have my own domain name: mydomain.com. I wanted to be able to run some webapps on my Raspberry Pi 4B running
perpetually at home in headless mode (just needs 5W power and wireless internet). I wanted to be able to access these apps from public Internet. Dynamic DNS wasn't an option because my ISP blocks all incoming traffic. ngrok would work but the free plan is too restrictive.
I bought a cheap 2GB RAM, 20GB disk VM + a 25GB volume on Hetzner for about 4 EUR/month. Hetzner gave me a static IP for it. I haven't purchased a floating IP yet.
AddOn:
chrome/userChrome.css in your profile directory:| 1="Unsupported protocol. This build of curl has no support for this protocol." | |
| 2="Failed to initialize." | |
| 3="URL malformed. The syntax was not correct." | |
| 4="A feature or option that was needed to perform the desired request was not enabled or was explicitly disabled at build-time. To make curl able to do this, you probably need another build of libcurl!" | |
| 5="Couldn't resolve proxy. The given proxy host could not be resolved." | |
| 6="Couldn't resolve host. The given remote host was not resolved." | |
| 7="Failed to connect to host." | |
| 8="Weird server reply. The server sent data curl couldn't parse." | |
| 9="FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that doesn't exist on the server." | |
| 10="FTP accept failed. While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar." |
| db/schema.rb merge=railsschema |
Mosh is a great way to overcome lag and flakey connection issues when accessing remote terminals over SSH: https://mosh.org/
Unfortunately, there's still not a lot of clear documentation for "idiots" because a lot of the existing guides assume a) "it just works", or b) you're already skilled enough to set everything up from scratch (assumed knowledge/use cases).
One of the problems I ran into for quite a long time yesterday was getting the darn thing to connect to my Google Cloud instance. I kept running into the mosh: Nothing received from server on UDP port 60001. [To quit: Ctrl-^ .] error (by the way - to quit, you have to press . after Ctrl-^ - it's not just Ctrl-^, there is a dot there too!)
FAQs and the like made vague spartan references to NATs, firewalls, iptables and the like and I tried out various commands and configurations on the se
| function TransformStream() { | |
| var readableController, | |
| writableController, | |
| readable = new ReadableStream({ | |
| start(controller) { | |
| readableController = controller; | |
| }, | |
| cancel(reason) { | |
| writableController.error(reason); | |
| } |