Skip to content
The frontend for the Open Event API Server https://eventyay.com | https://open-event-fe.netlify.com
JavaScript HTML CSS Other
Branch: development
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add placeholder for server version Aug 1, 2019
app fix: edit event accessible to user with event roles only (#3500) Sep 7, 2019
config Update to ember 3.10 stable May 24, 2019
docs docs: Get-Text linking error (#3288) Jul 20, 2019
fastboot/initializers Add support for Fastboot with content hydration Jun 16, 2018
hooks feat: Set up automated docker deploy (#2942) May 18, 2019
kubernetes Fix docker build Oct 1, 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 feat: add paytm to create event and order-form page (#3400) Aug 20, 2019
scripts Make fast-boot production ready. Add to docker image. (#1962) Jan 24, 2019
tests fix: Using ember tables for Admin/Sales/Invoices (#3429) Aug 31, 2019
translations Update translation files (#2044) Jan 31, 2019
vendor Add a customised version of Jquery UI Oct 23, 2018
.dockerignore Make fast-boot production ready. Add to docker image. (#1962) Jan 24, 2019
.editorconfig Initialize fresh ember application Apr 7, 2017
.ember-cli Initialize fresh ember application Apr 7, 2017
.env.example Disable fastboot by default for dev environment Oct 5, 2018
.eslintignore Migrate translation assets (#296) Jun 21, 2017
.eslintrc.js Add support to use decorators properly Jul 4, 2019
.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 feat: Set up automated docker deploy (#2942) May 18, 2019
LICENSE Initialize fresh ember application Apr 7, 2017
README.md Update netlify link Jul 3, 2019
app.json Add heroku deployment support Apr 7, 2017
crowdin.yml Update Crowdin configuration file Jun 29, 2017
ember-cli-build.js Bring all dependencies inline with each other and stabilize versions May 24, 2019
netlify.toml Configure netlify (#2902) May 13, 2019
package.json fix: notify services in files (#3438) Aug 26, 2019
testem.js Fix all failing tests Apr 13, 2018
yarn.lock chore(deps): bump eslint-utils from 1.3.1 to 1.4.2 (#3482) Aug 29, 2019

README.md

Open Event Frontend

Open Event Frontend

Build Status Netlify Status Gitter Mailing Codacy Badge codecov Known Vulnerabilities Crowdin Mailing List Twitter Follow

The front end for the Open Event Server

Deploy

API Documentation:

Communication

Please join our Mailing list or chat channel to get in touch with the developers.

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, Docker images and Releases

Deployments

Master branch

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

Development branch

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

Release Cycle

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:

Branch/Release Image
Master eventyay/open-event-frontend:latest
Development eventyay/open-event-frontend:development
Version(vx.y.z) eventyay/open-event-frontend:vx.y.z

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

You can’t perform that action at this time.