-
Notifications
You must be signed in to change notification settings - Fork 45
Docker container #339
Comments
It's absolutely useful for encouraging people use and contribute to the codebase and community. We've had feedback from the Web-A11y Slack community that the local setup time has discouraged someone from booting it up. |
That was the intention.
Sorry, I don't have access to that thread. Do you mean the local setup time for the installation procedure or the docker's build time (which initially is a bit higher)? |
Oh I meant the local setup time |
Hey @WBTMagnum , did you encounter an issue during installation, use or development of this tool? Did you miss information? Could you raise this in a new issue? If you encounter anyone else that has issues with the installation of this tool for local development (or any other issues), please refer them to the report tool issues and how to create them. I will be happy to help. Thank you! 🙏
I think this is a good example of how you can include this tool in your own setup / technicall stack. I will look for a place to mention this docked version. |
@anevins12 Please do let this someone know he or she can file an issue here. I'll be happy to help out! Thank you 🙏 |
Background
The current installation procedure requires some
npm
witchery, not everyone is capable of. Also systems vary widely, therefore dependencies might break.Proposed solution
A Docker container seemed like a good solution to us. We therefore drafted a docker setup. It can be found in our Github repository WIENFLUSS/wcag-em-report-tool-docker.
It currently features
After that the running container can be accessed via the browser. No additional steps required.
Possible next steps
If deemed useful
The text was updated successfully, but these errors were encountered: