omn1

Joined 16 years ago

Karma

1,809

Submissions

220

Member since

Feb 20

View on Hacker News

Recent submissions

Three Lessons from My Interview with Pieter Levels wannabe-entrepreneur.com

2 omn1 4 years ago 0 comments

Comment · 4 years ago

Same. Used shuttle for https://endler.dev/2022/zerocal/ lately and was super happy with the experience. I no longer have to worry about hosting and can focus on the product instead.

Comment · 4 years ago

True, but for others to resolve the calendar entries you'd need to serve that file somewhere.

Comment · 4 years ago

Update: self-hosting works now. Added instructions to the docs. Have fun.

Comment · 4 years ago

Got it. The generator logic is in Rust yes. I could have written it in JavaScript as well but it was just easier for me to do that part in Rust. Should have mentioned that. Of course you could host a static HTML with JS on Github pages, but Github pages also runs on a server. So to answer the original question, yes you do need some server for it unless you make it a command line app.

Comment · 4 years ago

Good question. It depends on your definition of serverless. Strictly speaking there is no serverless, there's always some infrastructure somewhere.

However the calendar file gets created out of thin air from the GET parameters alone. There is no state or storage involved. Other calendar apps have a backend with a DB; this one doesn't. Now whether that counts as truly serverless is up to you I guess. It's as close as you could get with a calendar I'd say. Not easy to get the point across in a title. ;) Hope that helps.

Comment · 4 years ago

You could do that but you'd have to create the ics file manually and not every platform allows you to share ics files. My original use-case was Github. Wanted to share invites for https://github.com/hello-rust/community. Github prevents sharing ics. Another thing is that people could edit a link in-place to e.g. update the time without creating a new file.

Comment · 4 years ago

Not sure I understand because that's what it is basically. The Rust part is just for the routing; it decides whether to serve the form or the generated calendar file.

Comment · 4 years ago

Thanks for the info. I thought I fixed that lately [1]. I don't have an iPhone to test it with but I'll see what I can do.

At least on the Chrome viewport emulator it looks fine to me...