This is the codebase that runs the Devographics surveys, such as State of JS and State of CSS.
This monorepo uses pnpm, and you should start by installing it.
You can clone all repositories in the right place and create blank .env files with the following install script:
curl -o- https://raw.githubusercontent.com/Devographics/Monorepo/main/install.sh | bash
git clone https://github.com/Devographics/Monorepo.gitThe survey apps rely on a lot of metadata. If you need to load or modify this metadata from your local filesystem instead of through our API, you can optionally also clone these other repos:
I suggest using the following file structure:
devographics parent directorydevographics/monorepodevographics/monorepo/surveyformdevographics/monorepo/resultsdevographics/monorepo/...devographics/entitiesdevographics/surveysdevographics/localesdevographics/locales/locale-en-USdevographics/locales/locale-fr-FRdevographics/locales/...Whenever you need to run a project in the monorepo directory (such as results, surveyform, etc.), you will need to first run pnpm install from within its subdirectory.
cd monorepopnpm installThis will install dependencies for all applications of the monorepository.
You can run each project with pnpm run dev when inside its subdirectory.
For example, for the surveyform app:
cd monorepocd surveyformpnpm run devIf this is your first time running a project, you will run into some issues that need to be fixed by configuring your local environment variables (see below).
You can run the results and surveyform project by connecting to our remote production API (https://api.devographics.com/graphql).
Alternatively, if you want to use local files for the surveys, locales, etc. you will need to run a local copy of the API project (monorepo/api) locally as well to load them. Once the API is running, you can then point the other apps to it via the API_URL env variable.
Note that even when the API is running locally, you will still need internet access to connect to the databases and load image assets.
Each app within monorepo needs its own environment variables defined inside a .env files (except for surveyform and surveyadmin, which use a .env.development.local file).
Here are some ways that can help with this setup:
.env.example file in each project subdirectory (such as this one for the surveyform project) as a starting point by pasting its contents into your own .env or .env.development.local (for Next.js projects such as surveyform) file.pnpm run dev you will get error messages indicating any remaining missing environment variables.You can also refer to variables.yml directly and look for variables corresponding to the current app (e.g. results).
The following apps are all contained within the monorepo.
Node.js TypeScript app.
GraphQL IDE
Next.js TypeScript app.
Gatsby TypeScript app.
Admin app.
MongoDB database.
You can plug to a staging database or run Mongo locally via Docker.
See "docker-compose.yml" and "Justfile" for our local setup. When running locally, data are stored in a ".mongo" folder in the monorepo folder. You can delete this folder to reset the local database.
Redis database.
You can plug to a staging database or run Redis locally.
Since we use Upstash, which rely on HTTP requests instead of direct Redis connection, we also setup an HTTP proxy.
See "docker-compose.yml" and "Justfile" for our local setup.
To reset the local Redis instance, the best approach is to remove the Redis container.
Locale strings
Outline and config files for each survey.
Static image files.
Emojis to distinguish commits within the monorepo:
:parking: for the whole monorepo ("P" for "Pnpm"):gear: for the shared folder:mag: for graphiql:satellite:for the api:bar_chart:for the results:house:for the homepage:writing_hand: for the surveyform:lock: for the surveyadmin:globe_with_meridians: for the locales:book: for the surveys:person_pouting: for the entities:frame_photo: for the imagesSee "shared/helpers/variables.yml" for a more up to date list.
| Variable | Description | Used By |
|---|---|---|
API_URL |
URL of the API | All |
| Variable | Description | Used By |
|---|---|---|
MONGO_URI |
URI of the Mongo database | All |
MONGO_PRIVATE_DB |
Name of the database where private data is stored | Surveyform |
MONGO_PUBLIC_DB |
Name of the database where public data is stored | API |
| Variable | Description | Used By |
|---|---|---|
REDIS_URL |
URL of the Redis database | Surveyform |
REDIS_TOKEN |
Redis token (needed for Upstash) | Surveyform |
| Variable | Description | Used By |
|---|---|---|
GITHUB_TOKEN |
GitHub access token | Results |
GITHUB_PATH_SURVEYS |
Path to surveys dir on GitHub (e.g. org/repo/(subdir)) |
Results |
GITHUB_PATH_LOCALES |
Path to locales dir on GitHub (e.g. org/(repo)/(subdir)) |
Results, API |
GITHUB_PATH_SURVEYS, the subdir segment can be omitted. It will then be assumed that the surveys data is at the root of the repo.GITHUB_PATH_LOCALES, both the repo and the subdir segments can be omitted. It will then be assumed that the locales each have their own separate repo.| Variable | Description | Used By |
|---|---|---|
EMAIL_OCTOPUS_APIKEY |
EmailOctopus API key | Surveyform |
DEFAULT_MAIL_FROM |
Default "from" email (e.g. info@mail.stateofjs.com) |
Surveyform |
SMTP_HOST |
SMTP host (e.g. email-smtp.us-east-1.amazonaws.com) |
Surveyform |
SMTP_PORT |
SMTP port (e.g. 465) |
Surveyform |
SMTP_SECURE |
Set to "1" | Surveyform |
SMTP_USER |
SMTP username | Surveyform |
SMTP_PASS |
SMTP password | Surveyform |
EMAIL_OCTOPUS_APIKEY
| Variable | Description | Used By |
|---|---|---|
ENCRYPTION_KEY |
Encryption key to hash emails | Surveyform |
SECRET_KEY |
Secret key used to verify external webhook requests | API |
ASSETS_URL |
URL for static assets (e.g. https://assets.devographics.com/) |
All |
| Variable | Description | Used By |
|---|---|---|
SURVEYS_DIR |
Local directory from which to load survey outlines | API |
LOCALES_DIR |
Local directory from which to load locale files | API |
ENTITIES_DIR |
Local directory from which to load entities files | API |
ENABLE_CACHE |
Set to false to always load data from the API |
All |
PORT |
Which port to run the app on | All |
LOGS_DIRECTORY |
Absolute path to logs dir (e.g. /Users/sacha/monorepo/surveyform/.logs) |
All |
SURVEYS_DIR is defined, surveys data will be loaded locally instead of from GitHub.LOCALES_DIR is defined, locales data will be loaded locally instead of from GitHub.ENTITIES_DIR is defined, entities data will be loaded locally instead of from GitHub.A glossary of terms used internally throughout the code and apps.
A single answer to a survey question. Note that some questions accept multiple answers.
The Node.js app that serves the GraphQL API which in turn gives all other apps (as well as any external client) access to the data.
A special auto-generated API field that returns how many respondents use 1 item in the current section, 2 items, 3 items, etc.
In the context of processing (or “coding”) freeform data, is synonymous with Token.
A dataset containing both freeform and fixed responses.
Optional comments left by respondents in relation with a specific question.
A config.yml file used to configure a given survey or survey edition.
For freeform questions that do not have a pre-established list of options, a list of options can be generated based on the dataset dynamically. This is useful for filtering.
A specific edition (i.e. year) of a survey.
The repo containing all entities definitions.
Any item, person, concept, etc. that can potentially be referenced in the surveys. Defined in the entities repo.
When used in opposition to Token, indicates a “real” item such as a feature, library, person, tc. with a homepage, social media links, or other associated m
$ claude mcp add Monorepo \
-- python -m otcore.mcp_server <graph>