Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • ind ind
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • totemtotem
  • indind
  • Issues
  • #54
Closed
Open
Issue created Mar 31, 2019 by Maarten de Waard@maarten👼Maintainer

Check the public files into the code repo

We currently require you to run paver collect_static on the machine where you run edX. If you don't do this you dont have the CSS, JS and SVG/indie files in the correct places.

This makes it harder to automatically update IND to the newest version, and running paver on your production server is generally bad practice. Especially because it requires(? not sure) docker to run, which you don't want to install on the production server that doesn't need it.

A solution is to check the public files into the repo. this means that you can deploy IND just by pulling the newest source code (however, you still have to run update-assets-[cl]ms).

Assignee
Assign to
Time tracking