This website requires JavaScript.
Explore
Help
Sign In
darkhelm
/
notifications-admin
Watch
1
Star
0
Fork
0
You've already forked notifications-admin
mirror of
https://github.com/GSA/notifications-admin.git
synced
2026-02-05 02:42:26 -05:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
Files
30a5b771e2d33a9017b02665502a9e40eaa221c8
notifications-admin
/
scripts
/
run_app.sh
4 lines
37 B
Bash
Raw
Normal View
History
Unescape
Escape
Start to create views
2015-11-20 16:22:44 +00:00
#!/bin/bash
Use a Node-based tools for handling assets …or how to move a bunch of things from a bunch of different places into `app/static`. There are three main reasons not to use Flask Assets: - It had some strange behaviour like only - It was based on Ruby SASS, which is slower to get new features than libsass, and meant depending on Ruby, and having the SASS Gem globally installed—so you’re already out of being a ‘pure’ Python app - Martyn and I have experience of doing it this way on Marketplace, and we’ve ironed out the initial rough patches The specific technologies this introduces, all of which are Node-based: - Gulp – like a Makefile written in Javascript - NPM – package management, used for managing Gulp and its related dependencies - Bower – also package management, and the only way I can think to have GOV.UK template as a proper dependency …speaking of which, GOV.UK template is now a dependency. This means it can’t be modified at all (eg to add a global `#content` wrapper), so every page now inherits from a template that has this wrapper. But it also means that we have a clean upgrade path when the template is modified. Everything else (toolkit, elements) I’ve kept as submodules but moved them to a more logical place (`app/assets` not `app/assets/stylesheets`, because they contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
python app.py runserver
Reference in New Issue
Copy Permalink