Persistent storage solution

[Sarahtonein]

Whats new

• One time Migration script from JSON => Database
• Database implementation
• Tests for various discord / database operations
• Updated to work with either a procfile (Heroku) or docker-compose
• Updated .env.example
• new github workflow when pull reqs are made to main / dev
• Updated operations to work with database tables instead of JSON file.

How to test

• To test migrations or database operations you can run:

python -m pytest tests/ -v

• You can also use the test server to run the migration / setup the DB and test out the various functionality if you desire

Following tests in a staging env have been run

• new event postings
• upcoming event postings
• DMing a contributor
• Listing / Adding / Updating / Removing contributors
• Creating / voting / concluding proposals
• Posting proposals to snapshot

Additional
I would like to merge this in after the scrape-props, and quorum-calc PRs have been merged. As this branch is based off of those.

[bagelface]

this seems like it got out of sync with dev

[Sarahtonein]

this seems like it got out of sync with dev

Merge conflicts resolved

[bagelface]

don't see how this will work with the current "notified_events.json" and "posted_events.json" json files?

[Sarahtonein]

We load the JSON and take the separate data and combine it into a dictionary which is then saved to the DB using the defined models

This can be replicated with

def test_migrate_events(test_db):
    """Test migrating events from events.json"""
    data_path = os.path.join(os.path.dirname(os.path.dirname(__file__)), "data")
    events_data = load_json_file(os.path.join(data_path, "events.json"))

    if not events_data:
        logger.info("No events data found in events.json")
        assert True
        return

    db_service = DatabaseService(session=test_db)
    result = db_service.migrate_events(events_data)
    assert result >= 0

    events = test_db.query(Event).all()
    assert len(events) >= 0

For example

[bagelface]

a few changes I think to be made, but overall i think this is a much better/simpler approach

[bagelface]

Docs need a little clean up. There is inconsistent stylizing throughout and probably is a bit wordier than it needs to be. If you agree, can you make a separate issue for that.

[Sarahtonein]

Docs need a little clean up. There is inconsistent stylizing throughout and probably is a bit wordier than it needs to be. If you agree, can you make a separate issue for that.

Agree it can be reduced in size. Will create an issue for this.

[bagelface]

briefly looked over again and this lgtm. lots of code changes so i didn't scrutinize everything they way i'd like to. i just want to get this merged in