Description of change

Adds button to /profile to delete all user data on the site and log them out.

Related issue

Fixes #17

How has this been tested?

Manually.

Screenshots (if appropriate):

Description of change

README.md had some formatting issues in the list for development instructions. Also updated .env.example with instructions on how to find out Kilometrikisa competition ID (works also before the competition starts).

Related issue

None.

How has this been tested?

Visually :)

Screenshots (if appropriate):

Before

After

It would be nice to have a possiblity for the user to delete all of their data from the database. Maybe just add a button to the account page "Delete all my data" etc. which prompts for verification and then deletes the row in the db containing the same stravaId as in user's session.

Description of change

Run worker in the main app for Heroku hobby plan. While it might be a good idea to run this in Heroku worker dyno, to save some hosting costs try to run it on web dyno. The code is async and shouldn't be that heavy anyway so I think it should be fine. Will be enabled in Beta for some time to see if any problems arise.

Description of change

Update some npm packages to remove critical security concerns and remove obsolete pieces of information from the site referring to previous developers and replacing those with Github links etc.

Description of change

Port to Typescript. Not completely verified in production just yet and missing unit tests etc. but better have this merged now for easier continued effort.

I exchanged emails with Kilometrikisa.fi about this app and ultimately decided that I'm not personally going to host this publicly. Main reasons being that I personally probably don't have time to maintain the production environment nor I feel that comfortable hosting a public service which stores users' usernames and passwords in its database in a reversible form, encrypted or not.

Personally I think the best option would be that Kilometrikisa.fi allows direct integration to Strava or exposes a public API for app developers instead of the current solution.

That being said they have certainly recognized the wish of community to have a Strava sync feature and as far as I can tell they seem to be open to make it possible as long as you cooperate with them. So if anyone (or their company/employer) would be willing to make this happen (with this project as a base or as a separate project), I'd encourage you to be in contact with them.

I'll leave this repository here in case anyone of you wants to host it or develop it further with Kilometrikisa.fi.

The site uses cookies only for necessary functions and doesn't contain tracking cookies etc. However, it might be good to be explicit about this because of GDPR. Maybe just adding a mention of this to the FAQ page explaining that the site uses only cookies which are required for it to function is enough (since no permission from user can/should be asked for them).

Could be something like: "What is the cookie policy?" "Only cookies which are essential for site's functionality are used."

We should separate frontend and backend code in top level instead of having the frontend JS inside the app/assets/ directory where webpack picks it up and for bundles to the app/assets/dist directory. Maybe something like

assets/
src/
  frontend/
    js/
    scss/
  backend/
    <backend files here...>

At the moment everything related to app routing and app setup of the Express in general have been stuffed to the index.ts as in the old app. It would not be a bad idea to go through the code and organize that to sensible separate files.

There is probably some common practices how routes etc. are usually organized in (small) Express apps.

Some of the depedencies of old webpack plugins have potential security vulnerabilities as reported by npm audit and dependabot. We should update webpack to version 5 to get rid of those.