envconfig | Small library to read your configuration | Configuration Management library

I have a complicated task to do. I need to separate my sequelize models in separate folders inside the models folder, just like this structure:

UPDATED

I want to make helper function for testing reading env vars function. It uses envconfig.

Background:

I have a nodejs app using express-session for session management. Recently we had a security checkup for the app and started using secure cookies. Here is the express-session configurations:

I'm trying to upload image with body params. On postman correctly sending:

And on Postman Console:

But on calling request on project, Xcode is freezing and not response.

I've noticed that every go command has stopped working, due to a panic from a main.go in a particular module:

I have a requirement to add a project and translate its description with an external API translation service into several languages (so they exist in the database and it's possible to fetch a project in different languages later). Since translation takes quite some time - I first need to return the API response and then translate description and add additional locale rows to the database.
The db schema looks like this:

DB Context setup:

I'm writing an ASP.NET Core REST API that returns 201s and 202s after kicking off long running asynchronous jobs using Hangfire. If the jobs fail mid way Hangfire will pick things back up, run retries, etc. Obviously in order to do so, it needs to know some state.

Hangfire recommends that the arguments to background jobs remain "small and simple", and that if a background job needs some more complicated object to write the ID to a database.

My background jobs need several API keys, passwords, some not so easy to serialize objects, and some YAML files loaded as config via an internal common configuration library. Because of the sensitivity of these data, I would rather not write them to the database. The options I see here are two:

1. Pass each and every piece of the larger objects as arguments to the Hangfire job and let Hangfire serialize them to its DB. For sensitive arguments like API keys and passwords, first encrypt them using some cert bundled with the app. The background job will have to decrypt them using the same cert after fetching them from the database when it begins running.
2. Set the objects to some public static property in a public static class at startup. The background job can just refer to that when it needs. For example:

I need to dockerize a nodejs application that uses webpack. I have this script below:

I'm using Kelsey Hightower's envconfig package which works like this: