janejeon / blink Goto Github PK

E.g.

• rather than hitting the database every request, cache id => req.user and make a node instance listen to the postgres changes. When a user change comes through, bust that cache.
• rather than having to hit settings every request (see #143), cache settings and basically only bust it when the node is notified of a settings change.

This can probably also help with #158, as having a stream of changes makes it easy to save it.

At the very least, when the express server stops, so should the nextjs server (webpack for dev, not sure for prod)

Should come after #29

And plan ahead for use by both private and public organizations of various sizes.

And really do consider using stock solutions, like keystone or strapi or adminbro.

role-acl works well for simpler stuff, but the need to rely on the clunky $. syntax for comparing anything and the inflexibility of constructing policies (it ALWAYS has to compare a resource field against a body field) is really shit for larger projects.

casl packages are annoying AF, the only reason we were using mongoose was to try casl.

Continuous Integration

https://dev.to/alexandrupero/continuous-delivery-with-github-actions-docker-and-traefik-on-a-virtual-private-server-part-1-3285 (i.e. build & push images to github docker registry)

Continuous Deployment

https://medium.com/swlh/deploying-docker-compose-applications-with-ansible-and-github-actions-7f1740392507
https://stackoverflow.com/questions/42302632/docker-compose-continuous-deployment-setup

We just updated the upstream objection-hashid dependency, meaning we can include EmOjIs as part of the link shortener.

EMOJIS.

To do this, we need to LOCK DOWN the alphabet (because otherwise the hashid for existing links might break), meaning we can't just "add" emoji support later on. So we'd have to include ALL emojis to support in the JSON schema regex...

/blah and /BlAh should both lead to the same place. While we're at it, should we have this be case-insensitive?

While /:hash doesn't work for find-my-way, you can have "default" route handlers... do we want to move to restana (not fastify because they don't believe in monkey patching and won't work with passport)?

https://github.com/JaneJeon/lynx/blob/8b248efc49883049fae11f234c2412b28155dbbb/.circleci/config.yml#L49-L53

This issue was generated by todo based on a TODO comment in 8b248ef. It's been assigned to @JaneJeon because they committed the code.

I'm just not sure how to go about this, or which ones to preserve.

For example, /login might be used internally to redirect people to the login page, etc.

For that sweet, sweet free runner minutes

We need some sort of dashboard to manage links and view stats.

Some candidates/inspirations:

• custom
• keystone
• strapi (imo too much scope)
• adminbro
• https://administrate-prototype.herokuapp.com/admin (holy shit it looks beautiful)

https://vincit.github.io/objection.js/recipes/polymorphic-associations.html

1. The policy itself should be configurable by the owner/admin
2. Adding a hash/setting a hash/"ownership" transfer after a user's deletion, etc.

Right now I’m dockerizing basically everything except the actual node server. With the addition of workers, it would be helpful to dockerize the entire stack so development & testing becomes easier.

However, there are some challenges:

1. Making code/dependency changes transparent to the development/test container
2. Making sure I don’t recreate everything from scratch anytime I change anything
3. “Productionizing” the stack (esp. with regards to HTTPS and reverse proxy - might have to turn to Traefik, eww), though that may come later after I get the dev/test setup completely dockerized.

Also of note, this is blocked by #428 since Circle does NOT play nice with docker-compose testing...

And point out the new focus

In either case, I want to renter the dashboard pages with React, just so I can try out @casl/react.

See knex/knex#2686

Including existing features

This should preferably be done with the “production” build (aka static SPA being served from the backend) since I’m pretty sure I fucked up some URL config somewhere

(and to be able to tie users between GH/GL means I'd need to normalize emails and use that as the sort of primary key)

https://github.com/JaneJeon/lynx/blob/29a450e11f8813579878b40bd17d3ed7458068a6/.circleci/config.yml#L40-L45

This issue was generated by todo based on a todo comment in 29a450e. It's been assigned to @JaneJeon because they committed the code.

Use acl.yml

and convert ACL while I'm at it

Blocked on #29. Also see #169.

Instead of directly setting id, maybe have hash setter? But how will this affect the ACL's property-based rules?

Also tangentially related to https://github.com/JaneJeon/myURL/projects/6?

I just noticed that despite caching ~/.npm, CircleCI is still downloading Firefox and Chrome!

- restore_cache:
        keys:
          - v1-deps-{{ checksum "package-lock.json" }}
    - run: npm install
    - save_cache:
        key: v1-deps-{{ checksum "package-lock.json" }}
        paths:
          - node_modules

Cause honestly "myURL" was a bad name...

• Links page
• The link shortener main page? Preferably pack it into a component so it can be moved later down the line
• Make Link views refer to users' names based on their ID's (lookup IdP)

This would be the "default" analytics, but it should be pluggable.

• Page for POST /links
• Page for GET /links
• Page for GET /links/:id
• Page for GET /users
• Page for GET /users/:id
• Page for GET /users/:id/links
• plus whatever navigational tools are needed (e.g. navbar)

No analytics yet. Depends on #31.

Specifically, when you have a link that has randomly generated hash and you want to give it a custom hash, either allow duplicate copies to exist or move the randomly generated one into the custom one

Just look at what bitly/kutt does and copy it I guess

• Endpoints for getting user info from user id’s (have to call OIDC userinfo endpoint, good fucking luck configuring that oof)
• “hydrating” the frontend information with said user info (e.g. user name/avatar)
• login/logout
• “self” info (aka who you’re logged in as)

We should also test w/ both MySQL and Postgres databases...

Plus I’m also leaning towards yeeting the knex case mapper

Currently, a few tests are hacky (at best) due to having to worry about global state during tests.

I should "transaction-ify" tests to make sure every test is idempotent.

• User models
• User routes

• Add knexcasemapper
• Change originalURL to originalUrl, and so on. This needs to be done for JSON Schema, model properties, and the frontend