| Read these guidelines in other languages |
|---|
The processes described here will come to effect in the upcoming version of freeCodeCamp.org. Some parts of the guide are applicable on the beta application.
We continuously deploy our current master, the default development branch on a separate isolated environment.
Typically, the master branch is merged into the production-staging branch once a day and released into an isolated infrastructure. This is known as our "staging / beta" application. It is identical to our live production environment at freeCodeCamp.org, other than it using a separate set of databases. This isolation lets us test ongoing development and features in a "production like" scenario, without affecting regular users of freeCodeCamp.org's platforms. Once the developer teams are satisfied with the changes on the staging application, these changes are moved every few days to the production-current branch. This branch as the name suggests is what you would see live on freeCodeCamp.org.
We welcome you to test these releases in a "public beta testing" mode and get early access to upcoming features to the platforms. Sometimes these features/changes are referred to as next, beta, staging, etc. interchangeably.
Your contributions via feedback and issue reports will help us in making the production platforms at freeCodeCamp.org more resilient, consistent and stable for everyone.
We thank you for reporting bugs that you encounter and help in making freeCodeCamp.org better. You rock!
The domain name will be different than freeCodeCamp.org. Currently this public beta testing version is available at:
Usually the dev team will merge the changes from the master branch to special branch called production-staging (beta/staging site) when they deploy. Usually the top commit should be what you see live on the site.
We use Azure Pipelines and other CI software (Travis, GitHub Actions), to continiously test and deploy our applications.
| Platform | Type | Status |
|---|---|---|
| Travis CI | Unit Tests |  |
| Azure Pipelines | Artifacts |
| Application | Version | Status |
|---|---|---|
| Client | Beta/Next | |
| API | Beta/Next | |
| Client | Production | |
| API | Production |
There will be some known limitations and tradeoffs when using this beta version of freeCodeCamp.
-
All data / personal progress on these beta applications
will NOT be saved or carried overto production.Users on the beta version will have a separate account from the production. The beta version uses a physically separate database from production. This gives us the ability to prevent any accidental loss of data or modifications. The dev team may purge the database on this beta version as needed.
-
Deployment is expected to be frequent and in rapid iterations, sometimes multiple times a day. As a result there will be unexpected downtime at times or broken functionality on the beta version. The dev team will usually notify for updates in the Contributors Chat room.
-
The beta site is and always has been to augment local development and testing, nothing else. It's not a promise of what’s coming, but a glimpse of what is being worked upon.
-
Google, GitHub and Facebook logins will NOT be available in this beta mode. This is simply a technical limitation, because we are using a separate
test domainfor this version. Email logins will work just as fine.The sign page may look different than production (as a measure to isolate the development and the production databases.)
Please open fresh issues for discussions and reporting bugs. You can label them as release: next/beta for triage.
- Checking and getting access to development logs and other resources
- Merging master into production-staging via fast forward
- ...