Have you ever struggled to layout the strategy for testing your React App? Well, you are not alone! Here a few hints from the lessons I learned during my experience testing a React/Redux app with a Phoenix/Elixir backend.
10 articles tagué avec "how-to"Voir tous les tags
Moving from Webpack to esbuild on Phoenix
We're very happy users of Elixir and Phoenix at OpenFn, given that we've been
using it continuously for about 6 years - upgrades and all. Our front-end
toolchain, albeit far from out of date (Webpack
5.52.1 today) has left some
room for improvement.
Improving Multistage Docker Builds using Buildx
So you're using docker's multi-stage builds and noticed that your build times aren't nearly as quick as you expected?
Wrapping my head around jobs
Jobs are business processes turned into functional-style scripts. What does that mean, how should you approach writing jobs?
Forms and Cases: CommCare and event-based integration
This is a quick one, but I just got off an exciting call with an organization that's going to set up some jobs to move data into Salesforce from CommCare and realized that despite this being one of our more common integration requirements, we haven't done a 'tips' article for this type of project. Until now.
Sync Like You Mean It: Thinking Through System “Syncing” Protocols
“Syncing” is getting two systems to a state of harmony. This might mean keeping a list of patients up to date, though modifications can be made in either system. It might mean copying transactions from one system to another on a nightly basis. It might mean a lot of things, but the key concept is that when you sync systems, you’re asking them to work together while simultaneously respecting both software systems’ independence.
In this post we’ll discuss two different syncing protocols to consider when designing your data integration. These include:
- Real-time, or event-based, syncs
- Scheduled syncs
Our Servers or Yours: Thinking through deployment options
Zandile is a program manager at an iNGO and she needs to use CommCare, DHIS2, and OpenFn for an upcoming public health project. She understands that all three pieces of software can be deployed locally, or accessed as SaaS (Software as a Service).
Essentially, Zandile needs to decide if she would like to run the software on someone else’s servers (SaaS), or on her organization’s own servers (deployed locally). Before making a decision she outlines the basic, non-technical considerations for both options.
Tracked entity instances in DHIS2
tl;dr: Lots of our users want to upsert tracked entity instances in dhis2, but
upserts aren’t supported by a standard DHIS2 API endpoint. We built one in our
dhis2 adaptor: it’s composed of existing APIs and a bit of logic 🤔. Now you can
upsert tracked entity instances to DHIS2 👍 ✅.
Allow Yourself to Fail
How Information Is Organized... In Organizations
Does your organization's information have an underlying structure? Try this exercise using boxes and crow's feet.
This article was originally posted by Taylor Downs, Head of Product, on The OpenFn Founder's blog as "The power of crow's feet."
It’s Saturday Morning in Cape Town and I’ve just spent an hour talking about how a non-profit is organized. I thought I was getting into a technical discussion—I’ve been doing system architecture discussions for years—but what we ended up talking about was how this NGO thinks.