songtianlun
84c224cf8d
- Schedule RefreshSitemapWorker after initialization - Implement error handling for scheduling task - Use Rails cache to prevent multiple tasks running simultaneously This commit introduces a mechanism that schedules the RefreshSitemapWorker to run once after the application starts in production. It ensures that the task does not run multiple times concurrently by using a cache key. Error handling is included to log any failures in scheduling the task, improving overall reliability. |
||
---|---|---|
.github | ||
.kamal | ||
app | ||
bin | ||
config | ||
db | ||
lib/tasks | ||
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
-
...