The frontend for the Open Event API Server https://open-event-frontend.herokuapp.com
Permalink
Failed to load latest commit information.
.github chore: Comment out hints in the issue templates May 26, 2018
app Fix a typo in discount-codes/edit.js (#1649) Sep 16, 2018
config Add a condition to check for enviromental variable (#1366) Jul 11, 2018
docs Fixes #1663 Add note about contributing from fork (#1664) Sep 21, 2018
fastboot/initializers Add support for Fastboot with content hydration Jun 16, 2018
kubernetes Make docker builds use fastboot Jun 16, 2018
lib Add scss linter and autoprefixer Jul 19, 2017
mirage Step-1 [Paypal Payment]: Add paypal checkout button to allow users au… Jul 25, 2018
public Adds Other.jpg to public/images/placeholders Sep 2, 2017
scripts Make docker builds use fastboot Jun 16, 2018
tests feat: Make discount codes applicable to orders (#1631) Aug 15, 2018
translations Change User(Email) to User e-mail (#1281) Jun 17, 2018
vendor Resolve tests. Part two. Apr 20, 2017
.editorconfig Initialize fresh ember application Apr 7, 2017
.ember-cli Initialize fresh ember application Apr 7, 2017
.env.example use 127.0.0.1 as API_HOST in .env.example May 27, 2018
.eslintignore Migrate translation assets (#296) Jun 21, 2017
.eslintrc.js Use app name from settings endpoint Jun 16, 2018
.gitignore Make docker builds use fastboot Jun 16, 2018
.sass-lint.yml Add scss linter and autoprefixer Jul 19, 2017
.template-lintrc.js Fix template lint errors Jun 12, 2018
.travis.yml fix: Fix failing Travis by adding global path for yarn (#1427) Jul 17, 2018
.watchmanconfig Initialize fresh ember application Apr 7, 2017
Dockerfile Docker compose (#1354) Jul 6, 2018
LICENSE Initialize fresh ember application Apr 7, 2017
README.md Docker compose (#1354) Jul 6, 2018
app.json Add heroku deployment support Apr 7, 2017
crowdin.yml Update Crowdin configuration file Jun 29, 2017
ember-cli-build.js Make docker builds use fastboot Jun 16, 2018
package.json Update qunit-dom to the latest version πŸš€ (#1651) Sep 16, 2018
testem.js Fix all failing tests Apr 13, 2018
yarn.lock Update qunit-dom to the latest version πŸš€ (#1651) Sep 16, 2018

README.md

Open Event Frontend

Open Event Frontend

Build Status Gitter Codacy Badge codecov Greenkeeper badge Known Vulnerabilities Crowdin

The front end for the Open Event Server

Deploy

API Documentation:

Communication

Please join our mailing list to discuss questions regarding the project :

https://groups.google.com/forum/#!forum/open-event

Our chat channel is on Gitter here :

gitter.im/fossasia/open-event-frontend

Installation

The Open Event Frontend can be easily deployed on a variety of platforms. Detailed platform specific instructions have been provided below.

  1. Local Installation
  2. Publish to GitHub Pages
  3. Running in Docker

Running / Development

Code Generators

Make use of the many generators for code, try ember help generate for more details.

Running Tests

This project has acceptance, integration and unit tests located inside the tests/ folder.

  • ember test - CLI output
  • ember test --server - Live browser preview and console access

Building

  • ember build (development)
  • ember build --environment production (production)

Deployments

Master (Staging Test) (master branch)

Development (development branch)

Further Reading / Useful Links

Contributions Best Practices

Commits

  • 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 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.

License

This project is currently licensed under the Apache License version 2.0.

To obtain the software under a different license, Please contact FOSSASIA.