https://github.com/rdvid/piano-weekly-task
a microsservice to generate weekly tasks and send by email with cronjob for music theory practice
https://github.com/rdvid/piano-weekly-task
api-rest cloud cronjob docker email-sender flask linux microservice music-theory pdf-generation python
Last synced: about 1 year ago
JSON representation
a microsservice to generate weekly tasks and send by email with cronjob for music theory practice
- Host: GitHub
- URL: https://github.com/rdvid/piano-weekly-task
- Owner: rdvid
- License: mit
- Created: 2024-02-06T00:40:24.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-02-22T23:29:18.000Z (about 2 years ago)
- Last Synced: 2025-01-02T14:29:23.900Z (about 1 year ago)
- Topics: api-rest, cloud, cronjob, docker, email-sender, flask, linux, microservice, music-theory, pdf-generation, python
- Language: Python
- Homepage:
- Size: 4.88 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README




"The piano is a monster that screams when you touch its teeth." - A.Segovia
## đź’ˇ What is it?
A microsservice who generates piano sheets. THe main goal here is to generate 7 random music sheets, one for each week day, composed by random keys inside a range of octaves (C and F major 2 scales) for beginners (like me) have material for practicize musical theory and enhance dynamism through piano notes.
### Technologies used
- Python
- Flask
- Docker
## ✨ Highlights
Some features that i'm proud for implement:
- Implemented music21, an MIT lib for abcnotation
- Lilypond for pdf generate
- Send email and cron jobs using linux Cron and sendinblue
## ⚙️ Next Features
The development process starts but never ends. Next features will be focused on:
- [ ] Load balancer with Nginx.
- [ ] An s3 integration for document storage.
- [ ] Maybe Aws lambda for cloud study purposes.
- [ ] More patterns, exploring themes like chords and even full music prodution for advanced pianists.
## đź“« Find a bug or have any suggestion?
### Pull Requests
1. Fork this repo.
2. Create a branch: `git checkout -b `.
3. Do your alterations and tell then in your commit message: `git commit -m ''`
4. Send then to origin fork: `git push origin / `
5. Create a pull request detailing your implementation.
[How to create a pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request).
### Issues
1. Access the Issues Section:
2. Click the “New issue” button.
3. In the “Title” field, type a descriptive title for your issue.
4. In the comment body field, provide a detailed description of the issue you’re facing or the feature you’d like to request.
5. Apply labels to categorize the issue.
- `Enhancement` for new features
- `Bug` for some issue in usability
6. Click “Submit new issue” to create the issue.
With ❤️ by: