Get a better name

[bep]

While this is mainly a tool motivated by my own need, I'm sure there are others that will find this useful. I plan to get this into a solid state with good test coverage.

And even if the current name s3tlsproxy covers what it currently does, it is a mouthful and may not be accurate in the future (I may add more storage providers in addition to Amazon S3).

Anyone got a good name for this?

[onedrawingperday]

How about Fantine? Or name it after another character from Victor Hugo's Les Misérables? https://en.wikipedia.org/wiki/Les_Mis%C3%A9rables#Characters

Since this is meant as "a poor man's Netlify". And the primary use case is for Hugo sites why not draw from Victor Hugo's work.

(just a suggestion)

[rdwatters]

I like the idea of keeping it with a Victor Hugo character too. There's also those form Hunchback:

• Quasimodo
• Esmeralda

That's if you want clever names. Sometimes more machine-readable titling has it's benefits in terms of discoverability and SEO:

• Hugo CDN
  ???

[bep]

Thanks for the input, gang;

I really like Fantine and I'm going to sing that for myself for a day or two. If I decide to pick a domain for it, the availability looks OK (domain sharks are coming ...). So, googling for "fantine" will always be filled with Anne Hatheaway, but I guess one could have domain "fantine.xx" and call it "Fantine Server" when talking about it.

[rdwatters]

.io domains are always overpriced. However...on second though, I'll DM you my suggestion:)

…

Sent from my iPhone

On Aug 26, 2017, at 2:47 PM, Bjørn Erik Pedersen ***@***.***> wrote: Thanks for the input, gang; I really like Fantine and I'm going to sing that for myself for a day or two. If I decide to pick a domain for it, the availability looks OK (domain sharks are coming ...). So, googling for "fantine" will always be filled with Anne Hatheaway, but I guess one could have domain "fantine.xx" and call it "Fantine Server" when talking about it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[bep]

On a side note: I'm very impressed with CircleCI 2.0.

▶ date; git push -f
Sun Aug 27 19:50:06 CEST 2017
...
level=info area=cache tag=purge prefix=<myhostname> count=2 time=2017-08-27T19:50:23.790456224+02:00

18 seconds from content change push to a call back received from CircleCI with a cache purge request is really, really fast considering the fair amount of steps included.