-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor deployment, default branches #118
Comments
I need to rope Peter into this one, so we won't get here until |
We could have an NPM package of the versioned compiled CSS … and use unpkg for the urls that people use? |
I've pinged Peter on this earlier in the week, him and Sandeep should hopefully be tackling soonish. |
Do we want the tags so granular in the deploy path? |
I think we need some way for, say, WP to opt in to changes. So it might be running on |
Discussion outcomes Pull request |
Now sorted by #304:
Won't be available until we merge to |
Looks like this is now working with @pwalter-ebi 's most recent edit (#309). Tagged releases will be added as they're made (so no alpha.1/2/3). Leaving open as a documentation task. |
Reflects the new deployment approach for static assets #118 This is also one of those things where "vanilla vf != EMBL"
Now that we're planning regular release we should:
master
develop
todev.assets.emblstatic.net/vf/
master
toassets.emblstatic.net/vf/
master
toassets.emblstatic.net/vf/{tag}
assets.emblstatic.net/vf/v2.0.0-alpha.1
This was already partly discussed in #28
The text was updated successfully, but these errors were encountered: