Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Tenant Sites and Workflows #14

Draft
wants to merge 19 commits into
base: main
Choose a base branch
from
Draft

Tenant Sites and Workflows #14

wants to merge 19 commits into from

Conversation

perigrin
Copy link
Member

No description provided.

This adds the ability to clone workflows from one schema to another and
sets up some default workflow to be copied (currently hard-coded)
@perigrin perigrin force-pushed the perigrin/tenant-sites branch from 3618a53 to 289e448 Compare February 14, 2025 05:34
This adds some command line options that will be useful I think in the
long run but that I'm hoping will help us suss out the issues with the
tests.

* template - Template management commands
* tenant   - Tenant management commands
* workflow - Workflow management commands

BREAKING CHANGE:

* App is renamed to `registry`
@perigrin perigrin force-pushed the perigrin/tenant-sites branch from 289e448 to 83c26d3 Compare February 14, 2025 05:39
This commit adds the ability to serialize and de-serialize workflows to
YAML. This is the first step in extracting the workflows from the SQL
import scripts and putting them into a `/workflows` directory so they're
easier to maintain and reason about.
The `html` column on the templates was a misnomer, this commit renames
it to `content` which is more generic
I realized I was doing a lot of DevX work and I didn't actually have a
persona written for that stakeholder PoV. This adds a simple document
for them so that we can ensure that their viewpoint is respected in this
process.
In our effort to make things more introspectable this commit adds
workflow import/export and exports all the current workflows from the
system.
This fixes the last bug with the copied tenant workflows. This means
that multi-tennancy _should be_ functional.
This adds a CONTRIBUTING guide that helps orient new developers to the
underlying principles involved.
I've started a docs/architecture folder to keep track of architectural
design ideas that come up during development. They may or may reflect
the current reality but it's a working space of thoughts and ideas.
Add some more documentation to make it easier for people to understand
what's going on where
CONTRIBUTING.md mentioned some features that aren't yet implemented so I
added some docs explaining that and touching on what they will
eventually be.
What we has as the draft workflow definition was really more accurately
the workflow step definition. To properly build the workflow definiton
we need to get continuations included in the yaml files as a first class
entity and possibly defined in teh database schema as well
This adds the basic metacircular workflow that allows you to create new
workflows. In theory _should be_ the only workflow you need to bootstrap a
working system, but in practice we have a bunch of workflows aready
written before we got here.
We had a broken workflow file for a little bit and it blew things up
pretty hard. This fixes things in case they don't load properly by
throwing an exception and in the correct places catching that exception
and doing something with it.
Adds some developer oriented docs including a project ROADMAP for the
next few steps we're gonna take. It's still very rough.
Improved developer on-boarding. Drop a docker-compose and
update the Dockerfile to actually run the app. Update CONTRIBUTING.md to
include better on-boarding docs.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant