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

Deploy ETUmulatorWeb to Heroku #2

Open
1 of 2 tasks
gorkemmulayim opened this issue Mar 6, 2018 · 2 comments
Open
1 of 2 tasks

Deploy ETUmulatorWeb to Heroku #2

gorkemmulayim opened this issue Mar 6, 2018 · 2 comments
Assignees
Labels

Comments

@gorkemmulayim
Copy link
Member

gorkemmulayim commented Mar 6, 2018

In this issue you will deploy ETUmulatorWeb to Heroku by using your account. Fork the project and setup an auto deployment to Heroku. After that open a pull request and include the link to your Heroku application. Easy, right?

However, there is no running services on ETUmulatorWeb. Therefore, we will not be able to show any web page when you deploy the project to Heroku. It would be nice if we had a homepage indicating that ETUmulatorWeb is under development.

In short, building a service in order to show homepage is also a necessary part of this issue. You will need to figure out the implementation details of the service by yourself. The current version of source code able to run a server with default dependencies to implement this service.

There is a great tool called Postman for testing web services. It might help you while dealing with the issue.

@gorkemmulayim
Copy link
Member Author

#3

@gorkemmulayim
Copy link
Member Author

It is stated by Heroku help site GitHub repos that use submodules will generally not deploy correctly on Heroku. This is because GitHub does not include submodule contents when repo-content tarballs are generated.

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

No branches or pull requests

2 participants