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

Use a proper service/daemon, not screen #5

Closed
joeduffy opened this issue Sep 26, 2017 · 7 comments
Closed

Use a proper service/daemon, not screen #5

joeduffy opened this issue Sep 26, 2017 · 7 comments
Assignees
Milestone

Comments

@joeduffy
Copy link
Member

No description provided.

@joeduffy joeduffy added this to the 0.6.1 milestone Sep 26, 2017
@chrsmith
Copy link
Contributor

Hey @ellismg you kindly volunteered to do this last night. Let's get er' done this afternoon if you have time.

@joeduffy
Copy link
Member Author

I actually wonder if, instead of this, we should just Dockerize the docs website. As I look at https://github.com/pulumi/pulumi-service/blob/master/cmd/docs/DEVOPS.md, and see the manual apt-gets, etc., it screams out for this. I'm also about to add some steps due to our use of LFS, and I'd really prefer to just update a Dockerfile and redeploy than to SSH into the machine and perform manual steps.

@joeduffy
Copy link
Member Author

joeduffy commented Oct 9, 2017

@chrsmith I was just going through and closing 0.6.1 (since it was still open in a few repos), and ran across this work item. Did we fix the issue of using screen?

Also /cc: @mmdriley @ellismg as I know you were discussing daemonizing with these guys (though, honestly, I prefer Dockerizing by an order of magnitude compared to maintaining a stateful server).

@chrsmith
Copy link
Contributor

chrsmith commented Oct 9, 2017

I do not believe we got around to daemonizing this, so the bug should still be open.

As for "properly Dockerizing", this is why we didn't do that initially:

When we can host our docs publicly, we can just host this from a static S3 bucket. So no need to set up infrastructure. The only reason we need a backend for now is for restricting to our super-amazing private beta users.

So we punted on adding it to our CloudFormation since it would be a short-term need anyways. (And because we don't really need N-versions of our docs floating around, but having a "LTS" and "HEAD" branches of our library docs might make sense.)

FWIW, I was planning on tackling "technical debt in Pulumi websites" in M8.

@joeduffy joeduffy modified the milestones: 0.6.1, 0.7 Oct 9, 2017
@chrsmith
Copy link
Contributor

chrsmith commented Oct 9, 2017

Plan of Record
We'll do this via an init script today and set up Pingdom. Long-term plan is to move this to an S3 bucket when we have no longer have access restriction, so we'll never Dockerize and/or move into our official Pulumi stack.

@chrsmith
Copy link
Contributor

chrsmith commented Oct 9, 2017

  • docs.pulumi.com is wired up to https://my.pingdom.com and will send a message to #ops in Slack, email/text Joe and myself.
  • Add an init script to the instance so the docs binary gets launched on machine restart.

@mmdriley
Copy link

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

4 participants