Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Heyo Gitcoiners! With an entire city of hackers, coders and blockchain innovators relocated on our platform, the atmosphere is just buzzing with crea…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
*Long description, but most of the work is already done*
Implement this. Quite a headstart has been made in the `hot-reloading` branch but it doesn't quite work yet. Set up a dev/watch/prod build pipeline for the application.
* [x] dev/watch/prod
* [x] dev: show debug messages for all pages in Django, compile with webpack in development `-d` mode, but it can be compiled just once.
* [x] watch: also show debug messages, but compile with webpack continuously and automatically on each update in the code base. The hot reloading is an in-memory and not an on-disk swap.
* [x] prod: everything optimised. This should work properly and pass the TravisCI
* [x] There are three parts to this: the settings files, the webpack files, and the view+html files
* [x] Both dev and watch can use local.py, unless you feel it's better to make two copies. The WEBPACK_LOADER section can be changed as you see fit. My suggestion is to have the two compiled files written to app/assets/webpack_bundles.
* [x] The webpack files may need to be work, although most of it is there. They need to inherit as much as possible from the base config file, might need some cleaning up. If file paths need to be changed to have the bundles written to app/assets/webpack_bundles, please go ahead.
* [ ] The porcupine html file needs to stay clean, but clearly it must load the webpack bundle in all different modes. To keep things clean, if could for example follow: https://cscheng.info/2016/08/03/integrating-webpack-dev-server-with-django.html
The user can currently switch from environments by changing the NODE_ENV variable in the `.env`. In the `env.sample`, this is set to 'watch'. Possible values are 'watch', 'development', and 'production'.
This issue is reserved for @arun1595 for 24 hours, because of prior communication about this issue.