Skip to content
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

Roadmap #22

Closed
1 of 7 tasks
warrenvw opened this issue May 18, 2017 · 2 comments
Closed
1 of 7 tasks

Roadmap #22

warrenvw opened this issue May 18, 2017 · 2 comments

Comments

@warrenvw
Copy link
Contributor

warrenvw commented May 18, 2017

Please do not modify this entry as it will be overwritten. I am maintaining markup in a separate file. Leave a new comment with any suggestions.

Objective

To provide an official Docker-based solution for StackStorm. It may be used for evaluation, pack development, and light production. Long term, we expect to provide a Docker-based solution that makes it easy to scale and build a highly available system that can be used in production.

Roadmap

We welcome you to submit issues and PR's. We expect the roadmap to change as new requests are submitted. The following short and long term tasks and goals have been identified.

Short term

Besides the known issues, we plan to complete the following within the next couple weeks:

  • Investigate supporting Docker Stack in addition to Docker Compose.
  • Remove VOLUME instruction in current Dockerfile. Update README.md with instructions on how to change docker-compose.yml, or do similar via CLI.
  • Remove Dockerfile#L74 and add /entrypoint.d like this: entrypoint.sh#L60-L67. Update README.md with instructions on how to modify pack_base_path.

Long term

These are features or tasks we expect to work on in the future. As we begin work, they will be moved to the "Short term" section.

@johnarnold
Copy link

IMO, don't get too wrapped up in container orchestration, as there are many competing solutions, and anybody with that level of sophistication can probably integrate it themselves. That's a second order optimization.

Start with getting the Images really ironed out, get the docs really solid and have one good example of how to deploy (e.g. Docker-compose), including best practices on how to pull in packs, configs and SSL certs, how to do upgrades.
Make a list of what is required to move from "eval, light production" to "full production, scale out" for transparency and so others can help out.

@shreyas-shinde
Copy link

any plan for supporting st2chatops 1ppc?

@arm4b arm4b closed this as completed in 6cc70fd Jul 17, 2020
transhapHigsn pushed a commit to DiligenceVault/st2-docker that referenced this issue Jun 8, 2021
You can find the old deprecated version in `DEPRECATED/all-in-one` branch archive: https://github.com/StackStorm/st2-docker/tree/DEPRECATED/all-in-one

Closes StackStorm#22, closes StackStorm#23, closes StackStorm#26, closes StackStorm#29, closes StackStorm#34, closes StackStorm#41, closes StackStorm#43, closes StackStorm#92, closes StackStorm#112, closes StackStorm#117, closes StackStorm#125, closes StackStorm#133, closes StackStorm#141, closes StackStorm#145, closes StackStorm#151, closes StackStorm#163, closes StackStorm#187,
closes StackStorm#188, closes StackStorm#189, closes StackStorm#190
Closes StackStorm#162, closes StackStorm#138, closes StackStorm#108, closes StackStorm#102, closes StackStorm#65
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants