These are chat archives for fossasia/open-event-server

20th
Nov 2017
Pepe Becker
@pepebecker
Nov 20 2017 01:40
@all where can I find the .env.example file for step 3 in local.md?
Mario Behling
@mariobehling
Nov 20 2017 01:41
Good point. Where is it?
Rahul Tiwari
@invinciblycool
Nov 20 2017 08:20
.env.example is in the project directory. Check the project directory where you have cloned the project.
Since the file is hidden acc to Linux file system. Try pressing Ctrl+H to view it on a Linux file system or a similar command if on Mac.
Hope this helps.
@mariobehling I agree with @anshumanv open-event-api-server is more descriptive and appropriate.
@pepebecker Feel free to ask here for any further issues
Pepe Becker
@pepebecker
Nov 20 2017 08:26
I just found it in the nextgen branch, thanks. I cloned the development branch like it says in the local.md. The development branch does not seam to have a .env.example file, that's why I was confused
Rahul Tiwari
@invinciblycool
Nov 20 2017 08:27
Oh! :sweat_smile:
The current development is on the nextgen branch.
:thumbsup:
Pepe Becker
@pepebecker
Nov 20 2017 08:28
Oh, so I should work on the nextgen branch instead of the development branch?
Rahul Tiwari
@invinciblycool
Nov 20 2017 08:29
Yes. Any commits are to be done on the nextgen branch.
Pepe Becker
@pepebecker
Nov 20 2017 08:29
Ok, thanks :+1:
Mario Behling
@mariobehling
Nov 20 2017 14:28
@shubham-padia @niranjan94 @geekyd I would like to separate the legacy system and the new API server as a next step before we switch to the new system completely
Shubham Padia
@shubham-padia
Nov 20 2017 14:33
@mariobehling There are seperate branches for the legacy system and the nextgen version. Is that what you mean by seperate here?
Mario Behling
@mariobehling
Nov 20 2017 14:33
People are getting confused by these branches
we could also rename the older branch to "legacy-dev" and "legcay-master"
Shubham Padia
@shubham-padia
Nov 20 2017 14:35
Yeah, we can do that
Mario Behling
@mariobehling
Nov 20 2017 14:35
Can it be deleted?
Shubham Padia
@shubham-padia
Nov 20 2017 14:39
It was a to-do feature then, we can delete that branch for now and revisit later when needed
Mario Behling
@mariobehling
Nov 20 2017 14:39
ok
Vaibhav Singh
@vaibhavsingh97
Nov 20 2017 14:39

There was a question in this issue (fossasia/open-event-orga-server#3931) about renaming the server deployments to reflect the project direction. Should we simply rename it to "Open Event Server"?

Aggreed with @anshumanv , open-event-api-server is more descriptive

Mario Behling
@mariobehling
Nov 20 2017 14:40
@shubham-padia We need to ensure the Heroku and Google cloud deployments still work when we change the branch names. Will this be the case?
I suggest the following:
  • development -> rename to legacy-dev
  • master -> rename to legacy-master ==> deploy to eventyay.com
  • nextgen -> rename to development ==> deploy to staging.eventyay.com
  • nextgen-backup -> rename to master ==> deploy to nextgen.eventyay.com
  • delete staging branch
Shubham Padia
@shubham-padia
Nov 20 2017 15:02
Some changes to the above:
nextgen -> rename to development/master ==> deploy to nextgen.eventyay.com
Delete nextgen-backup , it was kept as a backup after merging a major PR, the branch is no longer needed.
Keep staging branch as is, staging branch is needed for testing various configs of kubernetes before pushing them onto any of the active branch

We need to ensure the Heroku and Google cloud deployments still work when we change the branch names.

PRs changing the names of these branches in the deployment config would have to be made

Sumedh Nimkarde
@lunaticmonk
Nov 20 2017 15:35
Some changes to the above:
nextgen -> rename to development/master ==> deploy to nextgen.eventyay.com
Delete nextgen-backup , it was kept as a backup after merging a major PR, the branch is no longer needed.
Keep staging branch as is, staging branch is needed for testing various configs of kubernetes before pushing them onto any of the active branch
LGTM
Dilpreet Singh
@geekyd
Nov 20 2017 16:31
Renaming the branches sounds good :+1: