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

Shift from Heroku hosting to Openshift hosting #228

Open
1 of 3 tasks
rahulkumaran opened this issue Sep 30, 2018 · 1 comment
Open
1 of 3 tasks

Shift from Heroku hosting to Openshift hosting #228

rahulkumaran opened this issue Sep 30, 2018 · 1 comment

Comments

@rahulkumaran
Copy link
Contributor

I'm submitting a ... (check one with "x")

  • bug report
  • feature request
  • support request => Please do not submit support requests here, instead ask your query in out Gitter channel at https://gitter.im/fossasia/meilix

Actual Behaviour

Currently hosted on heroku.

Expected Behaviour

Start hosting on Openshift. It's easier to deploy this on Openshift. Moreover, it's one of the best free hosting platforms. The steps of deployment are easier on Openshift than Heroku too. We can also deploy using docker images if needed on Openshift.

Would you like to work on the issue?
Yes

@tabesin
Copy link
Member

tabesin commented Sep 30, 2018

In general that is a good idea. Important then would be to document it. However, Fossasia deploys a lot of sites and most of them on heroku. If we migrate we should have the perspective to migrate all, not have n projects with n entirely different tool chains.

So go forward to add it as a deployment feature but Heroku must be made work again anyway.

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

No branches or pull requests

2 participants