You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer I want a quick way to set up and use a local development environment to be able to develop with ease and confidence and improve the onboarding experience.
There should be a very simple "standard" way to set up a development environment that should always work and and shouldn't be allowed to break. If any proposed changes would break it, it must be fixed in the same branch, before it is merged.
Acceptance Criteria
There should exist a convenient way (e.g. script) to set up a local containerised dev environment for AIMAAS, ideally with a single command.
It's fine if other dependencies, such as Postgres, Memcached, RabbitMQ etc. are not containerised, but live on the host.
It would be nice, though, if we had the freedom to put them into containers, if we like. But this is less important.
We should use the same base container images for this as for our CI/CD pipelines.
The project code should be shared between the host and the container, so local work on the host is possible and changes are reflected in the container.
Ideally, it should be possible to also do this with the sources of dependent projects, so features or fixes that require code changes across projects can be worked one as one.
Any web service started in the container should be reachable from the host, so the local browser (and CLI tools like curl) can be used for debugging and testing.
The text was updated successfully, but these errors were encountered:
I would suggest using LXD. You can do the following in a few steps that can all be put in 1 bash script:
Spin up the container with lxd launch
Copy over a configuration file (ansible, salt) with lxd copy
Install the config system with zypper and run the config file to set up everything else.
in 1-2 minutes (depending on system speed), you should have a completely ready dev environment.
User Story
As a developer I want a quick way to set up and use a local development environment to be able to develop with ease and confidence and improve the onboarding experience.
There should be a very simple "standard" way to set up a development environment that should always work and and shouldn't be allowed to break. If any proposed changes would break it, it must be fixed in the same branch, before it is merged.
Acceptance Criteria
curl
) can be used for debugging and testing.The text was updated successfully, but these errors were encountered: