Open Event Frontend
The front end for the Open Event Server
- Every installation of the Open Event Server project includes API docs, (e.g. here on the test install https://open-event-api.herokuapp.com).
- A hosted version of the API docs is available in the
gh-pagesbranch of the Open Event Server repository at http://dev.eventyay.com/api/v1
The Open Event Frontend can be easily deployed on a variety of platforms. Detailed platform specific instructions have been provided below.
Running / Development
- Visit your app at http://localhost:4200.
Make use of the many generators for code, try
ember help generate for more details.
This project has acceptance, integration and unit tests located inside the
ember test- CLI output
ember test --server- Live browser preview and console access
ember build --environment production(production)
Deployments, Docker images and Releases
The master branch of open-event-frontend gets deployed in a production environment at https://eventyay.com It consumes the API exposed by master branch deployment of open event server, hosted at https://api.eventyay.com
The development branch of open-event-frontend gets deployed at https://opev-event-fe.netlify.com It consumes the API exposed by development branch of open event server, hosted at https://open-event-api-dev.herokuapp.com
Stable versions will released periodically, starting from version 1.0.0 when open-event-frontend went into production. Version names will follow semantic versioning
Docker Hub Images
Docker images hosted on open-event-frontend repository under eventyay organisation on docker hub are updated for each push on master and developement branch. Separate tags for each version release are also maintained. They are as follows:
Further Reading / Useful Links
- Semantic UI
- Development Browser Extensions
Contributions Best Practices
- Write clear meaningful git commit messages (Do read https://chris.beams.io/posts/git-commit/)
- Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at https://github.com/blog/1506-closing-issues-via-pull-requests )
- When you make very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at https://davidwalsh.name/squash-commits-git )
- When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.
Feature Requests and Bug Reports
When you file a feature request or when you are submitting a bug report to the issue tracker, make sure you add steps to reproduce it. Especially if that bug is some weird/rare one.
Join the development
- Before you join development, please set up the project on your local machine, run it and go through the application completely. Press on any button you can find and see where it leads to. Explore. (Don't worry ... Nothing will happen to the app or to you due to the exploring
😉Only thing that will happen is, you'll be more familiar with what is where and might even get some cool ideas on how to improve various aspects of the app.)
- If you would like to work on an issue, drop in a comment at the issue. If it is already assigned to someone, but there is no sign of any work being done, please feel free to drop in a comment so that the issue can be assigned to you if the previous assignee has dropped it entirely.
This project is currently licensed under the Apache License version 2.0.
To obtain the software under a different license, Please contact FOSSASIA.