Skip to content

WIP: consolidate our webpack config#752

Merged
bcolloran merged 3 commits intomasterfrom
webpack-config-consolidation
Aug 13, 2018
Merged

WIP: consolidate our webpack config#752
bcolloran merged 3 commits intomasterfrom
webpack-config-consolidation

Conversation

@bcolloran
Copy link
Copy Markdown
Contributor

@bcolloran bcolloran commented Aug 10, 2018

@wlach -- with @mdboom having completed #748, can you jump in to get this over the line?

i think you should be able to build off this PR, which a bunch of changes to consolidate our webpack config and get things working and streamlined since most of our testing will be done using the django server going forward.

things to note:

  • since we're not yet really versioning our resources, i don't think we need to have e.g. iodide.X.js for X = {master, stable, dev, iodide-server} all floating around. so this config just uses the 'dev' label everywhere other than tags (since really all this stuff is "dev" until we decide to get serious about versioning).

  • we'll probably need to move some of the stuff about which origin a given instance is being served from to the .env file (which will need to be configured per origin anyway since we'll need different GH secrets etc). this way, the .env file can pass the correct origin into the python and webpack templates.

i think other changes will be needed, but this should be a start.

working and streamlined for the time when most of our testing will be
done using the django server.
@bcolloran bcolloran requested review from mdboom and wlach August 10, 2018 17:52
@bcolloran bcolloran changed the title consolidate our webpack config WIP: consolidate our webpack config Aug 10, 2018
@bcolloran bcolloran added this to the 0.6.b - server milestone Aug 10, 2018
@bcolloran
Copy link
Copy Markdown
Contributor Author

WIP towards closing #749

Copy link
Copy Markdown
Contributor

@wlach wlach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@wlach wlach force-pushed the webpack-config-consolidation branch from e86cc73 to 4f6b425 Compare August 13, 2018 20:15
@wlach wlach temporarily deployed to iodide-server August 13, 2018 20:15 Inactive
@wlach wlach force-pushed the webpack-config-consolidation branch from 4f6b425 to 23aeff4 Compare August 13, 2018 20:20
@wlach wlach temporarily deployed to iodide-server August 13, 2018 20:20 Inactive
@wlach wlach force-pushed the webpack-config-consolidation branch from 23aeff4 to 78f74bf Compare August 13, 2018 21:35
@wlach wlach temporarily deployed to iodide-server August 13, 2018 21:37 Inactive
@wlach wlach force-pushed the webpack-config-consolidation branch from 78f74bf to cbc72c2 Compare August 13, 2018 21:45
@wlach wlach temporarily deployed to iodide-server August 13, 2018 21:51 Inactive
@wlach
Copy link
Copy Markdown
Contributor

wlach commented Aug 13, 2018

@bcolloran hey, so I think I have this mostly working, except that I'm not sure where I should be getting the assets from extremely-alpha.iodide.io?

https://extremely-alpha.iodide.app/iodide.eval-frame.dev.html

returns a 404

It was working ok when everything was served from the same origin on heroku. :)

@bcolloran
Copy link
Copy Markdown
Contributor Author

hmm ok. i thought @mdboom had gotten this with #748

@bcolloran
Copy link
Copy Markdown
Contributor Author

ah i see, i think we need to merge to master so that the other changes in the webpack config are picked up by mike's build script. so i'm going to go ahead and merge this because now that we're deploying off stable, doing so won't break our public site, yay :-)

@bcolloran bcolloran merged commit 398d8b8 into master Aug 13, 2018
@bcolloran
Copy link
Copy Markdown
Contributor Author

commented at #674 (comment) -- i think we want https for the heroku instance. then i think we'll be good to go.

@bcolloran
Copy link
Copy Markdown
Contributor Author

upgraded to heroku hobby instance, all good now

@bcolloran bcolloran deleted the webpack-config-consolidation branch August 14, 2018 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants