-
Notifications
You must be signed in to change notification settings - Fork 207
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
Comments
Hey @ellismg you kindly volunteered to do this last night. Let's get er' done this afternoon if you have time. |
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 |
@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). |
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. |
Plan of Record |
|
No description provided.
The text was updated successfully, but these errors were encountered: