songtianlun
c9aef3ddfe
- Add checkout step to retrieve full git history - Introduce a step to get the current version of the project - Modify login step to use the actor's username instead of a constant - Update the tags to use dynamic versioning in Docker image push These changes improve the Docker workflow by ensuring that the correct version tag is used when building and pushing Docker images. The modified steps enhance traceability and allow the workflow to handle versioning accurately based on current git tags, addressing the need for specific version control in the images produced. |
||
|---|---|---|
| .github | ||
| .kamal | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| lib/tasks | ||
| log | ||
| public | ||
| script | ||
| storage | ||
| test | ||
| tmp | ||
| vendor | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .node-version | ||
| .rubocop.yml | ||
| .ruby-version | ||
| 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
-
...