darylf / longbox Goto Github PK

Let's use pg_search gem for searching the models

Here are some modern fonts to consider:

Inter
Roboto
Poppins
Montserrat
Fira Sans

The latest rebuild removed the ability to upload a cover image of each book.

See rails/rails#41757

This could be worth using. Let's do a POC

https://github.com/gregnavis/active_record_doctor

The N+1 queries on the API are slowing down the app. We should use React Suspense to provide better loading feedback to the user.

See: https://reactjs.org/docs/concurrent-mode-suspense.html

Let's consider using the Guard gem to run a local continuous testing environment in the docker container.

Read more: https://github.com/guard/guard-rspec

Rails 5.2.0 was released on April 9, 2018. Basecamp and Shopify are using it in production already. Let's consider updating this app to the latest stable version of rails.

Some features to investigate:

• Active Storage
• Bootsnap

Read more:

• https://weblog.rubyonrails.org/2018/4/9/Rails-5-2-0-final/

I'd like the ability to add a cover image to a book. This would enhance the user experience by making it more graphical and unique looking.

Now's the best time to implement this as we don't have any production data.

https://guides.rubyonrails.org/v5.0/active_record_postgresql.html#uuid-primary-keys

Upgrade the API to Rails 6

see: https://pentacent.medium.com/nginx-and-lets-encrypt-with-docker-in-less-than-5-minutes-b4b8a60d3a71

I'm reading that a good Docker practice is to build a single container per repo.

Longbox-UI: Build the react app and maybe nginx front-end.
Longbox-API: Build the Graphq

My Ruby docker container is about 1GB. That feels too big.

The following webpack warning shows up when running a new server:

This can impact web performance.
Assets: 
  bundle.js (4.08 MiB)

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  main (4.08 MiB)
      bundle.js

WARNING in webpack performance recommendations: 
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

I feel like Create-React-App (CRA) is including too many outdated dependencies, and I'm tripping over the eslint that's included in CRA by default.

Let's consider removing CRA and running the React client on Webpacker directly.

The web ui container is giving the following deprecation warning when run:

 CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
 changes to assets earlier, e. g. in Compilation.hooks.processAssets.
 sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
(Use `node --trace-deprecation ...` to show where the warning was created)

The recent manual build/deploy from Heroku is failing with the following message:

=== Fetching app code failed

=!= Your app does not include a heroku.yml build manifest. To deploy your app, either create a heroku.yml: https://devcenter.heroku.com/articles/heroku-yml-build-manifest

Or change your stack by running: 'heroku stack:set heroku-16'

In order to reduce the size of the deployed image, let's investigate using a multistage build file for the node.js client container.

This non-production application is triggering a lot of security vulnerabilities. Before we continue development, let's upgrade the dependencies to the latest secured versions