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

deployment #12

Open
colinsullivan opened this issue Jan 14, 2017 · 3 comments
Open

deployment #12

colinsullivan opened this issue Jan 14, 2017 · 3 comments

Comments

@colinsullivan
Copy link

I learned how to deploy to Firebase (took a whole 3 minutes).

For now, I've created [email protected] and set up Firebase using that account. A credit card was not required, so that's good.

We can also set up Google Analytics using this account if desired.

Perhaps ideally we would have an <@kagyumonlam.org> email address to be used as the Firebase user account, or use a Google account that is already in use by folks on the monlam team doing web maintenance.

I think it will be difficult enough to get a DNS change.

https://kagyumonlamdev.firebaseapp.com

@colinsullivan colinsullivan changed the title deployment to Firebase deployment Jan 14, 2017
@colinsullivan
Copy link
Author

colinsullivan commented Jan 14, 2017

Deployment Option 1: Firebase

A deployment to Firebase would look something like this:

  • Archive entire existing monlam website
  • Integrate existing monlam website archives into our website hierarchy
    • We will need to archive the previous English version
    • we may also want to create a splash page similar to the current kagyumonlam.org which links to the existing Tibetan and Chinese versions of the site
  • Change kagyumonlam.org DNS to point to the Firebase deployment:
    • Acquire GoDaddy credentials or someone with credentials can do this
      • Possibly from James Chen <jchen1 [at] winbond.com>
      • Possibly from Ken McNamara <members [at] kagyumonlam.org>, <vajrabone [at] hotmail.com>
    • Add the below DNS records so Google can verify domain ownership
    • Once verified we will need to add another DNS entry (TBD)

DNS entries needed for domain verification:

kagyumonlam.org TXT globalsign-domain-verification=1iNNGLlJ6qSchnP2Ivr5P06LlcXvzzNZHMx8aZch_n
kagyumonlam.org TXT firebase=kagyumonlamprod

@colinsullivan
Copy link
Author

colinsullivan commented Jan 14, 2017

Deployment Option 2: Existing Host

Another possible strategy is to get FTP or shell access to the existing kagyumonlam.org file server and deploy our site there. In this case, the process would look something like this:

  • Integrate a link to http://kagyumonlam.org/English/archives into our website.
  • Acquire FTP or shell credentials to the existing kagyumonlam.org server.
  • On the existing kagyumonlam.org server:
    • Copy /English to /English/archives
    • Deploy our site to /English

To me, this deployment option seems more fragile because the website remains dependent on the existing kagyumonlam.org server which is not actively maintained.

@colinsullivan
Copy link
Author

@tallt0m, would you like to reach out to:

James Chen <jchen1 [at] winbond.com>
Ken McNamara <members [at] kagyumonlam.org>, <vajrabone [at] hotmail.com>
and Tashi

to find out who has access to the GoDaddy account? This will be necessary if we are to choose deployment option #1

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

1 participant