I'm very happy using docker swarm on a single host with traefik as reverse proxy using the setup described here: https://dockerswarm.rocks/
Super easy deployment of additional apps, defined completely in one file (incl setup on host, backups, reverse proxy config, etc).
Never found a reason to migrate away. Swarm was already considered dead when I started using it in 2022[1], but the investment was so low and benefits so big, that it was the right choice for me. I think a lot of people are replicating swarm features with compose, losing a lot of time. But hey, to each their own choice!
Docker context for remote access - over Internet or vpn, whatever.
Swarm-cronjob for scheduled things.
Labels for things that need to run in particular places.
So easy.
Personally, k8s is fine, but its an abstraction for building a service architecture, not the thing an end user (developer) should ever use. If you are in a big company and you are using helm or k8s yaml files to roll things out, your infra or platform teams have missed something out.. building the platform!
As I read it, they didn't look up the account to process the refund. They looked up the account to decide whether to process the refund, and then the decision was "no".
The rest of the support response is just pleasantries and padding, to dance around this fact ("Your detailed reproduction steps will be valuable" blah blah).
I have such a project I just can't shut down: https://myowndb.com/
I started it 20 years ago, with ruby on rails. I neglected it but then decided to rewrite it in F# and publish it as open source (https://gitlab.com/myowndb/myowndb).
There are very few users, some from many years ago, all non paying. None gave any feedback I asked during the rewrite.
I should have shut it down years ago, but I just can't take the step. I'm focused on another project now, but who knows, maybe I'll get back to it....
Hey that looks pretty neat! I sort of miss MS Access sometimes, and this feels like it might fill the same niche. The star count also just went up 50% :-D
Does it use Sqlite or something on the backend, or is it all it's own? Do you know if it runs on Linux?
Edit: My answers based on a quick review (please correct if I'm wrong). It uses Postgres (cool!) and definitely runs on Linux (I see Dockerfile in there). UI is through the browser?
Perfect website! Clear texts, clear screenshots, and an about page with a small photo of the person behind it. If I wasn't already using PHPMyAdmin I would definitely consider your product trustworthy. Am I right that it is - sort of - the same functionality as PHPMyAdmin?
I especially appreciate the honesty about the upcoming pricing. Do you plan/want to make it a business?
Thanks for the positive feedback!
It combines administration features and end user interace. The definition of data structure is not very intuitive, and that would be the first and most important thing to fix. I think a lot of people get lost at the definition of their first table....
Am I missing something? I'm genuinely surprised it was not deployed from the start on a dedicated server. Don't you make a cost analysis before deploy? And if the cost analysis was ok at initial deploy, why wait to have such a difference in cost before migrating? How much money goes wasted in such situations?
Managed services have value. It's less to set up, less to maintain, and less worrying about waking up at 3am when something breaks.
I've spent time eating the costs of things like DigitalOcean or SaaS products because my time is better spent growing my revenue than reducing infrastructure costs. But at some point, costs can grow large enough that's it's worthwhile to shift focus to reducing infrastructure spend.
One (amongst other) big problem with current software supply chain is that a lot of tools and dependencies are downloaded (eg from GitHub releases) without any validation that it was published by the expected author. That's why I'm working on an open source, auditable, accountless, self hostable, multi sig file authentication solution. The multi sig approach can protect against axios-like breaches. If this is of interest to you, take a look at https://asfaload.com/
Artifact attestation are indeed another solution based on https://www.sigstore.dev/ . I still think Asfaload is a good alternative, making different choices than sigstore:
- Asfaload is accountless(keys are identity) while sigstore relies on openid connect[1], which will tie most user to a mega corp
- Asfaload ' backend is a public git, making it easily auditable
- Asfaload will be easy to self host, meaning you can easily deploy it internally
- Asfaload is multisig, meaning event if GitHub account is breached, malevolent artifacts can be detected
- validating a download is transparant to the user, which only requires the download url, contrary to sigstore [2]
So Asfaload is not the only solution, but I think it has some unique characteristics that make it worth evaluating.
Yes, that's why I aim to make the checks transparant to the user. You only need to provide the download url for the authentication to take place. I really need to record a small demo of it.
Overall I believe this is the right approach and something like this is what's required. I can't see any code or your product though so I'm not sure what to make of it.
I'm working on a multi signature solution that helps to detect unauthorized releases in the case of an account hijack. It is open source, self hostable, accountless and I am looking for feedback!
Super easy deployment of additional apps, defined completely in one file (incl setup on host, backups, reverse proxy config, etc).
Never found a reason to migrate away. Swarm was already considered dead when I started using it in 2022[1], but the investment was so low and benefits so big, that it was the right choice for me. I think a lot of people are replicating swarm features with compose, losing a lot of time. But hey, to each their own choice!
1: https://www.yvesdennels.com/posts/docker-swarm-in-2022/
reply