[FOLIO-1105] Run local code (module) and allow debugging it against a local VM (folio env) Created: 06/Mar/18 Updated: 10/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | shale99 | Assignee: | Wayne Schneider |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ci, sprint33, sprint48 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
1. run ansible with a selected set of modules - for example - if you are developing mod-circ , you may have 7-8 modules that should be running in the vm preferable: comments welcomed.... |
| Comments |
| Comment by shale99 [ 07/Mar/18 ] |
|
once the module being tested is deployed it should also be activated for a predefined tenant |
| Comment by shale99 [ 07/Mar/18 ] |
|
with the ability to easily post the needed permissions <- major pain point in a local environment built from scratch (users + perms for an env) |
| Comment by Heikki Levanto [ 07/Mar/18 ] |
|
Personally, I have never liked the black box approach. I understand it is necessary for the front end developers to get a well known back end installation to work against, but for a back end developer like myself, it has always seemed like a clumsy way to get things up. I always try to develop directly on my workstation. I admit that it can be a hassle to set up. I would like to see it working this way:
We have (almost?) all machinery in place already. Okapi can pull MDs, resolve dependencies, and enable or upgrade a bunch of modules, thanks to Adam's install call. The missing piece is the test data modules. There is no technical reason why we could not have such, nobody has written one yet. Instead, most modules come with various different scripts to load their test data in, and to set things up. The test data modules could also install permissions for well-known users, and initialize anything else we may need in the system |
| Comment by shale99 [ 07/Mar/18 ] |
|
that is ok with me, it doesnt have to be in the vm as long as everything can be installed and deployed properly automatically and allows deploy / redeploy easily |
| Comment by Heikki Levanto [ 07/Mar/18 ] |
|
I wrote a bit more about my idea in
|
| Comment by Wayne Schneider [ 04/Oct/18 ] |
|
Something worth considering: https://www.virtualbox.org/manual/ch06.html#network_internal Could we simply set up the VM using internal networking and address the local module from within Okapi? |