moves the template folder under DBOS so the files are available locally
template expansion treats $package template folder and dbos-config.yaml file special. All other files are copied from template folder to user app folder w/o change
$package folder contents are copied to an import package folder (as per flat layout)
dbos-config.yaml is copied to the user app folder root, but substitues app name variables (app name, app db name, app package name)
Also updated test_package to use dbos init.
user flow:
User creates venv
user installs dbos (pip install dbos)
user initializes dbos (dbos init)
dbos init takes an optional string argument that is used as the app name. If not provided, attempt to read default from pyproject.toml file or parent directory name and query the user
at this point, we can dbos migrate and dbos start to run locally
for cloud deployment, a requirements.txt file needs to be generated. Typically this is done with the pip freeze > requirements.txt command.
at this point, generating requirements.txt is not automated
adds the dbos init CLI command
$packagetemplate folder anddbos-config.yamlfile special. All other files are copied from template folder to user app folder w/o change$packagefolder contents are copied to an import package folder (as per flat layout)dbos-config.yamlis copied to the user app folder root, but substitues app name variables (app name, app db name, app package name)Also updated
test_packageto usedbos init.user flow:
pip install dbos)dbos init)dbos inittakes an optional string argument that is used as the app name. If not provided, attempt to read default from pyproject.toml file or parent directory name and query the userdbos migrateanddbos startto run locallypip freeze > requirements.txtcommand.