almarklein

That's quite recent. I guess the app is broken for (Mobile) Safari then. Sorry about that. I will make an issue.

I think it took a while for the cert to work on al continents, because of caching - the site has been up just a few hours :)

The API is not public yet. I plan to though. Out of interest, what are you building? Perhaps we should keep in touch :)

Thanks!

Transip is the domain registrar I use. Could it be some sort of caching problem? The site (and it's cert) have only been up for a few hours ...

Now that you're all here, I'm playing with the idea to create a CLI tool so that you can start and stop records from the command line. Would this be interesting to you or would it only be a gimmick?

Automated solutions like that seem really nice, but it's not possible for a web app to know much about what you're doing outside of the app itself.

Thanks for the feedback. 1. Is indeed a bug, will fix! 2. It does that, right? 3. Not sure if I follow. ATM the tags are in one cell, delimited by spaces.

I would expect Safari to work, could you tell me what version of Safari that is?

It is an interesting model, and developers seem to like it. TimeTagger is the successor to a similar product that is not open source, which I've posted about here, but never quite got a response like this :)

I love open source and maintain several open source projects. By making TimeTagger open source, I was hoping to find a niche of "tech" users. And if it fails, at least the code can be useful to someone else.

Familiar as in I know them, and I occasionally use vi (over ssh), but not a proper user :) Anyway, I created an issue: https://github.com/almarklein/timetagger/issues/11

Thanks for the heads-up. Weird, it uses Let's Encrypt, and I don't see any problems :/

I don't think my server has seen so much traffic in so little time. It seems to be holding up pretty well, but there are occasional requests that take a second or 2. I'm keeping an eye on the monitoring ...

Hi, I'm the author of TimeTagger. Thanks for your feedback. Right now you can click the record button and since a description is optional, click start right away.

Could you please elaborate how you would want this to be faster? A one click option, or perhaps a keyboard shortcut to start a timer? I'm eager to learn about potential workflows to make the experience more smooth :)

Thanks, fixed :)

Actually, a function could do the trick: https://github.com/almarklein/faq-div/issues/7

Thanks!

Not sure how to fix that, TBH. That text is configurable (e.g. for other languages) and I don't like "result(s)". I'll think about it though ...

Haha, yeah you could be right about it being hard to sell. We'll see. This was a side-project with a relatively small time investment. A bit of an experiment, really ...

I recall that Let's Encrypt was somewhat untrivial to setup (but this may have changed?). And I liked the idea of just pushing a container/recipy with metadata and let the server handle the rest.

I should add that when I found out about Dokku and CapRover I was already using Traefik+Docker, so I was also simply biased for Traefik (Traefik is awesome).

I did not know swarmpit yet. That seems really nice and it looks like it has overlapping goals with MyPaas. Does it allow you to do remote deploys?

Thanks. Yes, CapRover seems really nice. And also see Dokku. At some point in the past I decided both did not suit my needs. I can't remember the details exactly, but one thing with CapRover was that auth goes via username and password only, which I don't feel is safe enough (MyPaas uses RSA key pairs).

Anyway, I started out by tying Docker and Traefik together with a mix of Python and bash scripts. Eventually I decided to roll that together into something easier to maintain, so its also useful for others. And "others" includes my future self ;)

No, at the moment it does not support Docker-compose.

Thanks, I will update the readme to include more info.

To answer some: It pushes a zipped directory to the server, which includes a Dockerfile. There, the server builds the image and deploys it.

Deploying pre-build images is probably best done by using a Dockerfile that uses FROM to point to the pre-build image.