Session timeouts

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
backend

Research direction

No files, tests, or entry points are named. First clarify whether both expiration and persistence across server restarts are required, then locate the session implementation and its existing tests; done means sessions expire after the chosen period and survive a server restart.

Written by the indexing model from the issue text.

Description

enhancement

Currently, sessions do not expire, but are lost when the racket-pkg-website server restarts.

It might be nice to (a) have them expire; perhaps after, oh, a week? and (b) have them survive server restarts.

(xref: This is half of issue #25)

Dominant language
Racket
Stars
13
Forks
17
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from racket/racket-pkg-website

All issues in racket/racket-pkg-website

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.