{"id":13533425,"url":"https://github.com/torchbox/wagtail-torchbox","last_synced_at":"2025-12-18T10:05:21.896Z","repository":{"id":39351798,"uuid":"16944327","full_name":"torchbox/wagtail-torchbox","owner":"torchbox","description":"Wagtail build of Torchbox.com","archived":true,"fork":false,"pushed_at":"2024-04-24T08:14:45.000Z","size":114153,"stargazers_count":124,"open_issues_count":3,"forks_count":46,"subscribers_count":31,"default_branch":"main","last_synced_at":"2024-11-02T20:33:09.595Z","etag":null,"topics":["django","python","torchbox","wagtail","website"],"latest_commit_sha":null,"homepage":"https://torchbox.com","language":"Python","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/torchbox.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2014-02-18T09:56:47.000Z","updated_at":"2024-05-29T08:44:15.000Z","dependencies_parsed_at":"2023-02-19T10:15:53.455Z","dependency_job_id":"3f954cce-6bcc-4a28-a51a-4ecb5d24c767","html_url":"https://github.com/torchbox/wagtail-torchbox","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/torchbox%2Fwagtail-torchbox","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/torchbox%2Fwagtail-torchbox/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/torchbox%2Fwagtail-torchbox/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/torchbox%2Fwagtail-torchbox/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/torchbox","download_url":"https://codeload.github.com/torchbox/wagtail-torchbox/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":246713373,"owners_count":20821877,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["django","python","torchbox","wagtail","website"],"created_at":"2024-08-01T07:01:19.719Z","updated_at":"2025-12-18T10:05:16.192Z","avatar_url":"https://github.com/torchbox.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Torchbox.com on Wagtail - RETIRED\n\n\u003e [!WARNING]  \n\u003e This version of the torchbox.com repo is now retired. You probably want https://github.com/torchbox/torchbox.com.\n\nThe old REAME content is preserved below for reference.\n\n\u003cpre\u003e\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n\u003c/pre\u003e\n\n# Historical documentation\n\n[![CI](https://github.com/torchbox/wagtail-torchbox/actions/workflows/test.yml/badge.svg)](https://github.com/torchbox/wagtail-torchbox/actions/workflows/test.yml)\n\nThis is the main Torchbox.com website. The careers section of this site can be found at [torchbox/careers](https://github.com/torchbox/careers).\n\n## Technical documentation\n\nThis project contains technical documentation written in Markdown in the `/docs` folder. This covers, among others:\n\n- continuous integration\n- deployment\n- git branching\n- project conventions\n\nYou can view it using `mkdocs` by running:\n\n```bash\nmkdocs serve\n```\n\nThe documentation will be available at: \u003chttp://localhost:8001/\u003e\n\n## Setting up a local build\n\nThis repository includes `docker-compose` configuration for running the project in local Docker containers,\nand a fabfile for provisioning and managing this.\n\nThere are a number of other commands to help with development using the fabric script. To see them all, run:\n\n```bash\nfab -l\n```\n\n## Dependencies\n\nThe following are required to run the local environment. The minimum versions specified are confirmed to be working:\nif you have older versions already installed they _may_ work, but are not guaranteed to do so.\n\n- [Docker](https://www.docker.com/), version 19.0.0 or up\n  - [Docker Desktop for Mac](https://hub.docker.com/editions/community/docker-ce-desktop-mac) installer\n  - [Docker Engine for Linux](https://hub.docker.com/search?q=\u0026type=edition\u0026offering=community\u0026sort=updated_at\u0026order=desc\u0026operating_system=linux) installers\n- [Docker Compose](https://docs.docker.com/compose/), version 1.24.0 or up\n  - [Install instructions](https://docs.docker.com/compose/install/) (Linux-only: Compose is already installed for Mac users as part of Docker Desktop.)\n- [Fabric](https://www.fabfile.org/), version 2.4.0 or up\n  - [Install instructions](https://www.fabfile.org/installing.html)\n- Python, version 3.6.9 or up\n\nNote that on Mac OS, if you have an older version of fabric installed, you may need to uninstall the old one and then install the new version with pip3:\n\n```bash\npip uninstall fabric\npip3 install fabric\n```\n\nYou can manage different python versions by setting up `pyenv`: https://realpython.com/intro-to-pyenv/\n\nAdditionally, for interacting with production / staging environments, you'll need:\n\n- [Heroku CLI](https://devcenter.heroku.com/articles/heroku-cli)\n- [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html)\n\n## Running the local build for the first time\n\nIf you are using Docker Desktop, ensure the Resources:File Sharing settings allow the cloned directory to be mounted in the web container (avoiding `mounting` OCI runtime failures at the end of the build step).\n\nStarting a local build can be done by running:\n\n```bash\ngit clone git@github.com:torchbox/wagtail-torchbox.git\ncd wagtail-torchbox\nfab build\nfab migrate\nfab start\n```\n\nThis will start the containers in the background, but not Django. To do this, connect to the web container with `fab sh` and run `honcho start` to start both Django and the Webpack dev server in the foreground.\n\nThen, connect to the running container again (`fab sh`) and:\n\n```bash\ndj createcachetable\ndj createsuperuser\n```\n\nThe site should be available on the host machine at: http://127.0.0.1:8000/\n\nIf you only wish to run the frontend or backend tooling, the commands `honcho` runs are in `docker/Procfile`.\n\nUpon first starting the container, the static files may not exist, or may be out of date. To resolve this, simply run `npm run build`.\n\n### Frontend tooling\n\nHere are the common commands:\n\n```bash\n# Install front-end dependencies.\nnpm install\n# Start the Webpack build in watch mode, without live-reload.\nnpm run start\n# Start the Webpack server build on port 3000 only with live-reload.\nnpm run build\n# Do a one-off Webpack production build.\nnpm run build:prod\n```\n\nThere are two ways to run the frontend tooling:\n\n- In Docker. This is the default, most portable and secure, but much slower on macOS.\n- Or run npm commands from a terminal on your local machine. Create a `.env` file in the project root (see `.env.example`) with `FRONTEND=local`. `fab start` will no longer start a `frontend` container. Now, when running `fab start`, Docker won't attempt to bind to the ports needed for the frontend dev server, meaning they can be run locally. All the tooling still remains available in the container.\n\n## Installing python packages\n\nPython packages can be installed using `poetry` in the web container:\n\n```\nfab sh\npoetry add wagtail-guide\n```\n\nTo reset installed dependencies back to how they are in the `poetry.lock` file:\n\n```\nfab sh\npoetry install --no-root\n```\n\n## Deployments\n\nTo deploy, merge your feature branch to `master` or `staging` branch. Once CI pipelines have passed, it will be deployed to the respective Heroku site automatically.\n\nThis is done via [Heroku Github integration](https://devcenter.heroku.com/articles/github-integration).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftorchbox%2Fwagtail-torchbox","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftorchbox%2Fwagtail-torchbox","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftorchbox%2Fwagtail-torchbox/lists"}