Colin Fay

Yeah the full story is that we've been thinking about this for a while now, but as that's not a trivial change (I mean at the `{golem}` level) I've been...

Ok so I can't stop going back and forth with this 🤔 I feel like having another package just for the deployment might add complexity for both `{golem}` developers and...

Will be working on this soon

Functions needed for deployment seem to be: - `add_resource_path` - `activate_js` - `invoke_js` - `inst/utils/golem-js.js` - `with_golem_options` - `get_golem_options` - `favicon` - the `dev_` suite from `make_dev`

Here is the current state of affair (version 0.3.2): + [ ] attempt (>= 0.3.0) : only has {rlang} as dep + [ ] cli (>= 2.0.0) : only has...

@berkorbay I'm not fully familiar with AWS, I successfully deploy to Amazon Elastic Container Service once, could you pitch me on how Beanstalk differs from ECS ?

I wonder if this should be dealt with in {dockerfiler} directly, or here?

@teofiln thanks for taking some time to suggest this! My issue with your solution is that it will only work with golem_wd, but theoretically speaking you could have any entry...

Woaw thanks @teofiln that's awesome. Would you be willing to make a PR? Thanks a lot, Colin

Full reprex : ``` MacBook-Air-de-colin:~ colin$ cd /tmp/ MacBook-Air-de-colin:tmp colin$ Rscript -e "golem::create_golem('plop')" ── Checking package name ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ✔ Valid package name ── Creating dir ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ✔ Creating 'plop/' ✔...