Delivery Circle - 12 February 2025

Product Development Process
1

Save and restore backups on staging servers

Want to save and restore at least one “baseline” database backup.

Regarding current ofn:sample_data: names “Freddy” and “Fred” can be confusing.
How to store the enterprises setup. (For example a detailed example set up with tax settings)
Also how to share these setups? We can use the sample_data script.
How can testers feed back into the sample data set?

Some solutions suggested:

  1. set up a more detailed sample data set, so that everyone can benefit (all saging servers, all developers, etc)

    • Maybe Filipe can edit this as needed.

  2. when deploying to staging, add additional options:

    • save to baseline
    • restore from baseline
    • execute sample_data on existing database
    • clear database and execute sample_data

@chahmedejaz

Producer edit products on hub’s orders. Facing lots of test failures.
Will work on that then move on the next

@maikel

Working on DFC orders. Was blocked by broken context from Shopify, but his has been fixed now.
Rachel: Garethe is co-ordinating that to ensure the missing backorders have been placed. Thanks Maikel for raising the alarm before the end of the order cycle!

Rachel: how can we share more broadly about this project?
Maikel: how can a new shopify shop join to use the integration? R: Currently it’s not open for more users (But that is probably the ultimate goal).

Pilot has been so successful that users don’t want it to be shut down! So it’s in production, but it’s still quite hacky…

Rachel to ask Garethe if he can join to share more details with us next time.

@dcook

Will continue working on DFC orders until more flower farms work is ready.

@Gaetan

Current tag implementation is in AngularJS. It will take some time to re-implement tags in Stimulus.
Also have been looking at S2 bugs.

@filipefurtado

Thanks Ahmed for great communication!

@Rachel

Working on Tags on Variants
We need to communicate more on Slack with Finance Circle.
Main message from FC to instance managers is to estimate money for the year.

Coming up, non-Aus staff may need to use different Clockify workspace.

2

FYI @filipefurtado , the sample data script is here: openfoodnetwork/lib/tasks/sample_data.rake at master · openfoodfoundation/openfoodnetwork · GitHub
With comment:

The sample data generated by this task is supposed to save some time during
manual testing. It is not meant to be complete, but we try to improve it
over time. How much is hardcoded here is a trade off between developer time
and tester time. We also can’t include secrets like payment gateway
configurations in the code since it’s public. We have been discussing this for
a while:

It includes all the files under this directory: openfoodnetwork/lib/tasks/sample_data at master · openfoodfoundation/openfoodnetwork · GitHub

It’s not exactly easy to read, but we can see that enterprises for example will only get created if no enterprise exists with the same name: find_or_create_by!(name:).
This means if the enterprise already exists, it won’t get updated. (But I think we can consider changing the script to overwrite if necessary.)

1 Like
3

Thank you for pointing that out @dcook :+1:
I’ll have a closer look, and discuss this again in the testing circle.