The logging level of the batch job worker has been changed from info to debug. The change affects how the batch job worker outputs information about the cities it is processing. - Original behavior: The batch job worker logs cities' information at the info level. - New behavior: The batch job worker logs cities' information at the debug level. The motivation behind this change is to reduce the noise in the logs. The new behavior will only log cities' information that is relevant for debugging purposes. |
||
---|---|---|
.github | ||
.kamal | ||
app | ||
bin | ||
config | ||
db | ||
lib | ||
log | ||
public | ||
script | ||
storage | ||
test | ||
tmp | ||
vendor | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.node-version | ||
.rubocop.yml | ||
.ruby-version | ||
compose.yaml | ||
config.ru | ||
Dockerfile | ||
Gemfile | ||
Gemfile.lock | ||
package.json | ||
Procfile.dev | ||
Rakefile | ||
README.md | ||
tailwind.config.js | ||
yarn.lock |
README
This README would normally document whatever steps are necessary to get the application up and running.
Things you may want to cover:
-
Ruby version
-
System dependencies
-
Configuration
-
Database creation
-
Database initialization
-
How to run the test suite
-
Services (job queues, cache servers, search engines, etc.)
-
Deployment instructions
-
...