Platform for Mozilla Support
Перейти к файлу
Paul McLanahan 7a9ef98903
Use custom host for git push of l10n files
2019-01-03 20:52:51 -05:00
.circleci Move to a single Dockerfile and docker-compose file 2018-11-12 11:22:56 -05:00
authority [Bug 1238055][Bug 1225606] Upgrade Django to 1.8. 2016-02-25 15:08:13 -08:00
bin Move to a single Dockerfile and docker-compose file 2018-11-12 11:22:56 -05:00
configs Remove Vagrant. 2017-11-20 12:50:28 +02:00
docker/bin Fix build issues 2019-01-03 19:38:38 -05:00
docs Lint and push l10n files during docker build (#3435) 2019-01-02 11:11:00 -06:00
jsi18n Collect jsi18n files via staticfiles to get hashed filenames. 2016-02-23 18:17:29 -08:00
k8s Scale up frankfurt failover deployment (#3422) 2018-11-19 14:48:55 -06:00
kitsune [fix bug 1514901] Non-fx downloads go to /new page 2018-12-18 13:34:41 -05:00
media Update base template code/styles based on new mockups for support.mozilla.org re-design. (#3243) 2018-09-18 16:35:34 -05:00
requirements Update test dependencies. 2018-11-06 12:36:32 -05:00
scripts Use custom host for git push of l10n files 2019-01-03 20:52:51 -05:00
tests Move WebQA Jenkinsfile under tests dir. 2017-11-23 09:22:37 +02:00
wsgi Migrate from raven to sentry-sdk 2018-11-05 11:08:18 -05:00
.dockerignore Split dockerfiles. 2017-11-30 15:39:49 +02:00
.editorconfig Move to a single Dockerfile and docker-compose file 2018-11-12 11:22:56 -05:00
.env-build Update env variables 2018-03-01 09:02:15 -06:00
.env-dist Preserved legacy trackEvent function, added analytics.js back to bundle 2018-03-21 10:24:40 +02:00
.env-test Move to a single Dockerfile and docker-compose file 2018-11-12 11:22:56 -05:00
.eslintrc Fix eslint problems. 2015-12-15 15:23:27 -08:00
.gitignore Lint and push l10n files during docker build (#3435) 2019-01-02 11:11:00 -06:00
.pre-commit-config.yaml Upgrade to pip8 2017-11-20 12:50:09 +02:00
.travis.yml Switch docker repo to mozmeao/kitsune. 2017-11-23 09:58:28 +02:00
CONTRIBUTORS.rst Replace manually curated list of contributors with link to generated versions. 2015-05-21 14:07:01 -07:00
Dockerfile Lint and push l10n files during docker build (#3435) 2019-01-02 11:11:00 -06:00
Jenkinsfile Lint and push l10n files during docker build (#3435) 2019-01-02 11:11:00 -06:00
LICENSE Fix a thing Ricky found that I missed when I fixed the other issue 2013-04-05 16:06:06 -04:00
Makefile Fix issue with docker-compose pull in Makefile 2019-01-03 20:13:39 -05:00
Procfile Add celery worker and cron commands. 2018-02-05 12:20:57 +02:00
README.md Move to a single Dockerfile and docker-compose file 2018-11-12 11:22:56 -05:00
bower.json Fix issues associated with broken bower config 2018-10-23 14:43:13 -04:00
contribute.json Update and serve contribute.json (#2905) 2017-08-03 10:02:01 +03:00
docker-compose.yml Fix build issues 2019-01-03 19:38:38 -05:00
gulpfile.js Fix a lot of lint errors. 2015-07-28 17:02:18 -07:00
jenkins.yml Move to a single Dockerfile and docker-compose file 2018-11-12 11:22:56 -05:00
manage.py Update docker. 2017-11-20 12:54:12 +02:00
newrelic.ini Add newrelic configuration file. (#3051) 2018-02-08 05:58:24 -06:00
package.json update bower to latest version for fixing bug 1500894 2018-10-23 14:42:23 -04:00
setup.cfg Run tests on travis. 2017-11-20 13:07:07 +02:00
tox.ini Add Jenkinsfile pipeline 2016-11-15 10:51:50 +00:00
yarn.lock Upgrade node version on dev image to match that on prod 2018-10-23 15:37:47 -04:00

README.md

Kitsune

Kitsune is the platform that powers SuMo (support.mozilla.org)

It is a Django application. There is documentation online.

You can access the staging site at https://support.allizom.org/

See what's deployed

Development

To get Kitsune running locally all you really need is to have Docker installed, and follow the following steps.

  1. Fork this repository & clone it to your local machine.

    git clone https://github.com/mozilla/kitsune.git
    
  2. Pull base Kitsune Docker images, create your database, and install node and bower packages.

    make init
    
  3. Run Kitsune.

    make run
    

    This will produce a lot of output (mostly warnings at present). When you see the following the server will be ready:

    web_1              | Starting development server at http://0.0.0.0:8000/
    web_1              | Quit the server with CONTROL-C.
    

The running instance will be located at http://localhost:8000/ unless you specified otherwise, and the administrative control panel will be at http://localhost:8000/admin/.

Another way you might choose to run the app (step 3 above) is by getting a shell in the container and then manually running the Django dev server from there. This should make frequent restarts of the server a lot faster and easier if you need to do that:

make runshell
bin/run-dev.sh

The end result of this method should be the same as using make run, but will potentially aid in debugging and act much more like developing without Docker as you may be used to. You should use make runshell here instead of make shell as the latter does not bind port 8000 which you need to be able to load the site.

Run make help to see other helpful commands.

The Admin

After the above you can do some optional steps if you want to use the admin:

  • Enable the admin control panel

    echo "ENABLE_ADMIN=True" >> .env
    
  • Create a superuser

    docker-compose exec web ./manage.py createsuperuser
    
  • Create some data

    docker-compose exec web ./manage.py generatedata
    
  • Update product details

    docker-compose exec web ./manage.py update_product_details
    

Get Search Working

First, make sure you have run the "Create some data" step above.

  1. Enter the web container: docker-compose exec web bash
  2. Build the indicies: ./manage.py esreindex (You may need to pass the --delete flag)
  3. Precompile the nunjucks templates: ./manage.py nunjucks_precompile