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

Package project in some way #56

Closed
jgriss opened this issue Aug 6, 2018 · 5 comments
Closed

Package project in some way #56

jgriss opened this issue Aug 6, 2018 · 5 comments

Comments

@jgriss
Copy link
Collaborator

jgriss commented Aug 6, 2018

We should provide a single ZIP file for people to download as a release.

This should ideally be done once all issues of a milestone are reached.

@jgriss jgriss added this to the version 0.1 milestone Aug 6, 2018
@jgriss
Copy link
Collaborator Author

jgriss commented Aug 13, 2018

Files to include:

  • run.but / run.sh
  • ? Maybe some kind of install script (as it is included in run.sh)
  • Basic documentation?

@veitveit
Copy link
Collaborator

The run.bat/ run.sh files should be enough if they point to the correct releases of the docker images.

@veitveit
Copy link
Collaborator

I now created the folder RELEASE and copied the run scripts into it.

The run scripts of the different release can then be named accordingly.

I close this now but you can reopen the issue if this is not what you envisioned.

@jgriss
Copy link
Collaborator Author

jgriss commented Aug 14, 2018

@veitveit

GitHub has a release function and I think we should use it. But having this RELEASE folder to collect all files that we want to ship to the user is a very good idea.

@veitveit
Copy link
Collaborator

veitveit commented Aug 15, 2018 via email

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