forked from crunk/distribusi-verse
45 lines
1.3 KiB
Markdown
45 lines
1.3 KiB
Markdown
# these are some notes
|
|
|
|
from distribusi.cli import build_argparser
|
|
from distribusi.distribusi import distribusify
|
|
this way we should be able to run distribusi from code on a folder, or multiple folders.
|
|
|
|
# Shit! We need entire CRUD functionality.
|
|
|
|
## Create:
|
|
There is a listing of the users distribusis. Purp
|
|
There is a yellow button, giving you the new option.
|
|
|
|
### Uploading
|
|
User can select the distribusi and upload/update.
|
|
|
|
User can upload based on $distribusiname field in db.
|
|
the zip file is changed to $distribusiname.
|
|
and a folder is made in the stash called $distribusiname
|
|
|
|
### CSS editing.
|
|
a user can edit CSS of a file in the folder called $distribusiname
|
|
|
|
### Theme selection
|
|
a user can select a CSS file from a dropdown menu.
|
|
|
|
### Distribusi
|
|
A flag in de DB is set to true and distribusi is run on the folder of the users
|
|
called $distribusiname
|
|
|
|
## Read:
|
|
Based on flags set in the user DB the distribusi folders are set to visible.
|
|
on the main index page there is a listing of distribusi sites.
|
|
|
|
## Update:
|
|
Same as create, uploading just redoes the entire process.
|
|
$distribusiname is overwritten.
|
|
|
|
CSS editing, and Theme selection is editing a single file in the folder.
|
|
$distribusiname stays the same
|
|
|
|
Distribusi button can only be reset when a new file is uploaded.
|
|
|
|
## Delete:
|
|
$distribusiname is deleted, files are removed, visible flag is set to false.
|