unknown uodates

vscode-notes/bodach.md

@@ -0,0 +1,4 @@
+# bodach 
+
+## bodach-daemon
+

vscode-notes/cpm.md

@@ -0,0 +1,4 @@
+# Bodach
+
+## bodach-boxes
+

vscode-notes/daily.md

@@ -0,0 +1,22 @@
+When creating a project you must be able to choose from 3 options (2 when from the browser)
+
+1. Create an empty DAW project. 
+There must be an empty project owned by the droplez user which is gonna be used as a template.
+For simplifying creating there must be a database table that will store empty projects object IDs.
+
+Example:
+
+| ID  | DAW           | Object ID |
+| --- | ------------- | --------- |
+| 1   | DAW_LOGIC_PRO | $UUID     |
+| 2   | DAW_ABLETON   | $UUID     |
+
+So, when creating an empty project, `droplez-studio` should go to `empty_projects` table and get object name. Then use this object as a file first for the first version
+
+2. Create a project from template 
+
+Project can be used as a template if it has a `template` flag.
+
+3. Create an empty droplez project. (Not working from the browser)
+
+Just init droplez config file in the specified folder. This should not be triggering a backend.

vscode-notes/droplez v0.1.0.md

@@ -0,0 +1,23 @@
+# droplez v0.1.0
+
+Release MVP
+
+Main client functions: 
+
+- Studio
+  - Projects 
+    - [ ] Project initialization
+      - droplez-frontend
+        - init empty project
+        - init empty DAW project (take the default project from the repo)
+        - init project from template
+      - droplez-desktop
+        - init empty project
+        - init empty DAW project
+        - init project from template
+      - droplez-cli
+        - init project in dir (like git or init with template)
+
+  - ProjectBoard
+  - Release 
+  - Templates

vscode-notes/droplez.md

@@ -0,0 +1,91 @@
+# droplez
+
+## MVP
+
+### droplez-frontend
+- Projects (Studio)
+  - Project initialization, listing, updating, commenting
+<!-- - Stock -->
+  <!-- - Sell beats -->
+  <!-- - Sell arrangements  -->
+  <!-- - Sell sounds  -->
+  <!-- - Sell vst presets -->
+<!-- - Plugins -->
+  <!-- - Donwload plugins  -->
+  <!-- - Save plugins to collection -->
+  <!-- - Attach presets to a plugin -->
+- Personal Page -> Auth service
+  - Post creation/listing/updating
+  - Reactions
+  - Music 
+  - Highligts
+- Player
+  - Timeline comments
+  - Lyrics
+### droplez-desktop
+- Project management (studio)
+- Player
+### droplez-cli
+- Project management (studio)
+
+Tasks: 
+1. 
+
+## Logic
+
+CLI: 
+```
+- Init project in the dir, where project file exists
+$ droplez init . 
+  -n | --name - project name
+  -a | --artist - artist name
+  -c | --collection - collection name
+  -t | --tags - project tags
+  droplez init creates a yaml file witt project params
+
+$ droplez add 
+  -m | --message - add message to new version
+
+$ droplez push 
+  
+```
+
+## Milestones
+---
+
+### **milestone 1**: Project Initialization
+
+#### droplez-studio
+- [x] CRUD operations
+#### droplez-frontend
+- [ ] Studio -> Projects page
+#### droplez-cli 
+- [ ] Basic CRUD client
+#### droplez-k8s
+- [ ] Create deploy for stage environment
+--- 
+
+### **milestone 2:** Files uploading and project versioning
+
+#### droplez-uploader
+- [ ] Init file uploader
+#### droplez-studio
+- [ ] Add information about files
+- [ ] Add versioning logic
+#### droplez-frontend
+- [ ] Add files uploading support 
+- [ ] Add versioning on project pages
+#### droplez-cli
+- [ ] File upload support
+
+---
+
+## Notes
+
+### Project creation vs Project initialization
+
+- When creating a project, the new empty project instance is created (supported in Web, Desktop and Cli)
+- When initializing a project, droplez config is added to already existing project (Desktop, Cli)
+
+On init, we have a project dir, so we can add a yaml file there, but on create we need to unzip template, add config there and zip again. It should be done the fastest way possible. 
+

vscode-notes/online performance platform.md

@@ -0,0 +1,2 @@
+# online performance platform
+

vscode-notes/деньги.md

@@ -0,0 +1,3 @@
+# деньги
+
+пришло