Skip to content

Create convenient way to set up "standard" containerised dev environment for local development  #210

@der-gabe

Description

@der-gabe

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

  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions