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

Deployment is complex #5

Open
GoogleCodeExporter opened this issue Mar 12, 2015 · 2 comments
Open

Deployment is complex #5

GoogleCodeExporter opened this issue Mar 12, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link
Contributor

Currently, deploying this software is rather complex, requiring

* Download of various tools.
* Adjusting lines of code in various tools to point to the actual tool
locations.
* Heavy use of command-line interface.

Not all of this is avoidable:

* Not all tools can be bundled for because of licensing
* Configuration needs to be done.

However, I can prepare compiled executables, and an archive of all required
files in the right locations to make life easier for those wishing to use
these XSLT files.


Original issue reported on code.google.com by jhellingman on 12 Nov 2009 at 2:07

@GoogleCodeExporter
Copy link
Contributor Author

Things todo:

* Replace C code with perl.
* Pack up everything in a zip file and make a release.
* Create script to download, install, and connect required software.

Original comment by jhellingman on 10 Dec 2009 at 1:19

@GoogleCodeExporter
Copy link
Contributor Author

Make deployment easy.

1. Use a tei2html.config file with all details
2. When this file is not found, run an auto-config file that detects the 
presence of required tools, by searching the $PATH, the windows registry, etc., 
and write it into a tei2html.config.

Original comment by jhellingman on 28 Feb 2011 at 9:20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants