46 karma · joined February 13, 2016
Currently working on https://serverbuddy.app.
Always open for chats/feedback about programming, devops and other topics.
E-mail: prabu at prabusoftware dot com
Yep, indie hackers are definitely a target group.
There is support for initial setup such as adding a new sudo user, installing Docker etc. but this isn't a single step operation. I'll write a document for this today or tomorrow.
I've though of adding support for Dokku(or something similar) in a separate tab to make managing apps easier. I will investigate and see what the best option might be.
In theory, the app can work on any Posix compliant Unix box and have fallbacks for tabs/sections where functionality is not implemented. However, this would require quite a bit of testing overhead. My current test suite matrix for a bunch of VMs with different auth methods already took quite a bit of effort to get working. I'm not sure I'd be able to ship new features/fixes quickly if the supported OSes list increases, at least for the time being.
When I need to accomplish something relatively large and standard(e.g. two node MySQL installation with a replica), I'd reach for my Ansible playbooks.
However, there are certain one-off flows for which I think SB has a sweet spot. Let's say I'm an agency managing web apps for multiple clients with separate VPS(es)/bare metal servers for each client.
If I get a ticket saying something's wrong with one of their app or its dependencies(let's say MySQL), it would be very easy for me to check the container health in the Docker tab and then check the detailed logs in the Logs tab to identify the issue. During this investigation, I might also check the Ports and other tabs to check external connectivity.
Another quick one off flow I can think of is to quickly check if everything's working after running an Anisble playbook on my server(s).
It might be worth writing Ansible playbooks for these workflows if one keeps finds they're doing them over and over, but I feel that a GUI option has some merit as well.
> As for hype: Another motive for "smalltalk" was the practice at the time of naming operating, and other, systems (which hardly did anything) after mighty indo-european gods, such as Thor, Zeus, Odin, etc. I figured that if Smalltalk ever did something neat, then people would be pleasantly surprised.
$ curl -I https://www.pharo.org/features
HTTP/1.1 200 OK
Date: Tue, 21 Jul 2020 05:18:23 GMT
Server: Zinc HTTP Components 1.0
Content-Type: text/html;charset=utf-8
Content-Length: 27546
Connection: close
Not sure how common it is to have it serve traffic directly instead of through a reverse proxy like nginx though.They should put their money where their mouth is and spend at least a few decades in such countries before criticising others who've made a choice to leave(for various reasons).
There are multiple search engines providing the same service that Google does and the cost of switching is so negligible as to be almost non-existent.
While I generally appreciate the EU's approach towards protecting the consumer's best interests, this just reeks of making up excuses to extort money from a highly successful company just because they can get away with it.
While using async is much easier with the new async/await syntax compared to traditional async solutions like twisted, tornado etc., a lot of popular database connectors and ORMs do not support async currently.
Even if the libraries a person needs are present at the moment, there's always the chance that a library maybe required in the future that does not support async and it may not be feasible to write a replacement(either due to the person's lack of expertise or due to lack of funds to hire someone else to write it).
In such a case, would using a traditional library by spawning threads to run any blocking operation be a good stop-gap solution(until an async replacement comes along)?