Back
Marc Köhlbrugge

Marc Köhlbrugge
PRO

@marc

Building too many things.
5
40
Joined September 2017
Load previous page…

Thank you! Appreciate it. And yes, production always ends up presenting new challenges somehow haha

Sorry yeah like @ben said I don't really maintain the Windows version as it's difficult for me to test. Getting Electron builds to work is tricky by itself, let alone if you don't have a machine to test one.

It's open source though, so if you want to have a look at it yourself you can do so here: github.com/marckohlbrugge/wip…

I also welcome any PRs that help fix the issue.

I plan on revisiting the menubar app in the future after I release the new API.

Oh, that's surprising. I wonder why?

The (new) founder, John, said that the user base isn’t as active as on Slack (though I doubt it is that much higher), and he is rebuilding the project. As far as I understood, the community can make their own bots, but no official ones in Telegram.

I mean it’s his own project, all and all, so I hope someone will make a TG bot at some point.

Again, gladly, WIP has an official bot hehe!

Appreciate that! Yes, the Telegram bot is a nice backup option for those that use it.

100% using managed databases. Don't trust myself to run those myself haha. At least with the web server, I know I can just nuke it and reset it with a few commands without any data loss.

And yes, Kamal lets you configure resources limits using Docker's config. I think it's called cap ? I haven't looked into it yet, but it seems like a good idea. So maybe set each container to use a maximum of 80% CPU usage, just so it never takes down the full machine? (assuming the other containers don't use up the remaining 20% at the same time)

I have never used cap but I have used resources with limits + reservations via compose which should just be passing those through as cli options: docs.docker.com/compose/compo… - I would ChatGPT this to see what args are 🤣

80% of 90% should be good enough to keep control of the box. I'm lazy and I have two or three dozen containers running without issues on a 4 GB droplet. Worse case, you can narrow it down to the service.

I'd typically pick a name where there's at least an upgrade path down the line to get the .com

So while you may not need it now, it would be smart to pick a name where the .com is unused even if it's at a high price right now. Long term, a good .com helps establish credibility and prevents any customer confusion.

This was my original concern, I feel like not having it may cost credibility should I look to garner significant investment or exit values down the line..

You're right though, just being unused, even if it's $10k and unattainable now, would be a good thing! Maybe that can be where I draw the filter line. Thanks!

This is a good strategy. I fear however it forces me to launch in stealth. Someone could easily grab the [.com] domain at that high price before you're able to buy it :( .

Current situation - juicy [.com] domain is available at $3,495 !

lol just noticed wip.com is some weird 90s crypto site 😆

Home
Search
Messages
Notifications
More